Unslung/WL500g packages available for Oleg's firmware

[rwhitby]

Oleg's latest custom firmware now has support for downloadable packages. The package format is the same "ipkg" format used in OpenZaurus, OpenWRT, OpenSlug, and other embedded linux projects.

The NSLU2-Linux project (www.nslu2-linux.org) has a repository of about 280 packages which have been ported to the Linksys NSLU2 device. That repository of package build source files is called the "Unslung" build system, and it lives in the Unslung CVS repository at http://sf.net/projects/nslu.

We have now modified the Unslung build system to support both the NSLU2 with the "Unslung" firmware, and the WL500g with Oleg's custom firmware. Note that the NSLU2 is an XScale (armeb) device running glibc, whilst the WL500g is a Broadcom (mipsel) device running uclibc, so a number of packages will need further modifications to compile for the WL500g. Also be aware that the startup scripts and configuration files have been designed for the NSLU2, and will probably need modification for the WL500g in many cases.

The current status is that the following packages compile for the wl500g:

adns_1.1-1_armeb.ipk appweb_1.2.3-3_armeb.ipk
automake_1.9.4-2_armeb.ipk bash_2.05b-3_armeb.ipk bc_1.06-1_mipsel.ipk
bind_9.3.0-1_mipsel.ipk bitchx_1.1-final-1_mipsel.ipk
busybox_1.00-8_armeb.ipk bzip2_1.0.2-2_armeb.ipk
ccxstream_1.0.15-1_armeb.ipk classpath_0.13-1_armeb.ipk
coreutils_5.2.1-4_armeb.ipk ctags_5.5.4-1_mipsel.ipk
cyrus-sasl_2.1.20-4_armeb.ipk dhcp_3.0.1-1_armeb.ipk
distcc_2.18.3-1_armeb.ipk dnsmasq_2.15-5_armeb.ipk
dropbear_0.44test4-1_armeb.ipk ed_0.2-1_armeb.ipk
expat_1.95.8-1_armeb.ipk ffmpeg_0.4.9-pre1-1_armeb.ipk
fixesext_2.0.1+cvs20050130-1_mipsel.ipk flac_1.1.2-2_armeb.ipk
fontconfig_2.2.99-2_mipsel.ipk freetype_2.1.9-1_mipsel.ipk
ghostscript_8.50-1_armeb.ipk gift-fasttrack_0.8.9-1_armeb.ipk
gift-gnutella_0.0.10-1_armeb.ipk gift-openft_0.2.1.5-1_armeb.ipk
gift-opennap_20050212-1_armeb.ipk gift_0.11.8.1-1_mipsel.ipk
groff_1.19.1-2_armeb.ipk inetutils_1.4.2-4_mipsel.ipk
iptables_1.2.11-1_armeb.ipk ircd-hybrid_7.0.3-2_armeb.ipk
joe_3.1-1_armeb.ipk jove_4.16.0.65-1_armeb.ipk lame_3.96.1-1_armeb.ipk
libcurl_7.12.2-1_armeb.ipk libdvdread_0.9.4-1_armeb.ipk
libevent_0.9-1_armeb.ipk libgd_2.0.33-2_mipsel.ipk
libid3tag_0.15.1b-1_mipsel.ipk libjpeg_6b-2_armeb.ipk
libogg_1.0-1_mipsel.ipk libpng_1.2.8-2_armeb.ipk
libtool_1.5.10-2_mipsel.ipk libvorbis_1.0-1_mipsel.ipk
lua_5.0.2-1_mipsel.ipk lynx_2.8.5-2_armeb.ipk lzo_1.08-2_mipsel.ipk
m4_1.4.1-1_armeb.ipk make_3.80-1_armeb.ipk man-pages_2.01-1_armeb.ipk
man_1.5p-1_armeb.ipk mc_4.1.35-1_armeb.ipk
mt-daapd_0.2.1.1-1_armeb.ipk nano_1.2.4-1_armeb.ipk
ncftp_3.1.8-2_armeb.ipk openvpn_2.0_rc17-1_mipsel.ipk
patch_2.5.4-2_armeb.ipk pkgconfig_0.15.0-1_mipsel.ipk
portmap_4-2_armeb.ipk postgresql_8.0.1-2_mipsel.ipk
proftpd_1.2.10-4_mipsel.ipk python_2.4-1_mipsel.ipk
recordext_1.13+cvs20050130-1_mipsel.ipk
renderext_0.8+cvs20050130-1_mipsel.ipk tcpwrappers_7.6-2_armeb.ipk
torrent_1.0-1_armeb.ipk ttf-bitstream-vera_1.10-1_mipsel.ipk
vdr-mediamvp_0.1.4-2_armeb.ipk w3cam_0.7.2-1_mipsel.ipk
xau_0.1.1+cvs20050130-1_mipsel.ipk
xdmcp_0.1.3+cvs20050130-1_mipsel.ipk xextensions_1.0.2-1_mipsel.ipk
xproto_6.6.2+cvs20050130-1_mipsel.ipk
xtrans_0.1+cvs20050130-1_mipsel.ipk

