public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: gas2@cygnus.com
Subject: how to handle incompatible things in libtool?
Date: Mon, 26 Jan 1998 20:26:00 -0000	[thread overview]
Message-ID: <19980126222548.54627@dgii.com> (raw)

Now it's time for me to pay the piper...

The SCO OpenServer compiler uses -bcoff, the default, and -belf to flip
between the two modes.  For years, there has been a well-distributed
version of GCC for OpenServer (but never an "official" one until very
recently).  Unfortunately, the newer versions use "-melf", the default,
and "-mcoff" to toggle between the modes.

I've been a derelect in checking GAS snapshots, but they don't do well
on this target on my host becuase they're finding GCC (egcs 1.0.1) and
they "know" to add -belf, which sends configure down in flames.

I'm guessing that I need to beat on these aclocal.m4 files, but they
look to be machine generated.


*-*-sco3.2v5*)
  # On SCO OpenServer 5, we need -belf to get full-featured binaries.
  CFLAGS="$CFLAGS -belf"
  ;;

will probably have to include a test of gcc and see if it supports
-belf.  If it's gcc and if -belf works, add it.  If it's gcc and -belf
fails, don't.  If it's not gcc, add -belf.  

But these seem to be generated files.   If anyone can offer hints what
they're generated *from*, I think I can submit a successful patch.

Thanx.

-- 
Robert Lipe       http://www.dgii.com/people/robertl       robertl@dgii.com

             reply	other threads:[~1998-01-26 20:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-26 20:26 Robert Lipe [this message]
1998-01-26 23:57 ` Robert Lipe

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=19980126222548.54627@dgii.com \
    --to=robertl@dgii.com \
    --cc=gas2@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).