https://sourceware.org/bugzilla/show_bug.cgi?id=29284
--- Comment #4 from Jan Engelhardt ---
Come to think of it, instead of truncation, compiler and linkers could:
* unlink (optional, but worthwhile, since it retains the
disk space usage pattern as truncation)
* create temp file in target
https://sourceware.org/bugzilla/show_bug.cgi?id=29284
--- Comment #3 from Nick Clifton ---
(In reply to Jan Engelhardt from comment #2)
Hi Jan,
> Is the output really empty - or at least empty in the BFD sense? a.out is
> 394 bytes in my case.
In a BFD sense yes - the file has nothing of intere
https://sourceware.org/bugzilla/show_bug.cgi?id=29284
--- Comment #2 from Jan Engelhardt ---
>ld: a.out: warning - empty output file - was this intended ?
Is the output really empty - or at least empty in the BFD sense? a.out is 394
bytes in my case.
--
You are receiving this mail because:
You
https://sourceware.org/bugzilla/show_bug.cgi?id=29284
--- Comment #1 from Nick Clifton ---
Created attachment 14179
--> https://sourceware.org/bugzilla/attachment.cgi?id=14179&action=edit
Proposed Patch
Hi Jan,
You are right in saying that we should not complain about empty input files.
B
https://sourceware.org/bugzilla/show_bug.cgi?id=29284
Nick Clifton changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |nickc at redhat dot com
Last
https://sourceware.org/bugzilla/show_bug.cgi?id=29284
Cristian RodrÃguez changed:
What|Removed |Added
CC||crrodriguez at opensuse dot org
