ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I found a lot of posts regarding this. They talked about Netscape.
I cross-compiled a program from a PC to a SBC. When I ran it, it said "Bus
Just one curious question, if I have lo in disk space, will it
also come up with this error?
When I first compiled this software (Berkeley DB)
, the final executable was a script file. So I copied
.lib/lt-excxx_example_database_read to the SBC, but now the program on
the SBC had this error. So how to resolve it if even the BDB example
failed, I tried , at build_unix ,typing ../dist/configure --enable-cxx
And another thin' is I had configured before with a previous installation of PC Berkeley DB on
the same installation dir. (frankly, I installed many applications carelessly but didn't have time to fix it)
How was that going to affect the cross compiling installation? is it a
good idea to do so?
How do you see what dependencies (packages) on the system and how do
you check disk space?
remarks: My application runs okay on my PC/Linux.
Bus error is usually very close to 'segmentation fault'. The thing is where it actually failed. If you have a debugger, you may try to run the program in it and see where it occurs. Then, looking in the code, you should be able to tell if it makes sense or not. If not, it's probably a compilation problem.
Edit: One more thing... If a program works on PC/Linux, it doesn't mean it wil run on any other platform. Bugs may actually occur on certain platforms, type sizes change (what can cause problems) etc.