From: ralf@uni-koblenz.de
To: Oliver Frommel <oliver@aec.at>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: compile problem with kernel
Date: Mon, 30 Mar 1998 15:42:44 +0200 [thread overview]
Message-ID: <19980330154244.19782@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.96.980330093827.20663A-100000@web.aec.at>; from Oliver Frommel on Mon, Mar 30, 1998 at 09:42:56AM +0200
On Mon, Mar 30, 1998 at 09:42:56AM +0200, Oliver Frommel wrote:
> i got the kernel (linux-980326) from linux.sgi.com and had the following
> problems crosscompiling it from intel-linux (which appeared on list once, but
> without any answer/solution as far as i remember):
>
> mips-linux-gcc -D__KERNEL__ -I/mnt/dsk1/devel/mips/linux-980326/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r4600 -mips2 -pipe -c entry.S -o entry.o
> entry.S: Assembler messages:
> entry.S:147: Error: .previous without corresponding .section; ignored
> entry.S:147: Error: .previous without corresponding .section; ignored
> entry.S:148: Error: .previous without corresponding .section; ignored
> entry.S:148: Error: .previous without corresponding .section; ignored
> entry.S:154: Error: .previous without corresponding .section; ignored
> entry.S:154: Error: .previous without corresponding .section; ignored
> entry.S:156: Error: .previous without corresponding .section; ignored
> entry.S:156: Error: .previous without corresponding .section; ignored
> entry.S:157: Error: .previous without corresponding .section; ignored
> entry.S:157: Error: .previous without corresponding .section; ignored
> entry.S:158: Error: .previous without corresponding .section; ignored
> entry.S:158: Error: .previous without corresponding .section; ignored
> make[1]: *** [entry.o] Error 1
> make[1]: Leaving directory `/mnt/dsk1/devel/mips/linux-980326/arch/mips/kernel'
> make: *** [linuxsubdirs] Error 2
>
>
> i'd appreciate an explanation what's happening here very much ..
In the vanilla FSF sources the .previous pseudo is broken resulting in
these messages. The fix is in 2.7-4 and newer.
Ralf
next prev parent reply other threads:[~1998-03-30 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-30 7:42 compile problem with kernel Oliver Frommel
1998-03-30 13:42 ` ralf [this message]
1998-03-31 7:26 ` Ulf Carlsson
1998-03-31 7:14 ` ralf
1998-03-31 7:32 ` Oliver Frommel
1998-03-31 14:49 ` ralf
1998-03-31 7:39 ` Oliver Frommel
1998-03-31 14:38 ` ralf
1998-03-31 14:46 ` Oliver Frommel
1998-03-31 14:55 ` ralf
1998-03-31 14:57 ` Oliver Frommel
1998-03-31 15:33 ` ralf
1998-03-31 15:59 ` Oliver Frommel
1998-03-31 16:16 ` Dong Liu
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=19980330154244.19782@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=oliver@aec.at \
/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