Suspicious Configure output #12123
Comments
From @maukeCreated by @maukeWhile configuring 5.16.0 I noticed the following two messages about ================================================================================ Creating config.sh... If you'd like to make any changes to the config.sh file before I begin
|
From @jkeenanOn Mon May 21 03:45:24 2012, l.mai@web.de wrote:
Can you provide the full command and options you used for 'sh ./Configure'? Thank you very much. |
|
The RT System itself - Status changed from 'new' to 'open' |
From @maukeOn 2012-05-21 James E Keenan via RT wrote:
% ./Configure -de |
From @jkeenanOn Tue May 29 05:24:57 2012, l.mai@web.de wrote:
Can we assume that the machine on which you noted this suspicious output I don't have access to a 64-bit machine and my highest version of gcc is ##### So, I saw a different set of error messages from 'try.c' from yours -- So I don't think you have anything big to worry about. Perhaps someone Thank you very much. |
From @maukeOn 2012-05-29 James E Keenan via RT wrote:
Yes, but it's a 32-bit Linux (and it also happens with gcc 4.7.0). |
From @jkeenanOn 6/1/12 11:13 AM, Lukas Mai wrote:
Okay. As I wrote previously, if this is not preventing you from But I hope some of our configuration experts can shed some light on what Thank you very much. |
From @doughera88On Tue, 29 May 2012, James E Keenan via RT wrote:
: Creating config.sh... Yes, that's normal and not a problem. It's defined in the hints file, : =========================================================================== [ and many more similar ones ] I don't recognize this one, and can't figure out what those extra However, I really doubt it's a real problem. The test is trying to
Those are all harmless. Configure tries lots of things as it tries to
Agreed. There's nothing to worry about here. Thanks for keeping on top of these tickets! -- |
From @maukeOn 2012-06-01 Andy Dougherty via RT wrote:
I did that, and the bad directives look like this: ... The C compiler complains because "__INT16_C(c)" is obviously not a % cpp -dM /dev/null | grep '(c)' |
From @doughera88On Fri, 1 Jun 2012, Andy Dougherty wrote:
This was fixed by commit 9e477c1 Replace $compile_ok by $compile for two probes that can fail. I already made corresponding changes to metaconfig with these two commits: commit ce92b45824804da828aa9a1cb53d69e1a54e2acc Replace $compile_ok by $compile since it's ok for this probe to fail. Replace $compile_ok by $compile since it's ok for this probe to fail. I'll push the prepocessor patches shortly. |
|
@cpansprout - Status changed from 'open' to 'resolved' |
From @doughera88On Wed, 6 Jun 2012, Andy Dougherty wrote:
The warnings: : Guessing which symbols your C compiler and preprocessor define... are now fixed with commit 6f87f40 Configure: Avoid Cppsym warnings for extra tokens [perl #113024] I also pushed the equivalent metaconfig patches commit 84a69cea86dfdcd6eb2538b1c7870351c617d99a Ensure Cppsym.true list is sorted (for later input to comm). commit 7bd925e6d5c37ea08d88d74f0c76456744d47b16 Avoid Cppsym warnings for extra tokens [perl #113024] This should resolve [perl #113024] -- |
Migrated from rt.perl.org#113024 (status was 'resolved')
Searchable as RT113024$
The text was updated successfully, but these errors were encountered: