1 |
I don't know if this has happened to anyone else, but I think it's |
2 |
happened to me once before, maybe 6 months ago. |
3 |
|
4 |
I tried to get a cross compiler working through crossdev, and it ended |
5 |
up bailing on the last stage (gcc stage 2 i guess). |
6 |
|
7 |
I tried it again, with a few different configurations, and noticed that |
8 |
every time it failed directly upon compilation of binutils... saying |
9 |
that /lib/cpp failed sanity checks. |
10 |
|
11 |
ok, i said.... fine, i'll just crossdev -C everything out. |
12 |
|
13 |
after that, i attempted to emerge another package. After a couple of |
14 |
tries, i noticed the same errors. |
15 |
|
16 |
It turns out that crossdev had done something unexpected, and removed |
17 |
several system headers, and left my machine in a pretty useless state |
18 |
for development. I can no longer compile anything, not even a kernel. |
19 |
|
20 |
So obviously, I'd like to ask anyone for some sort of suggestion to get |
21 |
my native development chain back. |
22 |
|
23 |
Why is crossdev in production if it does these sort of things? |
24 |
|
25 |
Can anyone recommend a GRP server for i686 ? hehehe... |
26 |
|
27 |
|
28 |
|
29 |
-- |
30 |
gentoo-embedded@g.o mailing list |