1 |
To solve this I had to rebuild more than glibc: |
2 |
|
3 |
# emerge linux26-headers gcc glibc xorg-x11 |
4 |
|
5 |
It then compiled xorg without any more problems. |
6 |
|
7 |
Regards, |
8 |
|
9 |
Mick |
10 |
|
11 |
-----Original Message----- |
12 |
From: Eric S. Johansson [mailto:esj@××××××.org] |
13 |
Sent: 08 December 2004 02:05 |
14 |
To: gentoo-user@l.g.o |
15 |
Subject: Re: [gentoo-user] building without X |
16 |
|
17 |
|
18 |
Uwe Thiem wrote: |
19 |
|
20 |
> Lemme guess. You are building a server for thing clients otherwise the |
21 |
|
22 |
> statement above wouldn't make much sense. Alright, I will assume that. |
23 |
|
24 |
effectively right but there are other models where this would fit. |
25 |
think colinux systems. |
26 |
> |
27 |
> The X applications still need all the X-related libs to link against. |
28 |
So you |
29 |
> better build the whole X. |
30 |
> |
31 |
>>If it is impossible to split X11 into client and server packages, then |
32 |
I |
33 |
>>would need some help figuring out why it is dying on two security |
34 |
>>related functions. |
35 |
> |
36 |
> |
37 |
> So, what are those issues? |
38 |
|
39 |
./../programs/Xserver/hw/xfree86/loader/libloader.a(xf86sym.o)(.data+0x |
40 |
124c): |
41 |
undefined reference to `__stack_smash_handler' |
42 |
./../programs/Xserver/hw/xfree86/loader/libloader.a(xf86sym.o)(.data+0x |
43 |
1254): |
44 |
undefined reference to `__guard' |
45 |
collect2: ld returned 1 exit status |
46 |
|
47 |
|
48 |
someone else claimed that emerge sync and rebuilding glibc fixed the |
49 |
problem. trying that now. |
50 |
|
51 |
--- eric |
52 |
|
53 |
|
54 |
-- |
55 |
"Part of the problem with the Wal-Mart business model is that it |
56 |
requires more poverty in order to grow." |
57 |
|
58 |
http://www.salon.com/mwt/feature/2004/11/22/wal_mart/print.html |
59 |
|
60 |
-- |
61 |
gentoo-user@g.o mailing list |
62 |
|
63 |
|
64 |
|
65 |
|
66 |
-- |
67 |
gentoo-user@g.o mailing list |