Re: Linking Assembly Code - Can't resolve printf

2006-09-21 Thread Tony Richardson
David Lariviere columbia.edu> writes: > > Hi Kai, > > Thank you so much. That got it compiling. I had tried it before, being > inspired by the results of objdump on libc.a, but it didn't work at that > point because I hadn't yet read about the importance of ordering the -lc > after the object. I

Re: Linking Assembly Code - Can't resolve printf

2006-09-20 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to David Lariviere on 9/20/2006 1:51 AM: > The code is actually taken out of "Professional Assembly Language" by > Richard Blum. Which is Linux specific. Don't expect it to work on cygwin, because cygwin has a different ABI. > > I presume

RE: Linking Assembly Code - Can't resolve printf

2006-09-20 Thread David Lariviere
-Original Message- From: Kai Tietz [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 3:30 AM To: David Lariviere Cc: cygwin@cygwin.com Subject: Re: Linking Assembly Code - Can't resolve printf Hallo David, Some OS's - as cygwin - expand names by underscores. Therefore simp

Re: Linking Assembly Code - Can't resolve printf

2006-09-20 Thread Kai Tietz
Hallo David, Some OS's - as cygwin - expand names by underscores. Therefore simply write instead of "printf" just "_printf". That should work for this unresolved symbol. But the rest does not seems to be ABI compatible for cygwin. Additionally the entry-point won't work this way ... Chears, i

Re: Linking Assembly Code - Can't resolve printf

2006-09-20 Thread Brian Dessent
David Lariviere wrote: > movl $0, %ebx > movl $1, %eax > int $0x80 > ... > > I've tried linking in numerous libraries, hoping one would resolve printf, > and in numerous order of where to include the -lxxx, but I can't get it to > compile. I've also tried it on numerous co