On Aug 28, 2006, at 10:40 PM, Justin C. Walker wrote:
On Aug 28, 2006, at 02:10 , Bill Northcott wrote:
Sorry to be dense, but why is this a 'multi-module' problem? Ld
is spitting the dummy because of common symbols in the objects
being linked. I thought the normal practice on Darwin/MacOS X was
to use the -fno-common option on all compiles for code to be used
in shared objects. If this had been done, it might even have linked.
So far, your comments seem valid. The problem is (as you may have
noticed) that the Singular config stuff is just a bit, oh, opaque.
The configure flummery is hard to take apart, but I think that, if
I can figure out how to modify the flags for a specific set of
files, this will work. The devil's in the details, and the details
are devilish.
I don't know a thing about Singular, but I grabbed the Singular 3.0.2
source tonight and tried to beat it into building. Here's how I got
it to build successfully:
kernel/configure.in:
Singular/configure.in:
For ppcMac-darwin and i386Mac-darwin, add -fno-common to SFLAGS
factory/configure.in:
kernel/configure.in:
modules/modgen/Makefile.in:
MP/configure.in:
Singular/configure.in:
Add -fno-common after each occurrence of -fomit-frame-pointer
Run autoconf for each of the configure.in files above.
Singular/ipconv.cc:
Add #include "ring.h"
./configure --enable-Plural
sudo make install
These changes aren't portable -- -fno-common should only be used on
Mac OS X, so the second set of configure.in changes should be
conditionalized for Mac OS X -- but they seem to build something.
Whether it works is another matter altogether....
-Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Unix-porting mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/unix-porting/email@hidden
