omit building the target libiberty when building a cross compiler

Bug #809435 reported by Ken Werner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
Undecided
Paul Sokolovsky
Linaro GCC
Fix Released
Medium
Unassigned

Bug Description

When using the Linaro GCC 4.6-2011.06-0 release as a base for building an Android cross toolchain the build fails with:
  checking for library containing strerror... configure: error: Link tests
  are not allowed after GCC_NO_EXECUTABLES.
  make[2]: *** [configure-target-libiberty] Error 1
  make[2]: Leaving directory

Android is using bionic and these configure tests are known to be fragile when using a different target libc. After applying the follwing patch to the Linaro GCC 4.6-2011.06-0 release the Android toolchain can be build without the --disable-libquadmath switch:
svn diff -r 175559:175560 svn://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch > 175560.patch

Since HP's patch is in the FSF's 4.6 branch already - Do we want to include it into our next release if it's not picked up automatically?

Revision history for this message
Ken Werner (kwerner) wrote :

The corresponding GNU Bugzilla is this one
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47836

Revision history for this message
Ramana Radhakrishnan (ramana) wrote :

I don't see why we can't just cherry pick that patch.

Ramana

Revision history for this message
Michael Hope (michaelh1) wrote :

The 2011.07 release is synced up to svn r175677 and will include this patch.

Changed in gcc-linaro:
status: New → Fix Committed
importance: Undecided → Medium
milestone: none → 4.6-2011.07
Michael Hope (michaelh1)
Changed in gcc-linaro:
status: Fix Committed → Fix Released
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

I confirm that Android gcc 4.6-2011.07 can be built without --disable-libquadmath

Changed in linaro-android:
assignee: nobody → Paul Sokolovsky (pfalcon)
status: New → Fix Committed
Changed in linaro-android:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.