From: Andrea Venturoli on 6 Apr 2010 02:14 On 04/06/10 00:26, Thierry Thomas wrote: > Le Mar 23 mar 10 à 22:37:24 +0100, Andrea Venturoli<ml(a)netfence.it> > écrivait : >> Just to let you know this used to work on 6.3, though I cannot test it >> anymore now. >> >> I can compile it without any problem on 7.2/i386, though I remove >> "USE_FORTRAN=yes". >> >> The latter is to avoid compilation with gcc4.4, which will lead to >> incompatibilities with other libraries (such as boost) I use on a >> project of mine. > > It should be fixed now. > > Actually, it used to work untill gcc-4.4.4.20100216. Gcc-44 is needed > because f77 has been removed from the base. Are you sure OpenCASCADE requires f77? I looked into the source and didn't find any file like "*.f" or "*.for", although of course they might have other extension or be generated during the build process. Also I can confirm it compiles with the base system gcc, although I don't remember if I had gcc44 installed at the time, so it might also be it picked f77 from gcc44 anyway. The whole point of the above is that, due to gcc44's libstdc++ recently becoming incompatible with older versions, if you mix different g++ versions in the same project, you'll get "Undefined symbol" errors when starting your executable. In my case, I'm linking (amongst others) against Boost and OpenCASCADE, so I need them to use the same compiler (and use that myself). Again, this is not a problem with OpenCASCADE only, but potentially affects any C++ library which is build with gcc44. bye & Thanks av. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Thierry Thomas on 10 Apr 2010 10:20 Le Mar 6 avr 10 � 8:14:57 +0200, Andrea Venturoli <ml(a)netfence.it> �crivait�: > Are you sure OpenCASCADE requires f77? > I looked into the source and didn't find any file like "*.f" or "*.for", > although of course they might have other extension or be generated > during the build process. > Also I can confirm it compiles with the base system gcc, although I > don't remember if I had gcc44 installed at the time, so it might also be > it picked f77 from gcc44 anyway. You're right: it builds succesfully in a tinderbox without USE_FORTRAN, which is just searched by configure. Should be some remaining of an older version... > The whole point of the above is that, due to gcc44's libstdc++ recently > becoming incompatible with older versions, if you mix different g++ > versions in the same project, you'll get "Undefined symbol" errors when > starting your executable. > > In my case, I'm linking (amongst others) against Boost and OpenCASCADE, > so I need them to use the same compiler (and use that myself). > > > > Again, this is not a problem with OpenCASCADE only, but potentially > affects any C++ library which is build with gcc44. True: that's why I think that libtool should'nt force $CC and $LD. Best regards, -- Th. Thomas. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
|
Pages: 1 Prev: Assistance needed to update sysutils/di Next: FreeBSD Port: php5-zip-5.2.12_2 |