public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] Fix for kernel DRM build
Date: Tue, 16 Jan 2001 01:13:45 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005048@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205902@msgid-missing>

On Mon, Jan 15, 2001 at 04:42:26PM -0800, Jim Wilson wrote:
> >     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
> 
> I've sent a proposed patch to binutils@sources.redhat.com for comment.
> 
> I don't like HJ's proposed solution, which is to ignore the ELF header flags
> if an object file is empty.  That can mask real errors, as this ar/ld -r
> trick is not the only way to create empty object files.
> 
> My proposed patch fixes the linker to notice when the output file is empty,
> and then we set the ELF header flags from the first member of the first
> archive even though we aren't linking it in.  This fixes the kernel build

Does that work with an empty archive or an archive with files of
mixed types? I thought about your approach. But I decided against
it since it didn't work with the cases above.


H.J.


  parent reply	other threads:[~2001-01-16  1:13 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
2001-01-10  1:35 ` H . J . Lu
2001-01-16  0:42 ` Jim Wilson
2001-01-16  1:13 ` H . J . Lu [this message]
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-105590693005048@msgid-missing \
    --to=hjl@valinux.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