From: "Eduardo Martinez Pardeiro" <eduxmp@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: crosscompiler for ia64
Date: Sat, 15 Dec 2007 15:49:00 -0000 [thread overview]
Message-ID: <43f288560712150749t540a31bbj57cbda9bbc2946c9@mail.gmail.com> (raw)
In-Reply-To: <4763228A.25D48A54@dessent.net>
Thanks Brian. I'll try to do it. Is neccesary to recompile binutils
with hpux target? I read somewhere that,but i don't know if it's
neccesary
> The problem that you're running into is that gcc is just the compiler,
> it is not the C library. If you try to build a cross compiler without a
> libc (i.e. just using what comes with gcc) you will get something that
> is not very useful as it can't link any programs -- which also means it
> won't be able to build libgcc or libstdc++ or any of the other required
> support libraries, let alone a "hello world" C program. This is
> probably not what you want.
>
> One way to supply these items is with a sysroot. Take the relevant
> items from the target system (e.g. /usr/include and /usr/lib or
> whereever they are located) and reproduce them in the same tree
> structure in some subdirectory on the cross host. Then supply the top
> of that location as --with-sysroot=/foo/bar when configuring the cross
> compiler. If you don't have an appropriate target system to get a copy
> of these files from then you're in a bit of a pickle. If the target is
> open source you can use a more complicated process to bootstrap them
> from source, but when you're targeting a proprietary target like HP-UX
> there's really no choice but to copy them from the target system.
>
> Brian
>
prev parent reply other threads:[~2007-12-15 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 21:01 Eduardo Martinez Pardeiro
2007-12-15 0:39 ` Brian Dessent
2007-12-15 15:49 ` Eduardo Martinez Pardeiro [this message]
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=43f288560712150749t540a31bbj57cbda9bbc2946c9@mail.gmail.com \
--to=eduxmp@gmail.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).