On Nov 2, 2007, at 11:00 PM, Roumen Petrov wrote:
Usually /etc/ld.so.conf contain /usr/local/lib.
Dunno why this path is not set on you host.
Benoit SIGOURE wrote:
Hi list,
On GNU/Linux Debian with GCC 4.1 / Debian's libtool 1.5.22-4
(1.1220.2.365 2005/12/18 22:14:06), I have Boost installed
Usually /etc/ld.so.conf contain /usr/local/lib.
Dunno why this path is not set on you host.
Benoit SIGOURE wrote:
Hi list,
On GNU/Linux Debian with GCC 4.1 / Debian's libtool 1.5.22-4
(1.1220.2.365 2005/12/18 22:14:06), I have Boost installed under
/usr/local/lib (pre-built binaries:
http://w
Jason Curl wrote:
Roumen Petrov wrote:
[SNIP]
Well, I think I've figured it out today (albeit I'm testing on a
different machine, similar software though) and there are two
executables. One in the build directory and one in .libs. e.g.
src/
.libs/
libmofo-1.dll
test/
libtest.exe <-
Hi list,
On GNU/Linux Debian with GCC 4.1 / Debian's libtool 1.5.22-4
(1.1220.2.365 2005/12/18 22:14:06), I have Boost installed under /usr/
local/lib (pre-built binaries: http://www.tsunanet.net/~tsuna/
boost_1_34_1-i486-linux-gcc41.tar.gz) and when I link with `-
lboost_thread-gcc41-mt-1_34
Jason Curl wrote:
> For Posix systems I agree (and I haven't had to care until now). It's an
> unnecessary burden for w32api however, especially for users that don't have
> any kind of sane build environment. I guess I'm saying I don't know how to
> package the result so that someone on w32 can
The command:
./configure --build=hppa64-hp-hpux11.11 ... CFLAGS="+DA2.0W"
worked, with the proviso that I had to add the
CFLAGS= for the configure script (its tests would bomb).
As far as --host vs --build, they both work. --host
just whines about whether it is a cross compile or
not.
Question i
