linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Plantz <plantz@sonoma.edu>
To: A D <a_d_249@hotmail.com>
Cc: jylam@lnxscene.org, linux-assembly@vger.kernel.org
Subject: Re: GAS colorr pixel problem
Date: Wed, 22 Nov 2006 14:45:21 -0800	[thread overview]
Message-ID: <1164235521.5255.62.camel@ubuntu> (raw)
In-Reply-To: <BAY22-F33AC6FFC9C9C95246563DF5E30@phx.gbl>

On Wed, 2006-11-22 at 16:08 -0500, A D wrote:
> Again my thanks goes to Jean-Yves Lamoureux and all the forum members. That 
> is all i wanted to know.
> 
> --STeve

Also, if you use C libraries for your I/O, you can assemble your
assembly language source files with
   as --gstabs -o foo.o foo.s
where --gstabs gives you debugging symbols. Then use gcc to
link your object file(s), even if you have only one file:
   gcc -o myProg foo.o

gcc recognizes that the input file is already an object file,
so it goes directly to the linking phase. The advantage of
doing it this way instead of using ld is that gcc will
automatically find the C libraries for you. If you use
ld, you need to explicitly list the C libraries.



  reply	other threads:[~2006-11-22 22:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BAY22-F18087E5BEE37FFA472DDD5F5E30@phx.gbl>
2006-11-22 20:38 ` GAS colorr pixel problem Jean-Yves Lamoureux
2006-11-22 21:08   ` A D
2006-11-22 22:45     ` Robert Plantz [this message]
2006-11-22 23:06   ` Frank Kotler
2006-11-22 20:35 A D
2006-11-22 20:59 ` Claudio Fontana
  -- strict thread matches above, loose matches on Subject: below --
2006-11-22 18:54 A D
2006-11-22 19:33 ` Robert Plantz
2006-11-22 19:44   ` Markus Rechberger
2006-11-22 19:49     ` Jean-Yves Lamoureux
2006-11-22 19:42 ` Jean-Yves Lamoureux
2006-12-31 18:43 ` Hendrik Visage
2007-01-01  2:36   ` Claudio Fontana

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1164235521.5255.62.camel@ubuntu \
    --to=plantz@sonoma.edu \
    --cc=a_d_249@hotmail.com \
    --cc=jylam@lnxscene.org \
    --cc=linux-assembly@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).