On 9 Jul 2000, Alexandre Oliva wrote:
> On Jul 9, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> > I am trying to understand how libtool configures itself and
> > I just can not figure out why ltconfig unsets CC.
>
> This may happen in the second step, when it's looking for a C++ or GCJ
> compiler, in case your configure.in mentions CXX or GCJ.
If it is looking for g++ or gcj, then why does it end up with cc?
I am not using anything except CC. Here are the two lang
related macros I call and the later call to libtool macros.
dnl Tell the system that we are going to use the C language
AC_LANG_C
dnl Have the system search for and test out the C compiler
AC_PROG_CC
...
dnl Do libtool related init macros
AC_LIBTOOL_WIN32_DLL
AC_PROG_LIBTOOL
The thing that is really strange is that everything seems to
get detected correctly during the first run, but the
results of the second run are what gets saved. This
is a big problem for me because I want to build
a dll. The ability to build a cross dll is detected
during the first round of libtool checks but
the results of the second round of test (using cc)
are what actually get used.
Mo DeJong
Red Hat Inc
