I tried emerging a few versions of plt-scheme using the profile flag. They all failed at the check for sizeof(char). It builds and installs fine without this use flag. Setting MAKEOPTS to -j1 doesn't help. The problem exists on both x86 and amd64 multilib. Reproducible: Always Steps to Reproduce: 1. USE="profile" emerge plt-scheme Actual Results: configure fails while trying to calculate sizeof(char): . . checking for iconv.h... yes checking iconv is usable... no checking for mbsrtowcs... no checking for char... yes checking size of char... configure: error: cannot compute sizeof (char) See `config.log' for more details. Expected Results: dev-scheme/plt-scheme should configure, build and install This is the test that is failing: | typedef char ac__type_sizeof_; | static long int longval () { return (long int) (sizeof (ac__type_sizeof_)); } | static unsigned long int ulongval () { return (long int) (sizeof (ac__type_sizeof_)); } | #include <stdio.h> | #include <stdlib.h> | int | main () | { | | FILE *f = fopen ("conftest.val", "w"); | if (! f) | return 1; | if (((long int) (sizeof (ac__type_sizeof_))) < 0) | { | long int i = longval (); | if (i != ((long int) (sizeof (ac__type_sizeof_)))) | return 1; | fprintf (f, "%ld\n", i); | } | else | { | unsigned long int i = ulongval (); | if (i != ((long int) (sizeof (ac__type_sizeof_)))) | return 1; | fprintf (f, "%lu\n", i); | } | return ferror (f) || fclose (f) != 0; | | ; | return 0; | } configure:7259: error: cannot compute sizeof (char) My best guess is it can't open 'conftest.val'.
Created attachment 204982 [details] emerge --info
Created attachment 204984 [details] config.log
from you config.log: i686-pc-linux-gnu-gcc: -pg and -fomit-frame-pointer are incompatible
(In reply to comment #3) > from you config.log: > i686-pc-linux-gnu-gcc: -pg and -fomit-frame-pointer are incompatible > Ah, you're right and that makes sense. It might be better if the ebuild checked for that and printed a useful error message as a hint if you try to use the profile flag. Thanks
(In reply to comment #4) > It might be better if the ebuild checked for that and printed a useful error > message as a hint if you try to use the profile flag. This has been discussed many times and the answer is no because a) where to stop with filtering flags? There are many flags that might break compilation or at run time. b) Users profiling applications are supposed to know what they are doing.
(In reply to comment #5) > (In reply to comment #4) > > It might be better if the ebuild checked for that and printed a useful error > > message as a hint if you try to use the profile flag. > > This has been discussed many times and the answer is no because a) where to > stop with filtering flags? There are many flags that might break compilation or > at run time. b) Users profiling applications are supposed to know what they are > doing. > Fair enough. Thanks for the help!
