All of lore.kernel.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: linuxppc-dev@lists.linuxppc.org,
	Josh_Hudson@DEWEY.ESD113.WEDNET.EDU (Josh Hudson)
Subject: Re: Assembler Error
Date: Sun, 18 Apr 1999 13:11:40 +0200	[thread overview]
Message-ID: <99041813221000.00903@ns1102.munich.netsurf.de> (raw)
In-Reply-To: fc.000f61e60004dff8000f61e60004dff8.4dffa@DEWEY.ESD113.WEDNET.EDU


Am Sat, 17 Apr 1999 schrieb Josh Hudson:
>When I try to compile big codes with lots of lines I get this:
>
>/tmp/cca00758.s: Assembler messages:
>/tmp/cca00758.s:40303: Error: Bad expression
>/tmp/cca00758.s:40303: Error: Rest of line ignored. First ignored
>character is `M'.
>make: *** [act_comm.o] Error 1  

Any chance you are compiling with -ggdb? If so, turn it into a simple -g option
and it should work.
Another possibility might be that the sources you are trying to compile contain
inline assembler for a non-PPC processor.

If the above isn't true for you, post more information, like the exact options
used to compile the sourcefile, the preprocessed source file and/or the
assembler file. You can get the latter 2 if you add -save-temps to the compiler
options. If you compile a .c/.cc/.C file with -save-temps, you will get
the intermediate .i/.ii (preprocessed) and .s (assembler) files, which
are usually not visible.

Franz.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      parent reply	other threads:[~1999-04-18 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-17 14:26 Assembler Error Josh Hudson
1999-04-17 20:48 ` Gary Thomas
1999-04-18 11:11 ` Franz Sirl [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=99041813221000.00903@ns1102.munich.netsurf.de \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=Josh_Hudson@DEWEY.ESD113.WEDNET.EDU \
    --cc=linuxppc-dev@lists.linuxppc.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.