Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -multi_module problem



Thanks to you, Martin, Peter, and Eric for the helpful comments.

See below...

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 pulled the source tarball for Singular and the description 'an "autoconf" package' can only be loosely applied. It uses a few autoconf macros, but it certainly does not follow autoconf practice or recommendations and does not use automake or GNU libtool.

I have not spent long on it but the only Darwin stuff seems to be in Singular/configure.in. The other packages in the bundle seem to inherit that configuration. The lines read:

I can't tell whether the kernel config stuff inherits or just duplicates.


This seems to me to be a mis-configuration problem rather than just a multi-module issue. Never mind the weird system names, just look at some of the flags:
[snip]
So yes, I think this is where you should be hacking, but I would want to understand the complex build system of this package rather more before declaring that one or other hack was reasonable.

I've followed your lead, and am attempting to understand what's going on; it's an uphill slog. I think you are correct in your assessments.


Martin has suggested (often :-}) that building without the dynamic kernel is the right approach; I will try this as well, but since I don't understand the the issues, I'm not entirely happy with the choice. I've asked the Singular folk for comments, and I'll see where this leads.

Thanks again.

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------



_______________________________________________
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

This email sent to email@hidden
References: 
 >Re: -multi_module problem (From: Bill Northcott <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.