From: Christopher Friedt <cfriedt@visible-assets.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] crossdev messes up system headers, etc
Date: Thu, 19 Oct 2006 20:35:43 +0200 [thread overview]
Message-ID: <4537C57F.9080507@visible-assets.com> (raw)
In-Reply-To: <0c8101c6f2d9$32b7f720$5b01a8c0@LXP0004>
I don't know if this has happened to anyone else, but I think it's
happened to me once before, maybe 6 months ago.
I tried to get a cross compiler working through crossdev, and it ended
up bailing on the last stage (gcc stage 2 i guess).
I tried it again, with a few different configurations, and noticed that
every time it failed directly upon compilation of binutils... saying
that /lib/cpp failed sanity checks.
ok, i said.... fine, i'll just crossdev -C everything out.
after that, i attempted to emerge another package. After a couple of
tries, i noticed the same errors.
It turns out that crossdev had done something unexpected, and removed
several system headers, and left my machine in a pretty useless state
for development. I can no longer compile anything, not even a kernel.
So obviously, I'd like to ask anyone for some sort of suggestion to get
my native development chain back.
Why is crossdev in production if it does these sort of things?
Can anyone recommend a GRP server for i686 ? hehehe...
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-19 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 10:35 [gentoo-embedded] C++ Exceptions Call Abort With Toolchain generated by crossdev Ryan Baldwin
2006-10-06 1:38 ` Mike Frysinger
2006-10-09 13:19 ` Ryan Baldwin
2006-10-15 7:47 ` Peter S. Mazinger
2006-10-16 9:13 ` [gentoo-embedded] GNAP & vmware-server-console Janusz Syrytczyk
2006-10-18 17:16 ` [gentoo-embedded] C++ Exceptions Call Abort With Toolchain generated by crossdev Ryan Baldwin
2006-10-19 18:35 ` Christopher Friedt [this message]
2006-10-19 22:23 ` [gentoo-embedded] crossdev messes up system headers, etc Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4537C57F.9080507@visible-assets.com \
--to=cfriedt@visible-assets.com \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox