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

> 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.

Here's where I am so far.

There's a GNU package called "libtool" which contains the source        
strings that get edited into this stuff.                                

Libtool is the package that needs to know all this.  So I have to
go give libtool all the knowledge of all the compiler options and 
then use that modified libtool to rebuild the binutils package. 

Ugh.

RJL

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

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

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=19980127015623.17872@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).