How to build static lib's

How to build static lib's

[Kevin Wright]

Hello,

I've been using cygwin for about a year and have 
always had some problems building static only 
versions of libraries such as glib and gtk+.

Here's the configure options I've tried:

./configure --disable-shared --disable-shm --disable-nls --no-recursion

However, I still end up building the .lo & subsequent .la files. 
I tried hacking the libtool files but that was useless because it gets
created during the configure process. The problem is that certain lib's
programs fail with messages such as:

gdk_imlib ERROR: Cannot load image: 
/usr/local/share/pixmaps/gnome-question.png
All fallbacks failed.

WARNING: previous dlopen of 
E:\usr\local\lib\libimlib-png.so wasn't correctly performed


Is there a way to make these libs truly static? 

I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a 
newer snapshot of the cygwin1.dll but I am waiting for the 
complete installation package to be released.

TIA,

Kevin Wright
Aspect Development
Mountain View, CA 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: How to build static lib's

[Mumit Khan]

"Kevin Wright" <kwright@aspectdv.com> writes:
> Hello,
> 
> I've been using cygwin for about a year and have 
> always had some problems building static only 
> versions of libraries such as glib and gtk+.
> 
> Here's the configure options I've tried:
> 
> ./configure --disable-shared --disable-shm --disable-nls --no-recursion
> 
> However, I still end up building the .lo & subsequent .la files. 
> I tried hacking the libtool files but that was useless because it gets
> created during the configure process. The problem is that certain lib's
> programs fail with messages such as:
> 
> gdk_imlib ERROR: Cannot load image: 
> /usr/local/share/pixmaps/gnome-question.png
> All fallbacks failed.
> 
> WARNING: previous dlopen of 
> E:\usr\local\lib\libimlib-png.so wasn't correctly performed

This problem is due to a bug in cygwin-b20, and is fixed in recent
snapshots. In most cases, it is quite harmless (unless you're creating
subprocesses using fork/exec, in which case odd things may happen).

> Is there a way to make these libs truly static? 
> 
> I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a 
> newer snapshot of the cygwin1.dll but I am waiting for the 
> complete installation package to be released.

You need to ask the GTK folks about it. --disable-shared should have
created static libs only, but for some packages, that is not an option.
It's not possible to tell what the problem is from just what you've 
posted, sorry.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Suhaib Siddiqi]

Gtk+ and GNOME for MingW32 are available.  They are build as shared
libs (DLLs) I do not remember URL from where I downloaded them
couple of weeks ago.

Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Monday, September 27, 1999 3:31 PM
> To: Kevin Wright
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: How to build static lib's
>
>
> "Kevin Wright" <kwright@aspectdv.com> writes:
> > Hello,
> >
> > I've been using cygwin for about a year and have
> > always had some problems building static only
> > versions of libraries such as glib and gtk+.
> >
> > Here's the configure options I've tried:
> >
> > ./configure --disable-shared --disable-shm
> --disable-nls --no-recursion
> >
> > However, I still end up building the .lo & subsequent
> .la files.
> > I tried hacking the libtool files but that was useless
> because it gets
> > created during the configure process. The problem is
> that certain lib's
> > programs fail with messages such as:
> >
> > gdk_imlib ERROR: Cannot load image:
> > /usr/local/share/pixmaps/gnome-question.png
> > All fallbacks failed.
> >
> > WARNING: previous dlopen of
> > E:\usr\local\lib\libimlib-png.so wasn't correctly performed
>
> This problem is due to a bug in cygwin-b20, and is fixed in recent
> snapshots. In most cases, it is quite harmless (unless
> you're creating
> subprocesses using fork/exec, in which case odd things
> may happen).
>
> > Is there a way to make these libs truly static?
> >
> > I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
> > newer snapshot of the cygwin1.dll but I am waiting for the
> > complete installation package to be released.
>
> You need to ask the GTK folks about it. --disable-shared
> should have
> created static libs only, but for some packages, that is
> not an option.
> It's not possible to tell what the problem is from just
> what you've
> posted, sorry.
>
> Regards,
> Mumit
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Tor Lillqvist]

Suhaib Siddiqi writes:
 > Gtk+ and GNOME for MingW32 are available.  They are build as shared
 > libs (DLLs) I do not remember URL from where I downloaded them
 > couple of weeks ago.

