From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] Fix for kernel DRM build
Date: Tue, 09 Jan 2001 22:46:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205903@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205902@msgid-missing>
This should be labeled a toolchain issue. The problem occurs whenever
someone is building and linking against an "empty" archive. The same
problem occurred in the "media/" subdirectory but I did a quick hack to
work around the problem.
--david
>>>>> On Tue, 09 Jan 2001 14:32:23 -0800, Uros Prestor <uros@turbolinux.com> said:
Uros> When building the latest 2.4.0-010109 kernel with DRI support
Uros> enabled, I got the following link-time error:
Uros> ld: drivers/char/drm/drm.o: linking 64-bit files with
Uros> 32-bit files ld: drivers/char/drm/drm.o: linking constant-gp
Uros> files with non-constant-gp files
Uros> It turns out that drm.o was built as follows:
Uros> rm -f drmlib.a ar rcs drmlib.a init.o memory.o proc.o
Uros> auth.o context.o drawable.o bufs.o lists.o lock.o ioctl.o
Uros> fops.o vm.o dma.o ctxbitmap.o rm -f drm.o ld -r -o drm.o
Uros> drmlib.a
Uros> Looks like the ar output confuses the linker. I don't even
Uros> know if this is supposed to work with the current toolchain.
Uros> In any case, if you remove the ar step and use ld -r directly
Uros> the problem disappears. The enclosed patch fixes the DRI
Uros> Makefile to remove the ar step.
Uros> Uros.
Uros> -- Uros Prestor uros@turbolinux.com
Uros> diff -ruN linux-2.4.0-010109/drivers/char/drm/Makefile
Uros> linux-2.4.0-010109.drm/drivers/char/drm/Makefile ---
Uros> linux-2.4.0-010109/drivers/char/drm/Makefile Thu Jan 4
Uros> 13:07:01 2001 +++
Uros> linux-2.4.0-010109.drm/drivers/char/drm/Makefile Tue Jan 9
Uros> 13:43:21 2001 @@ -63,9 +63,9 @@ lib-objs-mod := $(patsubst
Uros> %.o,%-mod.o,$(lib-objs))
Uros> ifdef MAKING_MODULES - lib = drmlib-mod.a + lib Uros> drmlib-mod.o else - obj-y += drmlib.a + obj-y += drmlib.o
Uros> endif
Uros> include $(TOPDIR)/Rules.make @@ -73,13 +73,11 @@ $(patsubst
Uros> %.o,%.c,$(lib-objs-mod)): @ln -sf $(subst -mod,,$@) $@
Uros> -drmlib-mod.a: $(lib-objs-mod) - rm -f $@ - $(AR)
Uros> $(EXTRA_ARFLAGS) rcs $@ $(lib-objs-mod) +drmlib-mod.o:
Uros> $(lib-objs-mod) + $(LD) -r -o $@ $(lib-objs-mod)
Uros> -drmlib.a: $(lib-objs) - rm -f $@ - $(AR) $(EXTRA_ARFLAGS) rcs
Uros> $@ $(lib-objs) +drmlib.o: $(lib-objs) + $(LD) -r -o $@
Uros> $(lib-objs)
Uros> gamma.o: $(gamma-objs) $(lib) $(LD) -r -o $@ $(gamma-objs)
Uros> $(lib)
next prev parent reply other threads:[~2001-01-09 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 22:32 [Linux-ia64] [PATCH] Fix for kernel DRM build Uros Prestor
2001-01-09 22:46 ` David Mosberger [this message]
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-105590678205903@msgid-missing \
--to=davidm@hpl.hp.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 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.