mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
To: jochen@tolot.escape.de, linux-kernel@vger.kernel.org
Subject: 2.4.4-pre6 does not compile
Date: Mon, 23 Apr 2001 22:14:27 +0200	[thread overview]
Message-ID: <3AE48D23.4A13FB91@folkwang-hochschule.de> (raw)

jochen wrote:
 
> 
>               Hi,
> 
>       2.4.4-pre6 actually is the 4th 2.4.4pre-Patch that does not compile
>       without further patching on my system. :-(
> 
> 
>       ld -m elf_i386 -T /usr/src/linux-2.4.4-pre6/arch/i386/vmlinux.lds -e stext 
>       arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
>               --start-group \
>               arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o 
>       ipc/ipc.o \
>               drivers/block/block.o drivers/char/char.o drivers/misc/misc.o 
>       drivers/net/net.o drivers/media/media.o  drivers/ide/idedriver.o 
>       drivers/scsi/scsidrv.o drivers/scsi/aic7xxx/aic7xxx_drv.o drivers/cdrom/driver.o 
>       drivers/pci/driver.o drivers/video/video.o \
>               net/network.o \
>               /usr/src/linux-2.4.4-pre6/arch/i386/lib/lib.a 
>       /usr/src/linux-2.4.4-pre6/lib/lib.a /usr/src/linux-2.4.4-pre6/arch/i386/lib/lib.a \
>               --end-group \
>               -o vmlinux
>       /usr/src/linux-2.4.4-pre6/lib/lib.a(rwsem.o): In function `__rwsem_do_wake':
>       rwsem.o(.text+0x30): undefined reference to `__builtin_expect'
>       rwsem.o(.text+0x73): undefined reference to `__builtin_expect'
>       make: *** [vmlinux] Error 1


same problem here.
i'm using
# gcc -v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/2.95.2/specs
gcc version 2.95.2 19991024 (release)

and this one has successfully built the last couple of kernels. if
compiler requirements have changed, may i humbly suggest to add this
to the pre-patch logfile ?

btw: i have installed clean vanilla sources. the only  possible
source of pollution was my old .config, which i copied into the tree
before making menuconfig. but this has always worked before.

regards,

jörn

(please cc: me, i only read the archives, which have some lag.
thanks.)

-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://www.folkwang.uni-essen.de/~nettings/
http://www.linuxdj.com/audio/lad/

             reply	other threads:[~2001-04-23 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 20:14 Jörn Nettingsmeier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-21 20:17 Jochen Striepe
2001-04-21 20:34 ` Russell King
2001-04-21 20:44 ` Philip Blundell

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=3AE48D23.4A13FB91@folkwang-hochschule.de \
    --to=nettings@folkwang-hochschule.de \
    --cc=jochen@tolot.escape.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®