Summary: | networkmanager-0.6.5_p20070823 does not compile with GCC 4.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cyril Jaquier <cyril.jaquier> |
Component: | Current packages | Assignee: | Steev Klimaszewski (RETIRED) <steev> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | anarki, cgibreak, ed, james, kanelxake, suka |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | noGNOME_DISABLE_DEPRECATED.patch |
Description
Cyril Jaquier
2007-08-24 19:02:13 UTC
Strange :/ Line 59 in nm-vpn-properties.c is header definition. I'm using gnome-experimental overlay (Gnome 2.19). Maybe this is related... Sorry, try with portage. This one is not related to paludis. Just have a look at the compilation error. I found the solution here: http://www.mail-archive.com/networkmanager-list@gnome.org/msg07075.html It seems to be more related to Gnome > 2.18 than GCC 4.2!? Same problem here, also with the gnome-experimental-overlay, so I guess this is related. Also this only happens with the gnome use-flag set. btw.: using portage and not paludis here. Created attachment 129187 [details, diff]
noGNOME_DISABLE_DEPRECATED.patch
fails to apply because of a whitespace wtf; here's a fixed version
Sorry, attached patch gives me the same error. GCC 4.2, GNOME 2.19.x here too Well, if you do not need the vpn-part then is seems like you just have to USE="-gnome" and wait for a updated version of nm and nm-applet where the problem files are moved to nm-applet and hopefully fixed. I got this bug too, Daniel told me to rebuild libgnomeui. Please try that. It works for me without any patch, rebuilding libgnomeui as suggested by Rémi. (In reply to comment #11) > It works for me without any patch, rebuilding libgnomeui as suggested by Rémi. > That's because Daniel fixed libgnomeui a few days ago: http://overlays.gentoo.org/proj/gnome/browser/gnome-base/libgnomeui/files/libgnomeui-2.19.1-enable-druid.patch The issue is Gnome 2.19 and Dang fixed it. |