Warning: New definition show

[milktrader]

Getting this warning when loading different packages

julia> using Gadfly
Warning: New definition show(Any,Options{T<:OptionsChecking}) is ambiguous with show(IO,ANY) at show.jl:6.
         Make sure show(IO,Options{T<:OptionsChecking}) is defined first.

Just did a git pull on Julia with a $clean && make

[johnmyleswhite]

You probably need to update Gadfly.

[milktrader]

[Gadfly ((5b8cf3a...))] 
✈  git pull origin master
From git://github.com/dcjones/Gadfly.jl
 * branch            master     -> FETCH_HEAD
Already up-to-date.

[johnmyleswhite]

What about Compose?

[milktrader]

[Compose ((cf9caf0...))] 
✈  git pull origin master
From git://github.com/dcjones/Compose.jl
 * branch            master     -> FETCH_HEAD
Already up-to-date.

DataFrames is also up-to-date.

[milktrader]

I'll do a $ make cleanall && make ...

... same results

[dcjones]

I just bumped both Compose and Gadfly, you might try updating now.

[milktrader]

Getting a fresh set of bad messages now ..

julia> using Gadfly

(process:23353): Pango-CRITICAL **: PangoContext *pango_font_map_create_context(PangoFontMap *): assertion `fontmap != NULL' failed
Warning: New definition show(Any,Options{T<:OptionsChecking}) is ambiguous with show(IO,ANY) at show.jl:6.
         Make sure show(IO,Options{T<:OptionsChecking}) is defined first.

Assuming nobody else is getting this so I'm going to do a complete fresh re-install.

Also, as I mentioned, this warning is happening with other packages including Thyme which leads me to believe my Julia (freshly installed two weeks ago) needs a fresh install.

[dcjones]

Possibly I made things worse. What os are you running? I'll try to reproduce.

[milktrader]

Running Mountain Lion (OSX 10.8.2). Also, just made sure packages in the REQUIRE file are up-to-date and last night did a complete fresh install of Julia. Just now, did another git pull make clean && make with Julia. Now the messages are multiplying ...

julia> using Gadfly

(process:77727): Pango-CRITICAL **: PangoContext *pango_font_map_create_context(PangoFontMap *): assertion `fontmap != NULL' failed
Warning: New definition show(Any,Options{T<:OptionsChecking}) is ambiguous with show(IO,ANY) at show.jl:6.
         Make sure show(IO,Options{T<:OptionsChecking}) is defined first.
Warning: Possible conflict in library symbol zlibVersion
Warning: Possible conflict in library symbol zlibCompileFlags

When I run my own package Thyme I get the following:

julia> using Thyme
Warning: New definition show(Any,Options{T<:OptionsChecking}) is ambiguous with show(IO,ANY) at show.jl:6.
         Make sure show(IO,Options{T<:OptionsChecking}) is defined first.
Warning: Possible conflict in library symbol zlibVersion
Warning: Possible conflict in library symbol zlibCompileFlags

Both packages use DataFrames and the same messages I get with Thyme come up. I'll open an issue on DataFrames. The Pango-CRITICAL message is unique to Gadfly of course.

[milktrader]

Okay, I found the issue on my side. I hadn't updated Options and that's where the original warning was coming from. I need to sort out how to update packages since it doesn't work for me to do Pkg.update() when I'm working on different branches of various packages but that's another issue of course. We still get the library symbol warnings but I'm pretty sure that has to do with a push @dmbates made yesterday so I'll open an issue on DataFrames for that.

[johnmyleswhite]

The library warnings don't actually belong in DataFrames, they're caused by the gzip functionality that @dmbates brought in. I get those warnings every time I run testall in Base Julia.