| Message ID | alpine.BSF.2.02.1507140816010.74899@arjuna.pair.com |
|---|---|
| State | New |
| Headers | show |
On Tue, Jul 14, 2015 at 5:22 AM, Hans-Peter Nilsson <hp@bitrange.com> wrote: > I tried the good old combined-tree approach (which some call > ubertree), and was bitten by bfd not depending on zlib *in the > gcc version of toplevel Makefile.in*. So, I did a partial sync > to include the particular commit from the binutils-gdb git and > committed as obvious after a auccessful build of > mmix-knuth-mmixware. > > (Test-results however are abysmal, likely due to a single ld bug > causing segfault with -flto.) > > Committed: > Sync with src: > 2015-03-30 H.J. Lu <hongjiu.lu@intel.com> > * Makefile.def (dependencies): Add all-zlib to all-bfd. > * Makefile.in: Regenerated. The shared files between gcc and binutils are way out of sync. I have synced binutils with gcc. I started submitting GCC patches to sync with binutils: https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00707.html I will commit changes to GCC to sync GCC with binutils. In the meantime, you can use the shared files from binutils with GCC.
On Tue, 14 Jul 2015, H.J. Lu wrote: > The shared files between gcc and binutils are way out of sync. Yeah I noticed, but didn't go for a full sync as that'd require testing other builds too. Thankfully your imported src commit was local. > I have synced binutils with gcc. I started submitting GCC > patches to sync with binutils: > > https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00707.html > > I will commit changes to GCC to sync GCC with binutils. Good! > In the meantime, you can use the shared files from binutils > with GCC. The commit I did means I don't have to, but this was for a bare-iron cross-target meaning likely less issues than a self-hosted target with all bells, whistles and subdirs; people may see other failures for other targets. brgds, H-P
On Tue, Jul 14, 2015 at 6:46 AM, Hans-Peter Nilsson <hp@bitrange.com> wrote: > On Tue, 14 Jul 2015, H.J. Lu wrote: >> The shared files between gcc and binutils are way out of sync. > > Yeah I noticed, but didn't go for a full sync as that'd require > testing other builds too. Thankfully your imported src commit > was local. > >> I have synced binutils with gcc. I started submitting GCC >> patches to sync with binutils: >> >> https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00707.html >> >> I will commit changes to GCC to sync GCC with binutils. > > Good! > >> In the meantime, you can use the shared files from binutils >> with GCC. > > The commit I did means I don't have to, but this was for a > bare-iron cross-target meaning likely less issues than a > self-hosted target with all bells, whistles and subdirs; people > may see other failures for other targets. > I have synced toplevel files as well as config/include directories between GCC and binutils-gdb. Please let me know if I have missed anything. Thanks.
Index: Makefile.def =================================================================== --- Makefile.def (revision 225768) +++ Makefile.def (working copy) @@ -402,6 +402,7 @@ dependencies = { module=configure-bfd; on=configure-intl; }; dependencies = { module=all-bfd; on=all-libiberty; }; dependencies = { module=all-bfd; on=all-intl; }; +dependencies = { module=all-bfd; on=all-zlib; }; dependencies = { module=configure-opcodes; on=configure-libiberty; hard=true; }; dependencies = { module=all-opcodes; on=all-libiberty; }; Index: Makefile.in =================================================================== --- Makefile.in (revision 225768) +++ Makefile.in (working copy) @@ -49977,6 +49977,14 @@ all-stage4-bfd: maybe-all-stage4-intl all-stageprofile-bfd: maybe-all-stageprofile-intl all-stagefeedback-bfd: maybe-all-stagefeedback-intl +all-bfd: maybe-all-zlib + +all-stage1-bfd: maybe-all-stage1-zlib +all-stage2-bfd: maybe-all-stage2-zlib +all-stage3-bfd: maybe-all-stage3-zlib +all-stage4-bfd: maybe-all-stage4-zlib +all-stageprofile-bfd: maybe-all-stageprofile-zlib +all-stagefeedback-bfd: maybe-all-stagefeedback-zlib configure-opcodes: configure-libiberty configure-stage1-opcodes: configure-stage1-libiberty