This is the mail archive of the
mailing list for the GDB project.
RE: Building GDB Statically
- From: "Fahd Abidi" <fabidi at ultsol dot com>
- To: "Daniel Jacobowitz" <drow at false dot org>, "Dave Korn" <dave dot korn at artimi dot com>
- Cc: <gdb at sourceware dot org>
- Date: Tue, 13 Mar 2007 17:52:13 -0500
- Subject: RE: Building GDB Statically
I finally found how to do it. Under gdb6.6root/gdb/Makefile.in edit
there is a commented line like so:
I Just had to comment in the first line and comment out the second. I
also built it with out the shared libraries. the resulting Binary still
does not work under RH9 though, complains that the kernel version is too
BTW another possibility was if you used the optional CFLAG parameter
from the make command itself:
I am instead Building GDB6.4 on RH9 and am going to use that as my cross
host GDB binary, I have built it statically on RH9 and thus far have
confirmed that it works on FC6.
thanks for the help.
From: firstname.lastname@example.org [mailto:email@example.com] On
Behalf Of Daniel Jacobowitz
Sent: Tuesday, March 13, 2007 3:16 PM
To: Dave Korn
Cc: Fahd Abidi; firstname.lastname@example.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