hg: bsd-port/bsd-port/jdk: . Add the missing define and endef lines for binary_file_verification on
Stephen Bannasch
stephen.bannasch at deanbrook.org
Wed Mar 9 11:33:14 PST 2011
At 10:03 AM -0800 3/9/11, Greg Lewis wrote:
>On Wed, Mar 09, 2011 at 12:02:10PM -0500, Stephen Bannasch wrote:
>> I'm using soylatte16-i386-1.0.3 and have backed out all my changes and John Roses patches and am getting an abort trap after a
>> seemingly successful build:
>>
> > testing build: ./build/bsd-amd64/j2sdk-image/bin/java -version
>
>Interesting. I see this too now that I try it.
>
>I don't see it if I do this though:
>
>% ./build/bsd-amd64/bin/java -version
>openjdk version "1.7.0-internal"
>OpenJDK Runtime Environment (build
>1.7.0-internal-greglew_2011_03_08_23_33-b00)
>OpenJDK 64-Bit Server VM (build 21.0-b03, mixed mode)
>
>Notionally this should do the same thing.
Hmmm ... that works for me also:
[bsd]$ ./build/bsd-amd64/bin/java -version
openjdk version "1.7.0-internal"
OpenJDK Runtime Environment (build 1.7.0-internal-stephen_2011_03_09_14_11-b00)
OpenJDK 64-Bit Server VM (build 21.0-b03, mixed mode)
I wonder why the executables in j2sdk-image aren't working?
I use this script to copy a successful build from build/bsd-amd64/j2sdk-image to /usr/local -- I am assuming that build/bsd-amd64/j2sdk-image is supposed to work.
#!/bin/sh
#
#
# Remove file with versioned name of last build and symbolic link to last build.
# Used when referring to a build when copying to /usr/local or creating a tarball.
if [ -e .last_build ]
then buildname=`cat .last_build`
fi
echo "copying build/bsd-amd64/j2sdk-image/* to /usr/local/$buildname"
sudo rm -rf /usr/local/$buildname
sudo mkdir /usr/local/$buildname
sudo cp -r build/bsd-amd64/j2sdk-image/* /usr/local/$buildname
cd /usr/local
sudo rm -f java-1.7.0
sudo ln -s $buildname java-1.7.0
echo '
/usr/local/java-1.7.0/bin/java -version
'
/usr/local/java-1.7.0/bin/java -version
cd -
More information about the bsd-port-dev
mailing list