public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kean Johnston" <jkj@sco.com>
To: <gcc@gcc.gnu.org>
Subject: 3.3 configure grep usage?
Date: Tue, 08 Apr 2003 09:41:00 -0000	[thread overview]
Message-ID: <002c01c2fd9d$30522da0$03419384@shrike> (raw)

Hi,

I am finally trying to get gcc 3.3 to work on OpenServer.
I ran into my first teeny problem. configure, while trying
to check "linker read-only and read-write section mixing"
uses an option "-A1" to grep. At least our grep doesn't
grok that option. What's it do? Can the test be written
another way?

Another configure oddity is it checks to see what linker
to use, finds (in my case) /usr/ccs/bin/ld, and then
in the aforementioned tst, uses option -shared. That's
almost certainly not portable. Should there be a test for
linker flags to use, possibly to see if the linker is
really the compiler .. AND the compiler is gcc, to then
use -shared, else to test for something like -G, especially
if the path found is in /usr/ccs/*, which is an SVR4-ism
on Solaris, UnixWare and OpenServer (possibly others)
and almost certainly *not* the GNU linker an almost
certainly *does* use -G for shared libraries?

One final thing ... any one have any ojections if I 
submit a patch that checks the directory "/usr/ccs/bin/elf"
before checking /usr/ccs/bin ... on OSR5 that will catch
the ELF tools, as opposed to the wrappers that need "-belf"
or "-bcoff" to distinguish between the two flavours those
tools support? This shouldn't affect any other hosts, I
don't think.

Kean

                 reply	other threads:[~2003-04-08  7:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='002c01c2fd9d$30522da0$03419384@shrike' \
    --to=jkj@sco.com \
    --cc=gcc@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).