[Note that I have tested very few of those packages, so even though they compile, they still may not run correctly. Over time we will sort out which is which.]

If a package listed above has "_mipsel" in the name, then it has been modified to emit an installable ipk correctly targetted for the WL500g. If the package has "_armeb" in the name, it means that it compiles, but still requires a simple (but tedious when there are a lot of them) modification to emit the correct ipk for the WL500g.

You can find out how to build these packages here: http://www.nslu2-linux.org/wiki/Unsl...ckageToUnslung

I presume that someone (perhaps Oleg, or one of the other Chupa administrators) will make the "_mipsel" binary packages available somewhere for direct download. Until that time, you can build them yourself following the instructions referenced above. It's a one line ("TARGET=wl500g") change to the top-level Unslung Makefile to retarget it from the NSLU2 to the WL500g and build the packages.

If someone wants to send me a patch for any or all of the "_armeb" packages above to make them generate the correct ipkg control file, I'll be happy to include that patch in the Unslung CVS repository. All that is involved is updating each package's <foo>.mk file to match the control file generation code in the template.mk file. Simple but tedious.

Note that I do not intend to (nor do I have the time to) update packages that I don't personally need on my wl500g, but I am happy to accept patches from others and apply them to the Unslung CVS repository. For frequent contributors, we should be able to grant write access directly to the repository (remembering that the repository was originally set up for the NSLU2-Linux project, and that remains the primary target for the packages, so any contributed packages need to take that into account). Oleg already has write access, and I expect that at least a couple of other experienced developers here will end up being contributors with write access to the Unslung package repository too ...

-- Rod

[rwhitby]

I presume that someone (perhaps Oleg, or one of the other Chupa administrators) will make the "_mipsel" binary packages available somewhere for direct download.

They are now available at:

http://ipkg.nslu2-linux.org/feeds/unslung/wl500g

That feed will be updated from the list of packages in the WL500G_PACKAGES variable in the Unslung top-level Makefile.

Note that I am not offering to personally support these packages in any way - they are provided on an as-is basis. In particular, I probably will not personally be answering any "how do I use this package" questions. If you wish to make changes or contribute new packages, then follow the instructions at:

http://www.nslu2-linux.org/wiki/Unsl...ckageToUnslung

My hope is that a number of wl500g package developers will take on the task of porting many of the Unslung packages to the wl500g. There are already two developers (Oleg and Jean-Fabrice) who have CVS write access to the Unslung source repository.

-- Rod

[Oleg]

Rod, you've done a great job, I will remove my unslung repository shortly as it's outdated now.
Also, I will update ipkg package, so it would point to the right place and include rc.unslung to it.

[hugo]

Just a quick note about some big package requesting readline, and readline libs. Is it compiling for wl-500, or does it needs more work?

[rwhitby]

