From: Manuel Krause <manuelkrause@netscape.net>
To: Chris Mason <mason@namesys.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: data-logging with 2.4.22-pre7+ and logging-export compiling fails
Date: Wed, 30 Jul 2003 05:04:08 +0200 [thread overview]
Message-ID: <3F2735A8.2090701@netscape.net> (raw)
Hi,
I don't really know what is wrong with the logging-export patch
(ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.22/06-logging-export.diff.gz),
but if I didn't exclude it for compiling the 2.4.22-pre kernels since
subversion 7 my kernel compile would fail.
As I always compiled reiserfs into kernel I don't really need it but I
kept this patch in so far. So this only info.
Bye,
Manuel
P.S.: Oh, yes, cool: My console even has still the failing lines of
"make bzImage" (already many patchings and compiles later...), just to
be complete.
[...]
make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o init/do_mounts.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/char/char.o drivers/block/block.o drivers/misc/misc.o
drivers/net/net.o drivers/char/drm/drm.o drivers/ide/idedriver.o
drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o
drivers/video/video.o drivers/usb/usbdrv.o drivers/media/media.o \
net/network.o \
/usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a
/usr/src/linux/arch/i386/lib/lib.a \
--end-group \
-o vmlinux
mm/mm.o(.kstrtab+0x40): multiple definition of
`__kstrtab_mark_page_accessed'
kernel/kernel.o(.kstrtab+0xca9): first defined here
mm/mm.o(__ksymtab+0x20): multiple definition of
`__ksymtab_mark_page_accessed'
kernel/kernel.o(__ksymtab+0x700): first defined here
make: *** [vmlinux] Error 1
firehead:/usr/src/linux #
reply other threads:[~2003-07-30 3:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F2735A8.2090701@netscape.net \
--to=manuelkrause@netscape.net \
--cc=mason@namesys.com \
--cc=reiserfs-list@namesys.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 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.