Answering my own question: It appears that I was missing the necessary package libgcj-3.4.2-6.fc3 RPM for i386 I found this package, downloaded it and tried to

Message 1 of 5
, Mar 2, 2006

0 Attachment

Answering my own question:

It appears that I was missing the necessary package
libgcj-3.4.2-6.fc3 RPM for i386

I found this package, downloaded it
and tried to install it,
only to be informed that a newer version of this package was already
installed?!

I was not prepared to force the install
possibly trashing the newer version of the package
upon which something else may depend

So I just created a symbolic link called /usr/share/java/libgcj-3.4.2.jar
pointing at /usr/share/java/libgcj-3.4.3.jar
(a risky thing to rely upon I know)

The build then ran to completion
and I have now got an unslung image :-)

The question is: Should I trust the resultant image?

Basically is it correct that
a "Fedora Core 3" "i386" architecture library
is only be used as part of the build process itself
and not actually bundled into the resultant image?

I.e. should I go ahead and flash this image?

> I have tried to build unslung 6.6 alpha
> under Fedora Core 3.

[snip of some "make" output containing error(s)]

> I looked into the referenced log file
> /bin/sh ../lib/javacomp.sh -d .
> <work[ing]_directory>/gettext-native-0.14.1-r3/gettext-0.14.1/gettext-runtime/intl-java/gnu/gettext/GettextResource.java
> incorrect classpath: /usr/share/java/libgcj-3.4.2.jar
>
> This [file] does *not* exist
> The parent directory "/usr/share/java" *does* exist
> and so do the files "/usr/share/java/libgcj-3.3.4.jar"
> and "/usr/share/java/libgcj-3.4.3.jar"
> and so does a symbolic link "/usr/share/java/libgcj-3.4.4"
> which points back at libgcj-3.4.3
>
> Anyone any idea what I am missing?
> Or why it is missing?
> Or more importantly what I do to fix it?

Mike Westerhof

Yes, the image is fine - it does not depend on the java. I seem to recall that I had problems with my Fedora Core 3 build machine in the same place

Message 2 of 5
, Mar 2, 2006

0 Attachment

Yes, the image is fine - it does not depend on the java.

I seem to recall that I had problems with my Fedora Core 3 build machine in
the same place (classpath). I didn't even have the java stuff installed on
FC.3, so I couldn't figure out why on earth the build process was trying to
use the java build tools (which were all sym links to /etc/alternatives, as
I recall). I finally found a file in /usr/bin (on FC.3) that I deleted; the
absence of the file prevents the build from actually attempting any java
stuff. (of course, I'll be unable to develop/build any real java
applications on my Linux system, so I'm hoping that will all get fixed when
I upgrade to FC.5 this summer some time!).

You can go ahead and flash the image.

(Or, you can also cd to /home/slug, and do a "make update" and build
again -- Unslung 6.7 is now checked into Monotone -- the updates should be
fairly small and only take 10 - 20 minutes or so of build time.)

> Answering my own question:
>
> It appears that I was missing the necessary package
> libgcj-3.4.2-6.fc3 RPM for i386
>
> I found this package, downloaded it
> and tried to install it,
> only to be informed that a newer version of this package was already
> installed?!
>
> I was not prepared to force the install
> possibly trashing the newer version of the package
> upon which something else may depend
>
> So I just created a symbolic link called /usr/share/java/libgcj-3.4.2.jar
> pointing at /usr/share/java/libgcj-3.4.3.jar
> (a risky thing to rely upon I know)
>
> The build then ran to completion
> and I have now got an unslung image :-)
>
> The question is: Should I trust the resultant image?
>
> Basically is it correct that
> a "Fedora Core 3" "i386" architecture library
> is only be used as part of the build process itself
> and not actually bundled into the resultant image?
>
> I.e. should I go ahead and flash this image?
>
> > I have tried to build unslung 6.6 alpha
> > under Fedora Core 3.
>
> [snip of some "make" output containing error(s)]
>
> > I looked into the referenced log file
> > /bin/sh ../lib/javacomp.sh -d .
> >
<work[ing]_directory>/gettext-native-0.14.1-r3/gettext-0.14.1/gettext-runtim
e/intl-java/gnu/gettext/GettextResource.java
> > incorrect classpath: /usr/share/java/libgcj-3.4.2.jar
> >
> > This [file] does *not* exist
> > The parent directory "/usr/share/java" *does* exist
> > and so do the files "/usr/share/java/libgcj-3.3.4.jar"
> > and "/usr/share/java/libgcj-3.4.3.jar"
> > and so does a symbolic link "/usr/share/java/libgcj-3.4.4"
> > which points back at libgcj-3.4.3
> >
> > Anyone any idea what I am missing?
> > Or why it is missing?
> > Or more importantly what I do to fix it?
>
>
> SPONSORED LINKS Communication and networking Wireless communication and
networking Linksys nslu2
>
>
> --------------------------------------------------------------------------
------
> YAHOO! GROUPS LINKS
>
> a.. Visit your group "nslu2-linux" on the web.
>
> b.. To unsubscribe from this group, send an email to:
> nslu2-linux-unsubscribe@yahoogroups.com
>
> c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>
>
> --------------------------------------------------------------------------
------
>
>

>
> (Or, you can also cd to /home/slug, and do a "make update" and build
> again -- Unslung 6.7 is now checked into Monotone -- the updates should be
> fairly small and only take 10 - 20 minutes or so of build time.)
>

> Yes, the image is fine - it does not depend on the java.
>
> I seem to recall that I had problems with my Fedora Core 3 build machine in
> the same place (classpath). I didn't even have the java stuff installed on
> FC.3, so I couldn't figure out why on earth the build process was trying to
> use the java build tools (which were all sym links to /etc/alternatives, as
> I recall). I finally found a file in /usr/bin (on FC.3) that I deleted; the
> absence of the file prevents the build from actually attempting any java
> stuff. (of course, I'll be unable to develop/build any real java
> applications on my Linux system, so I'm hoping that will all get fixed when
> I upgrade to FC.5 this summer some time!).
>
> You can go ahead and flash the image.
>
> (Or, you can also cd to /home/slug, and do a "make update" and build
> again -- Unslung 6.7 is now checked into Monotone -- the updates should be
> fairly small and only take 10 - 20 minutes or so of build time.)
>
> Mike (mwester)

Your message has been successfully submitted and would be delivered to recipients shortly.