This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

hppa-linux-gnu-ranlib: libcpp.a: File format not recognized

This stops an --enable-targets selection affecting the main target in
regards to forcing 64-bit archives.  It also means mips64 and s390x
will revert to binutils-2.25 and binutils-2.26 behaviour of not
forcing 64-bit archives at least in the common case when plugins were

Since it appears no one even noticed the 2.25 and 2.26 behaviour on
mips and s390, I think it's safe to go back to creating the standard
archives on those targets.  They will still create 64-bit archives if
the size of their contents is too large for the 32-bit format.

	PR binutils/20464
	PR binutils/14625
	* Revert 2016-05-25 configure change setting
	want_64_bit_archive for mips64 and s390x.  Revise USE_64_BIT_ARCHIVE
	* configure: Regenerate.
	* Regenerate.

diff --git a/bfd/ b/bfd/
index 3254dae..944fc56 100644
--- a/bfd/
+++ b/bfd/
@@ -786,20 +786,11 @@ else	# all_targets is true
     selarchs=`echo $selarchs | sed -e 's/^/\&/' -e 's/ \(.\)/,\&\1/g'`
 fi	# all_targets is true
-if test "x$want_64_bit_archive" = xunset; then
-  # 64-bit MIPS and s390 ELF targets use 64-bit archives.
-  case "${bfd_backends}" in
-    *elf64-mips* | *elf64-s390*)
-      want_64_bit_archive=true
-      ;;
-  esac
 # 64-bit archives need a 64-bit bfd_vma.
 if test "x$want_64_bit_archive" = xtrue; then
-    [Define if we should use 64-bit archives.])
+    [Define if 64-bit archives should always be used.])
 case ${host64}-${target64}-${want64} in

Alan Modra
Australia Development Lab, IBM

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]