Skip to Content.
Sympa Menu

freetds - RE: [freetds] Argue with the compiler?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Hirsch, Jonathan" <jonathan.hirsch AT gs.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Argue with the compiler?
  • Date: Thu, 10 Apr 2003 10:13:05 -0400

I sent that and the output of /bin/bash -x configure > outputfile 2>&1 to
James last night. He couldn't make sense out of them. He has had me install
and try to compile a slightly later version of the code. I have send him the
output files directly about 10 min ago.

Take care,

Jon

-----Original Message-----
From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
Sent: Thursday, April 10, 2003 10:00 AM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] Argue with the compiler?


You should probably just send your entire config.log. We may be able to get
more information from that.

Cheers,
--nick

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org]
Sent: Wednesday, April 09, 2003 4:10 PM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] Argue with the compiler?


Hi,

I can't see anything that looks like an error earlier up in the output file.
I do see this. The thing is I don't know where to look. Is there a string I
should be searching for? I have done searches on conftest.c and many others.
I don't see any indication of a target directory where it tries to write to
and then fails. Or anything else weird for that matter. Any help suggesting
what I should be looking for in the top section of the output would be
appreciated. I know that this isn't a permissions problem because I would
have seen the permission denied error if I was not able to write out a file
in the output log created with sh -x.

Take care,

Jon

(5916) # ./configure
checking for a BSD-compatible install... /opt/gnu/bin/install -c checking
whether build environment is sane... yes checking for gawk... gawk checking
whether make sets ${MAKE}... yes checking build system type...
sparc-sun-solaris2.6 checking host system type... sparc-sun-solaris2.6
checking for gcc... gcc checking for C compiler default output... cat:
cannot open conftest.c
configure: error: C compiler cannot create executables
check `config.log' for details.

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""

configure: exit 0
configure:1296: checking for a BSD-compatible install
configure:1350: result: /opt/gnu/bin/install -c
configure:1361: checking whether build environment is sane


...
## ----------- ##
## confdefs.h. ##
## ----------- ##
_ASBOX
echo
sed "/^$/d" confdefs.h | sort
echo
fi
test "$ac_signal" != 0 &&
echo "$as_me: caught signal $ac_signal"
echo "$as_me: exit $exit_status"
} >&5
rm -f core core.* *.core &&
rm -rf conftest* confdefs* conf$$* $ac_clean_files &&
exit $exit_status
0
+ trap ac_signal=1; { (exit 1); exit 1; } 1
+ trap ac_signal=2; { (exit 1); exit 1; } 2
+ trap ac_signal=13; { (exit 1); exit 1; } 13
+ trap ac_signal=15; { (exit 1); exit 1; } 15
+ ac_signal=0
+ rm -rf conftest* confdefs.h
+ echo
+ cat
+ cat
+ cat
+ cat
+ cat
+ test -z
+ test xNONE != xNONE
+ CONFIG_SITE=/usr/local/share/config.site /usr/local/etc/config.site
+ test -r /usr/local/share/config.site test -r
+ /usr/local/etc/config.site test -r /dev/null
+ test -f /dev/null
+ ac_cache_corrupted=false
++ sed -n s/^ac_env_\([a-zA-Z_0-9]*\)_set=.*/\1/p
+ eval ac_old_set=$ac_cv_env_CC_set
++ ac_old_set=set
+ eval ac_new_set=$ac_env_CC_set
++ ac_new_set=set
+ eval ac_old_val=$ac_cv_env_CC_value
++ ac_old_val=/opt/bin/gcc




Archive powered by MHonArc 2.6.24.

Top of Page