public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Martin MOKREJŠ" <mmokrejs@natur.cuni.cz>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/8920: Cannot compile libiberty on Solaris 2.6 inside gcc-3.2.1
Date: Fri, 13 Dec 2002 05:46:00 -0000 [thread overview]
Message-ID: <20021213134604.7814.qmail@sources.redhat.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
The following reply was made to PR other/8920; it has been noted by GNATS.
From: =?iso-8859-2?Q?Martin_MOKREJ=A9?= <mmokrejs@natur.cuni.cz>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: gcc-gnats@gcc.gnu.org, <gcc-prs@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>,
<nobody@gcc.gnu.org>
Subject: Re: other/8920: Cannot compile libiberty on Solaris 2.6 inside
gcc-3.2.1
Date: Fri, 13 Dec 2002 14:40:38 +0100 (CET)
On 13 Dec 2002, Rainer Orth wrote:
> Martin Mokrejs <mmokrejs@natur.cuni.cz> writes:
>
> > even when I remove libiberty from gcc-3.2.1 and soflink to libiberty
> > from binutils-2.11.2, I don't get much further:
> >
> > gcc -c -DIN_GCC -g -W -Wall -Wwrite-strings -Wstrict-prototypes
> > -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long
> > -DHAVE_CONFIG_H -DGENERATOR_FILE -I/software/@sys/usr/include
> > -I/software/@sys/usr/include/ncurses
> > -I/software/@sys/usr/openssl/include
> > -I/software/@sys/usr/include/freetype2 -I. -I. -I../../gcc
> > -I../../gcc/. -I../../gcc/config -I../../gcc/../include
>
> all those -I/software/@sys switches look completely unnecessary, and
No, that whole lots of files installed under prefix=/software/@sys/usr,
i.e. really header files, libs, binaries. It's located in AFS (@sys is a
speciable variable expanded by kernel, not by any shell!).
/usr/inlcude definitely doesn't contains my custom compiled/installed
stuff from /software/@sys/usr/include
Maybe only the freetype2 stuff could go away this time, I know.
> -I/software/@sys/usr/include may be an equivalent to -I/usr/include, which
> doesn't play nicely with gcc. Try removing all of them and start a fresh
> bootstrap (with libiberty included again).
What do you mean "doesn't play nicely with gcc"?
--
Martin Mokrejs <mmokrejs@natur.cuni.cz>, <m.mokrejs@gsf.de>
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics <http://mips.gsf.de>
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585
next reply other threads:[~2002-12-13 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 5:46 Martin MOKREJŠ [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 2:56 Martin MOKREJŠ
2002-12-13 5:56 Rainer Orth
2002-12-13 5:36 Rainer Orth
2002-12-13 3:16 Martin Mokrejs
2002-12-12 20:16 mmokrejs
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=20021213134604.7814.qmail@sources.redhat.com \
--to=mmokrejs@natur.cuni.cz \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).