ood idea.
If anyone of the libtool maintainers want to give it a look-over:
cvs -d :pserver:[EMAIL PROTECTED]:/export/cvsroot login
CVS password:(use "cvs")
cvs -d :pserver:[EMAIL PROTECTED]:/export/cvsroot checkout conf-macros
more conf-macros/check_mathlib.m4
Regards,
Morten Eriksen
Robert Boehne <[EMAIL PROTECTED]> writes:
> I have a large library that IRIX CC w/ multi-language libtool is not
> happy creating. It seems that the link line is too much for CC to
> handle.
Sounds familiar.. :^(
> Is the only solution to split this library into convience
> libs, then link tho
4:48:12
@@ -1,3 +1,8 @@
+2000-10-11 Morten Eriksen <[EMAIL PROTECTED]>
+
+ * libtool.m4 (_LT_AC_LTCONFIG_HACK): Fix invalid backslash
+ quoting.
+
2000-10-02 Gary V. Vaughan <[EMAIL PROTECTED]>
From Bruce Korb <[
e: /home/cvs/libtool/ChangeLog,v
retrieving revision 1.809
diff -u -r1.809 ChangeLog
--- ChangeLog 2000/10/02 01:18:16 1.809
+++ ChangeLog 2000/10/11 14:48:12
@@ -1,3 +1,8 @@
+2000-10-12 Morten Eriksen <[EMAIL PROTECTED]>
+
+ * libtool.m4 (_LT_AC_LTCONFIG_HACK): Fix invalid backslash
18:16 1.809
+++ ChangeLog 2000/10/12 16:43:57
@@ -1,3 +1,8 @@
+2000-10-12 Morten Eriksen <[EMAIL PROTECTED]>
+
+ * ltdl.m4 (AC_LIB_LTDL, AC_LTDL_SYMBOL_USCORE): Break a circular
+ dependency between AC_LTDL_SYMBOL_USCORE and AC_LTDL_DLSYM_USCORE.
+
2000-10-02 Gary V. Vaug
ose the attached
patch as a workaround for the IRIX ld problem. Changelog entry as
follows (I'm not sure in which format you want patches against release
tarballs, I guess you'd perhaps want to ignore the changes to the
autogenerated files):
2000-10-26 Morten Eriksen <[EMAIL PROTECTED
Marc van Woerkom <[EMAIL PROTECTED]> writes:
> [...] what happens if one really wants to use the Microsoft C/C++
> compiler?
One solution we've found to work well is to wrap the cl.exe compiler
(and the linker) within a shell script that converts "UNIX-style"
compiler arguments into what MSVC++
