Hi u all :)

OK, I've done some stupid things : "emerge -C .." of some packages (
including KDE ;) ), because I got collisions when updating or installing
needed packages . Now, I can boot and a lot of things work well, but I can't
reinstall kde, or gnome , I get a lot of 'econf errors' . Emerge world ,
emerge system, revdep-rebuild ... all of these fail with econf errors or
collisions ...
Then I'd like to reinstall my Gentoo, but I don't want to lose my datas (
photos, movies ) , and if possible, I'd like not to have to reinstall some
applications like VDR , witch is sometimes a bit painfull to get working ;)
..
As I can boot my Gentoo OK, do you think I could try an install from stage3,
booting normally ( not from CD and chroot ) , erase my \distfiles and get
the new portage....bz2 ( allready downloaded ) ?
Before all of this happened , I had allready updated the kernel, so the
differences should not be too big ?

Thanks a lot for your answers

cu,
jf

jef_m wrote:

> Hi u all :)
>
> OK, I've done some stupid things : "emerge -C .." of some packages (
> including KDE ;) ), because I got collisions when updating or installing
> needed packages . Now, I can boot and a lot of things work well, but I
> can't reinstall kde, or gnome , I get a lot of 'econf errors' . Emerge
> world , emerge system, revdep-rebuild ... all of these fail with econf
> errors or collisions ...

You don't say what errors you get. They might be all caused by a common
reason, so seeing the actual messages could help. If the underlying problem
can be solved, you may probably be able to get things working again.

"pk" <pk@pk.invalid> wrote in message news:fsb2h5$g59$1@aioe.org...
> You don't say what errors you get. They might be all caused by a common
> reason, so seeing the actual messages could help. If the underlying
> problem
> can be solved, you may probably be able to get things working again.
>

You are probably right, I'll post them as son as I can reboot ( using
windows at work; same machine ) .
But actually, as I recently changed the processor and motheboard, and even
if the kernel rebuild seemed to be ok, I thought it
would probably be better to re-install .

jf

jef_m wrote:

> But actually, as I recently changed the processor and motheboard, and even
> if the kernel rebuild seemed to be ok, I thought it would probably be
> better to re-install .

That is usually not necessary, as long as the new proc+mobo are binary
compatible with the old ones.
Rebuilding everything is rarely needed, and, even in those cases, you
usually don't need to do that all at once.
For example, some critical upgrades (eg, /some/ gcc upgrades) require that
you recompile everything; in that case, the docs tell you to do so, and
that is usually accomplished by issuing an "emerge -e world" and let it do
its job (may take hours however).
Another common case is where you change your CFLAGS (as you probably did
after changing cpu and mobo). However, if old binaries run fine, you don't
need to recompile everything at once; instead, each new package from then
on will be built using the new CFLAGS, and, after some time, following
portage's natural activity (upgrades, etc.), you will have recompiled
almost all your packages.

Le Tue, 25 Mar 2008 16:59:13 +0100, pk a écritÂ*:
>
> That is usually not necessary, as long as the new proc+mobo are binary
> compatible with the old ones.
> Rebuilding everything is rarely needed, and, even in those cases, you
> usually don't need to do that all at once. For example, some critical
> upgrades (eg, /some/ gcc upgrades) require that you recompile
> everything; in that case, the docs tell you to do so, and that is
> usually accomplished by issuing an "emerge -e world" and let it do its
> job (may take hours however).
> Another common case is where you change your CFLAGS (as you probably did
> after changing cpu and mobo). However, if old binaries run fine, you
> don't need to recompile everything at once; instead, each new package
> from then on will be built using the new CFLAGS, and, after some time,
> following portage's natural activity (upgrades, etc.), you will have
> recompiled almost all your packages.

OK, I've launched emerge --update --deep world and here is the content of
/var/log/emerge.log

***************************************
1206482064: Started emerge on: Mar 25, 2008 21:54:24
1206482064: *** emerge --deep --update world
1206482105: >>> emerge (1 of 229) dev-libs/nspr-4.6.8 to /
1206482105: === (1 of 229) Cleaning (dev-libs/nspr-4.6.8::/usr/portage/
dev-libs/nspr/nspr-4.6.8.ebuild)
1206482106: === (1 of 229) Compiling/Merging (dev-libs/nspr-4.6.8::/usr/
portage/dev-libs/nspr/nspr-4.6.8.ebuild)
1206482113: *** terminating.
****************************************

