[freetds] Argue with the compiler?

Castellano, Nicholas Nicholas_Castellano at acml.com
Thu Apr 10 10:00:28 EDT 2003

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

-----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?


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, 


(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_NAME ""

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. ##
## ----------- ##
      sed "/^$/d" confdefs.h | sort
    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
+ 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

-----Original Message-----
From: Lowden, James K [mailto:LowdenJK at bernstein.com] 
Sent: Wednesday, April 09, 2003 1:50 PM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] Argue with the compiler?

> From: Hirsch, Jonathan [mailto:jonathan.hirsch at gs.com]
> Sent: April 9, 2003 1:18 PM
> Further suggestions to run sh -x ./configure have produced a large 
> output file. From that I really still cannot see what configure is 
> doing. How can I make sure that I am setting _FREETDS_LIBRARY_SOURCE
>  variable on the way in ?
> ....from the output file...
> + echo configure:2085: checking for C compiler default output echo -n
> + checking for C compiler default output...
> checking for C compiler default output...
> ++ echo $CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS
conftest.$ac_ext $LIBS >&5

The problem must occur earlier, before compilation, because conftest.c was
not created.  At least, that's what I'd assume, since "cat" can't find it.  

FreeTDS mailing list
FreeTDS at lists.ibiblio.org http://lists.ibiblio.org/mailman/listinfo/freetds

The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.

More information about the FreeTDS mailing list