From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>
To: gas2@cygnus.com
Subject: sparc-rtems libiberty problem
Date: Mon, 08 Jul 1996 13:22:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.91.960708144851.17369G-100000@merlin> (raw)
This is the first one I have tried so far. I don't exactly know what the
problem is but it looks like something is being built which probably
shouldn't. Here is the error message:
/net/morgana/usr1/rtems/work/rtems-config/build-sparc/gcc/xgcc
-B/net/morgana/usr1/rtems/work/rtems-config/build-sparc/gcc/ -idirafter
/net/morgana/usr1/rtems/work/rtems-config/build-sparc/sparc-rtems/newlib/targ-include
-idirafter /net/morgana/usr1/rtems/work/rtems-config/src/newlib/libc/include
-nostdinc -c -g -I. -I../../../src/libiberty/../include
../../../src/libiberty/choose-temp.c
../../../src/libiberty/choose-temp.c:27: sys/file.h: No such file or
directory gmake[1]: *** [choose-temp.o] Error 1 g
Any hints would be appreciated.
--joel
next reply other threads:[~1996-07-08 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-08 13:22 Joel Sherrill [this message]
1996-07-08 13:36 ` Ian Lance Taylor
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=Pine.SV4.3.91.960708144851.17369G-100000@merlin \
--to=joel@merlin.gcs.redstone.army.mil \
--cc=gas2@cygnus.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).