[gentoo-user] Networkmanager-9999 won't compile

[gentoo-user] Networkmanager-9999 won't compile

[Nilesh Govindarajan]

This is what I get when I try to install networkmanager-9999 which is
required by gnome-3.2.0

#       source='nm-session-monitor.c'
object='NetworkManager-nm-session-monitor.o' libtool=no
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include
-I../marshallers -I../src/logging -I../src/dns-manager
-I../src/vpn-manager -I../src/dhcp-manager -I../src/ip6-manager
-I../src/supplicant-manager -I../src/dnsmasq-manager
-I../src/modem-manager -I../src/bluez-manager -I../src/settings
-I../libnm-util -I../callouts  -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include   -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include   -I/usr/include/gudev-1.0
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include    -pthread
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include   -pthread
-I/usr/include/polkit-1 -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include   -DG_DISABLE_DEPRECATED
-DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\"
-DLIBEXECDIR=\"/usr/libexec\" -DDATADIR=\"/usr/share\"
-DSYSCONFDIR=\"/etc\" -DLOCALSTATEDIR=\"/var\"
-DNM_RUN_DIR=\"/var/run/NetworkManager\"
-DNMLOCALEDIR=\"/usr/share/locale\" -DARP_DEBUG   -O3 -march=native
-mtune=native -pipe -msse -msse2 -mmmx -c -o
NetworkManager-nm-session-monitor.o `test -f 'nm-session-monitor.c' ||
echo './'`nm-session-monitor.c
/bin/sh ../libtool  --tag=CC   --mode=link x86_64-pc-linux-gnu-gcc  -O3
-march=native -mtune=native -pipe -msse -msse2 -mmmx -rdynamic -Wl,-O1
-Wl,--as-needed -o NetworkManager NetworkManager-nm-call-store.o
NetworkManager-nm-device.o NetworkManager-nm-device-interface.o
NetworkManager-nm-device-ethernet.o NetworkManager-nm-device-wifi.o
NetworkManager-nm-device-olpc-mesh.o NetworkManager-nm-device-bt.o
NetworkManager-nm-device-modem.o NetworkManager-nm-wifi-ap.o
NetworkManager-nm-wifi-ap-utils.o NetworkManager-nm-dbus-manager.o
NetworkManager-nm-udev-manager.o NetworkManager-nm-hostname-provider.o
NetworkManager-nm-ip4-config.o NetworkManager-nm-ip6-config.o
NetworkManager-nm-active-connection.o NetworkManager-nm-config.o
NetworkManager-main.o NetworkManager-nm-policy.o
NetworkManager-nm-policy-hosts.o NetworkManager-nm-policy-hostname.o
NetworkManager-NetworkManagerUtils.o NetworkManager-nm-system.o
NetworkManager-nm-manager.o NetworkManager-nm-manager-auth.o
NetworkManager-nm-netlink-monitor.o NetworkManager-nm-netlink-utils.o
NetworkManager-nm-netlink-compat.o
NetworkManager-nm-activation-request.o
NetworkManager-nm-properties-changed-signal.o NetworkManager-wpa.o
NetworkManager-nm-dhcp4-config.o NetworkManager-nm-dhcp6-config.o
NetworkManager-nm-session-monitor.o ../marshallers/libmarshallers.la
./logging/libnm-logging.la ./dns-manager/libdns-manager.la
./vpn-manager/libvpn-manager.la ./dhcp-manager/libdhcp-manager.la
./ip6-manager/libip6-manager.la
./supplicant-manager/libsupplicant-manager.la
./dnsmasq-manager/libdnsmasq-manager.la ./ppp-manager/libppp-manager.la
./modem-manager/libmodem-manager.la ./bluez-manager/libbluez-manager.la
./settings/libsettings.la  ./backends/libnmbackend.la
../libnm-util/libnm-util.la -ldbus-glib-1 -ldbus-1 -lpthread -lrt
-lgobject-2.0 -lglib-2.0   -pthread -lgthread-2.0 -lrt -lgobject-2.0
-lglib-2.0   -lgudev-1.0 -lgobject-2.0 -lglib-2.0   -lnl
-Wl,--export-dynamic -pthread -lgmodule-2.0 -lrt -lglib-2.0   -pthread
-lpolkit-gobject-1 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0
  -lm -ldl