and of '/var/log/portage/dev-libs:nspr-4.6.8:20080325-215506.log'.

********************************************
>>> Unpacking source...
>>> Unpacking nspr-4.6.8.tar.gz to /var/tmp/portage/dev-libs/nspr-4.6.8/
work
* Applying nspr-4.6.1-config.patch ...
 [ ok ]
* Applying nspr-4.6.1-config-1.patch ...
 [ ok ]
* Applying nspr-4.6.1-lang.patch ...
 [ ok ]
* Applying nspr-4.6.1-prtime.patch ...
 [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-libs/nspr-4.6.8/work/
nspr-4.6.8 ...
* econf: updating nspr-4.6.8/mozilla/nsprpub/build/autoconf/config.sub
with /usr/share/gnuconfig/config.sub
* econf: updating nspr-4.6.8/mozilla/nsprpub/build/autoconf/config.guess
with /usr/share/gnuconfig/config.guess
.../mozilla/nsprpub/configure --prefix=/usr --host=i686-pc-linux-gnu --
mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --
sysconfdir=/etc --localstatedir=/var/lib --disable-debug --enable-ipv6 --
libdir=/usr/lib/nspr --build=i686-pc-linux-gnu
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for whoami... /usr/bin/whoami
checking for c++... c++
checking whether the C++ compiler (c++ -O2 -march=i686 -fomit-frame-
pointer ) works... yes
checking whether the C++ compiler (c++ -O2 -march=i686 -fomit-frame-
pointer ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ accepts -g... yes
checking for gcc... gcc
checking whether the C compiler (gcc -O2 -march=i686 -fomit-frame-
pointer ) works... yes
checking whether the C compiler (gcc -O2 -march=i686 -fomit-frame-
pointer ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for ranlib... ranlib
checking for as... /usr/bin/as
checking for ar... /usr/bin/ar
checking for ld... /usr/bin/ld
checking for strip... /usr/bin/strip
checking for windres... no
checking for gcc -pipe support... cat: dummy-hello.s: No such file or
directory
no
checking for visibility(hidden) attribute... yes
checking for visibility pragma support... no
checking for perl5... no
checking for perl... /usr/bin/perl
checking for dlopen in -ldl... yes
checking for dlfcn.h... no
checking whether gcc needs -traditional... no
checking for lchown... yes
checking for strerror... yes
checking for pthread_create in -lpthreads... no
checking for pthread_create in -lpthread... no
checking for pthread_create in -lc_r... no
checking for pthread_create in -lc... no
checking whether gcc accepts -pthread... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
creating config/Makefile
creating config/autoconf.mk
creating config/nsprincl.mk
creating config/nsprincl.sh
creating config/nspr-config
creating config/nspr.pc
creating lib/Makefile
creating lib/ds/Makefile
creating lib/libc/Makefile
creating lib/libc/include/Makefile
creating lib/libc/src/Makefile
creating lib/tests/Makefile
creating pkg/Makefile
creating pkg/linux/Makefile
creating pkg/solaris/Makefile
creating pkg/solaris/SUNWpr/Makefile
creating pkg/solaris/SUNWprd/Makefile
creating pr/Makefile
creating pr/include/Makefile
creating pr/include/md/Makefile
creating pr/include/obsolete/Makefile
creating pr/include/private/Makefile
creating pr/src/Makefile
creating pr/src/io/Makefile
creating pr/src/linking/Makefile
creating pr/src/malloc/Makefile
creating pr/src/md/Makefile
creating pr/src/md/unix/Makefile
creating pr/src/memory/Makefile
creating pr/src/misc/Makefile
creating pr/src/threads/Makefile
creating pr/tests/Makefile
creating pr/tests/dll/Makefile
creating pr/src/pthreads/Makefile
cd config; make -j1 export
make[1]: Entering directory `/var/tmp/portage/dev-libs/nspr-4.6.8/work/
nspr-4.6.8/build/config'
gcc -o now.o -c -O2 -march=i686 -fomit-frame-pointer -Wall -pthread -
fPIC -UDEBUG -DNDEBUG=1 -DHAVE_VISIBILITY_HIDDEN_ATTRIBUTE=1 -
DXP_UNIX=1 -D_GNU_SOURCE=1 -DHAVE_FCNTL_FILE_LOCKING=1 -DLINUX=1 -Di386=1
-DHAVE_LCHOWN=1 -DHAVE_STRERROR=1 -D_REENTRANT=1 -DFORCE_PR_LOG -
D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM -D_PR_INET6 ../../mozilla/
nsprpub/config/now.c
In file included from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/stdio.h:34:21: stddef.h: No such file or directory
In file included from /usr/include/_G_config.h:44,
from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/gconv.h:72: error: syntax error before "size_t"
/usr/include/gconv.h:88: error: syntax error before "size_t"
/usr/include/gconv.h:97: error: syntax error before "size_t"
/usr/include/gconv.h:174: error: syntax error before "size_t"
/usr/include/gconv.h:177: error: syntax error before '}' token
In file included from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/_G_config.h:47: error: field `__cd' has incomplete type
/usr/include/_G_config.h:50: error: field `__cd' has incomplete type
In file included from /usr/include/stdio.h:72,
from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/libio.h:53:21: stdarg.h: No such file or directory
In file included from /usr/include/stdio.h:72,
from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/libio.h:354: error: syntax error before "size_t"
/usr/include/libio.h:363: error: syntax error before "size_t"
/usr/include/libio.h:475: error: syntax error before "__gnuc_va_list"
/usr/include/libio.h:477: error: syntax error before "__gnuc_va_list"
/usr/include/libio.h:479: error: syntax error before "_IO_sgetn"
/usr/include/libio.h:479: error: syntax error before "size_t"
In file included from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/stdio.h:77: error: syntax error before "va_list"
In file included from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/stdio.h:284: error: syntax error before "size_t"
/usr/include/stdio.h:290: error: syntax error before "size_t"
/usr/include/stdio.h:302: error: syntax error before "size_t"
/usr/include/stdio.h:309: error: syntax error before "size_t"
/usr/include/stdio.h:337: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:342: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:345: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:351: error: syntax error before "size_t"
/usr/include/stdio.h:355: error: syntax error before "size_t"
/usr/include/stdio.h:365: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:381: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:412: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:419: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:424: error: syntax error before "__gnuc_va_list"
/usr/include/stdio.h:560: error: syntax error before "size_t"
/usr/include/stdio.h:563: error: syntax error before "size_t"
/usr/include/stdio.h:573: error: syntax error before "size_t"
/usr/include/stdio.h:603: error: syntax error before "fread"
/usr/include/stdio.h:603: error: syntax error before "size_t"
/usr/include/stdio.h:609: error: syntax error before "fwrite"
/usr/include/stdio.h:609: error: syntax error before "size_t"
/usr/include/stdio.h:631: error: syntax error before "fread_unlocked"
/usr/include/stdio.h:631: error: syntax error before "size_t"
/usr/include/stdio.h:633: error: syntax error before "fwrite_unlocked"
/usr/include/stdio.h:633: error: syntax error before "size_t"
In file included from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/stdio.h:798: error: syntax error before "__gnuc_va_list"
In file included from /usr/include/stdio.h:828,
from ../../mozilla/nsprpub/config/now.c:38:
/usr/include/bits/stdio.h:34: error: syntax error before "__gnuc_va_list"
/usr/include/bits/stdio.h: In function `vprintf':
/usr/include/bits/stdio.h:35: error: number of arguments doesn't match
prototype
cc1: error: prototype declaration
/usr/include/bits/stdio.h:36: error: `__fmt' undeclared (first use in
this function)
/usr/include/bits/stdio.h:36: error: (Each undeclared identifier is
reported only once
/usr/include/bits/stdio.h:36: error: for each function it appears in.)
/usr/include/bits/stdio.h:36: error: `__arg' undeclared (first use in
this function)
/usr/include/bits/stdio.h: At top level:
/usr/include/bits/stdio.h:102: error: syntax error before "size_t"
/usr/include/bits/stdio.h: In function `getline':
/usr/include/bits/stdio.h:104: error: `__lineptr' undeclared (first use
in this function)
/usr/include/bits/stdio.h:104: error: `__n' undeclared (first use in this
function)
/usr/include/bits/stdio.h:104: error: `__stream' undeclared (first use in
this function)
In file included from ../../mozilla/nsprpub/config/now.c:39:
/usr/include/stdlib.h: At top level:
/usr/include/stdlib.h:140: error: syntax error before
"__ctype_get_mb_cur_max"
In file included from /usr/include/sys/types.h:266,
from /usr/include/stdlib.h:433,
from ../../mozilla/nsprpub/config/now.c:39:
/usr/include/bits/pthreadtypes.h:48: error: syntax error before "size_t"
/usr/include/bits/pthreadtypes.h:51: error: syntax error before
"__stacksize"
In file included from ../../mozilla/nsprpub/config/now.c:39:
/usr/include/stdlib.h:450: error: syntax error before "size_t"
/usr/include/stdlib.h:480: error: syntax error before "size_t"
/usr/include/stdlib.h:584: error: syntax error before "__size"
/usr/include/stdlib.h:586: error: syntax error before "__nmemb"
/usr/include/stdlib.h:595: error: syntax error before "size_t"
In file included from /usr/include/stdlib.h:606,
from ../../mozilla/nsprpub/config/now.c:39:
/usr/include/alloca.h:33: error: syntax error before "__size"
In file included from ../../mozilla/nsprpub/config/now.c:39:
/usr/include/stdlib.h:611: error: syntax error before "__size"
/usr/include/stdlib.h:616: error: syntax error before "size_t"
/usr/include/stdlib.h:768: error: syntax error before "size_t"
/usr/include/stdlib.h:773: error: syntax error before "size_t"
/usr/include/stdlib.h:846: error: syntax error before "size_t"
/usr/include/stdlib.h:849: error: syntax error before "size_t"
/usr/include/stdlib.h:853: error: syntax error before "size_t"
/usr/include/stdlib.h:857: error: syntax error before "size_t"
/usr/include/stdlib.h:866: error: syntax error before "size_t"
/usr/include/stdlib.h:869: error: syntax error before '*' token
/usr/include/stdlib.h:873: error: syntax error before "wchar_t"
/usr/include/stdlib.h:877: error: syntax error before "mbstowcs"
/usr/include/stdlib.h:877: error: syntax error before '*' token
/usr/include/stdlib.h:880: error: syntax error before "wcstombs"
/usr/include/stdlib.h:881: error: syntax error before '*' token
/usr/include/stdlib.h:943: error: syntax error before "size_t"
/usr/include/gconv.h:176: warning: array '__data' assumed to have one
element
make[1]: *** [now.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-libs/nspr-4.6.8/work/
nspr-4.6.8/build/config'
make: *** [export] Error 2
*
* ERROR: dev-libs/nspr-4.6.8 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2047: Called die
* The specific snippet of code:
* make || die
* The die message:
* (no error message)
*
* If you need support, post the topmost build error, and
the call stack if relevant.
* A complete build log is located at '/var/log/portage/dev-
libs:nspr-4.6.8:20080325-215506.log'.
* The ebuild environment file is located at '/var/tmp/
portage/dev-libs/nspr-4.6.8/temp/environment'.
*
********************************************

it seems that a lot of files are missing :(

cu,
jf

jef wrote:

> OK, I've launched emerge --update --deep world and here is the content of
> /var/log/emerge.log
>[cut]
> 1206482106: === (1 of 229) Compiling/Merging (dev-libs/nspr-4.6.8::/usr/
> portage/dev-libs/nspr/nspr-4.6.8.ebuild)

Well, it seems you've not updated your system for a *long* time. This is
most likely the source of your problems. You'll have to do some manual work
to sort things out.

> 1206482113: *** terminating.
> ****************************************
>
> and of '/var/log/portage/dev-libs:nspr-4.6.8:20080325-215506.log'.
>[cut]
> it seems that a lot of files are missing :(

First of all, updating your system on a regular basis (eg, once every 2/3
days or once a week), by using "emerge --sync" and "emerge -uD world" is
the way to go to avoid problems like this.

That said, let's see what we can do. The following are general instructions.
There isn't much to do, except trying to upgrade as many packages as
possible skipping those that fail, in the hope that those can be installed
later.

The general procedure is as follows: do an "emerge -uDvNt world" and let it
run until some package fails. When this happens, write down the name of the
failing package and resume the process skipping the offending package
using "emerge --resume --skipfirst". When there are no more packages to
build, try re-emerging those that had previously failed, one by one.

Depending on your situation, there are some critical packages you may want
to emerge before anything else, like for instance portage, python (which
portage is written in), linux-headers, glibc, gcc.

As a very general advice, if emerge wants to upgrade portage, do that first
(emerge portage), followed by linux-headers and glibc (emerge linux-headers
&& emerge glibc). Then go with the generic procedure described above.

However, be prepared to have some trouble during the process. You can post
your results here and ask for help, of course.

Regards

"pk" <pk@pk.invalid> wrote in message news:fsbut6$mgh$1@aioe.org...
> Well, it seems you've not updated your system for a *long* time. This is
> most likely the source of your problems. You'll have to do some manual
> work
>>[cut]
>
> As a very general advice, if emerge wants to upgrade portage, do that
> first
> (emerge portage), followed by linux-headers and glibc (emerge
> linux-headers
> && emerge glibc). Then go with the generic procedure described above.
>
> However, be prepared to have some trouble during the process. You can post
> your results here and ask for help, of course.
>
> Regards
>

Thanks a lot for your answers :) , I'll try that this evening ( maybe a part
of the night, too ;) ) .
Portage is up to date, merged without pb . gcc is ok too, but manually
compiled , the emerge complained about gcc being too old !

