Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 19501 - Gimp 1.3.14 Makefile seems messed up
Summary: Gimp 1.3.14 Makefile seems messed up
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-17 16:04 UTC by Anders Johansson
Modified: 2003-04-19 05: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 Anders Johansson 2003-04-17 16:04:24 UTC
When trying to emerge gimp 1.3.14, the compile breaks in plugins/common with

make[3]: *** No rule to make target `gimp-1.3.14.tar.bz2', needed by `all-am'.
Stop.
make[3]: *** Waiting for unfinished jobs....
CML_explorer.c:82:2: warning: #warning GTK_DISABLE_DEPRECATED
make[3]: Leaving directory
`/var/tmp/portage/gimp-1.3.14/work/gimp-1.3.14/plug-ins/common'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gimp-1.3.14/work/gimp-1.3.14/plug-ins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gimp-1.3.14/work/gimp-1.3.14'
make: *** [all] Error 2
 
!!! ERROR: media-gfx/gimp-1.3.14 failed.
!!! Function src_compile, Line 75, Exitcode 2
!!! (no error message)

gimp 1.3.13 emerged fine here, and I could compile 1.3.14 with garnome

Reproducible: Always
Steps to Reproduce:
1. Try to emerge gimp 1.3.14
2.
3.

Actual Results:  
compile broke

Expected Results:  
compiled

I'm not sure if packages masked through packages.mask should be reported in
bugzilla, but since 1.3.13 emerged fine, and I guess it's there for testing
anyways, I thought I would
Comment 1 khai 2003-04-17 21:23:00 UTC
This error occurs on my system as well.
Comment 2 foser (RETIRED) gentoo-dev 2003-04-17 21:46:16 UTC
emerge info ? i use flagged some stuff, may be the cause

try building with MAKEOPTS="-j1" set btw, see if that improves the situation
Comment 3 Arno 2003-04-17 23:03:16 UTC
Same error for me:
make[3]: *** No rule to make target `gimp-1.3.14.tar.bz2', needed by `all-am'.  Stop.

Here's my emerge info:
Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.20 i686 AMD Athlon(tm) MP 2000+
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY="/usr/local/portage"
USE="X 3dnow acpi avi berkdb cdr dga dvd encode gif gtk gtk2 java jpeg imlib mbox mpeg mmx mozilla moznoirc moznomail moznocompose ncurses oss pam pda pic png samba smooth spell sse ssl tcpd tiff truetype xml2 xmms xv x86 zlib"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-mp -O3 -pipe -mmmx -m3dnow -msse -fomit-frame-pointer"
CXXFLAGS="-march=athlon-mp -O3 -pipe -mmmx -m3dnow -msse -fomit-frame-pointer"
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j1"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
Comment 4 Philip Walls (RETIRED) gentoo-dev 2003-04-18 00:58:58 UTC
Every 1.3.x Gimp release seems to have this problem, it was previously corrected by simply touching the said file to avoid trying to build it but this was removed from the 1.3.14 release for some reason.

Commited fix to CVS, perhaps we should talk to the Gimp people directly about this oddity, as it appears to be quite a consistant one :-P

I'll leave it to the Gnome guys to resolve this if there are no other problems.
Comment 5 Anders Johansson 2003-04-18 02:44:31 UTC
Yep that seems to work, thanks.

btw, I just tried running configure manually, and it doesn't produce the broken dependency. I wonder if the bug here really is upstream.
Comment 6 foser (RETIRED) gentoo-dev 2003-04-18 06:04:51 UTC
oh drn, that's right. That was the part i removed, never thought of that :( Anyway, i got it to built several times like this, so it is a bit of an odd problem then.
Comment 7 Anders Johansson 2003-04-18 20:59:22 UTC
There's another problem with the ebuild. 1.3.13 was SLOT="1.4" while 1.3.14 is SLOT="2", so 1.3.13 was never unmerged.
Comment 8 foser (RETIRED) gentoo-dev 2003-04-19 05:50:19 UTC
hmm yeah, was a bit too eager there. changed it back to 1.4 .