[gentoo-user] cyrus-sasl build problem

[gentoo-user] cyrus-sasl build problem

[James]

Hello

I have cyrus-sasl built on one sytem but it fails on an identical mother
board both running gentoo:

crystal james # eix cyrus-sasl
* dev-libs/cyrus-sasl
     Available versions:  2.1.21-r2:2 ~2.1.21-r3:2 2.1.22:2 2.1.22-r1:2
     Installed:           2.1.22-r1

sheet james # eix cyrus-sasl
* dev-libs/cyrus-sasl
     Available versions:  2.1.21-r2:2 ~2.1.21-r3:2 2.1.22:2 2.1.22-r1:2
     Installed:           none

Both systems use the same mobo:
product: A7V8X-X

Both try to build with identical flags:
dev-libs/cyrus-sasl-2.1.22-r1  USE="berkdb crypt gdbm java ldap mysql pam
postgres ssl -authdaemond -kerberos -ntlm_unsupported_patch -sample -srp
-urandom" 0 kB

The successful system uses this kernel:
2.6.16-gentoo-r9
and these settings:
CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -pipe"
 equery depends cyrus-sasl
[ Searching for packages depending on cyrus-sasl... ]
dev-lang/php-5.1.6-r8
net-nds/openldap-2.3.27-r2
kde-base/kdepim-kioslaves-3.5.2-r3
kde-base/kdebase-kioslaves-3.5.2


The system that fails uses a newer kernel:
2.6.17-gentoo-r5
and is slightly more conservative  with these options:
CFLAGS="-O2 -march=athlon-xp  -pipe"
equery depends cyrus-sasl
[ Searching for packages depending on cyrus-sasl... ]
net-nds/openldap-2.3.27-r2
kde-base/kdepim-kioslaves-3.5.2-r3
kde-base/kdebase-kioslaves-3.5.2

I've used "equery belongs cyrus-sasl"
which comes back empty on both systems; so I'm not really sure
why it is even necessary?

Surely php is not the defining difference?


thoughts and ideas are most welcome.

James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] cyrus-sasl build problem

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

On Tue, 31 Oct 2006 19:45:39 +0000 (UTC), James wrote:

> I have cyrus-sasl built on one sytem but it fails on an identical mother
> board both running gentoo:

What's the failure message? I had the latest testing version fail to
build this week, because of a problem with my Java setup. Re-emerging
both java-config packages fixed it.


-- 
Neil Bothwick

Gotta run, cat's caught in the printer...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: cyrus-sasl build problem

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:


> > I have cyrus-sasl built on one sytem but it fails on an identical mother
> > board both running gentoo:

> What's the failure message? I had the latest testing version fail to
> build this week, because of a problem with my Java setup. Re-emerging
> both java-config packages fixed it.

I ran this:
 
emerge -v java-config java-config-wrapper

but it did not fix the problem.

Here is the error message echoed back to the terminal session:


configure: loading cache .././config.cache
configure: error: `CFLAGS' has changed since the previous run:
configure:   former value:  -O2 -march=athlon-xp  -pipe
configure:   current value: -O2 -march=athlon-xp -pipe
configure: error: changes in the environment can compromise the build
configure: error: run `make distclean' and/or `rm .././config.cache' 
and start over
configure: error: /bin/sh './configure' failed for saslauthd

!!! Please attach the following file when filing a report to 
bugs.gentoo.org:
!!! /var/tmp/portage/cyrus-sasl-2.1.22-r1/work/cyrus-sasl-2.1.22/config.log

!!! ERROR: dev-libs/cyrus-sasl-2.1.22-r1 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  cyrus-sasl-2.1.22-r1.ebuild, line 157:   Called econf
'--with-saslauthd=/var/lib/sasl2' '--with-pwcheck=/var/lib/sasl2'
'--with-configdir=/etc/sasl2' '--with-plugindir=/usr/lib/sasl2'
'--with-dbpath=/etc/sasl2/sasldb2' '--enable-login' '--enable-ntlm'
'--enable-auth-sasldb' '--disable-krb4' '--disable-otp' '--with-openssl'
'--with-pam' '--with-ldap' '--enable-ldapdb' '--disable-sample'
'--disable-gssapi' '--with-mysql' '--enable-mysql' '--enable-postgres'
'--with-pgsql=/usr/lib' '--disable-srp' '--enable-java'
'--with-javahome=/opt/blackdown-jdk-1.4.2.03' '--without-authdaemond'
'--enable-sql' '--with-dblib=gdbm'
  ebuild.sh, line 540:   Called die


The last portion of the error logs is:

host_vendor='pc'
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='/var/tmp/portage/cyrus-sasl-2.1.22-r1/work/
cyrus-sasl-2.1.22/config/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='/var/lib'
mandir='/usr/share/man'
oldincludedir='/usr/include'
plugindir='/usr/lib/sasl2'
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
subdirs=' saslauthd'
sysconfdir='/etc'
target='i686-pc-linux-gnu'
target_alias=''
target_cpu='i686'
target_os='linux-gnu'
target_vendor='pc'

configure: exit 1


ideas?


James



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: cyrus-sasl build problem

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

On Tue, 31 Oct 2006 22:39:12 +0000 (UTC), James wrote:

> > What's the failure message? I had the latest testing version fail to
> > build this week, because of a problem with my Java setup. Re-emerging
> > both java-config packages fixed it.  
> 
> I ran this:
>  
> emerge -v java-config java-config-wrapper

That will only update the highest slotted java-config package, and I'm
fairly sure it was java-config-1 causing problems for me. I did

emerge --oneshot =dev-java/java-config-1.3.7 =dev-java/java-config-2.0.30 

But it looks like your error is completely different.


-- 
Neil Bothwick

I don't work here. I'm a consultant.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: cyrus-sasl build problem

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

On Wednesday 01 November 2006 13:07, Neil Bothwick wrote:
> > emerge -v java-config java-config-wrapper
>
> That will only update the highest slotted java-config package [...].

Just wanted to point out that while this is true for the latest stable portage 
it is no longer true for the latest ~arch portage. The relevant bugs are:

https://bugs.gentoo.org/show_bug.cgi?id=150361
https://bugs.gentoo.org/show_bug.cgi?id=152175

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: cyrus-sasl build problem

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

On Wed, 1 Nov 2006 14:54:29 +0100, Bo Ørsted Andresen wrote:

> > > emerge -v java-config java-config-wrapper  
> >
> > That will only update the highest slotted java-config package [...].  
> 
> Just wanted to point out that while this is true for the latest stable
> portage it is no longer true for the latest ~arch portage. The relevant
> bugs are:
> 
> https://bugs.gentoo.org/show_bug.cgi?id=150361
> https://bugs.gentoo.org/show_bug.cgi?id=152175

A quick glance at those gives the impression that this only applies to
updates. My problem with updating cyrus-sasl required re-emerging the
same versions of java-config, in which case "emerge -1a java-config" only
offers to re-emerge java-config-2. This is with portage-2.1.2_rc1-r1


-- 
Neil Bothwick

One-seventh of your life is spent on Monday.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: cyrus-sasl build problem

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Wednesday 01 November 2006 16:03, Neil Bothwick wrote:
> On Wed, 1 Nov 2006 14:54:29 +0100, Bo Ørsted Andresen wrote:
> > > > emerge -v java-config java-config-wrapper
> > >
> > > That will only update the highest slotted java-config package [...].
> >
> > Just wanted to point out that while this is true for the latest stable
> > portage it is no longer true for the latest ~arch portage. The relevant
> > bugs are:
> >
> > https://bugs.gentoo.org/show_bug.cgi?id=150361
> > https://bugs.gentoo.org/show_bug.cgi?id=152175
>
> A quick glance at those gives the impression that this only applies to
> updates. My problem with updating cyrus-sasl required re-emerging the
> same versions of java-config, in which case "emerge -1a java-config" only
> offers to re-emerge java-config-2. This is with portage-2.1.2_rc1-r1

You're right, sorry. `emerge -1a java-config:{0,2}` would work with 
portage-2.1.2 though.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: cyrus-sasl build problem

[James]

Bo Ørsted Andresen <bo.andresen <at> zlin.dk> writes:


> On Tuesday 31 October 2006 23:39, James wrote:
> > configure: error: `CFLAGS' has changed since the previous run:
> > configure:   former value:  -O2 -march=athlon-xp  -pipe
                                                ^^
> > configure:   current value: -O2 -march=athlon-xp -pipe
> > configure: error: changes in the environment can compromise the build
> > configure: error: run `make distclean' and/or `rm .././config.cache'
> > and start over
> > configure: error: /bin/sh './configure' failed for saslauthd

> Remove the double space in your CFLAGS. There are a whole bunch of bugs about 
> this. E.g.:

This did the trick!

ju da main()


thanks,
James




-- 
gentoo-user@gentoo.org mailing list