From [http://tomatousb.org/forum/t-273081/] Post #9:
I found a lot of packages showed "Bus error" or "Segmentation fault"
> Sounds like you might have LD_LIBRARY_PATH set somewhere - either in one of the profile files, or by some scripts… If so, find it, and get rid of it!
What's the deal with that variable anyway? I spent hours trying to find out why I couldn't mount to /opt without producing
strange terminal behavior.
Initially, after preparing an external hard drive for Optware use I manually mounted /dev/sda1 to /opt and installed the
base ipkg stuff. Then I setup the auto mounting in Tomato's web gui and put in the 'mount -o bind' stuff in the appropriate
The next day after everything was started I'd log in via telnet or ssh and do an 'ls' and just got a red dot.
'ls /bin' got me a red colored "/bin" but no files listed. Later I saw very strange file permissions on the directories that were
just a jumble of characters. So I do a 'ls /bin/*' and get a list of files displayed in all manner of colors and attributes but
there was no problem in actually running, reading or editing programs or files (on the router, not in /opt/bin).
When I unmounted the partitions everything went back to normal. After that I kept playing with mounting via auto mount,
fstab, binding, and symlinking. Any time there was a mount pointing to /opt is when things were screwy.
'umount /opt' would fail with a read-only filesystem error so I had to use 'umount -l /opt'.
Reaching wits end I finished for the night.
Today the same thing but finally the culprit was revealed. When I logged in and ran mount manually there was no problem.
I then sourced /opt/etc/profile and the problem came back. Hmm. Umounted, logged out/in and remounted /opt and
copy/pasted each line for PS1, PATH, and LD_LIBRARY_PATH. No problem until I exported LD_LIBRARY_PATH. Aha!
Then went back to these forums to see if there was any info regarding that variable.
So, what is the deal with that? I didn't think something like that could cause so much trouble for me.
The potential clash is mentioned in the Optware - DD-WRT Wiki but I still wouldn't have made the connection given
the symptoms I was having.
Now I can finally get down to the business of setting up packages and whatnot.