From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cbf123@mail.usask.ca>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: error compiling ptrace in current mainline git
Date: Sat, 13 Jul 2013 09:03:45 +1000 [thread overview]
Message-ID: <1373670225.19894.211.camel@pasglop> (raw)
In-Reply-To: <51E02E7D.5050304@mail.usask.ca>
On Fri, 2013-07-12 at 10:27 -0600, Chris Friesen wrote:
> Hi all,
>
> I'm trying to build current mainline git with gcc version 4.4.1 as a
> cross compiler and I'm getting the following:
>
>
> CC arch/powerpc/kernel/ptrace.o
> {standard input}: Assembler messages:
> {standard input}:1619: Error: junk at end of line: `1'
> {standard input}:2074: Error: junk at end of line: `1'
> {standard input}:2742: Error: junk at end of line: `1'
> {standard input}:2855: Error: junk at end of line: `1'
> {standard input}:2943: Error: junk at end of line: `1'
> {standard input}:4699: Error: junk at end of line: `1'
> {standard input}:4794: Error: junk at end of line: `1'
> {standard input}:4915: Error: junk at end of line: `1'
> {standard input}:4985: Error: junk at end of line: `1'
> {standard input}:5087: Error: junk at end of line: `1'
> make[2]: *** [arch/powerpc/kernel/ptrace.o] Error 1
> make[1]: *** [arch/powerpc/kernel] Error 2
> make: *** [sub-make] Error 2
>
>
> Any ideas on how to deal with this? Is this a code error or a compiler
> error?
Can you send the .s and .i files ? Also you can try with newer compilers
(there are some cross compilers on kernel.org)
Cheers,
Ben.
next prev parent reply other threads:[~2013-07-12 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 16:27 error compiling ptrace in current mainline git Chris Friesen
2013-07-12 22:31 ` Tony Breeds
2013-07-12 23:40 ` Chris Friesen
2013-07-12 23:03 ` Benjamin Herrenschmidt [this message]
2013-07-12 23:44 ` Chris Friesen
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=1373670225.19894.211.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=cbf123@mail.usask.ca \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).