On Fri, 2006-12-22 at 13:05 -0600, Kenton Brede wrote: > I tried that and the output of gcc gave me enough information that I > was able to get the prog to compile on the system. Another program you may find useful is objdump -d myProg where "myProg" is the name of your executable. This will give you a disassembled view of your program as it looks in memory. You can see where the external library functions are called, etc. It's a long display, so pipe it through more or less. - To unsubscribe from this list: send the line "unsubscribe linux-assembly" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- suffix or operands invalid for
- From: Kenton Brede
- Re: suffix or operands invalid for
- From: Frank Kotler
- Re: suffix or operands invalid for
- From: Kenton Brede
- Re: suffix or operands invalid for
- From: Robert Plantz
- Re: suffix or operands invalid for
- From: Robert Plantz
- Re: suffix or operands invalid for
- From: Kenton Brede
- suffix or operands invalid for
- Prev by Date: Re: suffix or operands invalid for
- Next by Date: AsmIDE release
- Previous by thread: Re: suffix or operands invalid for
- Next by thread: Re: suffix or operands invalid for
- Index(es):