From: leonp@plris.com
To: Ben Elliston <bje@redhat.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Asm files in SN
Date: Mon, 24 Jul 2000 01:16:00 -0000 [thread overview]
Message-ID: <4.3.2.7.0.20000724111125.00b3edc8@plris.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0007240856240.11319-100000@moshpit.cygnus.com>
At 08:57 24/07/2000 +1000, you wrote:
> > Next, I have a small problem with my Linux installation: I
> > created the project which contains files of type *.S - assembler. When
> > I tried to add this files to my target, this didn't work. I was able
> > to add type ASM to build rules in .cfg file, but no more than that.
>Note that the assembly language parser is specifically for PowerPC assembly
>language. It may not manage to detect anything useful in assembly files for
>other targets. It's possible to generate your own, if you really want to.
>What kind of asm files are you trying to parse?
Thank you for reply.
My case is exactly PowerPC CPU.
But my question is not exactly about the parser (which, as I understand,
allows me to parse source code), but about more simple thing - I want to
build my target, which depends on several asm and C files. My attempt to
add an asm file to the target in the Tools->Build Settings->Source
Files->Add files does nothing, totally ignoring my asm files.
Many thanks again.
Leon Pollak
leonp@plris.com
prev parent reply other threads:[~2000-07-24 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <964343111.31392.ezmlm@sources.redhat.com>
2000-07-23 2:23 ` leonp
2000-07-23 15:58 ` Ben Elliston
2000-07-23 21:32 ` Future Development features (was: Asm files in SN) Gilles J. Seguin
2000-07-24 12:48 ` Syd Polk
2000-07-24 1:16 ` leonp [this message]
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=4.3.2.7.0.20000724111125.00b3edc8@plris.com \
--to=leonp@plris.com \
--cc=bje@redhat.com \
--cc=sourcenav@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).