-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
> Uh, no, not sure what you're referring to; got a reference?
http://cygwin.com/ml/cygwin/2008-04/msg00378.html
> Another thought occurs: does that work for cross-compilation?
You can't use /usr/bin/libtool for cross-compilati
Yaakov (Cygwin Ports) wrote on 13 October 2008 04:52:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dave Korn wrote:
>> Yep, you've got it. The problem is that OBJDUMP is not set to
>> anything, and so the regexes all fail pretty hard. And the reason that
>> OBJDUMP is not set to an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
> Yep, you've got it. The problem is that OBJDUMP is not set to anything, and
> so the regexes all fail pretty hard. And the reason that OBJDUMP is not set
> to anything is due to this very common idiom in GNU projects that exerc
Charles Wilson wrote on 15 April 2008 00:07:
> Yaakov (Cygwin Ports) wrote:
>> Charles Wilson wrote:
>>> Changes sine libtool2.2-2.2.2-1
>>> =
>>> o changed base package name from 'libtool2.2' to 'libtool'
>>> o Added patches from Yaakov Selkowitz
>>> http://cygwi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
| This package had AM_GNU_GETTEXT in configure.ac without any arguments
| nor AM_GNU_GETTEXT_VERSION. autoreconf decided "not using Gettext"[1]
| and didn't install config.rpath[2]. But AC_LIB_RPATH (from the included
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Looks like a gettext bug to me. Might be fixed in 0.16+, but please
| report upstream.
I'll admit I'm not that fluent in gettext internals. Obviously both
macros are supposed to be present; is having only one just old
behav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Well, that's not enough information at all. The c++ tests all pass, so
| I'm going to need a testcase or at least the actual project you're
| building that gives this error.
.cygport attached, as well as the diff between the
Yaakov (Cygwin Ports) wrote:
Here's yet another interesting case with libtool-2.2:
"interesting", as in "may you live in interesting times"?
/bin/sh ../../libtool --tag=CXX --mode=link g++ -O2 -pipe-o
libfoo-1.2.la -rpath /usr/lib -no-undefined sources.lo
libtool: link: rm -fr .libs/lib
Yaakov (Cygwin Ports) wrote:
* libtool should catch if the lt-foo.c compile fails;
Yes. I haven't tracked this one down yet.
I think I have also found a separate case of breakage when the CXX tag
is enabled, in which case LTCC is mysteriously undefined. The results:
./libtool: line 7737: -O
Charles Wilson wrote:
Yaakov (Cygwin Ports) wrote:
./.libs/lt-foo.c:263: warning: string length `4368' is greater than the
length `4095' ISO C99 compilers are required to support
This one can be fixed by splitting the string into two pieces. I'm
working on a patch for that.
./.libs/lt-foo.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
Here's yet another interesting case with libtool-2.2:
/bin/sh ../../libtool --tag=CXX --mode=link g++ -O2 -pipe-o
libfoo-1.2.la -rpath /usr/lib -no-undefined sources.lo
libtool: link: rm -fr .libs/libfoo-1.2.dll.a .libs/libfoo-1.2.la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| What's puzzling is there is no *error* message from the compiler -- just
| warnings.
|
|> strip: './foo.exe': No such file
|
| But obviously something went wrong.
|
| I wonder of the string length warning is from the pre-proc
Yaakov (Cygwin Ports) wrote:
I'm not sure what's triggering this, but *sometimes* I'm getting more
than that:
./.libs/lt-foo.c:263: warning: string length `4368' is greater than the
length `4095' ISO C99 compilers are required to support
./.libs/lt-foo.c: In function `main':
./.libs/lt-foo.c:288
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| That was fixed in libtool CVS after 2.2.2 was released:
| http://lists.gnu.org/archive/html/libtool-patches/2008-04/msg00019.html
| but this release is 'stock' libtool-2.2.2 with only your patches.
I'm not sure what's trigge
Charles Wilson wrote:
> way to get ld to print its search path (which is why Brian grep'ed the
> binary) like gcc's -print-search-dirs. So libtool has no mechanism to
I grepped the default linker script which is a plain text file. This
can be done programmatically by adding -Wl,-verbose to a tes
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
| Changes sine libtool2.2-2.2.2-1
| =
I'm also seeing these warnings (where 'foo' is the executable being
linked against a yet-uninstalled libtool library):
./.libs/lt-foo.c: In function `main':
./.libs/lt-foo.c:
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
| I think that libtool hasn't been told that LDFLAGS should include
| -L/usr/lib/w32api. I think this is something that should be passed on
| the invocation line in your makefile -- maybe AM_LDFLAGS needs to be set?
As I'm sure you're aware, /u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Changes sine libtool2.2-2.2.2-1
| =
I'm also seeing these warnings (where 'foo' is the executable being
linked against a yet-uninstalled libtool library):
./.libs/lt-foo.c: In function `main'
Charles Wilson wrote:
> I think that libtool hasn't been told that LDFLAGS should include
> -L/usr/lib/w32api. I think this is something that should be passed on
> the invocation line in your makefile -- maybe AM_LDFLAGS needs to be set?
But the linker searches this location by default:
$ grep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| I think that libtool hasn't been told that LDFLAGS should include
| -L/usr/lib/w32api. I think this is something that should be passed on
| the invocation line in your makefile -- maybe AM_LDFLAGS needs to be set?
As I'm su
Yaakov (Cygwin Ports) wrote:
Charles Wilson wrote:
| Changes sine libtool2.2-2.2.2-1
| =
| o changed base package name from 'libtool2.2' to 'libtool'
| o Added patches from Yaakov Selkowitz
| http://cygwin.com/ml/cygwin/2008-04/msg00378.html
Do you know why I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Changes sine libtool2.2-2.2.2-1
| =
| o changed base package name from 'libtool2.2' to 'libtool'
| o Added patches from Yaakov Selkowitz
| http://cygwin.com/ml/cygwin/2008-04/msg00378.html
D
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This update represents a name change from the previous 'libtool2.2'
package, to the new 'libtool' package (the embedded version number '2.2'
has been
23 matches
Mail list logo