regards,
jf

Le Wed, 26 Mar 2008 11:48:14 +0400, jef_m a écritÂ*:

> "pk" <pk@pk.invalid> wrote in message news:fsbut6$mgh$1@aioe.org...
>> Well, it seems you've not updated your system for a *long* time. This
>> is most likely the source of your problems. You'll have to do some
>> manual work
>>>[cut]
>>
>> As a very general advice, if emerge wants to upgrade portage, do that
>> first
>> (emerge portage), followed by linux-headers and glibc (emerge
>> linux-headers
>> && emerge glibc). Then go with the generic procedure described above.
>>
>> However, be prepared to have some trouble during the process. You can
>> post your results here and ask for help, of course.
>>
>> Regards
>>
>>
> Thanks a lot for your answers :) , I'll try that this evening ( maybe a
> part of the night, too ;) ) .
> Portage is up to date, merged without pb . gcc is ok too, but manually
> compiled , the emerge complained about gcc being too old !
>
> regards,
> jf

Hello :)

Not too much hope to emerge anything . I thought portage was up to date,
but "emerge -uDvNt world" gives :
*****************************
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-apps/portage-2.1.4.4/work/
portage-2.1.4 ...
In file included from tbz2tool.c:3:
/usr/include/stdio.h:34:21: stddef.h: No such file or directory
In file included from /usr/include/_G_config.h:44,
from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from tbz2tool.c:3:
/usr/include/gconv.h:72: error: syntax error before "size_t"
/usr/include/gconv.h:88: error: syntax error before "size_t"
/usr/include/gconv.h:97: error: syntax error before "size_t"
/usr/include/gconv.h:174: error: syntax error before "size_t"
/usr/include/gconv.h:177: error: syntax error before '}' token
In file included from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from tbz2tool.c:3:
[snip]
tbz2tool.c:217: warning: data definition has no type or storage class
tbz2tool.c:218: error: syntax error before "goto"
tbz2tool.c:227: error: syntax error before numeric constant
tbz2tool.c:227: warning: data definition has no type or storage class
/usr/include/gconv.h:176: warning: array '__data' assumed to have one
element
*
* ERROR: sys-apps/portage-2.1.4.4 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2388: Called die
* The specific snippet of code:
* $(tc-getCC) ${CFLAGS} ${LDFLAGS} -o tbz2tool
tbz2tool.c || die "Failed to build tbz2tool";
* The die message:
* Failed to build tbz2tool
*
* If you need support, post the topmost build error, and
the call stack if relevant.
* A complete build log is located at '/var/log/portage/sys-
apps:portage-2.1.4.4:20080326-215042.log'.
******************************

