I'm installing gentoo from scratch (stage 1). The bootstrap runs ok, but when I do emerge system it stops installing xfree-4.3.0-r4 while trying to apply the 0100_all_4.3.0-xf-4_3... patch If I edit the ebuild to change the PATCH_VER from 2.1.25.2 to 2.1.2.1 it patchs the source ok My system is a mobile Pentium4. I have pentium4 specific optimization flags (which I think should not interfer with the patching of the source) I have tried the same versions on an already installed gentoo on an Athlon and there it correctly patches it, so I don't know where's the problem. (maybe all those optimization flags breaks diff or patch?!?!?!?) I also modified the bootstrap.sh in order to compile binutils with different flags, since it didn't compile with the -m128bit-long-double but the rest of the bootstrap did, and to save a binary build of each package, but again I think this has nothing to do with the patch problem I also have the -b flag passed to emerge and FEATURES="builpkg" (but again I think this has nothing to do with the problem) I have seen a similar problem in bug #40314, but with a different patch Sorry I don't remember the exact USE and CFLAGS but I don't have my laptop here If you also need the /var/tmp/portage/xfree-4.3.0-r4/temp/0100_all_4.3.0-xf_bla_bla.out I'll try to submit it (I don't have Internet at home) Reproducible: Always Steps to Reproduce: 1.Install from stage 1 2.emerge -b system Actual Results: It says: * Failed Patch: 0100_all_4.3.0-xf-4-3_branch-01-19.patch! (well, I don't remember the exact ending of the patch, since I don't have my laptop here, but its the one which starts with "0100_all_4.3.0...") Expected Results: At least patch the source ok
I'm installing gentoo from scratch (stage 1). The bootstrap runs ok, but when I do emerge system it stops installing xfree-4.3.0-r4 while trying to apply the 0100_all_4.3.0-xf-4_3... patch If I edit the ebuild to change the PATCH_VER from 2.1.25.2 to 2.1.2.1 it patchs the source ok My system is a mobile Pentium4. I have pentium4 specific optimization flags (which I think should not interfer with the patching of the source) I have tried the same versions on an already installed gentoo on an Athlon and there it correctly patches it, so I don't know where's the problem. (maybe all those optimization flags breaks diff or patch?!?!?!?) I also modified the bootstrap.sh in order to compile binutils with different flags, since it didn't compile with the -m128bit-long-double but the rest of the bootstrap did, and to save a binary build of each package, but again I think this has nothing to do with the patch problem I also have the -b flag passed to emerge and FEATURES="builpkg" (but again I think this has nothing to do with the problem) I have seen a similar problem in bug #40314, but with a different patch Sorry I don't remember the exact USE and CFLAGS but I don't have my laptop here If you also need the /var/tmp/portage/xfree-4.3.0-r4/temp/0100_all_4.3.0-xf_bla_bla.out I'll try to submit it (I don't have Internet at home) Reproducible: Always Steps to Reproduce: 1.Install from stage 1 2.emerge -b system Actual Results: It says: * Failed Patch: 0100_all_4.3.0-xf-4-3_branch-01-19.patch! (well, I don't remember the exact ending of the patch, since I don't have my laptop here, but its the one which starts with "0100_all_4.3.0...") Expected Results: At least patch the source ok ¿shouldn't it?
The .out file would be helpful. Also the output of `patch --version`. CFLAGS wouldn't have any effect, in fact I'm not sure how it would manage to fail unless your patch utility is messed up, since I remade the patch to apply to our xfree. But it should be interesting to see why.
Well... incredible enought it HAS to do with my CFLAGS... (grrr... f*cking optimizations :) So the problem is that my flags make patch to do weird things (also to coreutils and some others), so I compiled patch again with other "less aggressive" flags and now it patches it correctly... My question now is if I should open a bug for this, in order to change the ebuilds of this packages to filter the "breaking" flags (I also have to see what exacts flags break it, I just removed almost every flag). Thank you for your support
In general, we don't filter any flags that aren't common, or in other words are "insane." File a bug if you want, and something might happen after discussion, or something may not. In the future, please recompile anything relevant with modest CFLAGS _before_ filing a bug. Thanks.
*** Bug 42622 has been marked as a duplicate of this bug. ***
If you wanna know the problematic flag is "malign-double"
