GNU bug report logs - #21445
LIBS not passed for creating a wrapper for cygwin/mingw

Previous Next

To reply to this bug, email your comments to 21445 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Damian Bogel <kele <at> google.com>
To: bug-libtool <at> gnu.org
Subject: LIBS not passed for creating a wrapper for cygwin/mingw
Date: Wed, 9 Sep 2015 10:35:45 -0400

[Message part 1 (text/plain, inline)]

Hi,

It seems that whenever a wrapper executable is built for cygwin/mingw,
libraries passed to libtool are ignored.

In my libtool there's a command:

# The wrapper executable is built using the $host compiler,
# because it contains $host paths and files. If cross-
# compiling, it, like the target executable, must be
# executed on the $host or under an emulation environment.
$opt_dry_run || {
  $LTCC $LTCFLAGS -o $cwrapper $cwrappersource
$STRIP $cwrapper
}

and clearly there's something missing after cwrappersource. In my project,
I'm currently just using sed to patch the libtool, but a variable like
LTLIBS would be useful.


-- 
Best,
Damian

[Message part 2 (text/html, inline)]

Message #8 received at 21445 <at> debbugs.gnu.org (full text, mbox):

From: Peter Rosin <peda <at> lysator.liu.se>
To: Damian Bogel <kele <at> google.com>, 21445 <at> debbugs.gnu.org
Subject: Re: bug#21445: LIBS not passed for creating a wrapper for cygwin/mingw
Date: Wed, 9 Sep 2015 22:48:04 +0200

On 2015-09-09 16:35, Damian Bogel wrote:
> Hi,
> 
> It seems that whenever a wrapper executable is built for cygwin/mingw, libraries passed to libtool are ignored.
> 
> In my libtool there's a command:
> 
> # The wrapper executable is built using the $host compiler,
> # because it contains $host paths and files. If cross-
> # compiling, it, like the target executable, must be
> # executed on the $host or under an emulation environment.
> $opt_dry_run || {
>   $LTCC $LTCFLAGS -o $cwrapper $cwrappersource
> $STRIP $cwrapper
> }
> 
> and clearly there's something missing after cwrappersource. In my project, I'm currently just using sed to patch the libtool, but a variable like LTLIBS would be useful.

Hi!

I don't understand why you would need any extra libraries to build the
cwrapper? It is not supposed to need any user-provided libraries, it's
a very simple C program that sets up the environment for the real
program and the execs that, no fancy libs needed for that. What is it
that you think should be added with $LTLIBS?

I wonder what the underlying problem is that you are apparently trying
to work around?

Cheers,
Peter

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.