the native jdk1.3 depends upon the linux version but because the port for the linux version requires the user to manually fetch some files, the port (for the linux version) simply displays a message informing the user about where to obtain these files and exits but does not return an error code so when the native jdk13 port tries to build the linux one, it keeps going after the build fails and then fails itself too. Fix: The linux version of the port should return an error code that signifies failure if it does not have the requisite files in /usr/ports/distfiles. How-To-Repeat: try to build java/jdk13 on a box that has never had the linux version of jdk13 built or installed on it.
Responsible Changed From-To: freebsd-ports->sobomax Over to maintainer; but this looks like more of a general problem too.
Responsible Changed From-To: sobomax->glewis Over to maintainer.
Responsible Changed From-To: glewis->portmgr I've worked around this issue for the particular port mentioned, but as one of the notes states "this looks like more of a general problem too". Hence I'm reassigning to portmgr to see if they consider it to be a general problem. The problematic scenario is as follows: . Port A uses the IGNORE variable to indicate that the distfile must be fetched by hand (for example). . Port B depends on port A (to build, for instance). . Building port B without port A installed will do the following: . Try to build port A but "fail" and spit out IGNORE message. Unfortunately this produces a 0 exit status and... . Continue with build of port B until an unexpected failure occurs. The build should really halt after the first step since continuing on obfuscates the reason for the failure. Maybe this is just an abuse of the IGNORE variable and there is already a better way to do this? If so please let me know and I'll fix the offending jdk ports. If not it would probably be worthwhile creating a way to do this.
On Mon, Jul 21, 2003 at 10:30:46AM -0700, Greg Lewis wrote: > . Try to build port A but "fail" and spit out IGNORE message. > Unfortunately this produces a 0 exit status and... IGNORE probably just needs to set a non-zero exit status. Kris
State Changed From-To: open->closed IGNORE does now cause the port build to exit with a non-zero status when its being built as a dependency.
On Mon, Jul 21, 2003 at 02:27:39PM -0700, Kris Kennaway wrote: > On Mon, Jul 21, 2003 at 10:30:46AM -0700, Greg Lewis wrote: > > > . Try to build port A but "fail" and spit out IGNORE message. > > Unfortunately this produces a 0 exit status and... > > IGNORE probably just needs to set a non-zero exit status. Oops, further investigation indicates that it now does when the package is being built as a dependency. Sorry! I'll close the PR. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org