Thanks, you've been a great help. I'll try to obtain the
libpthread.so from the TS distribution as you suggested. I'll keep
chipping away at this until I get it right.
--- In Christopher Friedt <> wrote:
>
> Hmm... ok, I'll upload my libpthread.so library
>
> Here it is:
>
> It should be possible to copy the libpthread.so from the standard 256MB
> SD card filesystem that TS distributes. You should also run ldd on
> jamvm, just to see exactly which dependencies are required. I'm not
sure
> if the symlink is there for ldd -> busybox in the standard TS
> filesystem, but if it isn't you could try 'busybox ldd
> </path/to/jamvm>'. If ldd isn't compiled into busybox, then you should
> try it out booting into the NFS root of the 256MB SD / Debian
filesystem
> that TS distributes.
>
> Sorry I couldn't be of more help, but I've got 1000 things on the go at
> the moment.
>
> ~/Chris
>
>
> tedapt wrote:
> > Thanks for your reply. A search of my TS-Linux installation doesn't
> > come up with anything close. Perhaps something has changed in the
> > distribution since your JamVM package was compiled and now I need to
> > compile it myself, or I need to obtain libpthread.so.0 elsewhere. Does
> > anyone have any suggestions?
> >
> > Excluding the newly installed JamVM libraries this is what I find:
> >
> > $ find / -name *.so* | grep -v jamvm
> >
> > /lib/libnss_files-2.3.2.so
> > /lib/libnss_nis.so.2
> > /lib/libnss_nisplus.so
> > /lib/libm.so.6
> > /lib/librt-2.3.2.so
> > /lib/libnss_nisplus-2.3.2.so
> > /lib/libnsl.so
> > /lib/libwrap.so.0
> > /lib/libwrap.so.0.7.6
> > /lib/libnss_files.so.2
> > /lib/libnss_nis-2.3.2.so
> > /lib/libnss_hesiod.so
> > /lib/libnsl.so.1
> > /lib/libnss_files.so
> > /lib/libm-2.3.2.so
> > /lib/libm.so
> > /lib/libutil.so.1
> > /lib/libgcc_s.so.1
> > /lib/libutil.so
> > /lib/libnss_compat.so.2
> > /lib/libutil-2.3.2.so
> > /lib/ld-2.3.2.so
> > /lib/libnss_compat.so
> > /lib/libnss_hesiod-2.3.2.so
> > /lib/libgcc_s.so
> > /lib/libwrap.so
> > /lib/libnss_hesiod.so.2
> > /lib/libcrypt.so.1
> > /lib/libnss_dns-2.3.2.so
> > /lib/libc-2.3.2.so
> > /lib/libcrypt.so
> > /lib/ld-linux.so.2
> > /lib/libdl.so.2
> > /lib/libnss_dns.so.2
> > /lib/libnss_compat-2.3.2.so
> > /lib/libdl-2.3.2.so
> > /lib/libdl.so
> > /lib/libnss_dns.so
> > /lib/libnss_nisplus.so.2
> > /lib/libanl-2.3.2.so
> > /lib/libc.so.6
> > /lib/libresolv-2.3.2.so
> > /lib/libnsl-2.3.2.so
> > /lib/ld-linux.so
> > /lib/libBrokenLocale-2.3.2.so
> > /lib/libnss_nis.so
> > /lib/libcrypt-2.3.2.so
> > /lib/libblkid.so.1
> > /lib/libresolv.so.2
> > /lib/libuuid.so.1
> > /usr/lib/libz.so
> > /usr/lib/libz.so.1
> > /usr/lib/libz.so.1.2.3
> >
> > --- In Christopher Friedt <cfriedt@> wrote:
> >> I would assume that if `find / -name 'libpthread.so.0'` returns
> >> something, then add that path to your LD_LIBRARY_PATH. Otherwise it
> >> might be a symlink thing. In that case, do a `find / -name
> >> 'libpthread.so*'` and create the appropriate symlink there.
> >>
> >> ~/Chris
> >>
> >> tedapt wrote:
> >>> Chris,
> >>>
> >>> Can you clarify how one to use the JamVM package on a TS-7250
running
> >>> TS-Linux? I've untarred your package on my device and not quite sure
> >>> where to go from here. Invoking the jamvm executable causes this
> > error:
> >>> $ /usr/local/jamvm/bin/jamvm
> >>> /usr/local/jamvm/bin/jamvm: error while loading shared libraries:
> >>> libpthread.so.0: cannot open shared object file: No such file or
> > directory
> >>> Do I need to configure a LD_LIBRARY_PATH or something like that?
Also
> >>> would it be standard to invoke the executable as I've done, or is
> >>> there a better way to do it?
> >>>
> >>> Thanks!
> >>>
> >>> --- In Christopher Friedt <cfriedt@> wrote:
> >>>> Along with the pre-packaged jamvm that I've already posted,
> >>>>
> >>>>
> >
http://vaiprime.visibleassets.com/~cfriedt/classpath-0.93_jamvm-1.4.5-20070412.tar.gz
> >>>> I've also posted the original glibj.zip file as well, just in case
> >>>> anyone would like to decide for themselves which classes are
> >>> stripped out.
> >>>> You can pick it up here:
> >>>>
> >>>> http://vaiprime.visibleassets.com/~cfriedt/glibj_original.zip
> >>>>
> >>>> ~/Chris
> >>>>
> >>>>
> >>>> Taj Morton wrote:
> >>>>> On 4/10/07, Christopher Friedt <cfriedt@> wrote:
> >>>>>> Does anyone know how to change all of the static paths that are
> >>> placed
> >>>>>> into libraries & exutable files during compile?
> >>>>>>
> >>>>>> For instance, i would like the --prefix stored in a library or
> >>>>>> executable to be /usr/local, but when I'm cross-compiling the
> >>> package, i
> >>>>>> do not actually want it installed to /usr/local but
> >>>>>> $PWD/../package-install/usr/local, so that I can easily create a
> >>> tarball
> >>>>>> of the installation files.
> >>>>> You can usually use make install DESTDIR=/path/to/package-install
> >>>>>
> >>>>> That will dump all the stuff into
> > /path/to/package-install/usr/local,
> >>>>> which you can then tar up.
> >>>>> For the binaries to actually work, though, you probably need to
> >>>>> install them into /usr/local.
> >>>>>
> >>>>> Alternatively, if I miss understood your question, and you were
> >>>>> wondering about how to compile so you can install and run into any
> >>>>> prefix, check out binreloc from the Autopackage project:
> >>>>> http://trac.autopackage.org/browser/binreloc/trunk/fdbr.c
> >>>>>
> >>>>> Cheers,
> >>>>> - Taj
> >>>>>
> >>>>>
> >>>
> >>>
> >
> >
> >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|