From: Uros Prestor <uros@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [PATCH] Fix for kernel DRM build
Date: Tue, 09 Jan 2001 22:32:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205902@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
When building the latest 2.4.0-010109 kernel with DRI support enabled,
I got the following link-time error:
ld: drivers/char/drm/drm.o: linking 64-bit files with 32-bit
files
ld: drivers/char/drm/drm.o: linking constant-gp files with
non-constant-gp files
It turns out that drm.o was built as follows:
rm -f drmlib.a
ar rcs drmlib.a init.o memory.o proc.o auth.o context.o
drawable.o bufs.o lists.o lock.o ioctl.o fops.o vm.o dma.o
ctxbitmap.o
rm -f drm.o
ld -r -o drm.o drmlib.a
Looks like the ar output confuses the linker. I don't even know if this
is supposed to work with the current toolchain. In any case, if you
remove the ar step and use ld -r directly the problem disappears. The
enclosed patch fixes the DRI Makefile to remove the ar step.
Uros.
--
Uros Prestor
uros@turbolinux.com
[-- Attachment #2: linux-2.4.0-ia64-drm-build.patch --]
[-- Type: text/plain, Size: 931 bytes --]
diff -ruN linux-2.4.0-010109/drivers/char/drm/Makefile linux-2.4.0-010109.drm/drivers/char/drm/Makefile
--- linux-2.4.0-010109/drivers/char/drm/Makefile Thu Jan 4 13:07:01 2001
+++ linux-2.4.0-010109.drm/drivers/char/drm/Makefile Tue Jan 9 13:43:21 2001
@@ -63,9 +63,9 @@
lib-objs-mod := $(patsubst %.o,%-mod.o,$(lib-objs))
ifdef MAKING_MODULES
- lib = drmlib-mod.a
+ lib = drmlib-mod.o
else
- obj-y += drmlib.a
+ obj-y += drmlib.o
endif
include $(TOPDIR)/Rules.make
@@ -73,13 +73,11 @@
$(patsubst %.o,%.c,$(lib-objs-mod)):
@ln -sf $(subst -mod,,$@) $@
-drmlib-mod.a: $(lib-objs-mod)
- rm -f $@
- $(AR) $(EXTRA_ARFLAGS) rcs $@ $(lib-objs-mod)
+drmlib-mod.o: $(lib-objs-mod)
+ $(LD) -r -o $@ $(lib-objs-mod)
-drmlib.a: $(lib-objs)
- rm -f $@
- $(AR) $(EXTRA_ARFLAGS) rcs $@ $(lib-objs)
+drmlib.o: $(lib-objs)
+ $(LD) -r -o $@ $(lib-objs)
gamma.o: $(gamma-objs) $(lib)
$(LD) -r -o $@ $(gamma-objs) $(lib)
next reply other threads:[~2001-01-09 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 22:32 Uros Prestor [this message]
2001-01-09 22:46 ` [Linux-ia64] [PATCH] Fix for kernel DRM build David Mosberger
2001-01-10 1:35 ` H . J . Lu
2001-01-16 0:42 ` Jim Wilson
2001-01-16 1:13 ` H . J . Lu
2001-01-16 2:02 ` Jim Wilson
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=marc-linux-ia64-105590678205902@msgid-missing \
--to=uros@turbolinux.com \
--cc=linux-ia64@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