From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32231 invoked by alias); 15 Dec 2007 15:49:31 -0000 Received: (qmail 32222 invoked by uid 22791); 15 Dec 2007 15:49:31 -0000 X-Spam-Check-By: sourceware.org Received: from wa-out-1112.google.com (HELO wa-out-1112.google.com) (209.85.146.180) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 15 Dec 2007 15:49:27 +0000 Received: by wa-out-1112.google.com with SMTP id m16so2015415waf.20 for ; Sat, 15 Dec 2007 07:49:26 -0800 (PST) Received: by 10.142.48.14 with SMTP id v14mr39201wfv.14.1197733765964; Sat, 15 Dec 2007 07:49:25 -0800 (PST) Received: by 10.143.9.19 with HTTP; Sat, 15 Dec 2007 07:49:25 -0800 (PST) Message-ID: <43f288560712150749t540a31bbj57cbda9bbc2946c9@mail.gmail.com> Date: Sat, 15 Dec 2007 15:49:00 -0000 From: "Eduardo Martinez Pardeiro" To: gcc-help@gcc.gnu.org Subject: Re: crosscompiler for ia64 In-Reply-To: <4763228A.25D48A54@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <43f288560712141301k6f5ef9fbvc4930bda898f2a7f@mail.gmail.com> <4763228A.25D48A54@dessent.net> X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00281.txt.bz2 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 >