From: "Lynn Feinauer" <lfeinauer@migratec.com>
To: <gnu@gnu.org>
Subject: gcc Installation for Linux IA64
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200003162133.QAA32461@delysid.gnu.org> (raw)
Message-ID: <20000401000000.v3vKiF11yMSoNIfNy0pwrhBSUZKaCq010yQ6MT481Hs@z> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
I have been trying to install the GNU C/C++
compiler IA-64 on Red-Hat Linux so that we can run our utility programs against
the Trillian compiler's header files. However, during the build process, I
encounter the error:
Â
      In file
included from
/usr2/GnuPro/instdir/gcc/include/syslimits.h:7, Â Â Â Â Â Â Â Â Â Â Â
           from
/usr2/GnuPro/instdir/gcc/include/limits.h:11, Â Â Â Â Â Â Â Â Â Â Â
           from
../../../../../src/newlib/libc/stdlib/std.h:4, Â Â Â Â Â Â Â Â Â Â Â
           from
../../../../../src/newlib/libc/stdlib/__adjust.c:7: Â Â Â
   /usr2/GnuPro/instdir/gcc/include/limits.h:117: limits.h: No
such file or directory   Â
       make[3]:
*** [__adjust.o] Error 1 Â Â Â Â Â Â make[3]:
Leaving directory
`/usr2/GnuPro/instdir/i486-pc-linux-gnu/newlib/libc/stdlib' Â Â Â
   make[2]: *** [all-recursive] Error 1   Â
   make[2]: Leaving directory
`/usr2/GnuPro/instdir/i486-pc-linux-gnu/newlib/libc' Â Â Â
   make[1]: *** [all-recursive] Error 1   Â
   make[1]: Leaving directory
`/usr2/GnuPro/instdir/i486-pc-linux-gnu/newlib' Â Â Â
   make: *** [all-target-newlib] Error 2
Â
and the installation will not continue further. The
build is apparently trying to recurse the various "limits.h" files in the
include path, and is fauling to find one of the directories, or is looking in
the wrong directory for the next "limits.h" in the include directory
chain.
Â
Has anyone else run into this? Is there an
alternate way for me to obtain the GCC header files without going through an
install?
Â
Thanks in advance.
Â
Lynn R.
Feinauer
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-16 13:33 Lynn Feinauer [this message]
2000-04-01 0:00 ` Lynn Feinauer
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=200003162133.QAA32461@delysid.gnu.org \
--to=lfeinauer@migratec.com \
--cc=gnu@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).