[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #TIC-838672]: ldm-6.11.2 configure error under Solaris 10 x86

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #TIC-838672]: ldm-6.11.2 configure error under Solaris 10 x86
  • Date: Mon, 04 Feb 2013 12:52:05 -0700
Tom,

> When attempting to run configure for LDM 6.11.2 on unidata2-new in
> the 'antldm' account, I get the following error:
> 
> /opt/antldm/ldm-6.11.2/src% ./configure --enable-logging=local3 
> --enable-port=389
> checking for a BSD-compatible install... /opt/csw/bin/ginstall -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /opt/csw/bin/gmkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... configure: error: in 
> `/opt/antldm/ldm-6.11.2/src':
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details

That's a serious error message.

> Since I thought that this was some sort of a problem with the build
> environment (C compiler, etc.), I let Mike know about it last Friday.
> This morning I decided to see if the same problem would present itself
> when building LDM 6.9.7 in the same account on the same machine (reason?
> LDM-6.9.7 was already unpacked and ready to test).  Interestingly, the
> problem did not occur for the same 'configure' invocation in LDM 6.9.7
> as it did in LDM 6.11.2.
> 
> Do you have any idea about what could be causing the problem?

The configure(1) output doesn't indicate the reason for the problem. The file 
"config.log" should. Search for "checking whether we are cross compiling".

> NB: the login for 'antldm' is the same as for 'ldm'
> 
> Cheers,
> 
> Tom
> --
> ****************************************************************************
> Unidata User Support                                    UCAR Unidata Program
> (303) 497-8642                                                 P.O. Box 3000
> address@hidden                                   Boulder, CO 80307
> ----------------------------------------------------------------------------
> Unidata HomePage                       http://www.unidata.ucar.edu
> ****************************************************************************


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TIC-838672
Department: Support LDM
Priority: Normal
Status: Closed