X-Spam-Check-By: sourceware.org Message-ID: <4510EC58.188C303D@dessent.net> Date: Wed, 20 Sep 2006 00:23:04 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Linking Assembly Code - Can't resolve printf References: <001d01c6dc83$fd77ef40$6cc027a0 AT davidiandesktop> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 computers, including those with a > first-time fresh install of cygwin. Compiling a simple helloworld C program > works fine. Even if you were able to resolve printf this code will never work. Int 0x80 is how syscalls work on linux but it is completely different under Windows. Cygwin offers API not ABI compatibility. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/