public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@cygnus.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Cross compilation vs. libiberty
Date: Wed, 02 Aug 2000 18:36:00 -0000	[thread overview]
Message-ID: <jmwvhzazy2.fsf@envy.cygnus.com> (raw)
In-Reply-To: <20000802182521R.mitchell@codesourcery.com>

Mark Mitchell <mark@codesourcery.com> writes:

> Folks --
> 
>   I have run into the problem where libiberty, only configured once,
> does not build for the target since the target configuration does not
> match the host.  In particular, I have stdlib.h on the host, but not
> on the target, but files in libiberty want to include stdlib.h because
> the host configury indicates that is the right thing to do.

I don't understand.  libiberty is configured once for the host, and
once for each multilib combination on the target:

Configuring in powerpc-eabisim/libiberty
creating cache ../config.cache
checking host system type... powerpc-unknown-eabisim
checking build system type... sparc-sun-solaris2.6
checking for powerpc-eabisim-ar... powerpc-eabisim-ar
checking for powerpc-eabisim-ranlib... powerpc-eabisim-ranlib
checking for gcc... /sloth/delay/tbox/build-gcc/gcc/xgcc -B/sloth/delay/tbox/build-gcc/gcc/ -B/sloth/delay/tbox/build-gcc/powerpc-eabisim/newlib/ -isystem /sloth/delay/tbox/build-gcc/powerpc-eabisim/newlib/targ-include -isystem /sloth/delay/tbox/cvs-gcc/egcs/newlib/libc/include -B/sloth/delay/tbox/objs/powerpc-eabisim/bin/ -B/sloth/delay/tbox/objs/powerpc-eabisim/lib/ -isystem /sloth/delay/tbox/objs/powerpc-eabisim/include
checking whether we are using GNU C... yes
...
checking for limits.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for unistd.h... yes
checking for strings.h... no

[this is significant because solaris does have /usr/include/strings.h.]

The target configuration happens after the compiler is built, of course, 
otherwise it couldn't work.

I think you have some other problem with your build.
-- 
- Geoffrey Keating <geoffk@cygnus.com>

  reply	other threads:[~2000-08-02 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-02 18:25 Mark Mitchell
2000-08-02 18:36 ` Geoff Keating [this message]
2000-08-02 18:42   ` Mark Mitchell
2000-08-02 18:39 ` Alexandre Oliva
2000-08-03  0:38 ` Jeffrey A Law

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=jmwvhzazy2.fsf@envy.cygnus.com \
    --to=geoffk@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.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).