Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: K.H.C.vanHouten@kpn.com
Cc: Adrian Bunk <bunk@fs.tum.de>,
	linux-mips@oss.sgi.com, K.H.C.vanHouten@research.kpn.com
Subject: Re: Compile error with current CVS kernel
Date: Tue, 13 Mar 2001 14:53:30 +0100	[thread overview]
Message-ID: <20010313145330.A1208@bacchus.dhis.org> (raw)
In-Reply-To: <200103130746.IAA07580@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com on Tue, Mar 13, 2001 at 08:46:43AM +0100

On Tue, Mar 13, 2001 at 08:46:43AM +0100, Houten K.H.C. van (Karel) wrote:

> I get the same error on a native compile:
> gcc version 2.95.3 19991030 (Maciej's src)
> binutils version 2.11.90 (from CVS)
> kernel source 2.4.0-test9 (from oss CVS)
> 
> I've attached my objdump output.
> Hope this helps.

Not necessary, Adrian already sent his output.  The fix isn't difficult
either, it's just putting .modinfo into the linker script also.  The
question is still why newer ld is placing sections be default so absurdly
which is what I'm currently enquiring.

  Ralf

  reply	other threads:[~2001-03-13 13:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-12 21:56 Compile error with current CVS kernel Adrian Bunk
2001-03-12 21:56 ` Adrian Bunk
2001-03-12 23:15 ` Ralf Baechle
2001-03-12 23:15   ` Ralf Baechle
2001-03-13  7:46   ` Houten K.H.C. van (Karel)
2001-03-13 13:53     ` Ralf Baechle [this message]
2001-03-13 14:22     ` Ralf Baechle
2001-03-13 18:18       ` Karel van Houten
2001-03-13 18:18         ` Karel van Houten
2001-03-13 18:27         ` Ralf Baechle
2001-03-13 18:27           ` Ralf Baechle
2001-03-13 18:38           ` Karel van Houten
2001-03-13 18:38             ` Karel van Houten
2001-03-13 18:40           ` Karel van Houten
2001-03-13 18:40             ` Karel van Houten
2001-03-13 21:15             ` Pete Popov
2001-03-21 17:39 ` Adrian Bunk
2001-03-21 17:39   ` Adrian Bunk

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=20010313145330.A1208@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=K.H.C.vanHouten@kpn.com \
    --cc=K.H.C.vanHouten@research.kpn.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-mips@oss.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