You might refer to the stuff I have available at
http://www.iki.fi/tml/gimp/win32/ . It's just GLib and GTk+ (and the
GIMP), nothing directly GNOME-related, though. Also, there is a
desperate need for documentation how to use my precompiled DLLs when
building GTk+ programs. (It is a bit complex, as you must use
gcc-2.95, and remember to use the -mno-cygwin and -fnative-struct
flags, and patch the gcc setup to use msvcrt and not crtdll. Well,
actually I don't know if it's absolutely necessary to use msvcrt in
the client program even if the gtk, gdk and glib DLLs use it.)

--tml


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Suhaib Siddiqi]

Yes right.  that is what i was refering to.  Thought not directly
related to Gnome, but I found GTK+ and GDK+ ports very useful.

The GIMP is impressive, too. It did crashed on me with errors, once
in
a while when loading tiff.exe plug-ins.  It does crash if you
attempt to
open a tiff or jpeg file which is corrupted.

Suhaib

Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> Tor Lillqvist
> Sent: Monday, September 27, 1999 3:55 PM
> To: ssiddiqi@nspm.ipass.net
> Cc: Mumit Khan; Kevin Wright; cygwin@sourceware.cygnus.com
> Subject: RE: How to build static lib's
>
>
> Suhaib Siddiqi writes:
>  > Gtk+ and GNOME for MingW32 are available.  They are
> build as shared
>  > libs (DLLs) I do not remember URL from where I downloaded them
>  > couple of weeks ago.
>
> You might refer to the stuff I have available at
> http://www.iki.fi/tml/gimp/win32/ . It's just GLib and
> GTk+ (and the
> GIMP), nothing directly GNOME-related, though. Also, there is a
> desperate need for documentation how to use my
> precompiled DLLs when
> building GTk+ programs. (It is a bit complex, as you must use
> gcc-2.95, and remember to use the -mno-cygwin and -fnative-struct
> flags, and patch the gcc setup to use msvcrt and not crtdll. Well,
> actually I don't know if it's absolutely necessary to use
> msvcrt in
> the client program even if the gtk, gdk and glib DLLs use it.)
>
> --tml
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Suhaib Siddiqi]

Yes right.  that is what i was refering to.  Thought not directly
related to Gnome, but I found GTK+ and GDK+ ports very useful.

The GIMP is impressive, too. It did crashed on me with errors, once
in
a while when loading tiff.exe plug-ins.  It does crash if you
attempt to
open a tiff or jpeg file which is corrupted.

Suhaib

Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> Tor Lillqvist
> Sent: Monday, September 27, 1999 3:55 PM
> To: ssiddiqi@nspm.ipass.net
> Cc: Mumit Khan; Kevin Wright; cygwin@sourceware.cygnus.com
> Subject: RE: How to build static lib's
>
>
> Suhaib Siddiqi writes:
>  > Gtk+ and GNOME for MingW32 are available.  They are
> build as shared
>  > libs (DLLs) I do not remember URL from where I downloaded them
>  > couple of weeks ago.
>
> You might refer to the stuff I have available at
> http://www.iki.fi/tml/gimp/win32/ . It's just GLib and
> GTk+ (and the
> GIMP), nothing directly GNOME-related, though. Also, there is a
> desperate need for documentation how to use my
> precompiled DLLs when
> building GTk+ programs. (It is a bit complex, as you must use
> gcc-2.95, and remember to use the -mno-cygwin and -fnative-struct
> flags, and patch the gcc setup to use msvcrt and not crtdll. Well,
> actually I don't know if it's absolutely necessary to use
> msvcrt in
> the client program even if the gtk, gdk and glib DLLs use it.)
>
> --tml
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Tor Lillqvist]

Suhaib Siddiqi writes:
 > Gtk+ and GNOME for MingW32 are available.  They are build as shared
 > libs (DLLs) I do not remember URL from where I downloaded them
 > couple of weeks ago.

You might refer to the stuff I have available at
http://www.iki.fi/tml/gimp/win32/ . It's just GLib and GTk+ (and the
GIMP), nothing directly GNOME-related, though. Also, there is a
desperate need for documentation how to use my precompiled DLLs when
building GTk+ programs. (It is a bit complex, as you must use
gcc-2.95, and remember to use the -mno-cygwin and -fnative-struct
flags, and patch the gcc setup to use msvcrt and not crtdll. Well,
actually I don't know if it's absolutely necessary to use msvcrt in
the client program even if the gtk, gdk and glib DLLs use it.)

--tml


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Suhaib Siddiqi]

