Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

Anytime I "emerge jpeg" (media-libs/jpeg-6b-r5), it quits, saying "configure:
error: static: invalid feature name"

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Actual Results:  
jpeg fails to configure, compile and install

Expected Results:  
jpeg should configure, compile and install

I will add the output of 'emerge info' as an attatchment.

Created an attachment (id=66670) [details]
output of 'emerge info'

Created an attachment (id=66671) [details]
output of 'emerge info'

Could you show me all output from that emerge, because i can't reproduce it.

and attach config.log from /var/tmp/portage/jpeg-6b-r5/work

Created an attachment (id=66783) [details]
output of 'emerge jpeg'

(In reply to comment #4)
> and attach config.log from /var/tmp/portage/jpeg-6b-r5/work

Sorry, it doesn't exist.

(In reply to comment #6)
> (In reply to comment #4)
> > and attach config.log from /var/tmp/portage/jpeg-6b-r5/work
> 
> Sorry, it doesn't exist.

Could you try the merge again and re-post the screen-scrape of the error
message?   The current one is funky...  the lines appear out of order.

Also, after this merge fails, could you check for the presence of that
config.log file?

Created an attachment (id=66829) [details]
output of 'emerge jpeg'

config.log is not present neither during nor after the emerge process -- I just
checked.

Created an attachment (id=66842) [details]
Output of emerge media-libs/jpeg

(From update of attachment 66842 [details])
Calculating dependencies ...done!
>>> emerge (1 of 1) media-libs/jpeg-6b-r5 to /
>>> md5 files   ;) jpeg-6b-r5.ebuild
>>> md5 files   ;) jpeg-6b-r4.ebuild
>>> md5 files   ;) files/jpeg-6b-freebsd.patch
>>> md5 files   ;) files/jpeg-6b-gentoo.patch
>>> md5 files   ;) files/digest-jpeg-6b-r4
>>> md5 files   ;) files/digest-jpeg-6b-r5
>>> md5 src_uri ;) jpegsrc.v6b.tar.gz
>>> Unpacking source...
>>> Unpacking jpegsrc.v6b.tar.gz to /var/tmp/portage/jpeg-6b-r5/work
 * Applying jpeg-6b-freebsd.patch ...
 * Applying uClibc/libtool patches ...
 * Fixing ${S}/ltconfig ...
 * Applying jpeg-6b-gentoo.patch ...
>>> Source unpacked.
 * econf: updating jpeg-6b/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating jpeg-6b/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --build=i686-pc-linux-gnu --enable-shared
--enable-static
configure: error: static: invalid feature name

(From update of attachment 66842 [details])
I also have encountered this. Here is my output of emerge jpeg.

The problem ocurred already in jpeg-6b-r4. 

Also, if I run the configure script in
/var/tmp/portage/jpeg-6b-r5/work/jpeg-6b/ with the same options, except
"--enable-static", the configure script completes fine.

what does this show on your systems ?  what version of sed do you guys have ?

ac_option="--enable-static"
ac_feature=`echo $ac_option|sed -e 's/-*enable-//' -e 's/=.*//'`
ac_sed=`echo $ac_feature| sed 's/[-_a-zA-Z0-9]//g'`
if test -n "$ac_sed"; then
  echo "configure: error: $ac_feature: invalid feature name ($ac_sed)"
else
  echo "configure: $ac_feature: feature name is ok"
fi

configure: error: static: invalid feature name (tt)

GNU Sed version 4.1.4

do you use a different LANG or something ?  if you export LC_ALL=C before
running that test code i posted, does it work ?

Ok, when I set LC_ALL to C, I can emerge jpeg (well, at least it doesn't stop
with the configure error). Thanks, but could anyone explain this weird behavior?

you never said what langauge you normally have your system set to use

not all languages have an alphabet which starts with a and ends with z

Created an attachment (id=67881) [details]
07_all_jpeg-LANG.patch

try this patch please

When I patched /var/tmp/portage/jpeg-6b-r5/work/jpeg-6b/configure and ran it
with the same options 'emerge jpeg' provides, it configured properly, so I guess
the patch works. Was that what I was supposed to do :)?

You're right about the system language; I never said what it is (it's Estonian
(et_EE.utf8)) and it doesn't end with z (it ends with 

When I patched /var/tmp/portage/jpeg-6b-r5/work/jpeg-6b/configure and ran it
with the same options 'emerge jpeg' provides, it configured properly, so I guess
the patch works. Was that what I was supposed to do :)?

You're right about the system language; I never said what it is (it's Estonian
(et_EE.utf8)) and it doesn't end with z (it ends with ü).

added patch to current ebuild

This patch isn't really a fix, just a ugly workaround, since it changes an
auto-created file. Its works only in the special case, that this ebuild doesn't
recreate ./configure. Maybe its okay for gentoo, but not for the upstream. 
(and the badness: this patch is used by other packages, ie gpm, too).

Could anyone explain what this patch actually does, exactly ?

It moves some lines (but I didn't track where they're exactly, yet), which seem
to come from some from somewhere in the deep of autoconf. So if there's a bug,
we should fix it there.

if you read more into autotools you'd know that is the correct fix

there is no fix for everyone else because if you simply regenerate configure
with a newer version of autoconf, the fix i posted will be part of it ...
that's all i did, rip code out of newer autoconf's that does not exist in older
autoconf's because autoconf-2.13 is broken now and forever