Just a quick note about some big package requesting readline, and readline libs. Is it compiling for wl-500, or does it needs more work?

Fixed - there were some packages that were built as required for other packages but had not been converted.

-- Rod

[Oleg]

Several new packages added, including gift plugins, madplay and microperl.
I've removed unslung directory from my server, so from now use this ipkg.conf line:

src unslung http://ipkg.nslu2-linux.org/feeds/unslung/wl500g

[rwhitby]

We have moved the Optware source code repository from sourceforge.net to our new svn.nslu2-linux.org site.

http://svn.nslu2-linux.org/svnroot/optware

You can also browse the source with the nice Trac interface at:

http://trac.nslu2-linux.org/optware

If you are an Optware developer, you need an NSLU2-Linux SSL client certficate to write to the new repository. All sourceforge.net write access has been disabled. Contact me if you need a certificate.

There is no change to the feed contents or location.

-- Rod

[oleo]

After many rip & build cycles, buildroot uClibc toolchain is finished and
ready for testing on mipsel arch.

It provides:

1. uclibc-0.9.28 with wchar support target for base instalation into /opt/lib
2. target toolchain 3.4.6 for packages cross compilation w/ ccache
3. native toolchain for compilation on embeded system w/ ccache
4. uClibc++ 0.2.0 for C++ packages

I have prepared uClibc buildroot toolchain to compile within optware. It
creates both host and target toolchain along with uClibc 0.9.28.
Target uClibc is installed into /opt/lib along with loader ld-uClibc.so

For testing purposes I've prebuild packages at http://www.wlan-sat.com/boleo/optware/oleg

Instalation scenario should be:

1. Prepare /opt directory as usual
2. ipkg.sh update
3. ipkg install ipkg
4. ipkg install uclibc
5. edit /opt/etc/ipkf.conf to src unslung http://www.wlan-sat.com/boleo/optware/oleg
6. ipkg update
7. ipkg install foobar

For people wanting native compiling on router one should install buildroot package instead of uclibc package only. Please note that this should be clean install of /opt packages to prevent search path clashes.

I have tested many packages on stock WL500gx-1.9.2.7-7f-pre4.trx and
confirmed that they works as expected. Native compilation verified.

Many packages now works as intended. Most notable mysql, svn, enhanced-ctorrent, elinks, ...

Here is complete list of 400+ AVAILABLE packages for Oleg firmware for testing: http://www.wlan-sat.com/boleo/optware/oleg/Packages

I am talking to Rod Whitby to provide official support for package download from nslu2-linux.org for Oleg and DD-WRT firmware.

[oleo]

Today official support for Oleg firmwares got additional package feed which completely replaces buggy uClibc 0.9.19 provided in firmware.

The main feature of this packages is that it installs all required files under /opt with 400+ ported applications. With buildroot toolchain is added also system library indenpendence. This means that packages now depends od /opt/lib/uClibc.so and dynamic loader also in /opt/lib with separate /opt/etc/ld-opt.so.conf for custom .so cache. Applications are built with wchar and locale support which makes uClibc library somewhat greater than other uClibc packages, but still far smaller than glibc based aplications.


Buildroot toolchain features:

• GCC 3.4.6
• uClibc 0.9.28 with patches
• uClibc++ 0.2.1
• Native POSIX Threads Library (NPTL) Support for uClibc

Users using package feed should change /opt/etc/ipkg.conf to

src unslung http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable         
dest root /

And then run ipkg update.

First we will install uClibc library which is required by all packages.

~ # ipkg install uclibc
Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/uclibc_0.9.28-1_mipsel.ipk ... 
Connecting to ipkg.nslu2-linux.org[212.18.63.81]:80
uclibc_0.9.28-1_mips 100% |*************************************************************|   440 KB 00:00:00 ETA 
Done.
Unpacking uclibc...Done.
Configuring uclibc...Updating /opt/etc/ld-opt.so.cache
Done.

