Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

[Bastian Balthazar Bux]

<snip>

> * Checking gcc for __thread support ... no
>
> * Could not find a gcc that supports the __thread directive!
> * please update to gcc-3.2.2-r1 or later, and try again.
>
>!!! ERROR: sys-libs/glibc-2.3.4.20040808-r1 failed.
>!!! Function check_nptl_support, Line 150, Exitcode 0
>!!! No __thread support in gcc!
>!!! If you need support, post the topmost build error, NOT this status 
>message.
>
>WHAT?!  GCC IS COMPILED WITH NPTL AND NOT NPTLONLY. What is going on? anyone 
>had same problems?
>  
>
I'm at the same point with the same problem, workaround:

gcc-config -l says you don't have any default profiles
don't care:
# gcc-config  1
# source /etc/profile
# gcc-config  -l
# gcc-config <whatever profile you want>
# source /etc/profile

cp /usr/portage/scripts/bootstrap.sh /usr/portage/scripts/bb.sh
edit  /usr/portage/scripts/bb.sh, comment the following lines:

#USE="-* build bootstrap ${STAGE1_USE}" emerge ${STRAP_EMERGE_OPTS} 
${myPORTAGE} || cleanup 1

#emerge ${STRAP_EMERGE_OPTS} ${myOS_HEADERS} ${myTEXINFO} ${myGETTEXT} 
${myBINUTILS} || cleanup 1

#if [ -n "${STRAP_RUN}" ]; then
    #emerge clean || cleanup 1
#fi

#emerge ${STRAP_EMERGE_OPTS} ${myGCC} || cleanup 1

#emerge clean || cleanup 1

you have only two emerge still to do:
emerge ${STRAP_EMERGE_OPTS} ${myLIBC} ${myBASELAYOUT} ${myZLIB} || cleanup 1
emerge ${STRAP_EMERGE_OPTS} ${myNCURSES} || cleanup 1

launch /usr/portage/scripts/bb.sh

starting the script I've seen the

# livecd portage # scripts/bb.sh

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2004 Gentoo Foundation; Distributed under the GPLv2
Resuming Bootstrap of base system ...


the last output frase make me think that commenting emerge lines is 
useless but who know ;)

ciao, hope it helps francesco



--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

[Bastian Balthazar Bux]

Bastian Balthazar Bux wrote:

> <snip>
>
>> * Checking gcc for __thread support ... no
>>
>> * Could not find a gcc that supports the __thread directive!
>> * please update to gcc-3.2.2-r1 or later, and try again.
>>
>> !!! ERROR: sys-libs/glibc-2.3.4.20040808-r1 failed.
>> !!! Function check_nptl_support, Line 150, Exitcode 0
>> !!! No __thread support in gcc!
>> !!! If you need support, post the topmost build error, NOT this 
>> status message.
>>
>> WHAT?!  GCC IS COMPILED WITH NPTL AND NOT NPTLONLY. What is going on? 
>> anyone had same problems?
>>  
>>
> I'm at the same point with the same problem, workaround:
>
> gcc-config -l says you don't have any default profiles
> don't care:
> # gcc-config  1
> # source /etc/profile
> # gcc-config  -l
> # gcc-config <whatever profile you want>
> # source /etc/profile
>
> cp /usr/portage/scripts/bootstrap.sh /usr/portage/scripts/bb.sh
> edit  /usr/portage/scripts/bb.sh, comment the following lines:
>
> #USE="-* build bootstrap ${STAGE1_USE}" emerge ${STRAP_EMERGE_OPTS} 
> ${myPORTAGE} || cleanup 1
>
> #emerge ${STRAP_EMERGE_OPTS} ${myOS_HEADERS} ${myTEXINFO} ${myGETTEXT} 
> ${myBINUTILS} || cleanup 1
>
> #if [ -n "${STRAP_RUN}" ]; then
>    #emerge clean || cleanup 1
> #fi
>
> #emerge ${STRAP_EMERGE_OPTS} ${myGCC} || cleanup 1
>
> #emerge clean || cleanup 1
>
> you have only two emerge still to do:
> emerge ${STRAP_EMERGE_OPTS} ${myLIBC} ${myBASELAYOUT} ${myZLIB} || 
> cleanup 1
> emerge ${STRAP_EMERGE_OPTS} ${myNCURSES} || cleanup 1
>
> launch /usr/portage/scripts/bb.sh
>
> starting the script I've seen the
>
> # livecd portage # scripts/bb.sh
>
> Gentoo Linux; http://www.gentoo.org/
> Copyright 1999-2004 Gentoo Foundation; Distributed under the GPLv2
> Resuming Bootstrap of base system ...
>
>
> the last output frase make me think that commenting emerge lines is 
> useless but who know ;)
>
> ciao, hope it helps francesco
>
>
it will stop emerging system at sys-devel/libtool
you need to emerge sys-devel/automake-wrapper