and each time I launch "emerge --resume --skipfirst" , it fails .

I tried to emerge glibc, and it fails with :

******************************
running configure fragment for sysdeps/i386/elf
checking for i386 TLS support... yes
running configure fragment for nptl/sysdeps/pthread
checking for forced unwind support... no
configure: error: forced unwind support is required
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3325: Called eblit-run
'src_compile'
* environment, line 1066: Called eblit-glibc-
src_compile
* src_compile.eblit, line 179: Called toolchain-
glibc_src_compile
* src_compile.eblit, line 120: Called
glibc_do_configure 'src_compile'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* "${S}"/configure ${myconf} || die "failed to
configure glibc"
* The die message:
* failed to configure glibc
************************************************** ****

do you know what is "forced unwind support" and how to enable it ?

thanks again .

regards,
jf

jef wrote:

> Not too much hope to emerge anything . I thought portage was up to date,
> but "emerge -uDvNt world" gives :
> *****************************
>>>> Source unpacked.
>>>> Compiling source in /var/tmp/portage/sys-apps/portage-2.1.4.4/work/
> portage-2.1.4 ...
> In file included from tbz2tool.c:3:
> /usr/include/stdio.h:34:21: stddef.h: No such file or directory

Apparently, stddef.h belongs to linux-headers. So, try emerging
linux-headers (emerge linux-headers, should be an unpack-only merge; it
should not need to compile anything) and then try an emerge -uDvNt world
again.

