Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Aug 2000 23:28:27 -0500
From:      Dan Nelson <dnelson@emsphone.com>
To:        Claude Cormier <techsupport@devises-or.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Version 2.2.8 - C compiler - vprintf()
Message-ID:  <20000813232827.A20494@dan.emsphone.com>
In-Reply-To: <39977194.D2D30AAD@devises-or.com>; from "Claude Cormier" on Mon Aug 14 00:12:04 GMT 2000
References:  <39960BCD.6E1622B@devises-or.com> <20000812223213.A12554@dan.emsphone.com> <3996AB0C.73240EF3@devises-or.com> <20000813094608.A13422@dan.emsphone.com> <399758F7.2F2E2C4F@devises-or.com> <20000813223535.A12309@dan.emsphone.com> <39977194.D2D30AAD@devises-or.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 14), Claude Cormier said:
> Dan Nelson wrote:
> > Ok; Run configure again and then take a look at the config.log file.
> > What is in the log right after the line reading "checking for vprintf"?
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> configure:3558: checking for socket     
> 
> So it doesn't generate any error.

?? so it just has:

configure:3428: checking for vprintf
configure:3558: checking for socket

That means it didn't even check at all.  Make sure you're building from
a clean directory (no config.cache).

> Also, I got these two errors in config.log
> 
> ltconfig:915: gcc -c -g -O2 -fno-rtti -fno-exceptions -c conftest.c
> -I/usr/local/include/openssl conftest.c 1>&5
> cc1: Invalid option `-fno-exceptions'

This error comes right after a line saying "ltconfig:914: checking if
cc supports -fno-rtti -fno-exceptions", which 2.2 doesn't, so that's
fine.

> and
> 
> ltconfig:1657: eval "/usr/bin/nm -p conftest.o | sed -n -e 's/^.*[ 	]\([BCDEGRST]\)[ 	][ 	]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2\3 \3/p' > conftest.nm"
> cannot find nm_test_var in conftest.nm

This is fine also, since the very next configure test tries another way
and succeeds.

> nm: vprintf.o
> utf2.o: no name list00000000 T _vprintf

This means that your system definitely does have vprintf, but for some
reason curl can't find it.  It's a curl bug, BTW, if ./configure
succeeds but can't compile the program.  ./configure should have failed
as soon as it detected a missing vprintf.

-- 
	Dan Nelson
	dnelson@emsphone.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000813232827.A20494>