public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@cygnus.com>
To: dj@delorie.com
Cc: cwilson@ece.gatech.edu, binutils@sourceware.cygnus.com
Subject: Re: binutils-20000625 ld.exe --shared broken
Date: Fri, 07 Jul 2000 10:16:00 -0000	[thread overview]
Message-ID: <200007071716.KAA17515@elmo.cygnus.com> (raw)

Hi Guys,

: No, I think that code is right.  Normally, when an archive is created,
: the member BFDs are read from disk, and written to the archive's disk
: file.  Thus, they must be in read mode to be read from the disk.  I
: don't think this test is testing the writability of the archive
: members, because it hasn't created them yet.  So, I think the right
: thing to do is make sure that pe_dll_generate_implib switches all the
: member bfds it creates from write mode (when it creates them) to read
: mode (so it can store them in the archive).

I agree with DJ, although I must confess I had to read the explanation
and look through the code a couple of times before understanding what
is going on.

I belive that the [not writable] test in _bfd_write_archive_contents()
is there because up until this point none of the archive contents
should have been written out, so there should be no reason for the
archive memeber to have the writeable attribute.  (Adding a comment to
this effect in the code would be a good idea).

Cheers
	Nick

             reply	other threads:[~2000-07-07 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 10:16 Nick Clifton [this message]
2000-07-07 10:31 ` DJ Delorie
2000-07-07 11:24   ` Charles Wilson
2000-07-07 12:00     ` DJ Delorie
2000-07-07 21:06       ` Charles Wilson
2000-07-12 11:30         ` DJ Delorie
     [not found] <396547F2.333FBD51@ece.gatech.edu>
     [not found] ` <200007070300.XAA08402@envy.delorie.com>
     [not found]   ` <396574C7.924FADB6@ece.gatech.edu>
2000-07-07  6:39     ` DJ Delorie
2000-07-07  8:55       ` Charles 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=200007071716.KAA17515@elmo.cygnus.com \
    --to=nickc@cygnus.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=cwilson@ece.gatech.edu \
    --cc=dj@delorie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).