[BuildTools-tickets] Re: [BuildTools] #30: Problem building MSVC v8
BuildTools
coin-trac at coin-or.org
Mon Dec 11 18:32:30 EST 2006
#30: Problem building MSVC v8
---------------------+------------------------------------------------------
Reporter: hpwalton | Owner: andreasw
Type: defect | Status: assigned
Priority: minor | Component: configuration tests
Version: 0.5 | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Changes (by andreasw):
* priority: major => minor
Comment:
What is the status on this?
Looking at the original output it seems that there is a problem with the
archiver; since it reads {{{false cru}}}. This should be either 'ar' or
something else with 'lib'. The value {{{false}}} means that libtool
doesn't have that correct value; I had implemented automatic changes of
the libtool script that correct this. I think that the original problem
was caused by the fact that this fix was only done for CXX=cl, but not for
CXX=CL.EXE.
Actually, I think, CXX=cl.exe will now work, but CXX=CL[.EXE] might still
fail.
I don't think this has anything to do with the "exit()" problem of
autoconf with the CL compiler. In the coin.m4 tests, I worked around this
issue by giving a first argument to AC_TRY_LINK, as in
{{{
AC_TRY_LINK([void $4();],[$4()],
[AC_MSG_RESULT(yes)],
[AC_MSG_RESULT(no)
AC_MSG_ERROR([Cannot find symbol $4 with
$2])])
}}}
This way, no automatic pretext is added to the C program (which would
contain that {{{exit}}} declaration), but instead the program text only
declares the function that we want to find.
This seems to overcome the problem for the CL compiler. Nevertheless, it
would be nice to switch to newer autoconf, so that this workaround is no
longer required.
--
Ticket URL: <https://projects.coin-or.org/BuildTools/ticket/30#comment:4>
BuildTools <http://projects.coin-or.org/BuildTools>
Tools for configuring and compiling COIN-OR codes
More information about the BuildTools-tickets
mailing list