when it's finished you can emerge system again, it will start emerging 
libtool (like emerge --resume that doesn't work because we have emerge 
something else in the meantime)



--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

[Bastian Balthazar Bux]

<snip>

> it will stop emerging system at sys-devel/libtool
> you need to emerge sys-devel/automake-wrapper
>
> when it's finished you can emerge system again, it will start emerging 
> libtool (like emerge --resume that doesn't work because we have emerge 
> something else in the meantime)
>
>
... and when I' will finish emerging system I'll discover that

sys-libs/ncurses
sys-apps/module-init-tools
app-editors/nano

have installed they binaries like this (you can check it emerging 
gentoolkit and doing "qpkg -l sys-libs/ncurses | grep bin"):

/bin/i686-pc-linux-gnu-lsmod
/bin/i686-pc-linux-gnu-nano

/usr/bin/i686-pc-linux-gnu-c++
/usr/bin/i686-pc-linux-gnu-captoinfo
/usr/bin/i686-pc-linux-gnu-clear
/usr/bin/i686-pc-linux-gnu-g++
/usr/bin/i686-pc-linux-gnu-gcc
/usr/bin/i686-pc-linux-gnu-infocmp
/usr/bin/i686-pc-linux-gnu-infotocap
/usr/bin/i686-pc-linux-gnu-reset
/usr/bin/i686-pc-linux-gnu-tic
/usr/bin/i686-pc-linux-gnu-toe
/usr/bin/i686-pc-linux-gnu-tput
/usr/bin/i686-pc-linux-gnu-tset

it's the era of the woozy numbat ;)

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

[Bastian Balthazar Bux]

Bastian Balthazar Bux wrote:

>
> <snip>
>
>> it will stop emerging system at sys-devel/libtool
>> you need to emerge sys-devel/automake-wrapper
>>
>> when it's finished you can emerge system again, it will start 
>> emerging libtool (like emerge --resume that doesn't work because we 
>> have emerge something else in the meantime)
>>
>>
> ... and when I' will finish emerging system I'll discover that
>
> sys-libs/ncurses
> sys-apps/module-init-tools
> app-editors/nano
>
> have installed they binaries like this (you can check it emerging 
> gentoolkit and doing "qpkg -l sys-libs/ncurses | grep bin"):
>
> /bin/i686-pc-linux-gnu-lsmod
> /bin/i686-pc-linux-gnu-nano
>
> /usr/bin/i686-pc-linux-gnu-c++
> /usr/bin/i686-pc-linux-gnu-captoinfo
> /usr/bin/i686-pc-linux-gnu-clear
> /usr/bin/i686-pc-linux-gnu-g++
> /usr/bin/i686-pc-linux-gnu-gcc
> /usr/bin/i686-pc-linux-gnu-infocmp
> /usr/bin/i686-pc-linux-gnu-infotocap
> /usr/bin/i686-pc-linux-gnu-reset
> /usr/bin/i686-pc-linux-gnu-tic
> /usr/bin/i686-pc-linux-gnu-toe
> /usr/bin/i686-pc-linux-gnu-tput
> /usr/bin/i686-pc-linux-gnu-tset
>
> it's the era of the woozy numbat ;)
>
BTW reemerging the previous ebuilds dont'change anything so u need to 
manual symlink them or you will never play again at the "clear ls clear 
ls clear ls" game

and I finish this monologue saying that
echo "=sys-boot/grub-0.95.20040823" >> /etc/portage/package.mask
is needed , see http://bugs.gentoo.org/show_bug.cgi?id=73419
dont try to change it WANT_AUTOMAKE= in the ebuild loss of time

