Dr. Volker Zell schrieb:
Yaakov == Yaakov Selkowitz writes:
Yaakov OK, here's the story. I built clamav after the following steps, and
Yaakov everything completed without errors, and cygcheck shows the applications
Yaakov are linked to cygclamav-1.dll. But when I try running one of
---BeginMessage---
Yaakov == Yaakov Selkowitz writes:
Yaakov OK, here's the story. I built clamav after the following steps, and
Yaakov everything completed without errors, and cygcheck shows the applications
Yaakov are linked to cygclamav-1.dll. But when I try running one of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| Make sure that the dll has executable permissions.
| chmod +x cygclamav-1.dll
(and echo from Volker Zell)
I wish it were that easy, but it's not, and I don't know why. When I
run install on it, all the executables are 755 as
Yaakov == Yaakov Selkowitz writes:
Yaakov OK, here's the story. I built clamav after the following steps, and
Yaakov everything completed without errors, and cygcheck shows the applications
Yaakov are linked to cygclamav-1.dll. But when I try running one of the
Yaakov programs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| Don't use dlltool. It's old and crotchety. Use gcc -shared (or
| libtool). For examples, see the dllhelpers
|
here:http://www.neuro.gatech.edu/users/cwilson/cygutils/dll-stuff/index.html
OK, so I got the dllhelpers-0.4.1 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
| Fribidi is not an easy candidate, they included libtool.m4 as
| acinclude.m4 in the source directory which is really bad since this
| overrides the system libtool.m4 when running configure creats libtool,
| see my patch here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wrote:
| I got the patch, and if I'm reading it right, then you did the following:
|
| 1) added -no-undefined to libfribidi_la_LDFLAGS
| 2) removed libtool.m4 from acinclude.m4
| 3) autoreconf -i -f -v
|
| Wondering if that's also the problem with
Yaakov Selkowitz wrote:
OK, here's the story. I built clamav after the following steps, and
everything completed without errors, and cygcheck shows the applications
are linked to cygclamav-1.dll. But when I try running one of the
programs that were built, I get a Windows error dialog:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wrote:
| Since you said fribidi has problems, let's move our test case to clamav.
| When I do it this way, it configures fine but make fails horribly:
|
| $ ./clamav-0.66-2.sh build
| cd /home/Yaakov/devel/testing/clamav/clamav-0.66 /bin/bash
|
Hallo Yaakov,
Am Freitag, 13. Februar 2004 um 07:22 schriebst du:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| You might want to use automake+autoconf+libtool, instead of just
| autoconf+libtool.
Do I need to --force these? See below.
I usually run `autoreconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
| Hallo Yaakov,
|
| I usually run `autoreconf --install --force --verbose` and add the
| -no-undefined flag where neccessary.
Since you said fribidi has problems, let's move our test case to clamav.
~ When I do it this way, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, after a lot of time looking at the user guide, FAQ, and Google, I
finally figured out (I think) how to get DLLs to build with the
autotools. But now I'm having troubles with building the executables
from the same package that depend on this
Yaakov Selkowitz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, after a lot of time looking at the user guide, FAQ, and Google, I
finally figured out (I think) how to get DLLs to build with the
autotools. But now I'm having troubles with building the executables
from the same package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Wilson wrote:
| You might want to use automake+autoconf+libtool, instead of just
| autoconf+libtool.
Do I need to --force these? See below.
| 2) I added an empty main function to one of the src .c files:
|
| +int main ()
| +{ return 0; }
|
|
14 matches
Mail list logo
