From: Paul Irofti <bulibuta@gmail.com>
To: linux-assembly@vger.kernel.org
Subject: 'defines.h' file not found
Date: Tue, 21 Jun 2005 18:36:30 +0000 [thread overview]
Message-ID: <42B85E2E.2060009@gmail.com> (raw)
i have a question, i just moved to AT&T syntax and linux assembly
programming. getting up-to-date with the new syntax and kernel syscalls
was easy
now i found on a few tutorials, meant to make your way easier on the
transition from intel and win assembly to AT&T and *nix assembly,
reffrences to a defines.h file that had the most numbers for output
souces and such already defined and passed along to a more human kind of
abordation (i.e. $1 gets to be #STDOUT).
my question is if there are this sort of headers standardized and
commonly used in the *nix asm world, or every coder makes his own.
searching google i found thousands of program samples that included the
file but no reffrence was made to it, as though it was a naturaly found
header file on every comp.
any comments on this will be very well apreciated...thanks!
next reply other threads:[~2005-06-21 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 18:36 Paul Irofti [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-22 0:04 'defines.h' file not found Paul Irofti
2005-06-22 0:09 ` Paul Irofti
[not found] ` <d03fdece5c2376836cd3ab3fed1b85ac@sonoma.edu>
2005-06-22 1:54 ` Paul Irofti
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=42B85E2E.2060009@gmail.com \
--to=bulibuta@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.