going to build "Zonked Quokka" -gentoo-r9 configured by "make oldconfig" 
&& "make menuconfig"

good night at everyone


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

[Bastian Balthazar Bux]

Bastian Balthazar Bux wrote:

> Bastian Balthazar Bux wrote:
>
>>
>> <snip>
>>
>>> it will stop emerging system at sys-devel/libtool
>>> you need to emerge sys-devel/automake-wrapper
>>>
>>> when it's finished you can emerge system again, it will start 
>>> emerging libtool (like emerge --resume that doesn't work because we 
>>> have emerge something else in the meantime)
>>>
>>>
>> ... and when I' will finish emerging system I'll discover that
>>
>> sys-libs/ncurses
>> sys-apps/module-init-tools
>> app-editors/nano
>>
>> have installed they binaries like this (you can check it emerging 
>> gentoolkit and doing "qpkg -l sys-libs/ncurses | grep bin"):
>>
>> /bin/i686-pc-linux-gnu-lsmod
>> /bin/i686-pc-linux-gnu-nano
>>
>> /usr/bin/i686-pc-linux-gnu-c++
>> /usr/bin/i686-pc-linux-gnu-captoinfo
>> /usr/bin/i686-pc-linux-gnu-clear
>> /usr/bin/i686-pc-linux-gnu-g++
>> /usr/bin/i686-pc-linux-gnu-gcc
>> /usr/bin/i686-pc-linux-gnu-infocmp
>> /usr/bin/i686-pc-linux-gnu-infotocap
>> /usr/bin/i686-pc-linux-gnu-reset
>> /usr/bin/i686-pc-linux-gnu-tic
>> /usr/bin/i686-pc-linux-gnu-toe
>> /usr/bin/i686-pc-linux-gnu-tput
>> /usr/bin/i686-pc-linux-gnu-tset
>>
>> it's the era of the woozy numbat ;)
>>
> BTW reemerging the previous ebuilds dont'change anything so u need to 
> manual symlink them or you will never play again at the "clear ls 
> clear ls clear ls" game
>
> and I finish this monologue saying that

I'm lier there are also this in /usr/sbin
/usr/sbin/i686-pc-linux-gnu-depmod                 
/usr/sbin/i686-pc-linux-gnu-generate-modprobe.conf 
/usr/sbin/i686-pc-linux-gnu-insmod                 
/usr/sbin/i686-pc-linux-gnu-insmod.static          
/usr/sbin/i686-pc-linux-gnu-modinfo                
/usr/sbin/i686-pc-linux-gnu-modprobe               
/usr/sbin/i686-pc-linux-gnu-rmmod                  
sigh

> echo "=sys-boot/grub-0.95.20040823" >> /etc/portage/package.mask
> is needed , see http://bugs.gentoo.org/show_bug.cgi?id=73419
> dont try to change it WANT_AUTOMAKE= in the ebuild loss of time
>
> going to build "Zonked Quokka" -gentoo-r9 configured by "make 
> oldconfig" && "make menuconfig"
>
> good night at everyone
>
>
> -- 
> gentoo-user@gentoo.org mailing list
>
>


--
gentoo-user@gentoo.org mailing list

[gentoo-user] Stage1 install: GCC 3.4 ebuild exports CTARGET and causes problems

[Philipp Hasse]

Hi,

I recently tried to install Gentoo with GCC 3.4. After running bootstrap.sh
some packages refused to compile during "emerge system".
For instance, the configure script of xterm could not find the program
/usr/bin/tic (which is included in ncurses) though ncurses was installed.
I found tic in /usr/bin/ but with a different name:
/usr/bin/i586-pc-linux-gnu-tic. I figured out that this was caused by the
configure script which was run with the --target switch: ./configure
... --target=i586-pc-linux-gnu ...
This target switch is used when emerge finds CTARGET set in the environment
variables. CTARGET is set when the GCC ebuild (versions 3.4 and up, I think)
finds a cross compile which infact applies to a Gentoo installation because
Gentoo assumes to be i386-pc-linux-gnu in stage1. The function that writes
the CTARGET entry in /etc/env.d/gcc/<host> is create_gcc_env_entry found in
toolchain.eclass (/usr/portage/eclass) (if it detects a cross compile).
This function isn't used in the ebuilds of GCC with version 3.3.x (except
3.3.5 which is ~x86 and not installed in general). This explains why my
current Gentoo installation works quite fine.
So, why is create_gcc_env_entry used in the newest versions of GCC and
should this the default behaviour to detect a cross compile and to set
CTARGET even if both system types are of pc-linux-gnu but different
processors?

