public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: "Aaron W. LaFramboise" <aaron98wiridge9@aaronwl.com>
Cc: binutils@sources.redhat.com
Subject: Re: mainline ld on mingw32/pe is broken, returns 1 without error.
Date: Sun, 27 Jun 2004 04:06:00 -0000	[thread overview]
Message-ID: <20040627040640.GM3469@bubble.modra.org> (raw)
In-Reply-To: <40DE22EB.7080001@aaronwl.com>

On Sat, Jun 26, 2004 at 08:29:15PM -0500, Aaron W. LaFramboise wrote:
> ld -o hello.exe
> c:/aaronwl/cs/env/mingw-3.4.0-2.15-3.3/bin/../lib/gcc/i686-pc-mingw32/3.4.0/../../../crt2.o
> -Lc:/aaronwl/cs/env/mingw-3.4.0-2.15-3.3/bin/../lib/gcc/i686-pc-mingw32/3.4.0
> hello.o -lmingw32 -lgcc -lmsvcrt -lkernel32
> 
> It prints absolutely no messages, but exits with code 1, and does not
> leave output files.
> 
> How should I begin to debug this?  Any ideas what change caused this?

There's a good chance this is due to my 2004-06-24 section sizing
change.  Build binutils from source just before this change went in, and
see if ld is good.  Assuming it is, compare hello.exe before and after
the patch.  Any change is suspicious, apart from the silly timestamp in
pe files.  objdump will let you look at section sizes..

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2004-06-27  4:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27  1:29 Aaron W. LaFramboise
2004-06-27  4:06 ` Alan Modra [this message]
2004-06-27  4:32   ` Aaron W. LaFramboise
2004-06-27 11:49     ` Alan Modra
2004-06-28  5:01       ` Aaron W. LaFramboise
     [not found]         ` <20040628051054.GR3469@bubble.modra.org>
     [not found]           ` <40DFA9A4.3010303@aaronwl.com>
2004-06-28  6:26             ` Alan Modra
2004-06-28 13:34               ` Alan Modra
2004-06-28 22:14                 ` Aaron W. LaFramboise

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=20040627040640.GM3469@bubble.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=aaron98wiridge9@aaronwl.com \
    --cc=binutils@sources.redhat.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).