Bugs item #1172824, was opened at 2005-03-29 13:41
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1172824&group_id=976

Category: compile or build problem
Group: bad behaviour
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Daniel Stenberg (bagder)
Summary: freebsd ports (4.x) won't build curl 7.13.1

Initial Comment:
using freebsd 4.x-stable (4.11), I get this when I try
to build:

...
checking for long long... no
checking for ssize_t... no
checking for socklen_t... no
checking for socklen_t equivalent... configure: error:
Cannot find a type to use in place of socklen_t
===> Script "configure" failed unexpectedly.
Please report the problem to roam_at_FreeBSD.org
[maintainer] and attach the
"/usr/ports/ftp/curl/work/curl-7.13.1/config.log"
including the output of the
failure of your make command. Also, it might be a good
idea to provide an
overview of all packages installed on your system (e.g.
an `ls /var/db/pkg`).
*** Error code 1

the build has been broken for a few weeks now. I
emailed the ports maintainer but never heard back.

I can be reached via email if you need more info:
bryan.levin+curl_at_gmail.com

thanks,

/bryan

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-03-29 16:04

Message:
Logged In: NO

ok, found MORE info. wow, this was a tricky one ;)

I have been using 'color-gcc' for a long time now and
without any trouble. well, up until now.

its a perl front-end script that runs gcc and colorizes its
output when it finds errors/warnings.

anyway, when I run as root and try to build this port using
color-gcc in my $PATH, things go badly. when I move that
gcc front-end out of the way and run 'raw' gcc, things are
fine again!

this would explain why I'm (one of) the only one to see this
problem. ahhhh.

still, not sure why openssl from ports seems to fix it.
very odd.

the colorgcc file is at: http://www.grateful.net/colorgcc (fwiw)

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-03-29 15:27

Message:
Logged In: NO

I don't think its a curl bug. but I did want the freebsd
guys to know that something isn't right in the ports
version, as distributed by freebsd's cvsup.

there are 2 work-arounds: edit the Makefile in
/usr/ports/ftp/curl, and comment out the SSL check. OR,
install the ports version of openssl and then rebuild curl
from ports.

if possible, please discuss this with the ports maintainer.
 I tried sending 'roam' email but never got a reply back -
which is why I posted here.

thanks,

/bryan

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2005-03-29 14:55

Message:
Logged In: YES
user_id=1110

I don't think the check is the bad guy here, I think your
built-in OpenSSL is bad somehow.

But I guess we can safely say that this is not a curl bug
and close this report?

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-03-29 14:50

Message:
Logged In: NO

more info:

yes, building it from pure dist tarball DOES work. so curl,
itself, seems to build fine on freebsd 4.x.

its the ports bits that are a bit odd, it seems.

when I edit the makefile to comment out some stuff (I'm just
poking around) things build better. here's what I edited:

.include <bsd.port.pre.mk>

#.if !defined(WITHOUT_SSL)
#CONFIGURE_ARGS= --with-ssl=${OPENSSLBASE}
#PLIST_SUB+= SSL=""
#.else
#CONFIGURE_ARGS= --without-ssl
#PLIST_SUB+= SSL="@comment "
#.endif
                
(around line 58)

ie, if I take out the SSL reference, it patches and builds fine.

another bit of info: if I install the PORTS version of
openssl, and then leave the ports makefile for curl alone,
it ALSO builds fine.

my perl is also fine. its perl5.8.6 and was installed from
ports.

so, what I've found is that there is some unholiness in the
configure script when it checks for the ports version of
openssl (/usr/ports/security/openssl) vs the built-in
version of freebsd openssl.

(nice, huh?)

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-03-29 14:31

Message:
Logged In: NO

The FreeBSD ports system contains a patched version of curl
configure script. Have you tried compiling curl from the
pristine sources? That is building successfully on a FreeBSD
4.7 system (see http://curl.haxx.se/auto/).

Your config.log is showing lots of errors of the form:

/usr/libexec/ld-elf.so.1: /usr/bin/perl: Undefined symbol
"PL_exit_flags"

This implies that there is a library mismatch in your
installation of perl, that could certainly cause problems
during the configure stage.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2005-03-29 14:31

Message:
Logged In: YES
user_id=1110

Great.

This log shows very weird things happening. Look at line
number 1192 where configure checks for inflateEnd in libz.
The error code you get back from that check is _very_
strange and is ld-elf.so complaining about a symbol in
/usr/bin/perl !

>From that point and onwards, all attempts to compile things
with cc renders that error message and the compilation
fails. Thus, of course the check for socklen_t since all
compiles fails!

But I can't really understand why this happens and what a
good fix would be...

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2005-03-29 14:12

Message:
Logged In: NO

logfile is at:

http://www.grateful.net/curl-config.log

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1172824&group_id=976
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-tracker
Received on 2005-03-30