Date: Thu, 8 Mar 2012 13:09:51 -0500 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-java@freebsd.org, Volodymyr Kostyrko <c.kworr@gmail.com> Cc: bug-followup@FreeBSD.org Subject: Re: ports/162991: java/openjdk6 fails to build Message-ID: <201203081309.55633.jkim@FreeBSD.org> In-Reply-To: <201203080750.q287oEA5033004@freefall.freebsd.org> References: <201203080750.q287oEA5033004@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 08 March 2012 02:50 am, Volodymyr Kostyrko wrote: > Ok, I found time to investigate it. > > Everything is about arch guessing. java/openjdk7 substitutes amd64 > for x86_64 while java/openjdk6 doesn't. I just added missing bits > from correspondent java/openjdk7 patch. > > Redports build: > https://redports.org/buildarchive/20120307160255-45601 > > Patch attached. Sorry but it doesn't make any sense. I guess you are patching this: ... # Platform settings specific to BSD ifeq ($(PLATFORM), bsd) OS_VERSION := $(shell uname -r) # Arch and OS name/version mach := $(shell uname -m) archExpr = case "$(mach)" in \ i[3-9]86) \ echo i586 \ ;; \ *) \ echo $(mach) \ ;; \ esac ARCH := $(shell $(archExpr) ) ARCH_FAMILY := $(ARCH) ... Unless "UNAME_m" environment variable is set, there is no way that this patch does anything at all. % uname -r 10.0-CURRENT % uname -m amd64 % env UNAME_m=x86_64 uname -m x86_64 I believe OpenJDK7 added it because some BSDs (e.g., DragonFlyBSD) return x86_64 for "uname -m". BTW, does "make DISABLE_MAKE_JOBS=yes" make any difference? Thanks, Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203081309.55633.jkim>