Gtk+ and GNOME for MingW32 are available.  They are build as shared
libs (DLLs) I do not remember URL from where I downloaded them
couple of weeks ago.

Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Monday, September 27, 1999 3:31 PM
> To: Kevin Wright
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: How to build static lib's
>
>
> "Kevin Wright" <kwright@aspectdv.com> writes:
> > Hello,
> >
> > I've been using cygwin for about a year and have
> > always had some problems building static only
> > versions of libraries such as glib and gtk+.
> >
> > Here's the configure options I've tried:
> >
> > ./configure --disable-shared --disable-shm
> --disable-nls --no-recursion
> >
> > However, I still end up building the .lo & subsequent
> .la files.
> > I tried hacking the libtool files but that was useless
> because it gets
> > created during the configure process. The problem is
> that certain lib's
> > programs fail with messages such as:
> >
> > gdk_imlib ERROR: Cannot load image:
> > /usr/local/share/pixmaps/gnome-question.png
> > All fallbacks failed.
> >
> > WARNING: previous dlopen of
> > E:\usr\local\lib\libimlib-png.so wasn't correctly performed
>
> This problem is due to a bug in cygwin-b20, and is fixed in recent
> snapshots. In most cases, it is quite harmless (unless
> you're creating
> subprocesses using fork/exec, in which case odd things
> may happen).
>
> > Is there a way to make these libs truly static?
> >
> > I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
> > newer snapshot of the cygwin1.dll but I am waiting for the
> > complete installation package to be released.
>
> You need to ask the GTK folks about it. --disable-shared
> should have
> created static libs only, but for some packages, that is
> not an option.
> It's not possible to tell what the problem is from just
> what you've
> posted, sorry.
>
> Regards,
> Mumit
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Suhaib Siddiqi]

The modified source code as well as  GTK+ and GNOME for
MINGW32 is at: It is compiled using egcs-1.1.2, as far I remember
from
the notes on URL.

For more information about the port or GLib, GTk+ and the GIMP to
native Windows, and pre-built binary packages, see
http://www.iki.fi/tml/gimp/win32/ or
http://www.gimp.org/~tml/gimp/win32/


Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Monday, September 27, 1999 3:31 PM
> To: Kevin Wright
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: How to build static lib's
>
>
> "Kevin Wright" <kwright@aspectdv.com> writes:
> > Hello,
> >
> > I've been using cygwin for about a year and have
> > always had some problems building static only
> > versions of libraries such as glib and gtk+.
> >
> > Here's the configure options I've tried:
> >
> > ./configure --disable-shared --disable-shm
> --disable-nls --no-recursion
> >
> > However, I still end up building the .lo & subsequent
> .la files.
> > I tried hacking the libtool files but that was useless
> because it gets
> > created during the configure process. The problem is
> that certain lib's
> > programs fail with messages such as:
> >
> > gdk_imlib ERROR: Cannot load image:
> > /usr/local/share/pixmaps/gnome-question.png
> > All fallbacks failed.
> >
> > WARNING: previous dlopen of
> > E:\usr\local\lib\libimlib-png.so wasn't correctly performed
>
> This problem is due to a bug in cygwin-b20, and is fixed in recent
> snapshots. In most cases, it is quite harmless (unless
> you're creating
> subprocesses using fork/exec, in which case odd things
> may happen).
>
> > Is there a way to make these libs truly static?
> >
> > I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
> > newer snapshot of the cygwin1.dll but I am waiting for the
> > complete installation package to be released.
>
> You need to ask the GTK folks about it. --disable-shared
> should have
> created static libs only, but for some packages, that is
> not an option.
> It's not possible to tell what the problem is from just
> what you've
> posted, sorry.
>
> Regards,
> Mumit
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's

[Suhaib Siddiqi]

The modified source code as well as  GTK+ and GNOME for
MINGW32 is at: It is compiled using egcs-1.1.2, as far I remember
from
the notes on URL.

