Hi! On Oct 08, 2011, at 08:36, Matthias Klose wrote: > On 10/07/2011 01:30 PM, Marcin Juszkiewicz wrote: >> W dniu 07.10.2011 11:48, Marcin Juszkiewicz pisze: >>>> When compiling a GCC stage1 cross-compiler, the generated control file >>>> depends on "libgcc" even when one is not built, making it impossible >>>> to install the stage1 compiler to prepare for stage2. >>> >>> I have to admit that I never installed stage1 or stage2 packages - I >>> only unpack them and use for next bootstrap step: >>> >>> http://anonscm.debian.org/gitweb/?p=collab-maint/cross-toolchain.git;a=shortlog;h=refs/heads/armel-cross-toolchain-base >>> >>> Will take a look at your patch. >> >> Tested-by: Marcin Juszkiewicz <marcin.juszkiew...@linaro.org> >> >> patch is sane - please merge > > except that it does break the native build :-/ pretty please test cross > patches > with a native build too. >
> with_libgcc is unset with this patch. the stage stuff should go after setting > setting with_common_libs etc. Oops! You are totally correct. I thought I'd been so careful to make sure that $(with_libgcc) was still set in the regular path. How about this alternative path? It does not end up moving the stage1/2 stuff around, but it does ensure that with_libgcc is always set unless DEB_STAGE=stage1. This should be much closer to the original code-path for native builds without affecting the altered cross-build state. NOTE: I'm just starting my build-tests for this patch, I'll send a separate followup email if both are successful. Cheers, Kyle Moffett
gcc-4.6-cross-stage1-dep-fix-v3.patch
Description: gcc-4.6-cross-stage1-dep-fix-v3.patch
