On Dec 14, 2005, at 5:57 PM, Martin Costabel wrote:
--- Martin Costabel <[EMAIL PROTECTED]> wrote:
We already have examples of packages that depend on
external stuff like specific commercial fortran compilers or parts
of the developer tools that are not installed by default, and which
manage their dependencies on these external components "by hand",
not via virtual packages.
Okay, this approach works for me and I've got a "system-ada" that's
working in my local branch.
But one of the subtleties of how GNAT-OSX works has stymied me.
GNAT-OSX replaces Apple's GCC with it's own GCC that is Ada-aware, but
that can't handle certain Apple things like dylibs. So one needs to
switch back and forth. (For example, fink's db42 won't build with
GNAT's gcc, and that stumps me every time I build a system till I
google it.)
So any package that depends on the GNAT compiler should check, at
*compile* time, that the GNAT compiler is currently selected via
gcc_select.
Is there a way to enforce that without hardcoding it into every package
that depends on "system-ada"?
Assuming there isn't, what's the best way to do the hardcoding? I could
do it by looking at gcc_select's output, or by "gcc -v", or I could
have "system-ada" install a script that could be run by every child
package. If the last, where do I put the script? I'm sure there are
other methods, as well.
Any thoughts would be appreciated.
Best,
Ben
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel