From: Belldandy <narumi@tpts5.seed.net.tw>
To: help-gcc@gnu.org
Subject: adding include directories?
Date: Sat, 04 Dec 1999 05:20:00 -0000 [thread overview]
Message-ID: <384914B3.7E50C92F@tpts5.seed.net.tw> (raw)
I'm running FreeBSD 3.2 and I built GCC 2.95.2 into /usr/gcc,
apart from the usual /usr/local. It runs perfectly, but it's
having problems when I compile packages that depend on headers
and libraries in /usr/local/. How do I add directories to the
search path? TIA.....
WARNING: multiple messages have this Message-ID
From: Belldandy <narumi@tpts5.seed.net.tw>
To: help-gcc@gnu.org
Subject: adding include directories?
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <384914B3.7E50C92F@tpts5.seed.net.tw> (raw)
Message-ID: <19991231222400.0AwPR4GX_0aCcCUHlFVp1Qw2IFNSpoPQaea9U5I9ybA@z> (raw)
I'm running FreeBSD 3.2 and I built GCC 2.95.2 into /usr/gcc,
apart from the usual /usr/local. It runs perfectly, but it's
having problems when I compile packages that depend on headers
and libraries in /usr/local/. How do I add directories to the
search path? TIA.....
next reply other threads:[~1999-12-04 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 5:20 Belldandy [this message]
1999-12-09 13:23 ` ergeorge1
1999-12-31 22:24 ` ergeorge1
1999-12-31 22:24 ` Belldandy
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=384914B3.7E50C92F@tpts5.seed.net.tw \
--to=narumi@tpts5.seed.net.tw \
--cc=help-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).