gnash-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] static cross compile gnash


From: Rob Savoye
Subject: Re: [Gnash-dev] static cross compile gnash
Date: Tue, 10 Nov 2009 09:14:08 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4

On 11/10/09 05:40, ???? wrote:

  Dynamic section at offset 0xe36e1c contains 30 entries:
   Tag        Type                         Name/Value
  0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
  0x00000001 (NEEDED)                     Shared library: [librt.so.1]
  0x00000001 (NEEDED)                     Shared library: [libdl.so.2]
  0x00000001 (NEEDED)                     Shared library: [libstdc++.so.6]
  0x00000001 (NEEDED)                     Shared library: [libm.so.6]
  0x00000001 (NEEDED)                     Shared library: [libc.so.6]
  0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
  0x0000000c (INIT)                       0x2175fc
  ...

  Now that I compiled in a static way,why does it still need these shared 
libraries??
  These shared libraries are in the toolchain directories.And all these shared 
libraries have static ones correspondingly in the toolchain.Why doesn't the 
toolchain built these libraries in a static way?

Configure with --enable-static to make Gnash built static libraries, but these other libraries are system ones. Statically building Gnash just makes the Gnash libs be compiled in. If any of these libraries is static archive, then they'll be compiled in too, but in this case they're dynamic ones. I think there is an option to libtool to only statically link everything, I can see if it works.

        - rob -




reply via email to

[Prev in Thread] Current Thread [Next in Thread]