libtool: link: x86_64-pc-linux-gnu-gcc -O3 -march=native -mtune=native
-pipe -msse -msse2 -mmmx -rdynamic -Wl,-O1 -o .libs/NetworkManager
NetworkManager-nm-call-store.o NetworkManager-nm-device.o
NetworkManager-nm-device-interface.o NetworkManager-nm-device-ethernet.o
NetworkManager-nm-device-wifi.o NetworkManager-nm-device-olpc-mesh.o
NetworkManager-nm-device-bt.o NetworkManager-nm-device-modem.o
NetworkManager-nm-wifi-ap.o NetworkManager-nm-wifi-ap-utils.o
NetworkManager-nm-dbus-manager.o NetworkManager-nm-udev-manager.o
NetworkManager-nm-hostname-provider.o NetworkManager-nm-ip4-config.o
NetworkManager-nm-ip6-config.o NetworkManager-nm-active-connection.o
NetworkManager-nm-config.o NetworkManager-main.o
NetworkManager-nm-policy.o NetworkManager-nm-policy-hosts.o
NetworkManager-nm-policy-hostname.o NetworkManager-NetworkManagerUtils.o
NetworkManager-nm-system.o NetworkManager-nm-manager.o
NetworkManager-nm-manager-auth.o NetworkManager-nm-netlink-monitor.o
NetworkManager-nm-netlink-utils.o NetworkManager-nm-netlink-compat.o
NetworkManager-nm-activation-request.o
NetworkManager-nm-properties-changed-signal.o NetworkManager-wpa.o
NetworkManager-nm-dhcp4-config.o NetworkManager-nm-dhcp6-config.o
NetworkManager-nm-session-monitor.o -pthread -Wl,--export-dynamic
-pthread -pthread  -Wl,--as-needed ../marshallers/.libs/libmarshallers.a
./logging/.libs/libnm-logging.a ./dns-manager/.libs/libdns-manager.a
./vpn-manager/.libs/libvpn-manager.a
./dhcp-manager/.libs/libdhcp-manager.a
./ip6-manager/.libs/libip6-manager.a
./supplicant-manager/.libs/libsupplicant-manager.a
./dnsmasq-manager/.libs/libdnsmasq-manager.a
./ppp-manager/.libs/libppp-manager.a
./modem-manager/.libs/libmodem-manager.a
./bluez-manager/.libs/libbluez-manager.a ./settings/.libs/libsettings.a
/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/libnm-util/.libs/libnm-util.so
./backends/.libs/libnmbackend.a ../libnm-util/.libs/libnm-util.so -luuid
-lssl3 -lsmime3 -lnssutil3 -lnss3 -lplds4 -lplc4 -lnspr4 -ldbus-glib-1
-ldbus-1 -lpthread /usr/lib64/libgudev-1.0.so -L/usr/lib64
/usr/lib64/libudev.so -lgthread-2.0 -lnl -lpolkit-gobject-1 -lgio-2.0
-lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0 -lm -ldl -pthread
NetworkManager-main.o: In function `main':
main.c:(.text+0xa63): undefined reference to `g_thread_supported'
collect2: ld returned 1 exit status
make[4]: *** [NetworkManager] Error 1
make[4]: Leaving directory
`/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999'
make: *** [all] Error 2


The error is g_thread_supported is an undefined reference. This seems to
be related to glib. Anybody has a solution? I tried masking
networkmanager, but emerge won't allow me to do that when I try to
install gnome-base/gnome-3.2.0 (layman overlay)

-- 
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] Networkmanager-9999 won't compile

[Canek Peláez Valdés]

On Wed, Oct 19, 2011 at 2:30 AM, Nilesh Govindarajan
<contact@nileshgr.com> wrote:
> This is what I get when I try to install networkmanager-9999 which is
> required by gnome-3.2.0
>
> #       source='nm-session-monitor.c'
> object='NetworkManager-nm-session-monitor.o' libtool=no
> x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include
> -I../marshallers -I../src/logging -I../src/dns-manager
> -I../src/vpn-manager -I../src/dhcp-manager -I../src/ip6-manager
> -I../src/supplicant-manager -I../src/dnsmasq-manager
> -I../src/modem-manager -I../src/bluez-manager -I../src/settings
> -I../libnm-util -I../callouts  -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include   -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include   -I/usr/include/gudev-1.0
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include    -pthread
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include   -pthread
> -I/usr/include/polkit-1 -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include   -DG_DISABLE_DEPRECATED
> -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\"
> -DLIBEXECDIR=\"/usr/libexec\" -DDATADIR=\"/usr/share\"
> -DSYSCONFDIR=\"/etc\" -DLOCALSTATEDIR=\"/var\"
> -DNM_RUN_DIR=\"/var/run/NetworkManager\"
> -DNMLOCALEDIR=\"/usr/share/locale\" -DARP_DEBUG   -O3 -march=native
> -mtune=native -pipe -msse -msse2 -mmmx -c -o
> NetworkManager-nm-session-monitor.o `test -f 'nm-session-monitor.c' ||
> echo './'`nm-session-monitor.c
> /bin/sh ../libtool  --tag=CC   --mode=link x86_64-pc-linux-gnu-gcc  -O3
> -march=native -mtune=native -pipe -msse -msse2 -mmmx -rdynamic -Wl,-O1
> -Wl,--as-needed -o NetworkManager NetworkManager-nm-call-store.o
> NetworkManager-nm-device.o NetworkManager-nm-device-interface.o
> NetworkManager-nm-device-ethernet.o NetworkManager-nm-device-wifi.o
> NetworkManager-nm-device-olpc-mesh.o NetworkManager-nm-device-bt.o
> NetworkManager-nm-device-modem.o NetworkManager-nm-wifi-ap.o
> NetworkManager-nm-wifi-ap-utils.o NetworkManager-nm-dbus-manager.o
> NetworkManager-nm-udev-manager.o NetworkManager-nm-hostname-provider.o
> NetworkManager-nm-ip4-config.o NetworkManager-nm-ip6-config.o
> NetworkManager-nm-active-connection.o NetworkManager-nm-config.o
> NetworkManager-main.o NetworkManager-nm-policy.o
> NetworkManager-nm-policy-hosts.o NetworkManager-nm-policy-hostname.o
> NetworkManager-NetworkManagerUtils.o NetworkManager-nm-system.o
> NetworkManager-nm-manager.o NetworkManager-nm-manager-auth.o
> NetworkManager-nm-netlink-monitor.o NetworkManager-nm-netlink-utils.o
> NetworkManager-nm-netlink-compat.o
> NetworkManager-nm-activation-request.o
> NetworkManager-nm-properties-changed-signal.o NetworkManager-wpa.o
> NetworkManager-nm-dhcp4-config.o NetworkManager-nm-dhcp6-config.o
> NetworkManager-nm-session-monitor.o ../marshallers/libmarshallers.la
> ./logging/libnm-logging.la ./dns-manager/libdns-manager.la
> ./vpn-manager/libvpn-manager.la ./dhcp-manager/libdhcp-manager.la
> ./ip6-manager/libip6-manager.la
> ./supplicant-manager/libsupplicant-manager.la
> ./dnsmasq-manager/libdnsmasq-manager.la ./ppp-manager/libppp-manager.la
> ./modem-manager/libmodem-manager.la ./bluez-manager/libbluez-manager.la
> ./settings/libsettings.la  ./backends/libnmbackend.la
> ../libnm-util/libnm-util.la -ldbus-glib-1 -ldbus-1 -lpthread -lrt
> -lgobject-2.0 -lglib-2.0   -pthread -lgthread-2.0 -lrt -lgobject-2.0
> -lglib-2.0   -lgudev-1.0 -lgobject-2.0 -lglib-2.0   -lnl
> -Wl,--export-dynamic -pthread -lgmodule-2.0 -lrt -lglib-2.0   -pthread
> -lpolkit-gobject-1 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0
>  -lm -ldl
> libtool: link: x86_64-pc-linux-gnu-gcc -O3 -march=native -mtune=native
> -pipe -msse -msse2 -mmmx -rdynamic -Wl,-O1 -o .libs/NetworkManager
> NetworkManager-nm-call-store.o NetworkManager-nm-device.o
> NetworkManager-nm-device-interface.o NetworkManager-nm-device-ethernet.o
> NetworkManager-nm-device-wifi.o NetworkManager-nm-device-olpc-mesh.o
> NetworkManager-nm-device-bt.o NetworkManager-nm-device-modem.o
> NetworkManager-nm-wifi-ap.o NetworkManager-nm-wifi-ap-utils.o
> NetworkManager-nm-dbus-manager.o NetworkManager-nm-udev-manager.o
> NetworkManager-nm-hostname-provider.o NetworkManager-nm-ip4-config.o
> NetworkManager-nm-ip6-config.o NetworkManager-nm-active-connection.o
> NetworkManager-nm-config.o NetworkManager-main.o
> NetworkManager-nm-policy.o NetworkManager-nm-policy-hosts.o
> NetworkManager-nm-policy-hostname.o NetworkManager-NetworkManagerUtils.o
> NetworkManager-nm-system.o NetworkManager-nm-manager.o
> NetworkManager-nm-manager-auth.o NetworkManager-nm-netlink-monitor.o
> NetworkManager-nm-netlink-utils.o NetworkManager-nm-netlink-compat.o
> NetworkManager-nm-activation-request.o
> NetworkManager-nm-properties-changed-signal.o NetworkManager-wpa.o
> NetworkManager-nm-dhcp4-config.o NetworkManager-nm-dhcp6-config.o
> NetworkManager-nm-session-monitor.o -pthread -Wl,--export-dynamic
> -pthread -pthread  -Wl,--as-needed ../marshallers/.libs/libmarshallers.a
> ./logging/.libs/libnm-logging.a ./dns-manager/.libs/libdns-manager.a
> ./vpn-manager/.libs/libvpn-manager.a
> ./dhcp-manager/.libs/libdhcp-manager.a
> ./ip6-manager/.libs/libip6-manager.a
> ./supplicant-manager/.libs/libsupplicant-manager.a
> ./dnsmasq-manager/.libs/libdnsmasq-manager.a
> ./ppp-manager/.libs/libppp-manager.a
> ./modem-manager/.libs/libmodem-manager.a
> ./bluez-manager/.libs/libbluez-manager.a ./settings/.libs/libsettings.a
> /media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/libnm-util/.libs/libnm-util.so
> ./backends/.libs/libnmbackend.a ../libnm-util/.libs/libnm-util.so -luuid
> -lssl3 -lsmime3 -lnssutil3 -lnss3 -lplds4 -lplc4 -lnspr4 -ldbus-glib-1
> -ldbus-1 -lpthread /usr/lib64/libgudev-1.0.so -L/usr/lib64
> /usr/lib64/libudev.so -lgthread-2.0 -lnl -lpolkit-gobject-1 -lgio-2.0
> -lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0 -lm -ldl -pthread
> NetworkManager-main.o: In function `main':
> main.c:(.text+0xa63): undefined reference to `g_thread_supported'
> collect2: ld returned 1 exit status
> make[4]: *** [NetworkManager] Error 1
> make[4]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999'
> make: *** [all] Error 2
>
>
> The error is g_thread_supported is an undefined reference. This seems to
> be related to glib. Anybody has a solution? I tried masking
> networkmanager, but emerge won't allow me to do that when I try to
> install gnome-base/gnome-3.2.0 (layman overlay)

Why don't you try networkmanager-0.9.1.90? It's working great for me
in GNOME 3.2.0

Is there something in the live ebuild that you need?

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] Networkmanager-9999 won't compile

[Albert W. Hopkins]

On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
> Why don't you try networkmanager-0.9.1.90? It's working great for me
> in GNOME 3.2.0
> 
> Is there something in the live ebuild that you need?
> 
I can't confirm (never tried it) but I've been told the autounmask
option in portage will "blindly" unmask even live ebuilds.. which might
account for people suddenly pulling in a surprising (and potentially
problematic) amount of live ebuilds.


> 

Re: [gentoo-user] Networkmanager-9999 won't compile

[Canek Peláez Valdés]

On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins
<marduk@letterboxes.org> wrote:
> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
>> Why don't you try networkmanager-0.9.1.90? It's working great for me
>> in GNOME 3.2.0
>>
>> Is there something in the live ebuild that you need?
>>
> I can't confirm (never tried it) but I've been told the autounmask
> option in portage will "blindly" unmask even live ebuilds.. which might
> account for people suddenly pulling in a surprising (and potentially
> problematic) amount of live ebuilds.

I haven't tried the autounmask option from portage, neither. The GNOME
overlay offers a series of files you can link to your
/etc/portage/package.{unmask,keywords,use,use.mask} directories: They
are located in

${OVERLAYDIR}/status/portage-configs/

I haven't used those either, though. I prefer to unmask/keyword
packages myself. What I do know is that using live ebuilds is
basically flipping a coin; sometimes will work great, sometimes it
will not even compile.

Right now the only live ebuilds I'm using are:

gnome-extra/libgda-9999
media-sound/rhythmbox-9999
sys-apps/gnome-disk-utility-9999
gnome-extra/gnome-shell-extensions-weather-9999
gnome-extra/gnome-shell-extensions-system-monitor-9999

Everything else works with the latest non-live ebuilds.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] Networkmanager-9999 won't compile

[Nilesh Govindarajan]

On Thu 20 Oct 2011 05:30:24 AM IST, Canek Peláez Valdés wrote:
> On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins
> <marduk@letterboxes.org> wrote:
>> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
>>> Why don't you try networkmanager-0.9.1.90? It's working great for me
>>> in GNOME 3.2.0
>>>
>>> Is there something in the live ebuild that you need?
>>>
>> I can't confirm (never tried it) but I've been told the autounmask
>> option in portage will "blindly" unmask even live ebuilds.. which might
>> account for people suddenly pulling in a surprising (and potentially
>> problematic) amount of live ebuilds.
>
> I haven't tried the autounmask option from portage, neither. The GNOME
> overlay offers a series of files you can link to your
> /etc/portage/package.{unmask,keywords,use,use.mask} directories: They
> are located in
>
> ${OVERLAYDIR}/status/portage-configs/
>
> I haven't used those either, though. I prefer to unmask/keyword
> packages myself. What I do know is that using live ebuilds is
> basically flipping a coin; sometimes will work great, sometimes it
> will not even compile.
>
> Right now the only live ebuilds I'm using are:
>
> gnome-extra/libgda-9999
> media-sound/rhythmbox-9999
> sys-apps/gnome-disk-utility-9999
> gnome-extra/gnome-shell-extensions-weather-9999
> gnome-extra/gnome-shell-extensions-system-monitor-9999
>
> Everything else works with the latest non-live ebuilds.
>
> Regards.

Did you just do emerge gnome (assumging that >=gnome-base/gnome-3.0 is 
in package.unmask)? I'll try doing that again then, till now autounmask 
was active.

-- 
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] Networkmanager-9999 won't compile

[Canek Peláez Valdés]

On Wed, Oct 19, 2011 at 6:00 PM, Nilesh Govindarajan
<contact@nileshgr.com> wrote:
> On Thu 20 Oct 2011 05:30:24 AM IST, Canek Peláez Valdés wrote:
>> On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins
>> <marduk@letterboxes.org> wrote:
>>> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
>>>> Why don't you try networkmanager-0.9.1.90? It's working great for me
>>>> in GNOME 3.2.0
>>>>
>>>> Is there something in the live ebuild that you need?
>>>>
>>> I can't confirm (never tried it) but I've been told the autounmask
>>> option in portage will "blindly" unmask even live ebuilds.. which might
>>> account for people suddenly pulling in a surprising (and potentially
>>> problematic) amount of live ebuilds.
>>
>> I haven't tried the autounmask option from portage, neither. The GNOME
>> overlay offers a series of files you can link to your
>> /etc/portage/package.{unmask,keywords,use,use.mask} directories: They
>> are located in
>>
>> ${OVERLAYDIR}/status/portage-configs/
>>
>> I haven't used those either, though. I prefer to unmask/keyword
>> packages myself. What I do know is that using live ebuilds is
>> basically flipping a coin; sometimes will work great, sometimes it
>> will not even compile.
>>
>> Right now the only live ebuilds I'm using are:
>>
>> gnome-extra/libgda-9999
>> media-sound/rhythmbox-9999
>> sys-apps/gnome-disk-utility-9999
>> gnome-extra/gnome-shell-extensions-weather-9999
>> gnome-extra/gnome-shell-extensions-system-monitor-9999
>>
>> Everything else works with the latest non-live ebuilds.
>>
>> Regards.
>
> Did you just do emerge gnome (assumging that >=gnome-base/gnome-3.0 is
> in package.unmask)? I'll try doing that again then, till now autounmask
> was active.

I did emerge =gnome-base/gnome-3.2.0, and unmasked/keyworded by hand
the necessary packages. But maybe just check that the "**" is not in
any file on /etc/portage/package.keyworks/* (except perhaps the ones
I'm using). If there is no "**" keyworkd, no non-live ebuild should be
installed.

Oh, and also in /etc/portage/package.unmask/*, of course.

Good luck.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] Networkmanager-9999 won't compile

[Nilesh Govindarajan]

On Thu 20 Oct 2011 01:41:25 AM IST, Canek Peláez Valdés wrote:
> On Wed, Oct 19, 2011 at 2:30 AM, Nilesh Govindarajan
> <contact@nileshgr.com> wrote:
>> This is what I get when I try to install networkmanager-9999 which is
>> required by gnome-3.2.0
>>
>> #       source='nm-session-monitor.c'
>> object='NetworkManager-nm-session-monitor.o' libtool=no
>> x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include
>> -I../marshallers -I../src/logging -I../src/dns-manager
>> -I../src/vpn-manager -I../src/dhcp-manager -I../src/ip6-manager
>> -I../src/supplicant-manager -I../src/dnsmasq-manager
>> -I../src/modem-manager -I../src/bluez-manager -I../src/settings
>> -I../libnm-util -I../callouts  -I/usr/include/dbus-1.0
>> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
>> -I/usr/lib64/glib-2.0/include   -pthread -I/usr/include/glib-2.0
>> -I/usr/lib64/glib-2.0/include   -I/usr/include/gudev-1.0
>> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include    -pthread
>> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include   -pthread
>> -I/usr/include/polkit-1 -I/usr/include/glib-2.0
>> -I/usr/lib64/glib-2.0/include   -DG_DISABLE_DEPRECATED
>> -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\"
>> -DLIBEXECDIR=\"/usr/libexec\" -DDATADIR=\"/usr/share\"
>> -DSYSCONFDIR=\"/etc\" -DLOCALSTATEDIR=\"/var\"
>> -DNM_RUN_DIR=\"/var/run/NetworkManager\"
>> -DNMLOCALEDIR=\"/usr/share/locale\" -DARP_DEBUG   -O3 -march=native
>> -mtune=native -pipe -msse -msse2 -mmmx -c -o
>> NetworkManager-nm-session-monitor.o `test -f 'nm-session-monitor.c' ||
>> echo './'`nm-session-monitor.c
>> /bin/sh ../libtool  --tag=CC   --mode=link x86_64-pc-linux-gnu-gcc  -O3
>> -march=native -mtune=native -pipe -msse -msse2 -mmmx -rdynamic -Wl,-O1
>> -Wl,--as-needed -o NetworkManager NetworkManager-nm-call-store.o
>> NetworkManager-nm-device.o NetworkManager-nm-device-interface.o
>> NetworkManager-nm-device-ethernet.o NetworkManager-nm-device-wifi.o
>> NetworkManager-nm-device-olpc-mesh.o NetworkManager-nm-device-bt.o
>> NetworkManager-nm-device-modem.o NetworkManager-nm-wifi-ap.o
>> NetworkManager-nm-wifi-ap-utils.o NetworkManager-nm-dbus-manager.o
>> NetworkManager-nm-udev-manager.o NetworkManager-nm-hostname-provider.o
>> NetworkManager-nm-ip4-config.o NetworkManager-nm-ip6-config.o
>> NetworkManager-nm-active-connection.o NetworkManager-nm-config.o
>> NetworkManager-main.o NetworkManager-nm-policy.o
>> NetworkManager-nm-policy-hosts.o NetworkManager-nm-policy-hostname.o
>> NetworkManager-NetworkManagerUtils.o NetworkManager-nm-system.o
>> NetworkManager-nm-manager.o NetworkManager-nm-manager-auth.o
>> NetworkManager-nm-netlink-monitor.o NetworkManager-nm-netlink-utils.o
>> NetworkManager-nm-netlink-compat.o
>> NetworkManager-nm-activation-request.o
>> NetworkManager-nm-properties-changed-signal.o NetworkManager-wpa.o
>> NetworkManager-nm-dhcp4-config.o NetworkManager-nm-dhcp6-config.o
>> NetworkManager-nm-session-monitor.o ../marshallers/libmarshallers.la
>> ./logging/libnm-logging.la ./dns-manager/libdns-manager.la
>> ./vpn-manager/libvpn-manager.la ./dhcp-manager/libdhcp-manager.la
>> ./ip6-manager/libip6-manager.la
>> ./supplicant-manager/libsupplicant-manager.la
>> ./dnsmasq-manager/libdnsmasq-manager.la ./ppp-manager/libppp-manager.la
>> ./modem-manager/libmodem-manager.la ./bluez-manager/libbluez-manager.la
>> ./settings/libsettings.la  ./backends/libnmbackend.la
>> ../libnm-util/libnm-util.la -ldbus-glib-1 -ldbus-1 -lpthread -lrt
>> -lgobject-2.0 -lglib-2.0   -pthread -lgthread-2.0 -lrt -lgobject-2.0
>> -lglib-2.0   -lgudev-1.0 -lgobject-2.0 -lglib-2.0   -lnl
>> -Wl,--export-dynamic -pthread -lgmodule-2.0 -lrt -lglib-2.0   -pthread
>> -lpolkit-gobject-1 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0
>>  -lm -ldl
>> libtool: link: x86_64-pc-linux-gnu-gcc -O3 -march=native -mtune=native
>> -pipe -msse -msse2 -mmmx -rdynamic -Wl,-O1 -o .libs/NetworkManager
>> NetworkManager-nm-call-store.o NetworkManager-nm-device.o
>> NetworkManager-nm-device-interface.o NetworkManager-nm-device-ethernet.o
>> NetworkManager-nm-device-wifi.o NetworkManager-nm-device-olpc-mesh.o
>> NetworkManager-nm-device-bt.o NetworkManager-nm-device-modem.o
>> NetworkManager-nm-wifi-ap.o NetworkManager-nm-wifi-ap-utils.o
>> NetworkManager-nm-dbus-manager.o NetworkManager-nm-udev-manager.o
>> NetworkManager-nm-hostname-provider.o NetworkManager-nm-ip4-config.o
>> NetworkManager-nm-ip6-config.o NetworkManager-nm-active-connection.o
>> NetworkManager-nm-config.o NetworkManager-main.o
>> NetworkManager-nm-policy.o NetworkManager-nm-policy-hosts.o
>> NetworkManager-nm-policy-hostname.o NetworkManager-NetworkManagerUtils.o
>> NetworkManager-nm-system.o NetworkManager-nm-manager.o
>> NetworkManager-nm-manager-auth.o NetworkManager-nm-netlink-monitor.o
>> NetworkManager-nm-netlink-utils.o NetworkManager-nm-netlink-compat.o
>> NetworkManager-nm-activation-request.o
>> NetworkManager-nm-properties-changed-signal.o NetworkManager-wpa.o
>> NetworkManager-nm-dhcp4-config.o NetworkManager-nm-dhcp6-config.o
>> NetworkManager-nm-session-monitor.o -pthread -Wl,--export-dynamic
>> -pthread -pthread  -Wl,--as-needed ../marshallers/.libs/libmarshallers.a
>> ./logging/.libs/libnm-logging.a ./dns-manager/.libs/libdns-manager.a
>> ./vpn-manager/.libs/libvpn-manager.a
>> ./dhcp-manager/.libs/libdhcp-manager.a
>> ./ip6-manager/.libs/libip6-manager.a
>> ./supplicant-manager/.libs/libsupplicant-manager.a
>> ./dnsmasq-manager/.libs/libdnsmasq-manager.a
>> ./ppp-manager/.libs/libppp-manager.a
>> ./modem-manager/.libs/libmodem-manager.a
>> ./bluez-manager/.libs/libbluez-manager.a ./settings/.libs/libsettings.a
>> /media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/libnm-util/.libs/libnm-util.so
>> ./backends/.libs/libnmbackend.a ../libnm-util/.libs/libnm-util.so -luuid
>> -lssl3 -lsmime3 -lnssutil3 -lnss3 -lplds4 -lplc4 -lnspr4 -ldbus-glib-1
>> -ldbus-1 -lpthread /usr/lib64/libgudev-1.0.so -L/usr/lib64
>> /usr/lib64/libudev.so -lgthread-2.0 -lnl -lpolkit-gobject-1 -lgio-2.0
>> -lgobject-2.0 -lgmodule-2.0 -lrt -lglib-2.0 -lm -ldl -pthread
>> NetworkManager-main.o: In function `main':
>> main.c:(.text+0xa63): undefined reference to `g_thread_supported'
>> collect2: ld returned 1 exit status
>> make[4]: *** [NetworkManager] Error 1
>> make[4]: Leaving directory
>> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory
>> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
>> make[2]: *** [all] Error 2
>> make[2]: Leaving directory
>> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999'
>> make: *** [all] Error 2
>>
>>
>> The error is g_thread_supported is an undefined reference. This seems to
>> be related to glib. Anybody has a solution? I tried masking
>> networkmanager, but emerge won't allow me to do that when I try to
>> install gnome-base/gnome-3.2.0 (layman overlay)
>
> Why don't you try networkmanager-0.9.1.90? It's working great for me
> in GNOME 3.2.0
>
> Is there something in the live ebuild that you need?
>
> Regards.

Also, I don't actually need networkmanager. I'm happy with dhcpcd, 
because there are just two network devices I connect to- my LAN card 
and the android tablet, both of which act as ethernet cards and dhcpcd 
takes care of them properly.

-- 
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] Networkmanager-9999 won't compile

[Nilesh Govindarajan]

On 10/20/2011 06:57 AM, Canek Peláez Valdés wrote:
> On Wed, Oct 19, 2011 at 6:00 PM, Nilesh Govindarajan
> <contact@nileshgr.com> wrote:
>> On Thu 20 Oct 2011 05:30:24 AM IST, Canek Peláez Valdés wrote:
>>> On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins
>>> <marduk@letterboxes.org> wrote:
>>>> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
>>>>> Why don't you try networkmanager-0.9.1.90? It's working great for me
>>>>> in GNOME 3.2.0
>>>>>
>>>>> Is there something in the live ebuild that you need?
>>>>>
>>>> I can't confirm (never tried it) but I've been told the autounmask
>>>> option in portage will "blindly" unmask even live ebuilds.. which might
>>>> account for people suddenly pulling in a surprising (and potentially
>>>> problematic) amount of live ebuilds.
>>>
>>> I haven't tried the autounmask option from portage, neither. The GNOME
>>> overlay offers a series of files you can link to your
>>> /etc/portage/package.{unmask,keywords,use,use.mask} directories: They
>>> are located in
>>>
>>> ${OVERLAYDIR}/status/portage-configs/
>>>
>>> I haven't used those either, though. I prefer to unmask/keyword
>>> packages myself. What I do know is that using live ebuilds is
>>> basically flipping a coin; sometimes will work great, sometimes it
>>> will not even compile.
>>>
>>> Right now the only live ebuilds I'm using are:
>>>
>>> gnome-extra/libgda-9999
>>> media-sound/rhythmbox-9999
>>> sys-apps/gnome-disk-utility-9999
>>> gnome-extra/gnome-shell-extensions-weather-9999
>>> gnome-extra/gnome-shell-extensions-system-monitor-9999
>>>
>>> Everything else works with the latest non-live ebuilds.
>>>
>>> Regards.
>>
>> Did you just do emerge gnome (assumging that >=gnome-base/gnome-3.0 is
>> in package.unmask)? I'll try doing that again then, till now autounmask
>> was active.
> 
> I did emerge =gnome-base/gnome-3.2.0, and unmasked/keyworded by hand
> the necessary packages. But maybe just check that the "**" is not in
> any file on /etc/portage/package.keyworks/* (except perhaps the ones
> I'm using). If there is no "**" keyworkd, no non-live ebuild should be
> installed.
> 
> Oh, and also in /etc/portage/package.unmask/*, of course.
> 
> Good luck.

BTW, which overlays did you use?
I tried after reading (translated version of) german guide on the web
these - gnome, keruspe, suka, rubenqba

-- 
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] Networkmanager-9999 won't compile

[Canek Peláez Valdés]

On Wed, Oct 19, 2011 at 7:07 PM, Nilesh Govindarajan
<contact@nileshgr.com> wrote:
> On 10/20/2011 06:57 AM, Canek Peláez Valdés wrote:
>> On Wed, Oct 19, 2011 at 6:00 PM, Nilesh Govindarajan
>> <contact@nileshgr.com> wrote:
>>> On Thu 20 Oct 2011 05:30:24 AM IST, Canek Peláez Valdés wrote:
>>>> On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins
>>>> <marduk@letterboxes.org> wrote:
>>>>> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
>>>>>> Why don't you try networkmanager-0.9.1.90? It's working great for me
>>>>>> in GNOME 3.2.0
>>>>>>
>>>>>> Is there something in the live ebuild that you need?
>>>>>>
>>>>> I can't confirm (never tried it) but I've been told the autounmask
>>>>> option in portage will "blindly" unmask even live ebuilds.. which might
>>>>> account for people suddenly pulling in a surprising (and potentially
>>>>> problematic) amount of live ebuilds.
>>>>
>>>> I haven't tried the autounmask option from portage, neither. The GNOME
>>>> overlay offers a series of files you can link to your
>>>> /etc/portage/package.{unmask,keywords,use,use.mask} directories: They
>>>> are located in
>>>>
>>>> ${OVERLAYDIR}/status/portage-configs/
>>>>
>>>> I haven't used those either, though. I prefer to unmask/keyword
>>>> packages myself. What I do know is that using live ebuilds is
>>>> basically flipping a coin; sometimes will work great, sometimes it
>>>> will not even compile.
>>>>
>>>> Right now the only live ebuilds I'm using are:
>>>>
>>>> gnome-extra/libgda-9999
>>>> media-sound/rhythmbox-9999
>>>> sys-apps/gnome-disk-utility-9999
>>>> gnome-extra/gnome-shell-extensions-weather-9999
>>>> gnome-extra/gnome-shell-extensions-system-monitor-9999
>>>>
>>>> Everything else works with the latest non-live ebuilds.
>>>>
>>>> Regards.
>>>
>>> Did you just do emerge gnome (assumging that >=gnome-base/gnome-3.0 is
>>> in package.unmask)? I'll try doing that again then, till now autounmask
>>> was active.
>>
>> I did emerge =gnome-base/gnome-3.2.0, and unmasked/keyworded by hand
>> the necessary packages. But maybe just check that the "**" is not in
>> any file on /etc/portage/package.keyworks/* (except perhaps the ones
>> I'm using). If there is no "**" keyworkd, no non-live ebuild should be
>> installed.
>>
>> Oh, and also in /etc/portage/package.unmask/*, of course.
>>
>> Good luck.
>
> BTW, which overlays did you use?
> I tried after reading (translated version of) german guide on the web
> these - gnome, keruspe, suka, rubenqba

I just have the gnome overlay, but I don't use layman. I just.

git clone git://git.overlays.gentoo.org/proj/gnome.git

put the resulting gnome dir in my PORTDIR_OVERLAY environment variable
in /etc/make.conf, and then

emerge -v =gnome-base/gnome-3.2.0

When I want to see if the overlay has updated, I just "git pull" it.
Also, I'm on amd64, not ~amd64 (i.e., I'm on stable). The GNOME stack,
udev and systemd are the only unstable packages in my system (except
for perhaps a couple of other seldom used programs).

I'm carrying my laptop around the globe, so NetworkManager has become
almost indispensable for me; I haven't touched
/etc/wpa_supplicant/wpa_supplicant.conf in months, and I can connect
to all kind of networks.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] Networkmanager-9999 won't compile

[Albert W. Hopkins]

On Thu, 2011-10-20 at 07:37 +0530, Nilesh Govindarajan wrote:
[...]
> BTW, which overlays did you use?

I'll just interject once again.

When you use many overlays, there is a feeling of a exponential increase
in complexity/instability.

The thing is when you use official tree, all the Gentoo devs are
(supposed to) play in the same sandbox.  This means the behaviors of
different packages and their dependencies and interactions with each
other are somewhat predictable, and when problems occur, they are easier
to debug and solve because everyone's playing in the same sandbox.

When you are mixing differing packages from differing repos (overlays),
then not everyone is on the same page.  The developers in overlay A may
not be aware of what's going on in overlay B as they are usually only
concerned about their own sandboxes (and the official repo).  This can
makes debugging much more complex and, if it's an interaction between
different overlays, usually it's going to be the user who is going to
have to figure it out, not the developers.

The if you add live ebuilds into the mix, you are adding even more
sandboxes, and the upstream repos are even more unpredictable.  So one
minute you can have a perfectly harmonious system, and the next you are
dealing with a bunch of unstable isotopes.

This is not to say you can't/shouldn't do these things.  After all this
is Gentoo, and one of the nice things about Gentoo is that we *do* have
this power.  But my point is "with great power comes great
responsibility".  And sometimes that means when it breaks, *you* get to
pick up the pieces.

-a

Re: [gentoo-user] Networkmanager-9999 won't compile

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

On Thu, 20 Oct 2011 07:23:30 +0530, Nilesh Govindarajan wrote:

> Also, I don't actually need networkmanager. I'm happy with dhcpcd, 

Then add NM to /etc/portage/profile/package.provided.


-- 
Neil Bothwick

Windows Error:01F Reserved for future mistakes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Networkmanager-9999 won't compile

[Jonas de Buhr]

Am Wed, 19 Oct 2011 15:00:23 +0530
schrieb Nilesh Govindarajan <contact@nileshgr.com>:

> This is what I get when I try to install networkmanager-9999 which is
> required by gnome-3.2.0
> [SNIP]
> -pthread -pthread
> -Wl,--as-needed ../marshallers/.libs/libmarshallers.a ./logging/.libs/libnm-logging.a ./dns-manager/.libs/libdns-manager.a ./vpn-manager/.libs/libvpn-manager.a ./dhcp-manager/.libs/libdhcp-manager.a
> ./ip6-manager/.libs/libip6-manager.a
> ./supplicant-manager/.libs/libsupplicant-manager.a
> ./dnsmasq-manager/.libs/libdnsmasq-manager.a
> ./ppp-manager/.libs/libppp-manager.a
> ./modem-manager/.libs/libmodem-manager.a
> ./bluez-manager/.libs/libbluez-manager.a ./settings/.libs/libsettings.a
> /media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/libnm-util/.libs/libnm-util.so
> ./backends/.libs/libnmbackend.a ../libnm-util/.libs/libnm-util.so
> -luuid -lssl3 -lsmime3 -lnssutil3 -lnss3 -lplds4 -lplc4 -lnspr4
> -ldbus-glib-1 -ldbus-1 -lpthread /usr/lib64/libgudev-1.0.so
> -L/usr/lib64 /usr/lib64/libudev.so -lgthread-2.0 -lnl
> -lpolkit-gobject-1 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lrt
> -lglib-2.0 -lm -ldl -pthread NetworkManager-main.o: In function
> `main': main.c:(.text+0xa63): undefined reference to
> `g_thread_supported' collect2: ld returned 1 exit status
> make[4]: *** [NetworkManager] Error 1
> make[4]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/media/500GB/gentoo_portage/tmp/portage/net-misc/networkmanager-9999/work/networkmanager-9999'
> make: *** [all] Error 2
> 
> 
> The error is g_thread_supported is an undefined reference. This seems
> to be related to glib. 

what is your version of glib? in the version i have installed
(dev-libs/glib-2.28.8) it is a macro in gthread:

# grep g_thread_supported /usr/include/glib-2.0/glib/gthread.h
 * g_thread_supported macro but provided for language bindings.
    (g_thread_supported () ? G_THREAD_UF (op, arg) : (fail))
    (g_thread_supported () ?
						\ (g_thread_supported
() ? ((void(*)(GCond*, GMutex*, gulong, gchar*))\ (g_thread_supported
() ?						\ #define
g_thread_supported()     1 #define g_thread_supported()
(g_threads_got_initialized)

an a macro is not a function you can link to compiled into the library:

# nm /usr/lib64/libgthread-2.0.a | grep g_thread_supported

that would explain why linking against it doesn't work.

maybe that changed in newer versions of glib?

> Anybody has a solution? I tried masking
> networkmanager, but emerge won't allow me to do that when I try to
> install gnome-base/gnome-3.2.0 (layman overlay)
>