Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jeff Harrell <jharrell@ti.com>
To: linux@cthulhu.engr.sgi.com
Cc: bbrown@ti.com
Subject: C/Assembler listing files
Date: Mon, 03 Jan 2000 15:36:03 -0700	[thread overview]
Message-ID: <38712453.B0BCE0CD@ti.com> (raw)

Has anyone tried to generate an interleaved C and Assembler listing file
with
the MIPS cross compilation tools?  I tried to pass the following flags
to gcc
(and the assembler):

-Wa,-ahl=file.txt

I get the following errors:
--------------------------------------------------------
mips-linux-gcc -D__KERNEL__ -I/home/jharrell/work/mips_linux/include
-Wall -g -Wa,-alh=signal.lst  -Wstrict-prototypes -O2
-fomit-frame-pointer  -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips3
-pipe   -DEXPORT_SYMTAB -c signal.c
signal.c: In function `dequeue_signal':
signal.c:106: warning: assignment from incompatible pointer type
signal.c:107: warning: assignment from incompatible pointer type
{standard input}: Assembler messages:
{standard input}:541: Fatal error: Symbol signals_init already defined.
signal.c: In function `sys_rt_sigprocmask':
signal.c:698: output pipe has been closed
cpp: output pipe has been closed

---------------------------------------------------------------

If I remove the  "-Wa,-ahl=file.txt" the kernel compiles with no
errors.  I attempt a
similar type of command on the x386 version of gcc and it seems to
work.  Is this a
command that is not supported on the MIPS cross-compilation tools?  Any
information
on this would be greatly appreciated.


Thanks,
Jeff Harrell

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeff Harrell                    Work:  (801) 619-6104
Broadband Access group/TI
jharrell@ti.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

             reply	other threads:[~2000-01-03 22:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-03 22:36 Jeff Harrell [this message]
2000-01-04  1:43 ` C/Assembler listing files Ralf Baechle

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=38712453.B0BCE0CD@ti.com \
    --to=jharrell@ti.com \
    --cc=bbrown@ti.com \
    --cc=linux@cthulhu.engr.sgi.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