For more information about the port or GLib, GTk+ and the GIMP to
native Windows, and pre-built binary packages, see
http://www.iki.fi/tml/gimp/win32/ or
http://www.gimp.org/~tml/gimp/win32/


Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Monday, September 27, 1999 3:31 PM
> To: Kevin Wright
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: How to build static lib's
>
>
> "Kevin Wright" <kwright@aspectdv.com> writes:
> > Hello,
> >
> > I've been using cygwin for about a year and have
> > always had some problems building static only
> > versions of libraries such as glib and gtk+.
> >
> > Here's the configure options I've tried:
> >
> > ./configure --disable-shared --disable-shm
> --disable-nls --no-recursion
> >
> > However, I still end up building the .lo & subsequent
> .la files.
> > I tried hacking the libtool files but that was useless
> because it gets
> > created during the configure process. The problem is
> that certain lib's
> > programs fail with messages such as:
> >
> > gdk_imlib ERROR: Cannot load image:
> > /usr/local/share/pixmaps/gnome-question.png
> > All fallbacks failed.
> >
> > WARNING: previous dlopen of
> > E:\usr\local\lib\libimlib-png.so wasn't correctly performed
>
> This problem is due to a bug in cygwin-b20, and is fixed in recent
> snapshots. In most cases, it is quite harmless (unless
> you're creating
> subprocesses using fork/exec, in which case odd things
> may happen).
>
> > Is there a way to make these libs truly static?
> >
> > I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
> > newer snapshot of the cygwin1.dll but I am waiting for the
> > complete installation package to be released.
>
> You need to ask the GTK folks about it. --disable-shared
> should have
> created static libs only, but for some packages, that is
> not an option.
> It's not possible to tell what the problem is from just
> what you've
> posted, sorry.
>
> Regards,
> Mumit
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

