RE: Creating static binaries

[Edward . Janowiak]

Dang. This still failed for me:

gcc  -g -O2  -static -o [  lbracket.o ../lib/libfetish.a  ../lib/libfetish.a
-lgen -lnsl 
ld: fatal: symbol `opterr' is multiply-defined:
        (file ../lib/libfetish.a(getopt.o) and file
/usr/lib/libc.a(opt_data.o));
ld: fatal: symbol `optind' is multiply-defined:
        (file ../lib/libfetish.a(getopt.o) and file
/usr/lib/libc.a(opt_data.o));
ld: fatal: symbol `optopt' is multiply-defined:
        (file ../lib/libfetish.a(getopt.o) and file
/usr/lib/libc.a(opt_data.o));
ld: fatal: File processing errors. No output written to [
collect2: ld returned 1 exit status
make[3]: *** [[] Error 1
make[3]: Leaving directory `/var/tmp/coreutils-5.2.1/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/coreutils-5.2.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/coreutils-5.2.1'
make: *** [all] Error 2

The following command succeeded:

make -e LDFLAGS=-all-static

but I don't think the binaries are really statically linked. When I truss
'id', it still references /usr/lib/ libraries.

-----Original Message-----
From: Jim Meyering [mailto:address@hidden
Sent: Tuesday, April 27, 2004 1:36 AM
To: address@hidden
Cc: address@hidden
Subject: Re: Creating static binaries


address@hidden wrote:
> I'm trying to create static binaries on Solaris 8 (Sparc) of the
> coreutilities for use in an intrusion response kit. I've tried both:
>
> ./configure
> make CC="gcc -static"
>
> and
>
> LDFLAGS=-static ./configure --prefix=/usr/local/coreutils
> make

This works for me:

  ./configure --prefix=/usr/local/coreutils
  make LDFLAGS=-static