All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: [linuxdc-dev] Problem trying to build 2.6.0-test1
Date: Mon, 21 Jul 2003 00:32:24 +0200	[thread overview]
Message-ID: <20030720223224.GJ26422@fs.tum.de> (raw)
In-Reply-To: <200307201500.46604.adrian@mcmen.demon.co.uk>

On Sun, Jul 20, 2003 at 03:00:46PM +0100, Adrian McMenamin wrote:
> This is a message I posted to the Dreamcast linux development list. It appears 
> to be a problem with the cross assembler (target is SH4, host is ia32) I am 
> using but before I put it down to that, I wonder if anybody else has seen 
> this and can offer a comment?
> 
> It is certainly not a configuration problem as the SH4 maintainer has built 
> this kernel for the Dreamcast (he's probably the only one apart from me to 
> have even tried :() and when I used his .config it failed in just the same 
> way.
>...
>   AS      usr/initramfs_data.o
> usr/initramfs_data.S: Assembler messages:
> usr/initramfs_data.S:2: Error: Unknown pseudo-op:  `.incbin'
> make[2]: *** [usr/initramfs_data.o] Error 1
> make[1]: *** [usr] Error 2
> make: *** [vmlinux] Error 2

You need more recent binutils.

Documentation/Changes lists 2.12 as the minimum required version.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2003-07-20 22:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 14:00 Fwd: [linuxdc-dev] Problem trying to build 2.6.0-test1 Adrian McMenamin
2003-07-20 22:32 ` Adrian Bunk [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=20030720223224.GJ26422@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=adrian@mcmen.demon.co.uk \
    --cc=linux-kernel@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.