[opensuse-factory] Another 'fun' build failure case in Factory
Hi all, another fun story you might be running in while looking at build failures. In factory, %{optflags} now contains "-grecord-gcc-switches". A bunch of 'funny' configure and make scripts try to be smart and, if for example built with --disable-build, replace -g in CFLAGS with '' using most stupid sed syntax. The result? gcc -grecord-gcc-switches main.c -o myCoolApp becomes gcc record-gcc-switches main.c -o myCoolApp => and there is (hopefully in call cases) no file called record-gcc-switches, and thus the build fails. In most cases this is visible in the error message (gcc: record-gcc-switches does not exist). In some cases this is a bit deeper burried. Again, I think I hit most cases in Factory and sent proposal SRs to the dev projects.. up to the maintainers to decide if they like the fixes (usually I just removed this mangling... even with --disable-debug, we usually want -g specified so we can get meaningful -debuginfo packages) Happy hacking... and happy chasing bugs! Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 22/04/13 20:49, Dimstar / Dominique Leuenberger escribió:
Hi all,
another fun story you might be running in while looking at build failures.
In factory, %{optflags} now contains "-grecord-gcc-switches".
Yes, that's probably a temporary way.. when we switch to 4.8 it will no longer be required as it is a default. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Apr 23, 2013 at 01:49:57AM +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
another fun story you might be running in while looking at build failures.
In factory, %{optflags} now contains "-grecord-gcc-switches". A bunch of 'funny' configure and make scripts try to be smart and, if for example built with --disable-build, replace -g in CFLAGS with '' using most stupid sed syntax.
The result?
gcc -grecord-gcc-switches main.c -o myCoolApp becomes gcc record-gcc-switches main.c -o myCoolApp => and there is (hopefully in call cases) no file called record-gcc-switches, and thus the build fails.
In most cases this is visible in the error message (gcc: record-gcc-switches does not exist). In some cases this is a bit deeper burried.
Again, I think I hit most cases in Factory and sent proposal SRs to the dev projects.. up to the maintainers to decide if they like the fixes (usually I just removed this mangling... even with --disable-debug, we usually want -g specified so we can get meaningful -debuginfo packages)
Happy hacking... and happy chasing bugs!
-g should not be patched out in usual scenarios at least. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/23/2013 01:49 AM, Dimstar / Dominique Leuenberger wrote:
(usually I just removed this mangling... even with --disable-debug, we usually want -g specified so we can get meaningful -debuginfo packages)
Just a note that -g slows down the build significantly. So it might not be that b&w. And if you build a -debuginfo for a package that was built previously with non-g, it should still work with gcc as it does the right thing in this case... (Clang doesn't.) -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Cristian Rodríguez -
Dimstar / Dominique Leuenberger -
Jiri Slaby -
Marcus Meissner