> Date: Fri, 14 Feb 2014 13:34:53 +0000 > From: lf...@cruziero.com (akhiezer) > To: BLFS Support List <blfs-support@linuxfromscratch.org> > Subject: Re: [blfs-support] Iced Tea 2.4.1 and iced tea 2.4.5 sed unknown > option to `s' > > > Date: Fri, 14 Feb 2014 10:13:47 -0300 > > From: Fernando de Oliveira <fam...@yahoo.com.br> > > To: akhiezer <lf...@cruziero.com>, > > BLFS Support List <blfs-support@linuxfromscratch.org> > > Subject: Re: [blfs-support] Iced Tea 2.4.1 and iced tea 2.4.5 sed unknown > > option to `s' > > > . > . > > > > Thanks, akh. Just adding what seems the original link: > > > > http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1665 > > > > I have seen that Armin also replied. > > > > I am trying to understand this better, and have found that configure and > > configure.ac have mentions to lsb_release. I am trying to understand if > > it is a required, recommended or optional dependency. However, in one > > machine I do not have it installed and it gives me linux-gnu and builds > > fine, so, I am intending to add as optional. > > > > What do you all think about this? I cannot understand why Christopher's > > is getting n/a. > > > > In the following, I am writing some observations and guesses. > > > > In configure, for 2.4.4, which is a build dir still in place in yet > > another machine, I see: > > > > {{{ > > if test -n "$ac_tool_prefix"; then > > # Extract the first word of "${ac_tool_prefix}lsb_release", so it can > > be a program name with args. > > set dummy ${ac_tool_prefix}lsb_release; ac_word=$2 > > { $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 > > $as_echo_n "checking for $ac_word... " >&6; } > > if ${ac_cv_path_LSB_RELEASE+:} false; then : > > $as_echo_n "(cached) " >&6 > > else > > case $LSB_RELEASE in > > [\\/]* | ?:[\\/]*) > > ac_cv_path_LSB_RELEASE="$LSB_RELEASE" # Let the user override the test > > with a path. > > ;; > > *) > > as_save_IFS=$IFS; IFS=$PATH_SEPARATOR > > }}} > > > > > > Also, I noticed that he is building at /opt, so probably as root. I have: > > > > {{{ > > $ xzgrep -C6 distro_name > > /home/fernando/Downloads/blfs/OpenJDK-1.7.0.51-2.4.5-2014.01.29-18h12m38s.log.xz > > rm -f > > /home/fernando/tmp/paco-build-2014.01.29-18h12m38s/icedtea-2.4.5/generated.build/sun/misc/Version.java > > rm -f > > /home/fernando/tmp/paco-build-2014.01.29-18h12m38s/icedtea-2.4.5/generated.build/sun/misc/Version.java.temp > > /bin/sed -e 's/@@launcher_name@@/java/g' \ > > -e 's/@@java_version@@/1.7.0_51-blfs/g' \ > > -e 's/@@java_runtime_version@@/1.7.0_51-blfs-b31/g' \ > > -e 's/@@jdk_derivative_name@@/IcedTea 2.4.5/g' \ > > -e 's/@@distro_name@@/Linux From Scratch/g' \ > > -e 's/@@distro_package_version@@/'7u51-2.4.5-blfs'/g' \ > > -e 's/@@java_runtime_name@@/OpenJDK Runtime Environment/g' \ > > -e 's/@@jdk_revid@@//g' \ > > -e 's/@@hotspot_revid@@//g' \ > > ../../../src/share/classes/sun/misc/Version.java.template > > > /home/fernando/tmp/paco-build-2014.01.29-18h12m38s/icedtea-2.4.5/generated.build/sun/misc/Version.java.temp > > make[5]: Leaving directory > > `/home/fernando/tmp/paco-build-2014.01.29-18h12m38s/icedtea-2.4.5/openjdk-boot/jdk/make/java/version' > > }}} > > > > I remember having sometime ago problems with PATH, for some packages, if > > I build as root, and for those, I have a line in the script: > > > > source /etc/profile > > > > and the PATH is well defined, because he needs: > > > > export CLASSPATH=.:/usr/share/java && > > export PATH="$PATH:/opt/OpenJDK-1.7.0.51-bin/bin" > > > > or similar, if the binary is another one, i.e., the binary has to be in > > the path, and, in my case, it is provided by: > > > > /etc/profile.d/openjdk.sh > > > > which is defined in OJDK/Icedtea BLFS page. > > > > > There was a recent case - maybe also a second case with same cause - where > the user was > doing things using 'sudo' instead of root, and it broke the PATH stuff ('cos > sudo cfg > essentially reset the PATH &c). 'Bout a few weeks or so ago - sorry not more > detail. > Resolution was to do as root: iirc user hadn't got root stuff setup properly > - tho' that > was in lfs. >
- sorry, that last part should be: -- The problem was (in the LFS cases of a few weeks ago) that the user hadn't setup - or hadn't su'd into - the user 'lfs', and so was "having" to issue commands via sudo; and it was that sudo's config file that was resetting PATH &c; and so command-paths weren't being found. The resolution was to do stuff as user lfs per book. -- So maybe something similar here? ((Also, it wouldn't really make sense to _have_ to be doing stuff as root in the present java/iced case, as it looks like a config stage.)) Apols for the noise. rgds, akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
