bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/14625] [2.23/2.24 regression] ar: File truncated


From: amodra at gmail dot com
Subject: [Bug binutils/14625] [2.23/2.24 regression] ar: File truncated
Date: Wed, 26 Sep 2012 02:23:17 +0000


http://sourceware.org/bugzilla/show_bug.cgi?id=14625



Alan Modra <amodra at gmail dot com> changed:



           What    |Removed                     |Added

----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED

                 CC|                            |amodra at gmail dot com

         Resolution|                            |INVALID



--- Comment #1 from Alan Modra <amodra at gmail dot com> 2012-09-26 02:23:17 
UTC ---

You're running into archive.c:2661

      /* Catch an attempt to grow an archive past its 4Gb limit.  */

      if (archive_member_file_ptr != (file_ptr) offset)

        {

          bfd_set_error (bfd_error_file_truncated);

          return FALSE;

        }

      if (!bfd_write_bigendian_4byte_int (arch, offset))

        return FALSE;



Previous versions of binutils created invalid armaps.  We can't do much about

this problem without changing archive format for x86_64.  I suppose that is a

possibility.



If you just want an archive for packaging purposes as distinct from using the

archive as a linker input, then you can work around this problem by disabling

the armap with ar's S option.



I'm closing this bug report as invalid since the archive format simply doesn't

support such large archives.  Please take any discussion (patches!) regarding

changing archive format to the binutils list.



-- 

Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email

------- You are receiving this mail because: -------

You are on the CC list for the bug.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]