Virus Alert
Este mensaje ha sido generado AUTOMATICAMENTE por el Sistema de deteccion de Virus de correo de la Universidad de Sevilla, el cual ha encontrado el virus WORM_SOBIG.F en el fichero: your_details.pif que ha enviado a [EMAIL PROTECTED], debido bien a que su sistema esta infectado por un virus que usa su libreta de direcciones para estos envios indiscriminados o bien a que el propio fichero que esta enviando esta infectado. Accion: rejected. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Inflex scan report [09052131432611]
Administrator Email Reply Address: avadmin Email sent to: [EMAIL PROTECTED] Inflex ID: 09052131432611 Report Details --- AntiVirus Results... SWEEP virus detection utility Version 3.71, July 2003 [Digital Unix/Alpha] Includes detection for 82974 viruses, trojans and worms Copyright (c) 1989,2003 Sophos Plc, www.sophos.com System time 21:31:02, System date 05 September 2003 Command line qualifiers are: -archive -all -rec -sc IDE directory is: /usr/local/sav Using IDE file webber-a.ide Using IDE file gruel-a.ide Using IDE file coconuta.ide Using IDE file cmjspy-b.ide Using IDE file golon-a.ide Using IDE file ataka-e.ide Using IDE file migmaf-a.ide Using IDE file mofei-b.ide Using IDE file viewmova.ide Using IDE file israza.ide Using IDE file graps-a.ide Using IDE file larx-fam.ide Using IDE file zwmvc-b.ide Using IDE file adenu-a.ide Using IDE file mylife-m.ide Using IDE file mumu.ide Using IDE file revas-a.ide Using IDE file klexe-a.ide Using IDE file sage-a.ide Using IDE file sluter-a.ide Using IDE file colevo-a.ide Using IDE file slanpera.ide Using IDE file cailonta.ide Using IDE file sandesa.ide Using IDE file raleka.ide Using IDE file sobig-e.ide Using IDE file frtnghte.ide Using IDE file relax-c.ide Using IDE file pcghosta.ide Using IDE file haclineb.ide Using IDE file nofer-c.ide Using IDE file magold-d.ide Using IDE file redist-c.ide Using IDE file nofer-b.ide Using IDE file mumu-b.ide Using IDE file sobig-d.ide Using IDE file frtnghtf.ide Using IDE file mystri-a.ide Using IDE file crock-a.ide Using IDE file suhd-a.ide Using IDE file nofer-a.ide Using IDE file anaco-d.ide File panjang.ide is older than 90 days Using IDE file gruel-c.ide Using IDE file gruel-b.ide Using IDE file mapson-c.ide Using IDE file gruel-d.ide Using IDE file gruel-e.ide Using IDE file dwnld-di.ide Using IDE file gruelfam.ide Using IDE file mofei-c.ide Using IDE file jantic-b.ide Using IDE file frtnghth.ide Using IDE file qqpass-a.ide Using IDE file babybr-a.ide Using IDE file mimail-a.ide Using IDE file randonr.ide Using IDE file cidu-a.ide Using IDE file gruel-m.ide Using IDE file boohoo-a.ide Using IDE file maila.ide Using IDE file autort-a.ide Using IDE file lovgatel.ide Using IDE file sview-a.ide Using IDE file randex-d.ide Using IDE file blastera.ide Using IDE file rpcsdb-a.ide Using IDE file blasterb.ide Using IDE file donkc.ide Using IDE file graybird.ide Using IDE file nachi-a.ide Using IDE file blasterd.ide Using IDE file sobigf.ide Using IDE file dumaru-a.ide Using IDE file bdoorrq.ide Using IDE file pandem-b.ide Using IDE file agobot-q.ide Using IDE file tzet-a.ide Using IDE file blastere.ide Using IDE file nugosh-a.ide Using IDE file yaha-t.ide Using IDE file lovgatep.ide Using IDE file blasterf.ide Using IDE file w32cailb.ide Using IDE file quatersa.ide Using IDE file phone-b.ide Using IDE file jsurf-a.ide Using IDE file sbf-dam.ide Using IDE file exedropb.ide Using IDE file neroma.ide Quick Sweeping 00:00 _headers_ 00:00 textfile0 00:00 textfile1 00:00 your_details.pif >>> Virus 'W32/Sobig-F' found in file >>> /usr/local/inflex/tmp/inf_09052131432611/unpacked/your_details.pif 00:00 textfile2 5 files swept in 0 seconds. 1 virus was discovered. 1 file out of 5 was infected. Please send infected samples to Sophos for analysis. For advice consult www.sophos.com, email [EMAIL PROTECTED] or telephone +44 1235 559933 End of Sweep. File NAME/TYPE Scan Results 09052131432611 from:[EMAIL PROTECTED] to: [EMAIL PROTECTED] scanning off. Name scanning off. Text scanning off. END OF MESSAGE. End. . ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: linking dynamic lib with static one.
J. Ali Harlow wrote: > On 2003.09.04 09:45 Alexander Kogan wrote: >> Hi! >> >> I build DLL with mingw/automake/autoconf/libtool. But this dll depends >> on external static lib, and libtool doesn't produce dll, but say that >> it will be built when I compile program with this library. But I use >> this dll in native windows app, coimpiled with VC without libtool... >> What should I do to link static lib into dll? > > I have the same problem (with Gtk+ and libuuid.a). I'm afraid I resorted > to cheating, by disabling the libtool checks as follows: > > mv libtool libtool.orig > sed -e 's/^\(deplibs_check_method\)=.*$/\1=\ > "file_magic ^x86 archive|^x86 DLL" \ > # [ALI] Treat static libs as shared/' < libtool.orig > libtool > chmod 755 libtool An alternate way to cheat is: lt_cv_deplibs_check_method='file_magic ^x86 archive|^x86 DLL' \ lt_cv_file_magic_cmd=win32_libid ./configure > This works in my case because it doesn't matter if libuuid is included > twice in the final application (once in the Gtk+ dll and once in the > main application). This may not be true of all libraries and could > cause some seriously odd behaviour under the right conditions but may > be a solution if you can assertain that the static library won't mind > having more than one instance. Yes, this is awkward - so much so, that I patch the file_magic regexp as a matter of routine. Possibility: Libtool could contain a list of libraries known to be suitable for this form of linking. Opinions? Max. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Detecting availability of a shared libray
Hi all, I have a package that produces a shared/static library via libtool. However this package needs to make use of some external library for data import/export. Since my library has both a shared and a static version this external library also needs to have at least a shared version available. If this is the case then linking my library with libtool and the appropriate -L and -l flags will work nicely. However, if only a static version of the external library is available then building a shared version of my library will fail (except perhaps on systems that do not need specific PIC flags when creating shared library object files). My problem is that if I use AC_CHECK_LIB to check for the external library, then the check that is being performed is to see whether the external library can be linked into a program. Now this works of course fine if the external library is only available as a static version. So my question now is, does anybody know whether there is a way to explicitly test for the availability of the shared version of the external library? Regards, Sander Niemeijer ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: linking dynamic lib with static one.
Hi! > I have the same problem (with Gtk+ and libuuid.a). I'm afraid I resorted > to cheating, by disabling the libtool checks as follows: > > mv libtool libtool.orig > sed -e 's/^\(deplibs_check_method\)=.*$/\1=\ > "file_magic ^x86 archive|^x86 DLL" \ > # [ALI] Treat static libs as shared/' < libtool.orig > libtool > chmod 755 libtool Ok, thank you. I'll try it. > Ali. -- Alexander Kogan Institute of Applied Physics Russian Academy of Sciences ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
Re: linking dynamic lib with static one.
On 2003.09.04 09:45 Alexander Kogan wrote: Hi! I build DLL with mingw/automake/autoconf/libtool. But this dll depends on external static lib, and libtool doesn't produce dll, but say that it will be built when I compile program with this library. But I use this dll in native windows app, coimpiled with VC without libtool... What should I do to link static lib into dll? I have the same problem (with Gtk+ and libuuid.a). I'm afraid I resorted to cheating, by disabling the libtool checks as follows: mv libtool libtool.orig sed -e 's/^\(deplibs_check_method\)=.*$/\1=\ "file_magic ^x86 archive|^x86 DLL" \ # [ALI] Treat static libs as shared/' < libtool.orig > libtool chmod 755 libtool This works in my case because it doesn't matter if libuuid is included twice in the final application (once in the Gtk+ dll and once in the main application). This may not be true of all libraries and could cause some seriously odd behaviour under the right conditions but may be a solution if you can assertain that the static library won't mind having more than one instance. Cheers, Ali. ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
