From: Jinsong Zhao <zhaojs@Cadence.COM>
To: egcs@egcs.cygnus.com
Subject: how to set include file directory?
Date: Thu, 21 Jan 1999 13:50:00 -0000 [thread overview]
Message-ID: <pur4spkthwj.fsf@aton.Cadence.COM> (raw)
I downloaded the newest libstdc++-2.90.2 and egcs-1.1.1.
1. If I replace libstdc++ in egcs with the newer version, compilation
fails on Solaris because the compilation needs the head files that are
prohibited by the -nostdc++ option.
2. If I compile egcs-1.1.1 first, then I configure, build and install
libstdc++-2.90.2, it works, except that the
/usr/local/egcs/include/g++-v3 is not in the search directory. Seems it
is still using /usr/local/gnu/include/g++.
My question: how can put g++-v3 into its automatic search directory
for include files?
Jinsong
WARNING: multiple messages have this Message-ID
From: Jinsong Zhao <zhaojs@Cadence.COM>
To: egcs@egcs.cygnus.com
Subject: how to set include file directory?
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <pur4spkthwj.fsf@aton.Cadence.COM> (raw)
Message-ID: <19990131235800.kzEfTTlkhdSHce6ugMptYIMH0AO0iBZGSHLrmRCvsns@z> (raw)
I downloaded the newest libstdc++-2.90.2 and egcs-1.1.1.
1. If I replace libstdc++ in egcs with the newer version, compilation
fails on Solaris because the compilation needs the head files that are
prohibited by the -nostdc++ option.
2. If I compile egcs-1.1.1 first, then I configure, build and install
libstdc++-2.90.2, it works, except that the
/usr/local/egcs/include/g++-v3 is not in the search directory. Seems it
is still using /usr/local/gnu/include/g++.
My question: how can put g++-v3 into its automatic search directory
for include files?
Jinsong
next reply other threads:[~1999-01-21 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-21 13:50 Jinsong Zhao [this message]
1999-01-31 23:58 ` Jinsong Zhao
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=pur4spkthwj.fsf@aton.Cadence.COM \
--to=zhaojs@cadence.com \
--cc=egcs@egcs.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).