​​​​​Posted: Tue Sep 25, 2007 11:17 am Post subject: Precompiled Linux (Debian Etch) Mipsel binaries(bytecode)

UPDATED
I have compiled (for fun) static cores running on an emulated system.
Please test this cores, if you are experiencing problems(DNS resolution problems or simply core fails to start) you can try with few tricks explained below.
I have build a collection of cores with different configure options, in this single giant archive.
Let's choose the release tarball which fits your needs in subfolders, i have also included my shared libraries (in case you need them):

Code:
full networks:ed2k-bittorrent-directconnect-FileTP Library disabled:none SUI enabled normal networks:ed2k-bittorrent-FileTP Library disabled:Libgd,libmagic SUI disabled normal_gd networks:ed2k-bittorrent-FileTP Library disabled:libmagic SUI disabled minimal networks:ed2k Library disabled:Libgd,libmagic SUI disabled libraries: This archive contatins my own needed libraries.(for static core too) Please TEST these cores, and give me suggestions-feedback. Hope useful. fabtar IMPORTANT NOTE(linkstation users?). Mlnet.static still needs a bunch of shared libraries. In case you are experiencing DNS resolution or libraries problems, I have added my libraries to the archive (there are sometimes libc problems or lacking libraries). THERE ARE 2 WAYS TO SOLVE DNS PROBLEMS 1) I have added my needed shared libs in the main archive.Copy them in(example) /new_libs_path I suggest to create a little script which sets this enviroment variable first to call mlnet (Thanks Georg for testing!):
Code:
LD_LIBRARY_PATH=/new_libs_path:$LD_LIBRARY_PATH export LD_LIBRARY_PATH /path_to_mldonkey/mlnet.static
(*I think*) This starts the static linked mlnet after setting the LD_LIBRARY_PATH environment variable as needed. And the variable is only set for the call of mlnet, thus the remainer of the installation is not affected. This will luckly cause to first call my libraries first of your ones. This is an hard hack. Another command in order to obtain the same result:
Code:
LD_LIBRARY_PATH=/new_libs_path:$LD_LIBRARY_PATH ./mldonkey_path/mlnet (arguments?)
2) You can also try launching mldonkey chrooted, providing my libraries: http://mldonkey.sourceforge.net/Chroot for linkstation's users Togeis's chroot walkthru: http://forum.nas-central.org/viewtopic.php?f=19&t=3682&st=0&sk=t&sd=a&start=30. P.s.: I think these cores should work if you have a debian linux. For NO-DEBIAN users, if you have problems please look at this libraries in your system:
Code:
/lib/libresolv.so.2 /lib/libnss_dns.so.2 /lib/ld.so.1 /lib/libc.so.6 /lib/libnss_files.so.2
If these libraries has different names on your system, you can try to create symoblic links with these names pointing to your current ones. for example could be: /lib/ld.so.1 -> /lib/ld.linux.so.3 _________________ Mldonkey Debian cores, ARM: http://mldonkey.sourceforge.net/forums/viewtopic.php?p=26582#26582 PowerPC: http://mldonkey.sourceforge.net/forums/viewtopic.php?t=4834 Mipsel: http://mldonkey.sourceforge.net/phpBB2/viewtopic.php?p=27075#27075​​​​​ Last edited by fabtar on Sun Oct 21, 2007 9:20 pm; edited 4 times in total