> > > On Mar 22, 2006, at 12:00 , Dennis Peterson wrote: > > > Dale Walsh wrote: > >> On Mar 21, 2006, at 21:32 , Dennis Peterson wrote: > >>> Dale Walsh wrote: > >>>> On Mar 20, 2006, at 09:03 , Dennis Peterson wrote: > >>> > >>>>> > >>>>> Torbjorn Granlund, the author of gmp, is aware of the problem > >>>>> and has stated he's not interested in a fix. > >>>>> > >>>>> If you google the error "tmp-dive_1.s:98..." you will see core > >>>>> duo owners are having the same problem. > >>>> Yes, I ran into this as well, but it does build if you disable > >>>> shared. > >>>> If you want to generate a proper fix, I'm sure that it would be > >>>> appreciated but one thing to note, I've been unable to build it > >>>> as a dual architecture and this would be good to achieve as well. > >>> > >>> Building it without shared was a slam-dunk but not especially > >>> helpful. This did the trick: > >>> > >>> configure --host=none-apple-darwin > >> Building for generic x86, reduces functionality but does provide a > >> working solution, now you just need to build using some additional > >> flags to get it built right. > > > > It wasn't my requirement to build it for general release - we're > > committed to Mac on Intel only going forward and so this works fine > > for our datacenters. > > What you have generated is marginal at best, doesn't include key > functions required for proper digital signature support but you can > choose to settle for what you have generated in the hopes that you > don't experience any problems. > > You have a partial functioning GMP/MP/MPFR library which makes the > digital signature support unreliable, the configure you used doesn't > enable specific features and functions required for full digital > support so if you're really committed to the Intel Mac and providing > proper software support, I'd look into correcting this. >
The configure string above was a simple test to ensure it built with shared libraries. It isn't likel the full production string for the final build. It does pass all the internal tests, though, and results in a basic functional clamAV suite. > Myself, I'm committed to finding a solution for Macs in general, I am > not narrow minded or biased and only support intel or ppc, I'm > ecstatic if my solutions/improvements work for other platforms but my > goal is ultimately to provide a better build for Macs. I think it is not being narrow minded to build to the need. We have no plans for using PPC macs in this role so there is no need to spend $$ on them. The object is a higly portable mail appliance to be dropped into datacenters of companies we purchase. Cost, supportability, installation ease, and capability are the principal needs. They're working rather well. And it means I can continue to use ClamAV. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
