[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: libtool--devo--1.0--patch-214
From: |
Peter O'Gorman |
Subject: |
Re: FYI: libtool--devo--1.0--patch-214 |
Date: |
Fri, 01 Oct 2004 13:31:14 +0900 |
User-agent: |
Mozilla Thunderbird 0.7.3 (Macintosh/20040803) |
Gary V. Vaughan wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Applied to HEAD.
This is just a bit of a hack really, but I want to make sure that
I get to release an alpha this weekend, even if I don't have time
to rewrite the hardcode tests in libtool.m4 by then.
This is bogus. Please revert and check what is wrong locally on your system.
Did a clean checkout and bootstrap, a VPATH build and make check.
demo-hardcode.test: === Running demo-hardcode.test
demo-hardcode.test: === Running `make hardcode' in demo
You may ignore any linking errors from the following command:
gcc -g -O2 -o hc-direct main.o ./.libs/libhello.dylib || echo
unsupported > hc-direct
echo unsupported > hc-libflag
You may ignore any linking errors from the following command:
DYLD_LIBRARY_PATH=./.libs gcc -g -O2 -o hc-libpath main.o -lhello ||
echo unsupported > hc-libpath
ld: can't locate file for: -lhello
gcc -g -O2 -o hc-minusL main.o -L./.libs -lhello || echo unsupported >
hc-minusL
demo-hardcode.test: === Finding libtool.m4's guesses at hardcoding values
= Searching for hardcoded library directories in each program
.libs was not hardcoded in `hc-direct', as libtool expected
`hc-libflag' was not linked properly, as libtool expected
`hc-libpath' was not linked properly, which fooled libtool
.libs was not hardcoded in `hc-minusL', as libtool expected
FAIL: demo-hardcode.test
Peter
--
Peter O'Gorman - http://www.pogma.com
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: FYI: libtool--devo--1.0--patch-214,
Peter O'Gorman <=