> checking for forced unwind support... no
> configure: error: forced unwind support is required
>[cut]
> do you know what is "forced unwind support" and how to enable it ?

A bit of googling seems to suggest that's something related to libpthreads.
Just a shot in the dark: after emerging linux-headers, try emerging gcc
(before emerging world).

Le Wed, 26 Mar 2008 20:42:45 +0100, pk a écritÂ*:

> jef wrote:

> Apparently, stddef.h belongs to linux-headers. So, try emerging
> linux-headers (emerge linux-headers, should be an unpack-only merge; it
> should not need to compile anything) and then try an emerge -uDvNt world
> again.
>
>> checking for forced unwind support... no configure: error: forced
>> unwind support is required
>>[cut]
>> do you know what is "forced unwind support" and how to enable it ?
>
> A bit of googling seems to suggest that's something related to
> libpthreads. Just a shot in the dark: after emerging linux-headers, try
> emerging gcc (before emerging world).

even linux-headers won't compile !

*********************************
>>> Compiling source in /var/tmp/portage/sys-kernel/linux-headers-2.6.23-
r3/work/gentoo-headers-base-2.6.23 ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-kernel/linux-headers-2.6.23-r3

>>> Install linux-headers-2.6.23-r3 into /var/tmp/portage/sys-kernel/
linux-headers-2.6.23-r3/image/ category sys-kernel
CHK include/linux/version.h
UPD include/linux/version.h
HOSTCC scripts/unifdef
In file included from /usr/include/ctype.h:28,
from scripts/unifdef.c:66:
/usr/include/bits/types.h:31:20: stddef.h: No such file or directory
In file included from scripts/unifdef.c:67:
/usr/include/err.h:26:20: stdarg.h: No such file or directory
scripts/unifdef.c:69:21: stdbool.h: No such file or directory
In file included from /usr/include/_G_config.h:44,
from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from scripts/unifdef.c:70:
/usr/include/gconv.h:72: error: syntax error before "size_t"
[snip]
scripts/unifdef.c: At top level:
/usr/include/gconv.h:176: warning: array '__data' assumed to have one
element
scripts/unifdef.c:185: warning: 'input' defined but not used
scripts/unifdef.c:204: warning: 'debug' declared `static' but never
defined
scripts/unifdef.c:775: warning: 'ifeval' defined but not used
scripts/unifdef.c:215: warning: 'process' declared `static' but never
defined
scripts/unifdef.c:510: warning: 'process' defined but not used
scripts/unifdef.c:986: warning: 'debug' defined but not used
make[1]: *** [scripts/unifdef] Error 1
make: *** [headers_install] Error 2
*
* ERROR: sys-kernel/linux-headers-2.6.23-r3 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 2910: Called
kernel-2_src_install
* environment, line 2150: Called
install_headers
* environment, line 2002: Called die
* The specific snippet of code:
* emake headers_install INSTALL_HDR_PATH="${D}"/
${ddir}/.. ${xmakeopts} || die;
* The die message:
* (no error message)
*
* If you need support, post the topmost build error, and
the call stack if relevant.
*******************************************

and if I try to update linux-headers , it tells me it's up-to-date , same
with "portage"

Sorry for all of this, I don't want you to get a headache because of me ;)

jf