Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
http://www.nslu2-linux.org/wiki/Optware/Dns323
The instruction allows you to build cross compilation toolchain and lots of ipk's very easily.
The toolchain build is now fully automated, and builds with host gcc4 as well.
Please test and send feedback to nslu2-linux@yahoogroups.com (or reply here, which packages build and which packages run). Depending on the testing result and user feedback, we may open an official feed.
Cheers,
bzhou at nslu2 dash linux dot org
Last edited by bzhou (2008-03-06 09:00:16)
Offline
zlib does not build, I am looking to a gcc-830-nonhidden.patch
Offline
Hi Bzhou,
I'm currently working on a web front end to ipkg which works with the dns-323 standard web based config pages to allow users to install/remove/manage extra software on the dns-323 without the need for telnet or linux knowledge. I currently have a feed setup that I'm using for devel work so barely contains any ipkgs at present - however I am planning on adding more pretty soon and add an "upload ipkg" web form for others to upload packages (to the testing feed first for safety). All I really have left to do is some ajax code to remove the need to reload the config page after each action (it shouldn't take long but I'm struggling for time at present) and then some documentation.
Anyway, if you manage to compile these ipk's I'll gladly host them on my feed - are you able to choose the "Section" option of individual ipk's with this build method? I'm currently using it to determine if a package is a service, library etc.
Haydn.
Offline
Err I just read the link and it appears to be just for compiling ipkg - not any actual packages... this is already done - search the forum for ipkg.
Offline
You know what compiling ipkg and packages leads to, right?
Feed similar to http://ipkg.nslu2-linux.org/feeds/optwa … /unstable/
Among the dozen of ipkg feeds available here: http://ipkg.nslu2-linux.org/feeds/optware/
Offline
bzhou wrote:
zlib does not build, I am looking to a gcc-830-nonhidden.patch
Ok, fixed zlib build, the toolchain does not like to link using ld, but works if link with gcc.
Offline
bzhou wrote:
You know what compiling ipkg and packages leads to, right?
<embarrassed>er no</embarrassed>
Do you use it to install other peoples ipkg files, or to make your own?
For example, the kissdx home page has an ipkg file listed:
http://kissdx.vidartysse.net/kissdx_0.1 … _armeb.ipk, but I don't think that will run on a DNS323 (it's intended for something called a "Slug"?)
Or am I wrong?
Can I use your tool to make the latest kissdx source in to a binary I can use on my DNS323?
How?
So far I've followed the instructions on http://www.nslu2-linux.org/wiki/Optware/Dns323 down to "make ipkg-opt-ipk"
Offline
sjmac: ipkg is just a simple way of installing/upgrading/removing software - the software still has to be compatible with the host you're installing the software on.
bzhou: Yes - I know ipkg... although you don't need ipkg compiled to install an ipk - just untarring them will do!
Offline
I've just checked most of the feeds at http://ipkg.nslu2-linux.org/feeds/optware and, as I thought, they won't run on the dns-323. The page linked in the FP only tells you how to get ipkg on the dns-323 (which we already have) and then suggests you "Setup a feed".
Offline
The first pass on our autobuild server last night gave the following BROKEN_PACKAGES list
http://trac.nslu2-linux.org/optware/bro … -dns323.mk
In other words, packages not in the list all build fine (962 of them). Some (bash, coreutils, lighttpd, openssh, php, util-linux-ng) are worth spending time to unbreak. Some are known not to build on uclibc platforms.
I'll open the feed soon so ppl can test without requiring them to build first. I don't have a DNS-323, I just think the more platform optware covers, the more people benefit, and it helps improve the quality of optware at the same time.
Offline
HaydnH wrote:
I've just checked most of the feeds at http://ipkg.nslu2-linux.org/feeds/optware and, as I thought, they won't run on the dns-323. The page linked in the FP only tells you how to get ipkg on the dns-323 (which we already have) and then suggests you "Setup a feed".
If you follow the build instruction and most package passes runtime test, we can use our autobuilder to setup an always-up-to-date feed specific for dns-323. (I hinted on the instruction page)
It was never my intention to ask anyone to use other optware feeds on dns-323. The future optware/dns323 feed will be just like all these existing feeds, populated with ipk's.
Last edited by bzhou (2008-03-21 17:56:19)
Offline
HaydnH wrote:
bzhou: Yes - I know ipkg... although you don't need ipkg compiled to install an ipk - just untarring them will do!
Optware patches ipkg and all packages to use /opt as prefix, so it minimizes interference with existing software.
Last edited by bzhou (2008-03-07 18:06:28)
Offline
sjmac wrote:
Do you use it to install other peoples ipkg files, or to make your own?
For example, the kissdx home page has an ipkg file listed:
http://kissdx.vidartysse.net/kissdx_0.1 … _armeb.ipk, but I don't think that will run on a DNS323 (it's intended for something called a "Slug"?)
Or am I wrong?
Can I use your tool to make the latest kissdx source in to a binary I can use on my DNS323?
You can either make your own ipk files/feed, or use other people's ipk files/feed - as long as the ipk files/feed are built specifically for dns-323 (uclibc version, endian, etc).
So you cannot use armeb.ipk above, you cannot use ipk from other optware feed either.
sjmac wrote:
How?
So far I've followed the instructions on http://www.nslu2-linux.org/wiki/Optware/Dns323 down to "make ipkg-opt-ipk"
Thanks for testing out the instruction.
Just try "make kissdx-ipk libdvdread-ipk libjpeg-ipk libiconv-ipk"
kissdx probably is not a good example to try as the first package, since it has some dependency. And i'm not entirely sure whether libiconv needs to be a separate on dns-323 yet.
Look at optware/make/ directory, if a package is not on the broken list in
http://trac.nslu2-linux.org/optware/bro … -dns323.mk
then you have a good chance of building it. Different feed has different broken list, it depends on toolchain quality, upstream package quality, and how hard we tweak in optware.
I don't have a dns-323 myself, so if you can runtime test some packages (such as python25, perl) and report back, it would help.
Offline
Sorry bzhou, I missed the section in your FP titled "Build packages" (DOH!) - I assume these make commands use a cross compiler compatible with the dns-323... also I didn't realise that you were affiliated with the web site you linked and were going to add a dns-323 feed at a later date - I thought you meant you thought the feeds already there were compatible with the dns-323 (again - DOH!).
Anyway - /opt won't work with the dns-323 as this is in rom, the path should be prefixed with "/mnt/HD_a2" (e.g: /mnt/HD_a2/opt or /mnt/HD_a2/ipkg/opt), although this isn;t important as it can be overridden in the ipkg.conf. As I said above, I'm currently creating an extension of the standard web based config pages which allows the user to install/remove/configure packages in ipkg format so I'm extremely interested in this - let me know the feed url when you have it and I'll happily test them.
Haydn.
Offline
HaydnH wrote:
Anyway - /opt won't work with the dns-323 as this is in rom, the path should be prefixed with "/mnt/HD_a2" (e.g: /mnt/HD_a2/opt or /mnt/HD_a2/ipkg/opt) ... let me know the feed url when you have it and I'll happily test them.
Haydn.
Can you bind mount to /opt ? This is quite important, since optware ipkg's all assume /opt as prefix.
It just finished rsync'ing. The feed URL is at:
http://ipkg.nslu2-linux.org/feeds/optwa … /unstable/
If you see the file but wget has error, be patient and allow some time for mirroring.
Both rtorrent and transmission are in the feed, and they're very up-to-date :-)
- bzhou at nslu2 dash linux dot org
Last edited by bzhou (2008-03-07 18:22:08)
Offline
cd /mnt/HD_a2/ mkdir ipkg cd ipkg wget http://ipkg.nslu2-linux.org/feeds/optware/dns323/cross/unstable/ipkg-opt_0.99.163-9_arm.ipk tar -xzf ipkg-opt_0.99.163-9_arm.ipk tar -xzf data.tar.gz mkdir /opt mount --bind /mnt/HD_a2/ipkg/opt /opt export PATH=/opt/bin:/opt/sbin:$PATH
works. i'll give some packets a try.
Last edited by oxygen (2008-03-08 00:40:34)
Offline
HaydnH wrote:
I assume these make commands use a cross compiler compatible with the dns-323...
When I followed the steps in the (page linked from) the first post I noticed that the DNS-GPL files are downloaded from DLink and the toolchain is built (with no manual input - nice).
Offline
I just installed python25 using the ipkg binary I have on my dns-323, python25 returns "R_ARM_PC24: Compile shared libraries with -fPIC!" - looks like the compile for it missed the CFLAGS option... other packages I've tried work though (tree, ltrace, bzip2)...
Offline
HaydnH wrote:
I just installed python25 using the ipkg binary I have on my dns-323, python25 returns "R_ARM_PC24: Compile shared libraries with -fPIC!" - looks like the compile for it missed the CFLAGS option... other packages I've tried work though (tree, ltrace, bzip2)...
Same here with svn, w3m, lynx e.g.:
root@oxygen-nas:~# /opt/bin/svn status R_ARM_PC24: Compile shared libraries with -fPIC!
wget, cvs work
Offline
oxygen - wget is installed as standard on the dns-323 anyway ;P
Offline
Take the new feed as experimental. Your help is needed to make it work.
I'm still not very confident about the newly built toolchain (currently built with host gcc4, and CONFIG_ARM926T).
Someone should try hook up the manually built toolchain from the wiki page under optware/dns323/toolchain/GPL (adjust optware/platforms/toolchain-dns323.mk accordingly) and see if it helps any on the "R_ARM_PC24: Compile shared libraries with -fPIC!" problem.
Sounds very much like: http://dns323.kood.org/forum/p9681-2008 … 40:27.html
We need more developers with dns-323 to work on this.
Last edited by bzhou (2008-03-07 21:13:05)
Offline
Ok, looks like appending " -fPIC" in optware/platforms/toolchain-dns323.mk TARGET_CUSTOME_FLAGS might help.
Offline
I just checked out the latest optware from svn (version 7930), and it looks like you've already added -fPIC, is that right?
BTW, there are two initializations for TARGET_CUSTOM_FLAGS in toolchain-dns323.mk, and one is empty. Is that for the unused case where the build is done on the host platform?
I've built the toolchain using gcc 3.4 (on CentOS 4.4) - I'll have a go a building and installing Perl, 'cos that's pretty harmless ;-) then check out what I really want, which is the kissdx server.
Thanks your help Brian & everyone ...
Offline
sjmac wrote:
I just checked out the latest optware from svn (version 7930), and it looks like you've already added -fPIC, is that right?
BTW, there are two initializations for TARGET_CUSTOM_FLAGS in toolchain-dns323.mk, and one is empty. Is that for the unused case where the build is done on the host platform?
Thanks your help Brian & everyone ...
Yes, I've committed change after testing on utf8proc.mk.
One TARGET_CUSTOM_FLAGS is for native compilation (only placeholder right now); the other one with "-O2 -pipe -fPIC" is for cross compilation.
Have fun! I'm rebuilding the feed with new options.
Offline