DSM-G600, DNS-3xx and NSA-220 Hack Forum

HaydnH wrote:

Python 2.5 now works.

bzhou: what are the post install scripts trying to do? I don't have an update-alternatives binary/script so they fail... although it doesn't really matter...

Code:

Configuring bzip2
/mnt/HD_a2/ipkg//usr/lib/ipkg/info/bzip2.postinst: /opt/bin/update-alternatives: No such file or directory
postinst script returned status 127
ERROR: bzip2.postinst returned 127

How come you don't have /opt/bin/update-alternatives ? It's in the ipkg-opt package. You probably should bind mount your prefix to /opt. Are you using your own ipkg, or optware ipkg-opt ?

/opt/bin/update-alternatives is useful to give priority when binary with the same name exist from different packages. In this case, busybox.ipk may give you a /opt/bin/bzip2, and bzip2.ipk also gives you one, bzip2 package has priority.

Last edited by bzhou (2008-03-11 18:12:53)

HaydnH wrote:

Yes my own ipkg binary... however, shouldn't the control file for any packages using "update-alternatives" have a dependency listed on ipkg-opt??

Strictly speaking, yes. OTOH, it's just not a scenario that happens very often:

1. optware packages gets managed by some unknown ipkg
2. and that unknown ipkg does not have update-alternative (if that ipkg has a known prefix, we can set UPD_ALT_PREFIX during build time, see http://trac.nslu2-linux.org/optware/bro … -fsg3v4.mk for example)
3. and one has to install ipkg-opt just for /opt/bin/update-alternatives

At that point, we might as well ask the user to start using ipkg-opt in the first place.

Hi Brian,

The ssh-keygen binary is broken in OpenSSH.

/opt/bin # ssh-keygen
Generating public/private rsa key pair.
Illegal instruction

Last edited by JRT (2008-03-14 11:10:51)

I wonder if anyone can try copy

toolchain/uclibc-toolchain-src-20040609/gcc-3.3.x/toolchain_arm/arm-linux-uclibc/lib/librt*so*

to dns-323:/opt/lib and see if that can get packages such as transmission, swi-prolog working.

Similarly copy libffi*so* for jamvm.

And the other mentioned library, if anyone wants to try ...

In case it's useful to anyone, here are the shared library files that are present by default on the DNS323:

/ # ls /lib
ld-uClibc-0.9.28.so     libiconv.so.2           libresolv-0.9.28.so
ld-uClibc.so.0          libiconv.so.2.2.0       libresolv.so.0
libc.so.0               libid3tag.so.0          librpc-parse-3-0.so.0
libconfuse              libid3tag.so.0.3.0      libsmb-3-0.so.0
libconfuse.0            liblib-3-0.so.0         libsqlite3.so.0
libconfuse.0.0.0        liblpr.so.0             libsqlite3.so.0.8.6
libcrypt-0.9.28.so      libm-0.9.28.so          libstdc++.so.5
libcrypt.so.0           libm.so.0               libthread_db-0.9.28.so
libdl-0.9.28.so         libmsrpc-3-0.so.0       libthread_db.so.1
libdl.so.0              libnsl-0.9.28.so        libuClibc-0.9.28.so
libgcc_s.so             libnsl.so.0             libutil-0.9.28.so
libgcc_s.so.1           libparam-3-0.so.0       libutil.so.0
libgdbm.so.3            libpassdb-3-0.so.0      libz.so.1
libgdbm.so.3.0.0        libpthread-0.9.28.so    libz.so.1.2.3
libiconv.so             libpthread.so.0         modules

Last edited by sjmac (2008-03-15 23:29:55)

---

Attachments:
libffi-so.tgz, Size: 26,374 bytes, Downloads: 861

jules wrote:

Just an update on this.
Swi-prolog doesn't work, when launched an error "swipl: pl-write.c: 763: writePrimitive: Assertion `0' failed." is displayed. But anyway, i don't think that there are many prolog programmers here.
Regarding the java support, jikes and jamvm packages, both of them work. But, while jikes speed is acceptable (btw we don't need to compile on the dns), jamvm is extremely slow. 10 sec to start and run hello world. Too slow for any real-world application.

If phoneme-advanced runs, it should perform much much better. For usage and simple test method, see http://www.nslu2-linux.org/wiki/HowTo/UseJavaOnTheSlug

If it does not run, post the error message here, probably not too difficult to tweak the build configuration to get it run (I've done that for lots other optware platforms).

It's the package. A "strace rtorrent" might give more clue. (If it's epoll related, we can change the build options)
BTW, you don't need to install dependencies manually, "ipkg install rtorrent" will do.

bzhou wrote:

A patch to build kissdx 0.14.0.b1a

I've been compiling from kissdx svn trunk, and have submitted patches to the authors/kissdx Makefile and the optware kissdx.mk.

http://www.vidartysse.net/BUGS/view_bug.php?bug_id=78

The kissdx developer 'vit' is also listed as the maintainer of the kissdx.mk file in optware, and I'm hoping that he'll look at the changes and move them in to Optware, (or bluediver, who did the last check in on that file ...), but they've not made any comment yet.

Regarding the kissdx Makefile, it looks like the authors know about Optware, but they weren't setting the prefix correctly in the Makefile. As well as fixing that, my patched Makefile uses any cross compilation options that are passed in (for example from kissdx.mk)

I passed in the options in this non-standard way because there is no kissdx configure script to pass them to.

(I've attached my patches here, in case someone wants to look without creating an account on the kissdx bug tracker.)

The kissdx.mk references a local location for the kissdx source so that I can easily incorporate my changes, so that would need tweaking for your build setup.

Any comments on the changes? Could I have done anything more cleanly?

I want to also link in libxml2, and for that I want to know if the build is a cross compile or native compile - how should I check for that?

Last edited by sjmac (2008-03-31 16:43:59)

---

Attachments:
kissdx.mk, Size: 9,071 bytes, Downloads: 859

Well, I don't get the strace output, but hopefully someone else can.

Attachment is the output...

//T

---

Attachments:
strace_rtorrent.txt, Size: 17,838 bytes, Downloads: 801

EDIT: Never mind that. I accidentally did it locally.

Caught Segmentation fault, dumping stack:
Stack dump not enabled.

[screen is terminating]

Last edited by ojve (2008-03-31 19:36:32)

ojve wrote:

EDIT: Never mind that. I accidentally did it locally.

Code:

Caught Segmentation fault, dumping stack:
Stack dump not enabled.

[screen is terminating]

Are you using Putty, xterm, or something else?

Still problems in openssh ...

I just updated the optware tree, built and tested openssh. The install goes like this (see seg faults in postinstall scripts):

/ # ipkg install openssh
Installing openssh (4.9p1-1) to root...
Downloading file:///mnt/HD_a2/optware_builds/openssh_4.9p1-1_arm.ipk
Configuring openssh

Generating RSA Key...
Generating public/private rsa1 key pair.
Segmentation fault
Generating RSA Key...
Generating public/private rsa key pair.
Segmentation fault
Generating DSA Key...
Generating public/private dsa key pair.
Segmentation fault
Fixing permissions on the /tmp directory...
killall: /opt/sbin/sshd: no process killed
Could not load host key: /opt/etc/openssh/ssh_host_rsa_key
Could not load host key: /opt/etc/openssh/ssh_host_dsa_key
Disabling protocol version 2. Could not load host key
sshd: no hostkeys available -- exiting.
postinst script returned status 1
ERROR: openssh.postinst returned 1
Successfully terminated.

How can I make and use a debug build to see what's going on?

(Could this be related to the rtorrent problems reported above?)

@bzhou

would it be possible for you to fix rtorrent? I would be very grateful, its the last piece of my puzzle.

//T