Alternatively if one wants to have C and C++ compiler to do native compiling on router, ipkg install buildroot can be issued instead. But this requires al least 100MB of free space for the whole toolchain.

Old application from http://ipkg.nslu2-linux.org/feeds/unslung/wl500g should be reinstalled with

ipkg install -force-reinstall package

Tho get a list of installed packages use:

ipkg list_installed

[jensm]

Hi,

I am afraid that I don't have the skills to compile packages myself - anybody interested in having a go at sdparm and sg_start as described in http://www.wl500g.info/showthread.php?t=6197&page=2 ?

Thanks,

Jens

[ptnemot]

Oleo mentions above that he has succeeded in providing an updated uClibc package removing some of the issues with the current uClibc package - which is great news because I'm actually stuck on some of the current packages I want to get compiled because of uClibc issues.

However from the post I can't understand how I am supposed to be using this new package. I am currently compiling packages following the instructions at http://www.nslu2-linux.org/wiki/Unsl...ckageToUnslung, together WL500g recommendations at http://www.nslu2-linux.org/wiki/FAQ/OptwareWl500gBuild and I don't get how I should get the new uClibc from oleo installed (probably because I'm still not very clear on the whole toolchain story). So I'd like to have some concrete guidance on how to use this or if possible a complete step-by-step overview on how to cross-compile C/C++ programs for the WL-500g.

Any help on this would be very much appreciated!

[gdraanen]

Rod (e.a.),

Is there a mechanism/ procedure to request other known packages from e.g. sourceforge to be included in the ipkg list ?

Specifically, I'd like to get libmtp, mtpfs, mtpfsync to be added as an installable package for the wl500g. I am however not a developper !

It will allow me to connect my Creative Zen Vision:M (or any other 'MTP' or 'PlayforSure') device to be connected via usb to the wl-hdd / wl500g.
This means that the mediaplayer can then be accessed through WiFi, can work as external-HDD, and can sync with music dirs on wl-hdd's internal HDD.

Would you ?
Please ?

Gerard.

[oleo]

http://trac.nslu2-linux.org/optware/changeset/5782
adds MTP library for Oleg feed but not for wl500g as it is broken somehow.

Did not find mtpfs, mtpfsync projects on sourceforge. Respond with exact URL locations to source download and project page!

[gdraanen]

Oleo, thank you very much ..... BUT
I have no experience with these 'trunk' files, and your message indicates that the 'build' for the wl500g is broken "somehow".
So... what do I need to do to get a working libmtp on my WL-HDD ?
Can you help me out a little here ?

On the libmtp page
( http://libmtp.sourceforge.net/ )
the mtpsync ( http://www.adebenham.com/mtpsync/ ) and
mtpfs ( http://www.adebenham.com/mtpfs/ ) are mentioned as 'downstream'.
The links show their .tar files

It seems that where mtpsync does the 'obvious', mtpfs may also be needed because it supports r/w of files while allowing determination of the fileTYPE.
This results in the player properly recognizing the video and m3u filetypes, and facilitating a /Playlist directory.

Also, the applications Gnomad2 (http://gnomad2.sourceforge.net/ ) and mtpdude (http://sourceforge.net/projects/mtpdude ) are mentioned.

In looking up info on these, the mtpdude seems a likely candidate for usage as it has a command line based interface (where gnomad2 has a gui ... which is difficult for the wl-hdd)

Thanks for picking up on this,

Gerard.

[oleo]

mtpsync uses gtk and that means that you must run X on router. But xlibraries were not fully ported to uclibc. There are provisions for command line in mtpsync, but sources neeed to be patched to exclude gtk part. This is hard to do as command line is merely convenience feature.
So, no mptsync.

mtpfs uses FUSE userspace filesystem than needs to be included in kernel This could be done by creating custom Oleg firmware as in http://trac.nslu2-linux.org/optware/...rmware-oleg.mk
Kernel 2.4 needs to be patched. Another obstacle, but can be done.

gnomad is another gtk application. no go.

MTPdude also requires gtk. Sorry.