#396363 FTBFS: Makefile:69: *** target pattern contains no `%'. Stop.

Package:
grace
Source:
grace
Description:
XY graphing and plotting tool
Submitter:
Goswin von Brederlow
Date:
2010-04-14 12:12:13 UTC
Severity:
minor
#396363#5
Date:
2006-10-31 12:28:09 UTC
From:
To:
Hi,

when building grace I get the following error:

make[2]: Entering directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/src'
Makefile:69: *** target pattern contains no `%'.  Stop.
make[2]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20/src'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/mrvn/build/grace_1:5.1.20-3/grace-5.1.20'
make: *** [common-install-impl] Error 2

Build log is attached.

MfG
	Goswin

#396363#10
Date:
2006-10-31 16:16:33 UTC
From:
To:
Have you altered the sources in any way? Please check your building
environment. grace 1:5.1.20-3 build OK on all architectures, including
amd64

http://buildd.debian.org/build.php?arch=&pkg=grace

Ionut

#396363#15
Date:
2006-10-31 17:54:50 UTC
From:
To:
Ionut Georgescu <george@pks.mpg.de> writes:

I saw that too and I saw a few more of the same errors in other
packages. I stoped on reporting anymore after recognising that pattern
and you are just unlucky to be at the top of the failed list.

The source is not altered in any way and the build environment is a
up-to-date sid chroot (updated daily after the mirror pusle) but not
neccesarily a clean one (cleaning is done once a day before updates
but not between builds). Building is done with

apt-get --only-source build-dep grace=1:5.1.20-3
apt-get --only-source source grace=1:5.1.20-3
cd */ && debuild -us -uc -B

I have no idea what causes this. I would suspect the last make
upload. But packages have been build fine a month after that and now
they fail. The buildd chroots should have had the latest make by then.

Can you reproduce it?

MfG
        Goswin

#396363#20
Date:
2006-11-02 09:48:29 UTC
From:
To:
severity 396363 minor
thanks

Ionut Georgescu <george@pks.mpg.de> writes:

Hi,

from other packages that failed with similar messages I found that the
problem is the ':' in thedirectory name. I suspect that you have a
dependency with a full path in line 69.

I'm not sure what to do about that or if it is worth fixing. Shouldn't
be RC imho, severity adjusted.

MfG
        Goswin