On Friday, December 13, 2002, at 05:57 PM, Ben Hines wrote:
Yes, I understand that, however sablotron was using gcc in a place where g++ was needed instead. This caused the build to fail. I'm about the farthest thing from an autoconf expert so I just fiddled with the links and then put them back after. Obviously I don't recommend this ;-) to anyone else, but ... As I said I'm sure there's a better way to fix it, but I don't know what it is. When sablotron is updated I may make a package out of it since I understand that I can use the .info file to change the compiler. RIght now I have it working and I'm lazy.On Friday, December 13, 2002, at 01:05 PM, S Woodside wrote:Yeah :-)Um, what? Don't mess with those links by hand. You need to compile with "c++" or "g++" rather than gcc.
g++ did the trick. I relinked /usr/bin/gcc to g++3 and rebuild sablot and sabcmd finally works! (I'm sure there's a better way to do >> that..)
simon
---
www.simonwoodside.com
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
