Date: Thu, 10 Jun 2004 12:52:07 -0600 From: John E Hein <jhein@timing.com> To: bv@wjv.com Cc: freebsd-emulation@freebsd.org Subject: Re: Further info on jdk14 problem Message-ID: <16584.44503.75265.254038@gromit.timing.com> In-Reply-To: <20040610183615.GA14521@wjv.com> References: <20040610011333.GA75565@wjv.com> <16584.32782.434690.477238@gromit.timing.com> <20040610154858.GA87267@wjv.com> <16584.34488.476072.477118@gromit.timing.com> <20040610163130.GA87958@wjv.com> <16584.37476.784566.563221@gromit.timing.com> <20040610183615.GA14521@wjv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Vermillion wrote at 14:36 -0400 on Jun 10, 2004: > execution of glibc-2.2.4-33 script failed, exit status 0 > **** error code 1. Too vague for me (and an exit status of 0 being considered a failure seems... abnormal). Maybe you can determine which script is being run and where it's failing. This basically means trying to manually do what the port build is doing and figure out where it's breaking. Again, make -dl can be helpful here. How about other port dependencies? Did you do portupgrade -R (or is it -r?) to update linux_base deps (like rpm)? It's probably rpm that's trying to run that script that seems to be failing. This may be digressing to a ports@ rather than emulation@ issue. > > You didn't say what the failure was, but obviously installing 7.1_7 > > works okay here. > > No. That all that I get is the script failed. I meant "here" as in... works on my 4.10 box.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16584.44503.75265.254038>