fork/exec fixed? [was Re: How to build static lib's]

[Charles S. Wilson]

Mumit Khan wrote:

> 
> This problem is due to a bug in cygwin-b20, and is fixed in recent
> snapshots. In most cases, it is quite harmless (unless you're creating
> subprocesses using fork/exec, in which case odd things may happen).
> 

Does this mean that the old fork/exec problem that plagued cygwin-perl a
while back is fixed in recent snapshots? Not fixed? Partially fixed?

Reference: "fork + dlls" thread on May 21-23, 1999.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: fork/exec fixed? [was Re: How to build static lib's]

[Chris Faylor]

On Mon, Sep 27, 1999 at 04:22:46PM -0400, Charles S. Wilson wrote:
>Mumit Khan wrote:
>
>> 
>> This problem is due to a bug in cygwin-b20, and is fixed in recent
>> snapshots. In most cases, it is quite harmless (unless you're creating
>> subprocesses using fork/exec, in which case odd things may happen).
>> 
>
>Does this mean that the old fork/exec problem that plagued cygwin-perl a
>while back is fixed in recent snapshots? Not fixed? Partially fixed?
>
>Reference: "fork + dlls" thread on May 21-23, 1999.

I don't think so.  I investigated this a while ago.  I looks like the problem
is due to the fork code loading the DLLs in the wrong order which causes the
DLLs in the child to be loaded in different locations than the parent.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: fork/exec fixed? [was Re: How to build static lib's]

[Chris Faylor]

On Mon, Sep 27, 1999 at 04:22:46PM -0400, Charles S. Wilson wrote:
>Mumit Khan wrote:
>
>> 
>> This problem is due to a bug in cygwin-b20, and is fixed in recent
>> snapshots. In most cases, it is quite harmless (unless you're creating
>> subprocesses using fork/exec, in which case odd things may happen).
>> 
>
>Does this mean that the old fork/exec problem that plagued cygwin-perl a
>while back is fixed in recent snapshots? Not fixed? Partially fixed?
>
>Reference: "fork + dlls" thread on May 21-23, 1999.

I don't think so.  I investigated this a while ago.  I looks like the problem
is due to the fork code loading the DLLs in the wrong order which causes the
DLLs in the child to be loaded in different locations than the parent.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

fork/exec fixed? [was Re: How to build static lib's]

[Charles S. Wilson]

Mumit Khan wrote:

> 
> This problem is due to a bug in cygwin-b20, and is fixed in recent
> snapshots. In most cases, it is quite harmless (unless you're creating
> subprocesses using fork/exec, in which case odd things may happen).
> 

Does this mean that the old fork/exec problem that plagued cygwin-perl a
while back is fixed in recent snapshots? Not fixed? Partially fixed?

Reference: "fork + dlls" thread on May 21-23, 1999.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's - prob with gtk/glib

[Kevin Wright]

Mumit Khan writes:

>You need to ask the GTK folks about it. --disable-shared should have
>created static libs only, but for some packages, that is not an option.
>It's not possible to tell what the problem is from just what you've
>posted, sorry.

Here is a snippet of the output from running configure:

checking for ld used by GCC... /bin/ld.exe
checking if the linker (/bin/ld.exe) is GNU ld... yes
checking for BSD-compatible nm... /bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking for object suffix... o
checking for executable suffix... .exe
checking for gcc option to produce PIC... none
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking if the linker (/bin/ld.exe) is GNU ld... yes
checking whether the linker (/bin/ld.exe) supports shared libraries... yes
checking command to parse /bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /bin/ld.exe option to reload object files... -r
checking dynamic linker characteristics... Win32 ld.exe
checking if libtool supports shared libraries... yes
checking if package supports dlls... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes

It seams that the configure script is broken because even though I specify
using no static libs, it still checks for whether libtool support shared
libs and it still tries to create the shared libs. I realize this is not the
fault of the compiler.

Here is the snipped of output from the build process:

/bin/sh ../libtool --mode=link gcc  -g -O2 -Wall  -o libgdk.la -rpath
/usr/local/lib -version-info 5:0:5 -release
1.2 -export-dynamic -L/usr/X11/lib -lXext -lX11 -lipc -lm gdk.lo gdkcc
libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin
shared libraries

Thanks to everyone who posted information regarding windows versions of gtk
but I'm only interested in building this under cygwin using X.

Kevin

>-----Original Message-----
>From: Mumit Khan [ mailto:khan@thor.xraylith.wisc.edu ]
>Sent: Monday, September 27, 1999 12:31 PM
>To: Kevin Wright
>Cc: cygwin@sourceware.cygnus.com
>Subject: Re: How to build static lib's
>
>
>"Kevin Wright" <kwright@aspectdv.com> writes:
>> Hello,
>>
>> I've been using cygwin for about a year and have
>> always had some problems building static only
>> versions of libraries such as glib and gtk+.
>>
>> Here's the configure options I've tried:
>>
>> ./configure --disable-shared --disable-shm --disable-nls
>--no-recursion
>>
>> However, I still end up building the .lo & subsequent .la files.
>> I tried hacking the libtool files but that was useless
>because it gets
>> created during the configure process. The problem is that
>certain lib's
>> programs fail with messages such as:
>>
>> gdk_imlib ERROR: Cannot load image:
>> /usr/local/share/pixmaps/gnome-question.png
>> All fallbacks failed.
>>
>> WARNING: previous dlopen of
>> E:\usr\local\lib\libimlib-png.so wasn't correctly performed
>
>This problem is due to a bug in cygwin-b20, and is fixed in recent
>snapshots. In most cases, it is quite harmless (unless you're creating
>subprocesses using fork/exec, in which case odd things may happen).
>
>> Is there a way to make these libs truly static?
>>
>> I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
>> newer snapshot of the cygwin1.dll but I am waiting for the
>> complete installation package to be released.
>
>You need to ask the GTK folks about it. --disable-shared should have
>created static libs only, but for some packages, that is not an option.
>It's not possible to tell what the problem is from just what you've
>posted, sorry.
>
>Regards,
>Mumit
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's - prob with gtk/glib

[Suhaib Siddiqi]

Please check the configure script.  It could be possible that
GTK does not support static libs.  Several sofwtare do, for example
GGI
will build only as shared lib no matter what you do.  The GGI
was designed to be a shared lib only.  It could be same for GTK, I
do not know.  you could check the documents and/or configure scripts
if this is the case. You may need to modify configure script to
build dlls instead of *.so.

Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> Kevin Wright
> Sent: Monday, September 27, 1999 5:58 PM
> To: 'Mumit Khan'
> Cc: cygwin@sourceware.cygnus.com
> Subject: RE: How to build static lib's - prob with gtk/glib
>
>
> Mumit Khan writes:
>
> >You need to ask the GTK folks about it. --disable-shared
> should have
> >created static libs only, but for some packages, that is
> not an option.
> >It's not possible to tell what the problem is from just
> what you've
> >posted, sorry.
>
> Here is a snippet of the output from running configure:
>
> checking for ld used by GCC... /bin/ld.exe
> checking if the linker (/bin/ld.exe) is GNU ld... yes
> checking for BSD-compatible nm... /bin/nm -B
> checking whether ln -s works... yes
> updating cache ./config.cache
> loading cache ./config.cache within ltconfig
> checking for object suffix... o
> checking for executable suffix... .exe
> checking for gcc option to produce PIC... none
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.lo... yes
> checking if gcc supports -fno-rtti -fno-exceptions ... yes
> checking if gcc static flag -static works... -static
> checking if the linker (/bin/ld.exe) is GNU ld... yes
> checking whether the linker (/bin/ld.exe) supports shared
> libraries... yes
> checking command to parse /bin/nm -B output... ok
> checking how to hardcode library paths into programs... immediate
> checking for /bin/ld.exe option to reload object files... -r
> checking dynamic linker characteristics... Win32 ld.exe
> checking if libtool supports shared libraries... yes
> checking if package supports dlls... no
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
>
> It seams that the configure script is broken because even
> though I specify
> using no static libs, it still checks for whether libtool
> support shared
> libs and it still tries to create the shared libs. I
> realize this is not the
> fault of the compiler.
>
> Here is the snipped of output from the build process:
>
> /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall  -o
> libgdk.la -rpath
> /usr/local/lib -version-info 5:0:5 -release
> 1.2 -export-dynamic -L/usr/X11/lib -lXext -lX11 -lipc -lm
> gdk.lo gdkcc
> libtool: link: warning: undefined symbols not allowed in
> i686-pc-cygwin
> shared libraries
>
> Thanks to everyone who posted information regarding
> windows versions of gtk
> but I'm only interested in building this under cygwin using X.
>
> Kevin
>
> >-----Original Message-----
> >From: Mumit Khan [ mailto:khan@thor.xraylith.wisc.edu ]
> >Sent: Monday, September 27, 1999 12:31 PM
> >To: Kevin Wright
> >Cc: cygwin@sourceware.cygnus.com
> >Subject: Re: How to build static lib's
> >
> >
> >"Kevin Wright" <kwright@aspectdv.com> writes:
> >> Hello,
> >>
> >> I've been using cygwin for about a year and have
> >> always had some problems building static only
> >> versions of libraries such as glib and gtk+.
> >>
> >> Here's the configure options I've tried:
> >>
> >> ./configure --disable-shared --disable-shm --disable-nls
> >--no-recursion
> >>
> >> However, I still end up building the .lo & subsequent
> .la files.
> >> I tried hacking the libtool files but that was useless
> >because it gets
> >> created during the configure process. The problem is that
> >certain lib's
> >> programs fail with messages such as:
> >>
> >> gdk_imlib ERROR: Cannot load image:
> >> /usr/local/share/pixmaps/gnome-question.png
> >> All fallbacks failed.
> >>
> >> WARNING: previous dlopen of
> >> E:\usr\local\lib\libimlib-png.so wasn't correctly performed
> >
> >This problem is due to a bug in cygwin-b20, and is fixed
> in recent
> >snapshots. In most cases, it is quite harmless (unless
> you're creating
> >subprocesses using fork/exec, in which case odd things
> may happen).
> >
> >> Is there a way to make these libs truly static?
> >>
> >> I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
> >> newer snapshot of the cygwin1.dll but I am waiting for the
> >> complete installation package to be released.
> >
> >You need to ask the GTK folks about it. --disable-shared
> should have
> >created static libs only, but for some packages, that is
> not an option.
> >It's not possible to tell what the problem is from just
> what you've
> >posted, sorry.
> >
> >Regards,
> >Mumit
> >
> >
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's - prob with gtk/glib

[Suhaib Siddiqi]

Please check the configure script.  It could be possible that
GTK does not support static libs.  Several sofwtare do, for example
GGI
will build only as shared lib no matter what you do.  The GGI
was designed to be a shared lib only.  It could be same for GTK, I
do not know.  you could check the documents and/or configure scripts
if this is the case. You may need to modify configure script to
build dlls instead of *.so.

Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> Kevin Wright
> Sent: Monday, September 27, 1999 5:58 PM
> To: 'Mumit Khan'
> Cc: cygwin@sourceware.cygnus.com
> Subject: RE: How to build static lib's - prob with gtk/glib
>
>
> Mumit Khan writes:
>
> >You need to ask the GTK folks about it. --disable-shared
> should have
> >created static libs only, but for some packages, that is
> not an option.
> >It's not possible to tell what the problem is from just
> what you've
> >posted, sorry.
>
> Here is a snippet of the output from running configure:
>
> checking for ld used by GCC... /bin/ld.exe
> checking if the linker (/bin/ld.exe) is GNU ld... yes
> checking for BSD-compatible nm... /bin/nm -B
> checking whether ln -s works... yes
> updating cache ./config.cache
> loading cache ./config.cache within ltconfig
> checking for object suffix... o
> checking for executable suffix... .exe
> checking for gcc option to produce PIC... none
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.lo... yes
> checking if gcc supports -fno-rtti -fno-exceptions ... yes
> checking if gcc static flag -static works... -static
> checking if the linker (/bin/ld.exe) is GNU ld... yes
> checking whether the linker (/bin/ld.exe) supports shared
> libraries... yes
> checking command to parse /bin/nm -B output... ok
> checking how to hardcode library paths into programs... immediate
> checking for /bin/ld.exe option to reload object files... -r
> checking dynamic linker characteristics... Win32 ld.exe
> checking if libtool supports shared libraries... yes
> checking if package supports dlls... no
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
>
> It seams that the configure script is broken because even
> though I specify
> using no static libs, it still checks for whether libtool
> support shared
> libs and it still tries to create the shared libs. I
> realize this is not the
> fault of the compiler.
>
> Here is the snipped of output from the build process:
>
> /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall  -o
> libgdk.la -rpath
> /usr/local/lib -version-info 5:0:5 -release
> 1.2 -export-dynamic -L/usr/X11/lib -lXext -lX11 -lipc -lm
> gdk.lo gdkcc
> libtool: link: warning: undefined symbols not allowed in
> i686-pc-cygwin
> shared libraries
>
> Thanks to everyone who posted information regarding
> windows versions of gtk
> but I'm only interested in building this under cygwin using X.
>
> Kevin
>
> >-----Original Message-----
> >From: Mumit Khan [ mailto:khan@thor.xraylith.wisc.edu ]
> >Sent: Monday, September 27, 1999 12:31 PM
> >To: Kevin Wright
> >Cc: cygwin@sourceware.cygnus.com
> >Subject: Re: How to build static lib's
> >
> >
> >"Kevin Wright" <kwright@aspectdv.com> writes:
> >> Hello,
> >>
> >> I've been using cygwin for about a year and have
> >> always had some problems building static only
> >> versions of libraries such as glib and gtk+.
> >>
> >> Here's the configure options I've tried:
> >>
> >> ./configure --disable-shared --disable-shm --disable-nls
> >--no-recursion
> >>
> >> However, I still end up building the .lo & subsequent
> .la files.
> >> I tried hacking the libtool files but that was useless
> >because it gets
> >> created during the configure process. The problem is that
> >certain lib's
> >> programs fail with messages such as:
> >>
> >> gdk_imlib ERROR: Cannot load image:
> >> /usr/local/share/pixmaps/gnome-question.png
> >> All fallbacks failed.
> >>
> >> WARNING: previous dlopen of
> >> E:\usr\local\lib\libimlib-png.so wasn't correctly performed
> >
> >This problem is due to a bug in cygwin-b20, and is fixed
> in recent
> >snapshots. In most cases, it is quite harmless (unless
> you're creating
> >subprocesses using fork/exec, in which case odd things
> may happen).
> >
> >> Is there a way to make these libs truly static?
> >>
> >> I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
> >> newer snapshot of the cygwin1.dll but I am waiting for the
> >> complete installation package to be released.
> >
> >You need to ask the GTK folks about it. --disable-shared
> should have
> >created static libs only, but for some packages, that is
> not an option.
> >It's not possible to tell what the problem is from just
> what you've
> >posted, sorry.
> >
> >Regards,
> >Mumit
> >
> >
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: How to build static lib's - prob with gtk/glib

[Kevin Wright]

Mumit Khan writes:

>You need to ask the GTK folks about it. --disable-shared should have
>created static libs only, but for some packages, that is not an option.
>It's not possible to tell what the problem is from just what you've
>posted, sorry.

Here is a snippet of the output from running configure:

checking for ld used by GCC... /bin/ld.exe
checking if the linker (/bin/ld.exe) is GNU ld... yes
checking for BSD-compatible nm... /bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking for object suffix... o
checking for executable suffix... .exe
checking for gcc option to produce PIC... none
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking if the linker (/bin/ld.exe) is GNU ld... yes
checking whether the linker (/bin/ld.exe) supports shared libraries... yes
checking command to parse /bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /bin/ld.exe option to reload object files... -r
checking dynamic linker characteristics... Win32 ld.exe
checking if libtool supports shared libraries... yes
checking if package supports dlls... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes

It seams that the configure script is broken because even though I specify
using no static libs, it still checks for whether libtool support shared
libs and it still tries to create the shared libs. I realize this is not the
fault of the compiler.

Here is the snipped of output from the build process:

/bin/sh ../libtool --mode=link gcc  -g -O2 -Wall  -o libgdk.la -rpath
/usr/local/lib -version-info 5:0:5 -release
1.2 -export-dynamic -L/usr/X11/lib -lXext -lX11 -lipc -lm gdk.lo gdkcc
libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin
shared libraries

Thanks to everyone who posted information regarding windows versions of gtk
but I'm only interested in building this under cygwin using X.

Kevin

>-----Original Message-----
>From: Mumit Khan [ mailto:khan@thor.xraylith.wisc.edu ]
>Sent: Monday, September 27, 1999 12:31 PM
>To: Kevin Wright
>Cc: cygwin@sourceware.cygnus.com
>Subject: Re: How to build static lib's
>
>
>"Kevin Wright" <kwright@aspectdv.com> writes:
>> Hello,
>>
>> I've been using cygwin for about a year and have
>> always had some problems building static only
>> versions of libraries such as glib and gtk+.
>>
>> Here's the configure options I've tried:
>>
>> ./configure --disable-shared --disable-shm --disable-nls
>--no-recursion
>>
>> However, I still end up building the .lo & subsequent .la files.
>> I tried hacking the libtool files but that was useless
>because it gets
>> created during the configure process. The problem is that
>certain lib's
>> programs fail with messages such as:
>>
>> gdk_imlib ERROR: Cannot load image:
>> /usr/local/share/pixmaps/gnome-question.png
>> All fallbacks failed.
>>
>> WARNING: previous dlopen of
>> E:\usr\local\lib\libimlib-png.so wasn't correctly performed
>
>This problem is due to a bug in cygwin-b20, and is fixed in recent
>snapshots. In most cases, it is quite harmless (unless you're creating
>subprocesses using fork/exec, in which case odd things may happen).
>
>> Is there a way to make these libs truly static?
>>
>> I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a
>> newer snapshot of the cygwin1.dll but I am waiting for the
>> complete installation package to be released.
>
>You need to ask the GTK folks about it. --disable-shared should have
>created static libs only, but for some packages, that is not an option.
>It's not possible to tell what the problem is from just what you've
>posted, sorry.
>
>Regards,
>Mumit
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: How to build static lib's

[Mumit Khan]

"Kevin Wright" <kwright@aspectdv.com> writes:
> Hello,
> 
> I've been using cygwin for about a year and have 
> always had some problems building static only 
> versions of libraries such as glib and gtk+.
> 
> Here's the configure options I've tried:
> 
> ./configure --disable-shared --disable-shm --disable-nls --no-recursion
> 
> However, I still end up building the .lo & subsequent .la files. 
> I tried hacking the libtool files but that was useless because it gets
> created during the configure process. The problem is that certain lib's
> programs fail with messages such as:
> 
> gdk_imlib ERROR: Cannot load image: 
> /usr/local/share/pixmaps/gnome-question.png
> All fallbacks failed.
> 
> WARNING: previous dlopen of 
> E:\usr\local\lib\libimlib-png.so wasn't correctly performed

This problem is due to a bug in cygwin-b20, and is fixed in recent
snapshots. In most cases, it is quite harmless (unless you're creating
subprocesses using fork/exec, in which case odd things may happen).

> Is there a way to make these libs truly static? 
> 
> I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a 
> newer snapshot of the cygwin1.dll but I am waiting for the 
> complete installation package to be released.

You need to ask the GTK folks about it. --disable-shared should have
created static libs only, but for some packages, that is not an option.
It's not possible to tell what the problem is from just what you've 
posted, sorry.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

How to build static lib's

[Kevin Wright]

Hello,

I've been using cygwin for about a year and have 
always had some problems building static only 
versions of libraries such as glib and gtk+.

Here's the configure options I've tried:

./configure --disable-shared --disable-shm --disable-nls --no-recursion

However, I still end up building the .lo & subsequent .la files. 
I tried hacking the libtool files but that was useless because it gets
created during the configure process. The problem is that certain lib's
programs fail with messages such as:

gdk_imlib ERROR: Cannot load image: 
/usr/local/share/pixmaps/gnome-question.png
All fallbacks failed.

WARNING: previous dlopen of 
E:\usr\local\lib\libimlib-png.so wasn't correctly performed


Is there a way to make these libs truly static? 

I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a 
newer snapshot of the cygwin1.dll but I am waiting for the 
complete installation package to be released.

TIA,

Kevin Wright
Aspect Development
Mountain View, CA 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com