Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Jan 2009 12:04:33 -0900
From:      Mel <fbsd.questions@rachie.is-a-geek.net>
To:        freebsd-questions@freebsd.org, Matthias Apitz <guru@unixarea.de>
Subject:   Re: gsasl 0.2.28_1 does not link in 7.1R
Message-ID:  <200901311204.33808.fbsd.questions@rachie.is-a-geek.net>
In-Reply-To: <20090131175922.GA50313@rebelion.Sisis.de>
References:  <20090130154311.GA7964@rebelion.Sisis.de> <200901310814.23334.fbsd.questions@rachie.is-a-geek.net> <20090131175922.GA50313@rebelion.Sisis.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 31 January 2009 08:59:23 Matthias Apitz wrote:
> El d=EDa Saturday, January 31, 2009 a las 08:14:23AM -0900, Mel escribi=
=F3:
> > The reason I ask is that I'd like to be able to reproduce your problem
> > and therefore need the configuration of dependencies. My options don't
> > contain krb and snmp linking,so somewhere down the line of dependencies=
 I
> > disabled them.
>
> In any case, thanks for spending your time on this;
>
> > Could you show output of:
> > make -C /usr/ports/security/gsasl showconfig-recursive
> >
> > and trim ports that don't contain krb/gssapi or snmp as the output can =
be
> > quite long.
>
> it's quite short:
>
> # make -C /usr/ports/security/gsasl showconfig-recursive
> =3D=3D=3D> The following configuration options are available for gsasl-0.=
2.28_1
> and dependencies =3D=3D=3D> The following configuration options are avail=
able for
> perl-5.8.9: DEBUGGING=3Doff (default) "Build with debugging support"
>      GDBM=3Doff (default) "Build GDBM_File extension"
>      PERL_MALLOC=3Don (default) "Use Perl malloc"
>      PERL_64BITINT=3Don (default) "Use 64 bit integers (on i386)"
>      THREADS=3Doff (default) "Build threaded perl"
>      SUIDPERL=3Doff (default) "Build set-user-id suidperl binary"
>      SITECUSTOMIZE=3Doff (default) "Run-time customization of @INC"
>      USE_PERL=3Don (default) "Rewrite links in /usr/bin"
> =3D=3D=3D> Use 'make config' to modify these settings
> =3D=3D=3D> The following configuration options are available for libiconv=
=2D1.11_1:
>      EXTRA_ENCODINGS=3Don (default) "Include extra character sets"
>      EXTRA_PATCHES=3Doff (default) "Apply patches to fix CP932 add EUCJP-=
MS"
> =3D=3D=3D> Use 'make config' to modify these settings

Ok, it's not snmp. On second glance my link line is:
/usr/local/libexec/ccache/world-cc -std=3Dgnu99 -O2 -fno-strict-aliasing -p=
ipe \
	-o .libs/gsasl gsasl.o gsasl_cmd.o imap.o smtp.o \
	callbacks.o  -L/usr/local/lib ../lib/src/.libs/libgsasl.so -L/usr/lib \
	/usr/local/lib/libidn.so /usr/local/lib/libntlm.so -lgssapi -lkrb5 \
	-lasn1 -lcrypto -lroken -lcrypt -lcom_err ../gl/.libs/libgl.a \
	/usr/local/lib/libiconv.so -lreadline  -Wl,--rpath -Wl,/usr/local/lib

gnutls is the difference.
And with that it also succeeds for me:
/usr/local/libexec/ccache/world-cc -std=3Dgnu99 -O2 -fno-strict-aliasing -p=
ipe \
	-o .libs/gsasl gsasl.o gsasl_cmd.o imap.o smtp.o \
	callbacks.o  -L/usr/local/lib ../lib/src/.libs/libgsasl.so -L/usr/lib \
	/usr/local/lib/libidn.so /usr/local/lib/libntlm.so -lgssapi -lkrb5 \
	-lasn1 -lcrypto -lroken -lcrypt -lcom_err ../gl/.libs/libgl.a \
	/usr/local/lib/libiconv.so -lreadline /usr/local/lib/libgnutls.so \
	-lz /usr/local/lib/libgcrypt.so /usr/local/lib/libgpg-error.so  \
	-Wl,--rpath -Wl,/usr/local/lib

vs your:
                                cc -std=3Dgnu99 -O2 -fno-strict-aliasing -p=
ipe \
	-o .libs/gsasl gsasl.o gsasl_cmd.o imap.o smtp.o \
	callbacks.o =A0-L/usr/local/lib ../lib/src/.libs/libgsasl.so -L/usr/lib \
	/usr/local/lib/libntlm.so -lgssapi -lkrb5 -lasn1 -lcrypto -lroken \
	-lcrypt -lcom_err ../gl/.libs/libgl.a -lreadline /usr/local/lib/libgnutls.=
so\
	 -lz /usr/local/lib/libgcrypt.so /usr/local/lib/libgpg-error.so \
	/usr/local/lib/libintl.so /usr/local/lib/libiconv.so =A0-Wl,--rpath=20
	-Wl,/usr/local/lib

Other then libidn, which should be unrelated, I don't see a difference. You=
=20
may need to file a problem report with the port maintainer.
=2D-=20
Mel

Problem with today's modular software: they start with the modules
    and never get to the software part.



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