| 1 |
On Fri, 2002-12-27 at 00:03, Richard Reich wrote: |
| 2 |
> Attached you will find the output of glibc errors... I've tried emerge |
| 3 |
> world -u, emerge glibc, emerge glibc -e. All before and after an emerge |
| 4 |
> clean. I get the same error in any case. Does anybody have any ideas |
| 5 |
> on what to do? |
| 6 |
> |
| 7 |
|
| 8 |
I have only seen this for two reasons. First was due to using |
| 9 |
experimental HTREE support in ext3. Second an most probibly are |
| 10 |
due to kernel headers. |
| 11 |
|
| 12 |
Edit the ebuild and change src_compile to: |
| 13 |
|
| 14 |
------------------------ |
| 15 |
src_compile() { |
| 16 |
local myconf="" |
| 17 |
|
| 18 |
# If we build for the build system we use the kernel headers from |
| 19 |
the target |
| 20 |
( use build || use sparc || use x86 ) \ |
| 21 |
&& myconf="${myconf} --with-headers=${ROOT}usr/include" |
| 22 |
# Set it without "build" as well, else it might use the current |
| 23 |
kernel's |
| 24 |
# headers, which might just fail (the linux-headers package is |
| 25 |
usually well |
| 26 |
# tested...) |
| 27 |
--------------------------- |
| 28 |
|
| 29 |
And see if that fixes it. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
|
| 34 |
Martin Schlemmer |
| 35 |
Gentoo Linux Developer, Desktop/System Team Developer |
| 36 |
Cape Town, South Africa |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives