Summary: | little bug in emerge cyrus-sasl-2.1.17 on not normalized CFLAGS string | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Moreno Rizzo <morenorizzo> |
Component: | [OLD] Library | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | alpeterson, dberkholz, dev-portage, htam, max, tseng |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Moreno Rizzo
2004-01-18 08:09:38 UTC
I have the same error.. but I think the bug is in portage, or the documentation for the make.conf. It should be specified that a single space delimiters are required in the CFLAGS section, or portage should just make it be single spaced for it's opperation... I DON'T THINK THIS IS A BUG WITH CYRUS-SASL, I think it's with portage, and the ebuild could theoretically take care of this special case, but this type problem is likely to crop up elsewhere again unless it's fixed... or documented. in my make.conf: CFLAGS="-march=athlon-xp -mmmx -m3dnow -msse -fomit-frame-pointer -O2 -pipe -Wall" (two spaces between -pipe and -Wall) doesn't work, and I get this error: ***************** configure: loading cache .././config.cache configure: error: `CFLAGS' has changed since the previous run: configure: former value: -march=athlon-xp -mmmx -m3dnow -msse -fomit-frame-pointer -O2 -pipe -Wall configure: current value: -march=athlon-xp -mmmx -m3dnow -msse -fomit-frame-pointer -O2 -pipe -Wall 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 !!! ERROR: dev-libs/cyrus-sasl-2.1.18 failed. !!! Function econf, Line 365, Exitcode 1 !!! econf failed *********** CFLAGS="-march=athlon-xp -mmmx -m3dnow -msse -fomit-frame-pointer -O2 -pipe -Wall" in my /etc/make.conf makes it work.. *********** *** Bug 46554 has been marked as a duplicate of this bug. *** I also correct the problem by removing a remaning space in my CFLAGS definition. This is a rediculous check in the package. The flags are probably passed in two different ways... "${CFLAGS}" and ${CFLAGS} The latter is broken down by bash into a single spaced list and the former is quoted and retains it's spacing. The package is broken, portage doesn't need to be making special fixes for anal package checks. well, resolved fixed, was the actual bug was fixed? I don't care how it's done. So, there is already a way to get the single spaced cflags out of portage, You can't have too anal checks, it's what you choose to do with them that can be too anal... If things break when there are two spaces between my cflags, then portage had better check for that, or have the package deal/ use already existing facilities to do so. If cyrus-sasl doesn't emerge properly when there are two spaces, or some other documentation (imposing rediculous checks on end users!!!) doesn't mention the format requirements of the string, or if there are not these facilities, to get the single spaced list, then this bug should be reopened. (you just said that there are facilities, and that the package is broken), so then this bug is aboutthe package, and it needs to be open. Ok, I diffed the new ebuild and the one that had the problem, I didn't see anything obviously fixed. Reopening. (I'm doing VNC into my computer, so It's really hard to fix this messages tone and spelling, sorry) Ah, I can't reopen.. Please reopen, untill the problem is reported fixed. |