From: "Johannes Lorenz" <johannes89@mailueberfall.de>
To: gcc-help@gcc.gnu.org
Cc: "Andrew Haley" <aph@redhat.com>, "Kai Ruottu" <kai.ruottu@wippies.com>
Subject: Aw: Re: How to compile gcc toolchain with special sysroot correctly?
Date: Wed, 27 Nov 2013 15:17:00 -0000 [thread overview]
Message-ID: <trinity-b0175885-2659-4e20-85f2-2f0486409b2b-1385560673943@3capp-gmx-bs06> (raw)
@Andrew:
I copied these crt*.o libraries, but now, it complains that it is missing stdio.h. I really guess it would be better to link to the whole old glibc. Is there any good trick to tell gcc: Search in your sysroot, but if you can not find it, try in "/usr/include" ? (somehow the opposite of "-I")
@Kai:
> Are you trying to build the target Linux system from scratch? The
> produced glibc runtime parts (shared
> libs) being installed onto the originally unexisting target system? If
> not then your goal is "conceptually
> wrong"
I don't know what you mean, but I am trying to install glibc to another "root" on the same target system. I have gcc 4.4, but want to have 4.7 (on the same target), so I tried to compile a new toolchain in ~/local, using my gcc 4.4.
> In a simple Ubuntu 12.04 to OpenSuSE 12.2 cross compiler case using a
> sysroot'ed glibc for the target system
> one of course would produce only the target binutils and the target GCC
> for the $host (that usually being a
> totally different arch, different CPU, and system, for instance
> Solaris2.10).
Ok, I don't want to compile to a different target. I only mentioned openSuSE to say that the versions of binutils, gcc and glibc work on "some system". But I just want to compile on $host for $host ;) Both are Ubuntu.
> If this isn't clear then one should ask : "Do people REALLY
> replace the target C library in native
> binutils and GCC builds?" It would sound "sane" to rebuild the system
> glibc with the updated binutils and
> GCC afterwards, they are newer and should produce a better and quicker C
> library, or how? But please
> believe me, the native binutils and GCC builders don't try to replace
> the target C library in '/lib*', '/usr/lib*',
> '/usr/include' etc. Neither all the X11 libraries in the system! So why
> on earth any cross GCC builder would
> do that if all the target libraries are already there, prebuilt and tested?
So you'd say, unlike Andrew, that I should not compile a new glibc. I need a new libstdc++, I hope this will be compatible with the old glibc. But if I really want to compile a new glibc, you think this is impossible/very difficult?
Thanks and regards,
Johannes
--
Diese E-Mail wurde aus dem Sicherheitsverbund E-Mail made in
Germany versendet: http://www.gmx.net/e-mail-made-in-germany
next reply other threads:[~2013-11-27 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 15:17 Johannes Lorenz [this message]
2013-11-27 19:10 ` Andrew Haley
-- strict thread matches above, loose matches on Subject: below --
2013-12-01 8:27 Johannes Lorenz
2013-11-28 9:36 Johannes Lorenz
2013-11-27 9:07 Johannes Lorenz
2013-11-27 9:11 ` Andrew Haley
2013-11-27 10:02 ` Aw: " Johannes Lorenz
2013-11-27 11:35 ` Andrew Haley
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=trinity-b0175885-2659-4e20-85f2-2f0486409b2b-1385560673943@3capp-gmx-bs06 \
--to=johannes89@mailueberfall.de \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kai.ruottu@wippies.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).