Peter,
Actually I think the problem with lam 7.1.1 originates more from the
massive changes they have made to its aclocal.m4 file. The libtool that
is generated from configure during the build shows the following diffs
from that generated by lam 7.0.6...
# How to create reloadable object files.
reload_flag=" -r"
-reload_cmds="\$LD\$reload_flag -o \$output\$reload_objs"
+reload_cmds="\$CC -nostdlib \${wl}-r -o \$output\$reload_objs"
# Whether dlopen is supported.
-dlopen_support=unknown
+dlopen_support=yes
# Whether dlopen of programs is supported.
-dlopen_self=unknown
+dlopen_self=yes
# Whether dlopen of statically linked programs is supported.
-dlopen_self_static=unknown
+dlopen_self_static=yes
# Compiler flag to prevent dynamic linking.
link_static_flag="-static"
@@ -171,7 +171,7 @@
export_dynamic_flag_spec=""
# Compiler flag to generate shared objects directly from archives.
-whole_archive_flag_spec="-all_load \$convenience"
+whole_archive_flag_spec=""
which I believe explains why MACOSX_DEPLOYMENT_TARGET has to be forced
now. I'll see if I can puzzle out how to regress these changes in
7.1.1 so that ld is used for linking once again and dlopen is not used.
Jack
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
