Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well, after I worked out some problems with libsdl, I ran ./configure gmake and gmake install and everything went fine. The program works perfectly and I didn't receive any errors. This was done on a mandrake box. I'm now going to try it on knoppix, suse, and then freebsd to see if I can figure it out.
At this point, I think your problems have something to do with nasm. This addrni.o/.asm seems to be causing a segfault in nasm. Do you think you can tell me what version of nasm you're using? Also, maybe trying a different version may help, but wait on that because I'm not quite sure yet.
So I'm going to wait to you tell me what version of nasm you have so I can install and see if that is causing the segfault, and until then I'll compile zsnes on as many different types of machines as possible.
Originally posted by Inexactitude Well, after I worked out some problems with libsdl, I ran ./configure gmake and gmake install and everything went fine. The program works perfectly and I didn't receive any errors. This was done on a mandrake box. I'm now going to try it on knoppix, suse, and then freebsd to see if I can figure it out.
At this point, I think your problems have something to do with nasm. This addrni.o/.asm seems to be causing a segfault in nasm. Do you think you can tell me what version of nasm you're using? Also, maybe trying a different version may help, but wait on that because I'm not quite sure yet.
So I'm going to wait to you tell me what version of nasm you have so I can install and see if that is causing the segfault, and until then I'll compile zsnes on as many different types of machines as possible.
Hey thanks i really appreciate you trying to help, my current version of nasm is:
"NASM version 0.98.37 compiled on Sep 5 2003"
Sorry, I haven't been able compile the program on another system yet.
It seems my version of nasm is only about a month older than yours:
Code:
NASM version 0.98.38 compiled on Oct 13 2003
Maybe I'm wrong about nasm, since our versions are probably almost identical. Maybe it's gmake itself. I'm using version 3.80, check to see what version you're using. Are you getting the error as soon as you execute gmake or is it working for a while and then giving you the error?
As I said, I'm going to compile this program on all my different machines tonight and see if I can figure out what the problem is. I just wish that I had a slackware box so I can have an environment more similiar to yours.
You said you worked out a problem with libSDL. Can you go into detail on that?
I'm having trouble getting Freevo outputting to dfbmga (direct framebuffer for my Matrox G400), and my friend thinks it's an SDL issue, but we can't figure it out. Maybe fixing the SDL problem can kill two birds.
Last edited by ultrabomberman; 07-13-2004 at 09:19 AM.
For me, the configure script couldn't locate the sdl-config script, which I didn't have because the version of sdl installed with my operating system seemed a little messed up. After that I just compiled SDL from source, and everything worked fine. This isn't going to do much for you, but it may very well help your friend out if he/she is indeed having problems with SDL.
Well, I was successful in my attempts to compile it on knoppix. I compiled it using nasm 0.98.36, so I guess it doesn't have anything to with nasm. Right now, I'm basically totally stumped. If you want, I can make the binary that I compiled available to you, and it should work decently. Email if you want me to do that.
I'm sorry, but for now I don't know what to say. I'll try it in a bsd setup and see what happens. I'll play around with some environments and see if I can pinpoint the problem.
Well that basically tells us that the problem lies with software provided by the Slackware 9.1 distrobution. Once we can figure out what piece of software is the problem, we can probably just recompile that particular package and then things would be going good. This is a problem though, since it's sort of hard to figure out what exactly is causing the problem here. It's either gmake, nasm or gcc. What makes me think it's nasm is that it's an assembly file which it is stumbling on. Still, it can be gmake. My course of action would be to compile a new version nasm, and if it continues, to compile a new version of gmake. This can lead to a lot of work however, but from what I see now seems like the only thing to do, especially since I can't replicate the error myself and use my own machines to test it.
As I said before, if you want I'll make the binaries I compiled available to you, just email me and I'll set it up.
I have to say, this is some of the strangest source I've ever seen. It compiles on some things, and not on others, for seemingly no reasons. Well, at least everyone seems to have it working now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.