toolchain gcc next builders are broken |
|||
Issue descriptionFailed to apply the following patch. * Applying gcc-disable-linker-pie-copyreloc.patch ... * Failed Patch: gcc-disable-linker-pie-copyreloc.patch ! * ( /usr/local/portage/crossdev/cross-armv7a-cros-linux-gnueabi/gcc/files/gcc-disable-linker-pie-copyreloc.patch )
,
Jul 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/e8d76b1b8d613efb369021663269e1585c54d4c5 commit e8d76b1b8d613efb369021663269e1585c54d4c5 Author: Manoj Gupta <manojgupta@google.com> Date: Wed Jul 12 23:36:45 2017 gcc: Move copy reloc with pie patch to src_prepare. The patch fails with USE+"next_gcc" since the directory layout is different. Move to src_prepare where it applies cleanly. BUG= chromium:741896 TEST=sudo emerge sys-devel/gcc builds with and without USE="next_gcc" Change-Id: If7fde183b0b57a283cfce05035034a1f13db2397 Reviewed-on: https://chromium-review.googlesource.com/569074 Reviewed-by: Rahul Chaudhry <rahulchaudhry@chromium.org> Commit-Queue: Manoj Gupta <manojgupta@chromium.org> Tested-by: Manoj Gupta <manojgupta@chromium.org> [modify] https://crrev.com/e8d76b1b8d613efb369021663269e1585c54d4c5/sys-devel/gcc/gcc-9999.ebuild
,
Jul 13 2017
The builders are fixed, and Manoj fixed them.
,
Jul 17 2017
Rahul, can you commit the change to next_gcc repo? The builders are failing a Unit Test since gcc is producing the unsupported relocation.
,
Jul 17 2017
The change is already in next_gcc repo: https://chromium.googlesource.com/chromiumos/third_party/gcc/+/svn-mirror/google/gcc-4_9 This seems to be some other issue.
,
Jul 17 2017
There are similar failures on the gcc-toolchain builder as well: https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-gcc-toolchain And that builder is not even using binutils-2.27.
,
Jul 17 2017
Thx, I don't think it's worth investigating that failure since we have no plans to use next_gcc.
,
Jul 17 2017
there is something weird with that failure. Why did it appear? it is true we are not planning to roll to next version of gcc (yet) but something must have changed that caused this...
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by rahulchaudhry@chromium.org
, Jul 12 2017Status: Started (was: Untriaged)