Hi,

I compiled last version of amule (v2.3.1) and wxbase (v2.8.12), in order to have it running on my WZR-HP-AG300H, with Attitude Ajustment r30878.

No problem with compile, when I try to run amule I have this error

root@OpenWrt:/etc# amuled start
 2012-03-10 22:17:31: Initialising aMuleD 2.3.1 compiled with  v2.8.12
!2012-03-10 22:17:31: Invalid eD2k link "start" - ERROR: Not a valid ed2k-URI
 2012-03-10 22:17:31: Checking if there is an instance already running...
 2012-03-10 22:17:31: No other instances are running.
!2012-03-10 22:17:31: ERROR: WARNING Warning! You are running aMule as root.
!2012-03-10 22:17:31: Doing so is not recommended for security reasons,
!2012-03-10 22:17:31: and you are advised to run aMule as an normal
!2012-03-10 22:17:31: user instead.

--------------------------------------------------
Warning! You are running aMule as root.
Doing so is not recommended for security reasons,
and you are advised to run aMule as an normal
user instead.
--------------------------------------------------

amuled: can't resolve symbol 'atexit'

I tried also normal amule 2.2.6 from packages, both from trunk and last backfire, with same error (backfire give me a little different one, but result is the same)

What this error means? is an environment error (so I can open a ticket) or is my error that i can fix?

Thanks
FunMan

(Last edited by FunMan on 11 Mar 2012, 13:41)

I would suspect that the configuration of your libc differs between your buildroot and your router. At least in uClibc there is a config option for visible atexit support.

Can you tell me more about it? how can i verify it?

I have a trunk compiled on my router, but some packages are compiled with backfire buildroot due to several segmentation fault i obtain with trunk....

Thanks
FunMan

I'm not a OpenWRT developer...

But I would suspect this changeset: https://dev.openwrt.org/changeset/25517

So you will need to switch this option back.

Ok,

so I should revert back that changeset and recompile and reflash device, right? If I have to do so, there is a way to mantain my extroot configuration, if you know (i read that you're not an openwrt developer)?

Thanks
FunMan

I resolved compiling with compact_atexit enabled.

Thanks
FunMan

It should be fixed in amule instead. Adding unnecessary bloat to libc for a rarely used package is not a good solution.

I was trying to run twonky media server (twonky-mipseb-uclibc-0.9.28-special-7.0.8), but it throws: "can't resolve symbol 'atexit'". Would it be as simple as reverting https://dev.openwrt.org/changeset/25517 to enable the backwards compatibility?

I don't expect binaries compiled for a different uclibc version to work properly.