public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bruce M Beach <bmbeach@lynchburg.net>
To: gcc@gcc.gnu.org
Subject: Binutils
Date: Sun, 12 Sep 1999 16:10:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.95.990912135932.141A-100000@lynchburg.net> (raw)

   Hello All

    I couldn't find a mailing list for binutils (2.9.1) so I thought
    that this list might be the closest thing to it. 
   
    I can build binutils without any problems but what I can't
    do is build them statically. I have tried
    env LDFLAGS=-static ./configure which sometimes works on other packages
    or exporting LDFLAGS=-static to the environment and even manually
    editing the Makefiles resulting from configure. Does anyone know
    how to get them to compile statically?
 
    Bruce

bmbeach@lynchburg.net

WARNING: multiple messages have this Message-ID

From: Bruce M Beach <bmbeach@lynchburg.net>
To: gcc@gcc.gnu.org
Subject: Binutils
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.95.990912135932.141A-100000@lynchburg.net> (raw)
Message-ID: <19990930180200.M_J7jwWCkZV9NL2W7GpKvAIM3t3EJE3vWUch9hzMWnI@z> (raw)

   Hello All

    I couldn't find a mailing list for binutils (2.9.1) so I thought
    that this list might be the closest thing to it. 
   
    I can build binutils without any problems but what I can't
    do is build them statically. I have tried
    env LDFLAGS=-static ./configure which sometimes works on other packages
    or exporting LDFLAGS=-static to the environment and even manually
    editing the Makefiles resulting from configure. Does anyone know
    how to get them to compile statically?
 
    Bruce

bmbeach@lynchburg.net

             reply	other threads:[~1999-09-12 16:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-12 16:10 Bruce M Beach [this message]
1999-09-12 22:03 ` Binutils Alex Buell
1999-09-30 18:02   ` Binutils Alex Buell
1999-09-30 18:02 ` Binutils Bruce M Beach
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27 18:38 Binutils Diego Morales
2003-01-28  5:43 ` Binutils Ben Elliston
2002-01-14  2:33 binutils Earl Healey
2002-01-14  2:43 ` binutils Craig Rodrigues
     [not found] <200106181556.LAA06106@one-point.com>
2001-06-19  5:47 ` Binutils Jeff Sturm
2001-06-19 15:13   ` Binutils Philip Blundell
2001-06-19 19:25     ` Binutils Jeff Sturm
2001-06-19 23:35       ` Binutils Philip Blundell
2001-06-20  4:40       ` Binutils Benoît Sibaud
2001-06-20 14:32       ` Binutils Alexandre Oliva
     [not found] <md5:679D2BAAB79B012F46C5D7BC9D8A4E84>
2001-06-18  9:01 ` Binutils Paolo Carlini
2001-06-18  8:12 Binutils Mathieu Chouinard
1998-02-06 17:06 Binutils John Karcz
1998-02-07  1:06 ` Binutils Jeffrey A Law

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=Pine.LNX.3.95.990912135932.141A-100000@lynchburg.net \
    --to=bmbeach@lynchburg.net \
    --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).