MLDonkey Forum Index
Homepage •  Bugs •  Tasks •  Patches •  SF.net Project Page •  ChangeLog •  German forum •  Links •  Wiki •  Downloads
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Precompiled Linux (Debian Etch) ARM cores binaries-release
Goto page 1, 2, 3 ... 21, 22, 23  Next
 
Post new topic   Reply to topic    MLDonkey Forum Index -> Alternative platforms
View previous topic :: View next topic  
Author Message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Tue Aug 07, 2007 2:35 pm    Post subject: Precompiled Linux (Debian Etch) ARM cores binaries-release Reply with quote

I like to thank QNAP Sytems for actively supporting my initiative! QNAP Systems has sent to me a generous gift:
http://www.qnap.com/pro_detail_feature.asp?p_id=85
A powerful&wonderful QNAP 409 Pro! I have a real ARM developement enviroment and a low-power server.
Thank again to QNAP Systems and Ivan Hsu


UPDATED
I have compiled (for fun) static cores on a Debian Etch/Lenny running on an emulated ARM system.
The cores can run effectively on a real Linux-ARM system (about linkstations please read below) but feedback is appreciated.
My binaries are been tested with sucess on on these boxes:

S3C2410 board (arm9+linux)
Linkstation Pro/Live (?) (few positive feedbacks, no known version/firmware)
ARM-9 platform using montavista and LSI SOC chip
QNAP ts-109
Qnap TS-109 Pro II
mybook world edition I, with 01.01.18 firmware (it uses an embedded linux version)
Thecus N2100 chemist have developed a module for this platform
nslu2 and debian lenny
S3C6410
Zyxel NSA-310 (Armel)


I have build a collection of cores with different configure options, in a single giant archive:

NOTE: cores have been compiled both in native and bytecode version. Native is the quicker one, bytecode is provided in case you have problems.
Feedback is appreciated.


Brand new version Mldonkey 3.1.3 arm alias OLDABI (etch)
please refer to the "arm" release. Released both in native (very quick) and bytecode.

Brand new beta version MLdonkey 3.1.3 armel alias EABI (Lenny)
please refer to the "armel" release. Released both in native (very quick) and bytecode.

All the cores are here (new hosting thanks to ygrek):
http://fabtar.ygrek.org.ua/

Qnap NAS installation:
Qnap users has an alternate and easier mldonkey installation, they should use the automated QPKG pakage management (new firmwares):
http://www.qnap.com/pro_features_QPKG.asp
http://www.qnap.com/faq_detail.asp?q_id=461

OLDABI or EABI?
They are different "architectures": your linux's kernel could be compiled with different features.
EABI is cutting edge, in case you have an old and not updated arm box OLDABI is(probably) the right core for you.
Linkstations have sometimes cuttin' edge kernels with EABI.
When in doubt you can simply try the different cores looking for the best working one.

Let's choose the release tarball which fits your needs in subfolders!
The archive contains a lot of directories, inside these directories there are complete ready to use mldonkey's tarballs.
These tarballs have various features, there are heavy cores with all the fetures bundled in, and light cores with minimal features for tiny boxes.
You have to choose the core which fits your needs!

full
Enabled networks:ed2k-bittorrent-directconnect-FileTP
Library disabled:none - SUI enabled
Upnp: enabled
normal
Enabled networks:ed2k-bittorrent-FileTP
Library disabled:Libgd,libmagic - SUI enabled
normal_gd
Enabled networks:ed2k-bittorrent-FileTP
Library disabled:libmagic - SUI enabled
minimal
Enabled networks:ed2k
Library disabled:Libgd,libmagic - SUI disabled

libraries This archive contatins my own needed libraries.(for static core too)
Upnp libraries are under the /patch subfolder.. let's copy these libraries too when needed.

This is about the compilation enviroment & version:

OABI configuration on etch
Code:

Compilers:
 - Ocaml version     3.12.0
 - gcc version       4.1.2
 


EABI configuration on Lenny
Code:

Compilers:
 - Ocaml version     3.12.0


Please give me suggestions-feedback.
I think I'll keep compiling this cores.
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, it is better to use only when you have reserved a users for mldonkey's sake.
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.

Both ways has been reported to work properly on linkstations.

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


LOCALES ISSUES ( _____.avi )

I have tried to solve this issue by patching the CVS sources in order to force UTF8 charset. Some users have used patched cores with success please try the cores and give feedback.

-OLD SOLUTION (obsolete)
About solving locales problems with chinese and other languages:
for example:
_____.avi

this post could be useful:
http://forum.qnap.com/viewtopic.php?f=87&t=654&start=135

