From: "Deno, Emerson" <Emerson.Deno@blackrock.com>
To: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: warnings i can't get rid off
Date: Fri, 03 Aug 2001 06:58:00 -0000 [thread overview]
Message-ID: <0132D06F0EF0D311A3E6009027BA1EA90F123679@brnyc-exch02.brnycdom.blkint.com> (raw)
i am using gcc-2.95.2 on solaris 2.5.1. i use the -B option to specify the
directory
where to find the linker and assembler (because the native solaris ones have
problems)
everything works great, except i get two warnings i can't get rid off
when compiling an object file with g++ -c i ALWAYS get
cpp: -lang-c++: linker input file unused since linking not done
and when linking
i ALWAYS get
g++.real: file path prefix `.../bin/' never used
but if i take out out the -B option i get horrible linking errors.
does anyone know of a way to get rid of these two warnings?
emerson
next reply other threads:[~2001-08-03 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 6:58 Deno, Emerson [this message]
2001-08-03 13:51 ` Alexandre Oliva
2001-09-20 3:48 ` David Forth
2001-09-28 17:08 ` Alexandre Oliva
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=0132D06F0EF0D311A3E6009027BA1EA90F123679@brnyc-exch02.brnycdom.blkint.com \
--to=emerson.deno@blackrock.com \
--cc=gcc-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).