-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 6 Dec 2004 20:15:09 -0600 (CST)
C. Bensend [EMAIL PROTECTED] wrote:
There are some environment variable that you can set to specify
arguments to gcc, such as additional include paths and additional
library paths. Something like:
Could someone offer me some assistance so I can find out where this is
breaking for me?
I use the unofficial port, and it works great.
I had to do some pthread and lib fiddling to get it to build natively
on my 3.6 machines.
Benny
--
... i want to be a farting burping maniac.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 6 Dec 2004 16:59:37 -0600 (CST)
C. Bensend [EMAIL PROTECTED] wrote:
I use the unofficial port, and it works great.
I had to do some pthread and lib fiddling to get it to build natively
on
ed wanted us to know:
Can you state what you did in both cases, I had to modify the headers to
get past curl include.. but that didn't get me a build.
There are some environment variable that you can set to specify
arguments to gcc, such as additional include paths and additional
library paths.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am having some problems building Clamav-0.80 on my OpenBSD system. I
would like to point out that I have not had this same trouble with any
of my Debian boxen.
My make output is:
- --[ snip ]--
# make
/bin/sh ../libtool --mode=link gcc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 5 Dec 2004 22:12:12 +
ed [EMAIL PROTECTED] wrote:
Which compiles without complaints but has no effect on the overall
build process.
Could someone offer me some assistance so I can find out where this is
breaking for me?
Oh, P.S.
I