This is focused on qnap 109-209 but on toher boxes the problem could be tracked in a similar ways.
You need to install on your box the majority of locales mappings.
Perhaps in future realese I'll try to add locales data containted in deb files.
This 'll permit to power users to easily fix locales problem(when arises)-[/url]


Last edited by fabtar on Sat Nov 24, 2012 8:42 am; edited 72 times in total
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Thu Aug 09, 2007 11:14 am    Post subject: Reply with quote

+ do you like other cores options/combinations... tell me.
+ please give me feedback&suggestions&observations

I don't think fasttrack is a useful network, plus gnutella's plugin is a bit junky at the moment.

P.s: I think I'll do the same for PowerPC architecture, are Linkstation PPC using debian too?


Last edited by fabtar on Fri Sep 07, 2007 7:13 pm; edited 1 time in total
Back to top
View user's profile Send private message
Kasei99
neophyte


Joined: 10 Sep 2006
Posts: 37
Location: Germany

PostPosted: Thu Aug 09, 2007 11:57 am    Post subject: Reply with quote

Hello there,

tried your static build from the other thread on my linkstation(arm9 bigendian) and SUI wonīt work.

--Buildinfo--
Version: MLNet Multi-Network p2p client version 2.9.0.CVS
SCM version: 2007-08-07 11:05:23
Networks: Global Shares Direct Connect Fasttrack FileTP BitTorrent Donkey (SUI)
Ocaml version: 3.09.2 - C compiler version: 4.1.2 - C++ compiler version: 4.1.2
Built on: Linux armv5tejl 2.6.18-4-versatile (little endian) with glibc 2.3.6
Features: threads zlib-1.2.3 bzip2-1.0.3 gd(jpg/png-1.2.15) iconv(active) magic(active) no-check-bounds

iirc there was a bug in ocaml regarding the arm emulated fpu which should be fixed in 3.10. Sadly its not even in the unstable debian branch yet:
http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=ocaml

As far as i know both arm and ppc linkstations use either debian or gentoo.

I do appreciate your efforts Surprised
Back to top
View user's profile Send private message
spiralvoice
Sage


Joined: 06 Jan 2003
Posts: 3999
Location: Germany

PostPosted: Thu Aug 09, 2007 12:15 pm    Post subject: Reply with quote

Kasei99 wrote:
linkstation(arm9 bigendian) and SUI wonīt work.

fabtar wrote:
Built on: Linux armv5tejl 2.6.18-4-versatile (little endian) with glibc 2.3.6

A little endian binary on a big endian machine will never work well.
I am surprised that it started at all Wink
_________________
Link overview and precompiled cores here: http://mldonkey.sourceforge.net/DownloadLinks
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Thu Aug 09, 2007 1:07 pm    Post subject: Reply with quote

Thx Kasei99 for feedback,
I have heard that debian-arm is little-endian only, I'll post in linkstation wiki to inspect on this, Have you debian?

Plus I have to ask into qemu forum how to emulate big-endian machine (or is ARM low/big endian at same time and depends only on OS?)

Fisrt self answer: http://www.debian.org/ports/arm/
Tehre are 2 debian releases: low endian and big endian
Second answer, I have both a low endian Arm-Qemu and BE Arm-qemu, they are separate emulators.
I fear I need to install another ARM-Debian installation. Very Happy
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
Kasei99
neophyte


Joined: 10 Sep 2006
Posts: 37
Location: Germany

PostPosted: Thu Aug 09, 2007 1:21 pm    Post subject: Reply with quote

Well actually arm9 does support both little and big endian byte ordering but most of the xscale processors usually have only big endian mode enabled because its not that easy to keep the core endian neutral for whatever reasons.

Guess i confused the two endianesses, sorry Embarassed
http://mldonkey.sourceforge.net/forums/viewtopic.php?t=4636&start=0

In any case i got higher cpu load with this binary (~0.7 to ~0.4) but the speed is ok (BT ~250kB/s atm).

Yes im running debian on my box.

http://www.arm.com/products/CPUs/ARM926EJ-S.html
This is the processor from the Linkstation Pro/Live but i canīt see whether it supports both or just one endian.
Back to top
View user's profile Send private message
spiralvoice
Sage


Joined: 06 Jan 2003
Posts: 3999
Location: Germany

PostPosted: Thu Aug 09, 2007 2:55 pm    Post subject: Reply with quote

Kasei99 wrote:
In any case i got higher cpu load with this binary (~0.7 to ~0.4) but the speed is ok (BT ~250kB/s atm).

