gwyddion-2.19 build fails: Undefined symbols: _GTK_WIDGET_NO_WINDOW _GTK_WIDGET_REALIZED _GTK_WIDGET_TOPLEVEL

[theryanator@…]

Running Tiger 10.4.11, XCode 2.5

Basically, I'm trying to follow instructions <​http://gwyddion.net/documentation/user-guide-en/installation-osx.html> exactly as written (for Tiger).

MacPorts seems to install the associated libraries, but always fails on the actual install of gwyddion itself.

shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_gwyddion/work/gwyddion-2.19" && /usr/bin/make all " returned error 2
Error: Target org.macports.build returned: shell command failed
DEBUG: Backtrace: shell command failed
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
Warning: the following items did not execute (for gwyddion): org.macports.activate org.macports.build org.macports.destroot org.macports.install
Log for gwyddion is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_gwyddion/main.log

Any help would be appreciated.

[theryanator@…]

Associated log file

[jmroot (Joshua Root)]

Please remember to cc the maintainers.

[rowue@…]

We have to circumvent the

_GTK_WIDGET_NO_WINDOW _GTK_WIDGET_REALIZED _GTK_WIDGET_TOPLEVEL

items which where depraced and removed in gtk 2.20 (at least in macports)

(afterwards we can plug gwyddion 2.20 to macports)

[yeti@…]

Symbols are not deprecated *and* removed in the same release in Gtk+. In fact, nothing can be actually removed until Gtk+ 3.0.

So I suppose the source is pedantically compiled with -DGTK_DISABLE_DEPRECATED. The fix would be then to stop doing that because this is bound to break things every time Gtk+ deprecates something. I cannot see from the attached log how GTK_DISABLE_DEPRECATED gets there though.

Using gtk_widget_is_toplevel() instead of GTK_WIDGET_TOPLEVEL, etc. is of course the long-term solution, however, Gwyddion is compatible with Gtk+ 2.8 so using a symbol defined only in 2.18+ is not an option and I don't see a point using #ifdefs in Gwyddion code when Gtk+ headers define the deprecated symbols for us when we don't explicitly ask to avoid defining them. So, please try to find how GTK_DISABLE_DEPRECATED gets defined.

[sewebster@…]

GTK_DISABLE_DEPRECATED appears in the following places in gtkglext 1.2.0 ... could that be it?

/examples/Makefile.am
/examples/Makefile.in
/gtk/Makefile.am
/gtk/Makefile.in

[sewebster@…]

Cc Me!

[rowue@…]

Replying to sewebster@…:

GTK_DISABLE_DEPRECATED appears in the following places in gtkglext 1.2.0 ... could that be it?

/examples/Makefile.am
/examples/Makefile.in
/gtk/Makefile.am
/gtk/Makefile.in

had tried

the configure script and also gtk/Makefile.*

does not work - maybe also GDK_DISABLE_DEPRECATED must be removed. On the way to copenhaven by now - can work further in approx two weeks.

[sewebster@…]

I don't really know what I'm doing, but I decided to work on this while procrastinating on writing my thesis... but I can't reproduce this bug (with gwyddion 2.19). I am using 10.6.4 though, not tiger. Is that relevant? I also don't understand the relationship with this bug and moving to gwyddion 2.20...

[rowue@…]

Replying to sewebster@…:

I don't really know what I'm doing, but I decided to work on this while procrastinating on writing my thesis... but I can't reproduce this bug (with gwyddion 2.19). I am using 10.6.4 though, not tiger. Is that relevant?

Have you checked this against an actual gtk2 port? - It principle it should also fail on 10.6 as on 10.4 - if not it would be very interesting to find the cause ...

I also don't understand the relationship with this bug

and moving to gwyddion 2.20...

Quite simple:

a) If we update to gwyddion 2.20 many people will upgrade gwyddion. If also the relationships where upgraded we might get "tons of users" which can't use gwyddion any more (downgrade is not possible on macports)

b) I like to fix things before updating - otherwise you will get at some time a shiny new version which works for no one (perhaps except you) - and this is not the nicest picture to give ...

[sewebster@…]

Replying to rowue@…:

Have you checked this against an actual gtk2 port? - It principle it should also fail on 10.6 as on 10.4 - if not it would be very interesting to find the cause ...

What do you mean by "checked this against an actual gtk2 port"? I have: gtk2 @2.20.1_0+x11 (active).

I now understand the rationale for not upgrading gwyddion yet, thanks (if of course, this problem is widespread).

[rowue@…]

Replying to sewebster@…:

Replying to rowue@…:

Have you checked this against an actual gtk2 port? - It principle it should also fail on 10.6 as on 10.4 - if not it would be very interesting to find the cause ...

What do you mean by "checked this against an actual gtk2 port"? I have: gtk2 @2.20.1_0+x11 (active).

I just mean this ;) - Because the problem mentioned above comes in conjuction with gtk2 2.20 - 2.19 was fine.

Now it seems that this is a 10.4 perhaps including 10.5 problem - if this problem does not appear with 10.5 we can in principle move to gwyddion 2.20 because macports only supports 10.5 and 10.6 by now (10.4 went out of support) - however I would like to fix the problem itself before updating ...

I now understand the rationale for not upgrading gwyddion yet, thanks (if of course, this problem is widespread).

There are several users outside (including mine) which where using 10.4 - even in my case I'm rather not using OS X any more and also not using gwyddion (not beeing in experimental SPM any more (was only a very short period during my stuies)

kind regs,

rowue

PS: Good luck for your thesis! - (PhD?)

[ryandesign (Ryan Carsten Schmidt)]

Replying to rowue@…:

Replying to sewebster@…:

What do you mean by "checked this against an actual gtk2 port"? I have: gtk2 @2.20.1_0+x11 (active).

I just mean this ;) - Because the problem mentioned above comes in conjuction with gtk2 2.20 - 2.19 was fine.

Rolf, I imagine you were thinking of the German word "aktuell", whose correct translation is not "actual" but "current".

[rowue@…]

Replying to ryandesign@…:

Replying to rowue@…:

Replying to sewebster@…:

[...]

Rolf, I imagine you were thinking of the German word "aktuell", whose correct translation is not "actual" but "current".

Ryan: you were right (as usual ;) - what's your opinion on this case - should we update to gwydion 2.20 if it works in 10.5 also (10.6 seems to work) or fix this error before?

Kind regs,

Rolf

[sewebster@…]

I'm not sure if #25782 is relevant... (yes, my PhD)

[sewebster@…]

#25782 is closed now, is this problem resolved with the new gtkglext?

[rowue@…]

Replying to sewebster@…:

#25782 is closed now, is this problem resolved with the new gtkglext?

At least for the x11 variant it is fixed now - haven't checked the quartz one. Will close this ticket now and check gwyddion 2.20 later or tomorrow.

Thanks,

Rolf