Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Fahd Abidi" <fabidi@ultsol.com>
To: "Daniel Jacobowitz" <drow@false.org>,	"Dave Korn" <dave.korn@artimi.com>
Cc: <gdb@sourceware.org>
Subject: RE: Building GDB Statically
Date: Tue, 13 Mar 2007 18:22:00 -0000	[thread overview]
Message-ID: <071DB0C788671B48940BC79F8B49306907260C@ultsol01.tewks.ultsol.local> (raw)

-Compiling a dynamically linked binary on the oldest interesting system
works best.

I was going to do Just that. But I have thus far been unable to get
GDB6.6 to build on my RH9 box. Compiles just fine on my FC6. I'll try
your suggestion of setting LDFLAGS with a -static option and will let
you know the result. Will also try the --disable-shared option.

Fahd
 


-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Tuesday, March 13, 2007 3:16 PM
To: Dave Korn
Cc: Fahd Abidi; gdb@sourceware.org
Subject: Re: Building GDB Statically


On Tue, Mar 13, 2007 at 06:07:55PM -0000, Dave Korn wrote:
>   Most GNU software allows you to specify "--disable-shared" as an 
> option to the configure command to obtain a statically-linked build; 
> this takes care of everything you need to do for both compiler flags, 
> linker flags, libtool settings etc.

Actually, --disable-shared normally only generates static libraries
instead of shared libraries.

Setting LDFLAGS or CFLAGS should work.  However GDB may or may not when
moved between systems; I do not recommend the use of static binaries.
Compiling a dynamically linked binary on the oldest interesting system
works best.

-- 
Daniel Jacobowitz
CodeSourcery




             reply	other threads:[~2007-03-13 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13 18:22 Fahd Abidi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-14 12:18 Fahd Abidi
2007-03-13 18:03 Fahd Abidi
2007-03-13 18:08 ` Dave Korn
2007-03-13 18:15   ` Daniel Jacobowitz

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=071DB0C788671B48940BC79F8B49306907260C@ultsol01.tewks.ultsol.local \
    --to=fabidi@ultsol.com \
    --cc=dave.korn@artimi.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.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