Known problem if you set share_scan_interval = 0, fixed in CVS
_________________
Link overview and precompiled cores here: http://mldonkey.sourceforge.net/DownloadLinks
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Thu Aug 09, 2007 3:09 pm    Post subject: Reply with quote

The last cores, I have posted, are bleeding edge CVS Very Happy
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
spiralvoice
Sage


Joined: 06 Jan 2003
Posts: 3999
Location: Germany

PostPosted: Thu Aug 09, 2007 9:09 pm    Post subject: Reply with quote

@fabtar: If your cores are proven to work I am considering to give
you upload rights to MLDonkey Sourceforge project page.

There is a page about release guidelines for official binaries
which you could read through if you are interested in becoming
an official provider for MLDonkey binaries.
Interesting for you would be the part with the official build commands:
Quote:
* build binaries

Code:
./configure --enable-checks
make release.mlnet.static
make release.utils.static

As I never used ARM hardware/emulation I would like to know
which filenames are chosen by configure/make.
_________________
Link overview and precompiled cores here: http://mldonkey.sourceforge.net/DownloadLinks
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Fri Aug 10, 2007 7:54 am    Post subject: Reply with quote

Thanks,
I appreciate a lot, I like to contribuite more to Mldonkey's community.
I'm going to read guidlines this afternoon.
I'll post again this evening, I hope to be able to understand and follow the official release policy.
I am also waiting for more feedback from mldonkey and linkstation 's comunities in order to completely prove core's reliability.

P.s:I'm trying to set up a PowerPC emualted system.
But PowerPC emulators (QEMU too) sucks! Sad Very Happy
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Fri Aug 10, 2007 9:13 am    Post subject: Reply with quote

@Spiralvoice
In guidelines you mention the sarge distribution.
On my arm system I have installed a debian etch (stable), I am supposed to install a sarge?
You also decided for mlnet.static release.A question arises: to distribuite shared cores is useless? Since now, I have done .distri releases and I'm a bit curious on this point.
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
spiralvoice
Sage


Joined: 06 Jan 2003
Posts: 3999
Location: Germany

PostPosted: Fri Aug 10, 2007 10:15 am    Post subject: Reply with quote

fabtar wrote:
In guidelines you mention the sarge distribution.
On my arm system I have installed a debian etch (stable), I am supposed to install a sarge?

No, the reason I am using Sarge for i386 cores is a historic one, but
you can use Etch if you like. The archive filename should reflect
this in the glibc version number. Which filenames do the produced
archives have?
fabtar wrote:
You also decided for mlnet.static release.A question arises: to distribuite shared cores is useless?

Not useless, but it requires users to have the same set of shared libs
than you, this means libbz2.so, libstdc++.so.6, libgd.so and so on.
Providing a statically linked core produces less bug reports from users Wink

On Mac OS X and Solaris its not possible to statically link mlnet
because they lack some .a (static version of .so libs) libs. When
you search the Mac OS X area here you will find frequent reports
of missing libraries. Distributing static cores reduces forum traffic Twisted Evil
_________________
Link overview and precompiled cores here: http://mldonkey.sourceforge.net/DownloadLinks
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Fri Aug 10, 2007 4:09 pm    Post subject: Reply with quote

spiralvoice wrote:
. Which filenames do the produced
archives have?

The generated names are:
Code:
mldonkey-2.9.0.static.arm-Linux_glibc-2.3.6.tar.bz2
mldonkey-tools-2.9.0.static.arm-Linux_glibc-2.3.6.tar.bz2

You have suggested a plain ./configure but
Have I to disable SUI compilation ? (since the ocalm SoftArm support is fixed?)
Or have I to compile SUI? (final user has to enable/disable SUI by options)
What do you prefer?

I think I have to provide binaries exactly from the last release, so I have downloaded the 2.9.0 sources form sourceforge and compiled.
I also think to keep providing CVS cores here in this thread.
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Fri Sep 07, 2007 7:14 pm    Post subject: Reply with quote

First post updated with new binaries/instructions/notes
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
fabtar
Sage


Joined: 04 Feb 2004
Posts: 1580
Location: Italy

PostPosted: Thu Sep 13, 2007 6:22 pm    Post subject: Reply with quote

updated
_________________
ARM,ARMEL,MIPS,MIPSEL,POWERPC mldonkey cores: http://fabtar.ygrek.org.ua/
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    MLDonkey Forum Index -> Alternative platforms All times are GMT
Goto page 1, 2, 3 ... 21, 22, 23  Next
Page 1 of 23

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Sourceforge.net Logo