Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 76835 - links-2.1_pre15 won't compile with jpeg USE flag
Summary: links-2.1_pre15 won't compile with jpeg USE flag
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High minor
Assignee: Seemant Kulleen (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-05 17:23 UTC by Leung Ki Chi
Modified: 2005-03-14 09:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leung Ki Chi 2005-01-05 17:23:31 UTC
When I try to emerge links with jpeg in the USE flag: it aborts with the following error:
jpeg.c:35:27: macro 'nop' passed 1 arguments, but takes just 0
jpeg.c:36: error: syntax error before '{' token
jpeg.c: In function 'jpeg_start':
jpeg.c:90: error: 'nop' undeclared (first use in this function)
jpeg.c:90: error: (Each undeclared identifier is reported only once
jpeg.c:90: error: for each function it appears in.)
gcc -DHAVE_CONFIG_H -I. -I. -I. -march=pentium3 -Os -pipe -c jsint.c
make: *** [jpeg.o] Error 1
make: *** Waiting for unfinished jobs....

When I remove the USE flag and emerge links, it emerges with no errors.

Reproducible: Always
Steps to Reproduce:
1.Include jpeg in the USE flag and emerge links

Actual Results:  
Emerge fails with the above error message.

Expected Results:  
links should have emerged ok.

Gentoo Base System version 1.6.8
Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0,
2.6.10-gentoo-r2 i686)
==================================================
System uname: 2.6.10-gentoo-r2 i686 Pentium III (Coppermine)
Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jan 5 2005, 13:44:35)
dev-lang/python: 2.3.4
sys-devel/autoconf: 2.59-r6, 2.13
sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3
sys-devel/binutils: 2.15.92.0.2-r2
sys-devel/libtool: 1.5.10-r2
virtual/os-headers: 2.6.8.1-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -Os -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="ftp://mirror.averse.net/pub/gentoo
ftp://ftp.isu.edu.tw/pub/Linux/Gentoo"
LDFLAGS=""
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://mirror.averse.net/gentoo-portage"
USE="x86 acpi alsa apm avi bitmap-fonts cjk crypt cups encode fbcon foomatic db
fortran gdbm gif gnome gpm gtk gtk2 icq ithreads jpeg libwww mad mikmod motif
mpeg msn ncurses nls nptl oggvorbis opengl oss pam pdflib perl png ppds pthreads
python quicktime readline sdl spell ssl tcpd threads truetype truetype-fonts
unicode usb zlib"
Comment 1 Daniel Black (RETIRED) gentoo-dev 2005-01-06 05:18:59 UTC
Ingo if you've got a fix for this I'd be gratefull.
 Seemant's away for a bit.
Comment 2 Daniel Black (RETIRED) gentoo-dev 2005-01-24 06:08:11 UTC
Seemant's back :-). Sorry I didn't get around to this one.
Comment 3 Ingo -LaSombra- Hoffmann 2005-03-04 04:19:50 UTC
I was away for a long time, sorry
:(
It's working fine for me, including the new pre17.
I'm using media-libs/jpeg-6b-r4, which one are you using?

Regards
Comment 4 Leung Ki Chi 2005-03-07 16:36:30 UTC
The bug (or whatever it was) disappeared when I emerged links 2 days ago.

jpeg libs version:
$ emerge -pv media-libs/jpeg

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] media-libs/jpeg-6b-r4  -debug 0 kB

Total size of downloads: 0 kB

And links version:
$ emerge -pv links

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] net-www/links-2.1_pre15  +X -directfb -fbcon +gpm +javascript +jpeg +png +ssl -svga -tiff +unicode 0 kB

Total size of downloads: 0 kB
Comment 5 Seemant Kulleen (RETIRED) gentoo-dev 2005-03-14 09:50:30 UTC
bug seems to have fixed itself. closing.  If this problem reappears, please re-open.