Regards
Philipp Hasse


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Gentoo with Kernel 2.6, GCC 3.4 and NPTL?

[Philipp Hasse]

Hi,

----- Original Message ----- 
From: "Bastian Balthazar Bux" <BastianBalthazarBux@pnpitalia.it>
To: <gentoo-user@lists.gentoo.org>
Sent: Monday, December 06, 2004 3:24 AM
Subject: Re: [gentoo-user] Re: Gentoo with Kernel 2.6, GCC 3.4 and NPTL?


> Bastian Balthazar Bux wrote:
>
> > Bastian Balthazar Bux wrote:
> >
> >>
> >> <snip>
> >>
> >>> it will stop emerging system at sys-devel/libtool
> >>> you need to emerge sys-devel/automake-wrapper
> >>>
> >>> when it's finished you can emerge system again, it will start
> >>> emerging libtool (like emerge --resume that doesn't work because we
> >>> have emerge something else in the meantime)
> >>>
> >>>
> >> ... and when I' will finish emerging system I'll discover that
> >>
> >> sys-libs/ncurses
> >> sys-apps/module-init-tools
> >> app-editors/nano
> >>
> >> have installed they binaries like this (you can check it emerging
> >> gentoolkit and doing "qpkg -l sys-libs/ncurses | grep bin"):
> >>
> >> /bin/i686-pc-linux-gnu-lsmod
> >> /bin/i686-pc-linux-gnu-nano
> >>
> >> /usr/bin/i686-pc-linux-gnu-c++
> >> /usr/bin/i686-pc-linux-gnu-captoinfo
> >> /usr/bin/i686-pc-linux-gnu-clear
> >> /usr/bin/i686-pc-linux-gnu-g++
> >> /usr/bin/i686-pc-linux-gnu-gcc
> >> /usr/bin/i686-pc-linux-gnu-infocmp
> >> /usr/bin/i686-pc-linux-gnu-infotocap
> >> /usr/bin/i686-pc-linux-gnu-reset
> >> /usr/bin/i686-pc-linux-gnu-tic
> >> /usr/bin/i686-pc-linux-gnu-toe
> >> /usr/bin/i686-pc-linux-gnu-tput
> >> /usr/bin/i686-pc-linux-gnu-tset
> >>
> >> it's the era of the woozy numbat ;)
> >>
> > BTW reemerging the previous ebuilds dont'change anything so u need to
> > manual symlink them or you will never play again at the "clear ls
> > clear ls clear ls" game
> >
> > and I finish this monologue saying that
>
> I'm lier there are also this in /usr/sbin
> /usr/sbin/i686-pc-linux-gnu-depmod
> /usr/sbin/i686-pc-linux-gnu-generate-modprobe.conf
> /usr/sbin/i686-pc-linux-gnu-insmod
> /usr/sbin/i686-pc-linux-gnu-insmod.static
> /usr/sbin/i686-pc-linux-gnu-modinfo
> /usr/sbin/i686-pc-linux-gnu-modprobe
> /usr/sbin/i686-pc-linux-gnu-rmmod
> sigh

See my email "[gentoo-user] Stage1 install: GCC 3.4 ebuild exports CTARGET
and causes problems".
This is exactly the problem I had here.

>
> > echo "=sys-boot/grub-0.95.20040823" >> /etc/portage/package.mask
> > is needed , see http://bugs.gentoo.org/show_bug.cgi?id=73419
> > dont try to change it WANT_AUTOMAKE= in the ebuild loss of time
> >
> > going to build "Zonked Quokka" -gentoo-r9 configured by "make
> > oldconfig" && "make menuconfig"
> >
> > good night at everyone
> >
> >
> > -- 
> > gentoo-user@gentoo.org mailing list
> >
> >
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>


--
gentoo-user@gentoo.org mailing list