Thanks for the update... glad it wasn't serious. I've done the non-static thing myself. I suppose there's probably a way we could tell by looking at the binary and print a descriptive error message in the loader, but I've never looked into that.

We already received a patch for fstat64 (and a few other syscalls) last fall... unfortunately we don't have a good way of rolling out minor updates at this point, so it's not released yet. I found the original patch and I'll send it to the list as a stopgap.

We're hoping to move to a good open-source revision control system (probably Mercurial) so that we can host a repository that we can easily push minor updates to so others can track it. This will have to wait until after the 2.0 release though, since we're pretty consumed with that at this point.

Steve

Patrick Meredith wrote:
Oh sorry, I should have posted a follow up to this. It came down to sheer stupidity. I forgot to use the -static flag ;-) It's a bit odd that some other error didn't crop up from that.
You are missing the fstat64 syscall right now, however, I added support for
it by just calling the fstat function for syscall 467. I'll submit a patch to the sourceforge
page soon as I get a chance.  Our Alpha is an ev67 running Linux.

On May 26, 2006, at 8:14 AM, Steve Reinhardt wrote:


This is odd... we have run natively compiled binaries frequently in the past with no problem. M5 gets the entry point from the ELF header, so it shouldn't matter what the symbol name is.

What is your actual Alpha running, Linux or Tru64?

If you got the deadlock message, you must be running FullCPU... does the same thing happen with SimpleCPU?

Steve

Patrick Meredith wrote:
Everything I cross compile and link on my x86 machine runs perfectly, but things that I compile and link on our actual Alpha don't run at all on ALPHA_SE. It never even fetches/executes an instruction, it doesn't do anything except print out the deadlock after xxxx cycles of nothing committing. This is fairly annoying because I don't have any alpha libraries on my x86 machine, and I'd like to avoid having to install them if I can (and I'm wondering if the problem won't crop up again on x86 if I link the libraries, it seems to not like any program where main isn't the first function in the binary). Has anyone else run into this problem?
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
m5sim-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m5sim-users


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
m5sim-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m5sim-users

Reply via email to