All of lore.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: Wed, 10 Jan 2001 01:35:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205909@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205902@msgid-missing>

On Tue, Jan 09, 2001 at 02:46:27PM -0800, David Mosberger wrote:
> 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.
> 

This patch seems to work for me.


H.J.
---
2001-01-09  H.J. Lu <hjl@valinux.com>

	* elf64-ia64.c (elf64_ia64_merge_private_bfd_data): Don't
	merge with the empty input file.

--- bfd/elf64-ia64.c.empty	Tue Jan  9 17:06:55 2001
+++ bfd/elf64-ia64.c	Tue Jan  9 17:28:42 2001
@@ -3973,6 +3973,10 @@ elf64_ia64_merge_private_bfd_data (ibfd,
       || bfd_get_flavour (obfd) != bfd_target_elf_flavour)
     return false;
 
+  /* If the input file has no data, we have nothing to merge.  */
+  if (ibfd->sections = NULL)
+    return true;
+
   in_flags  = elf_elfheader (ibfd)->e_flags;
   out_flags = elf_elfheader (obfd)->e_flags;
 


  parent reply	other threads:[~2001-01-10  1:35 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 [this message]
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-105590678205909@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 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.