Skip Menu |

This queue is for tickets about the Test-Smoke CPAN distribution.

Report information
The Basics
Id: 60857
Status: resolved
Priority: 0/
Queue: Test-Smoke

People
Owner: Nobody in particular
Requestors: njh [...] bandsman.co.uk
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.43
Fixed in: (no value)



Subject: Ignores CC and CFLAGS
You can't use Test::Smoke to test whether Perl builds with a different compiler, because Test::Smoke ignores the values of CC and CFLAGS in your environment.
On Sun Aug 29 12:03:34 2010, njh@bandsman.co.uk wrote: Show quoted text
> You can't use Test::Smoke to test whether Perl builds with a different > compiler, because Test::Smoke ignores the values of CC and CFLAGS in > your environment.
Two options here: 1) use the -Dcc= and -Dccflags= options for configure Put these options on a single line in the first section of the build configurations file (perlcurrent.cfg); or (preferred) create a new configuration with its own build configurations file that has these options in a single section. 2) Create a new configuration, edit the .sh file and add the environment variables as needed.
From: njh [...] bandsman.co.uk
On Sun Aug 29 14:03:48 2010, ABELTJE wrote: Show quoted text
> On Sun Aug 29 12:03:34 2010, njh@bandsman.co.uk wrote:
> > You can't use Test::Smoke to test whether Perl builds with a different > > compiler, because Test::Smoke ignores the values of CC and CFLAGS in > > your environment.
> > Two options here: > 1) use the -Dcc= and -Dccflags= options for configure > Put these options on a single line in the first section of the build > configurations file (perlcurrent.cfg); or (preferred) create a new > configuration with its own build configurations file that has these > options in a single section. > > 2) Create a new configuration, edit the .sh file and add the environment > variables as needed.
I tried option 1 - thanks for the suggestion. However when I tried to test I got this: "Skipping this smoke, patchlevel (7d6ecb1f6c7eabec011b66526161fcf678919c99) did not change." Which is not that helpful since I am trying with a different compiler, so the test done with a different compiler is of no relevance. Do you think that the test result should include more than just the Perl version? Would it not help me to at least include the compiler version with the results?
On Sun Aug 29 16:21:25 2010, njh@bandsman.co.uk wrote: Show quoted text
> On Sun Aug 29 14:03:48 2010, ABELTJE wrote:
> > On Sun Aug 29 12:03:34 2010, njh@bandsman.co.uk wrote:
> > > You can't use Test::Smoke to test whether Perl builds with a
different Show quoted text
> > > compiler, because Test::Smoke ignores the values of CC and CFLAGS
in Show quoted text
> > > your environment.
> > > > Two options here: > > 1) use the -Dcc= and -Dccflags= options for configure > > Put these options on a single line in the first section of the
build Show quoted text
> > configurations file (perlcurrent.cfg); or (preferred) create a new > > configuration with its own build configurations file that has these > > options in a single section. > > > > 2) Create a new configuration, edit the .sh file and add the
environment Show quoted text
> > variables as needed.
> > > I tried option 1 - thanks for the suggestion. However when I tried to > test I got this: > > "Skipping this smoke, patchlevel > (7d6ecb1f6c7eabec011b66526161fcf678919c99) did not change." > > Which is not that helpful since I am trying with a different compiler, > so the test done with a different compiler is of no relevance. Do you > think that the test result should include more than just the Perl > version? Would it not help me to at least include the compiler version > with the results?
If you run the smokes one after the other, you can set the second configuration to not do smartsmoke (just edit the _config file). PS: These are not really bugs, please just send me e-mail with questions. Good luck, -- Abe.
Subject: Re: [rt.cpan.org #60857] Ignores CC and CFLAGS
Date: Tue, 07 Sep 2010 09:45:47 +0100
To: bug-Test-Smoke [...] rt.cpan.org
From: Nigel Horne <njh [...] bandsman.co.uk>
On 29/08/10 22:29, Abe Timmerman via RT wrote: Show quoted text
>>>
>>>> You can't use Test::Smoke to test whether Perl builds with a >>>>
> different >
>>>> compiler, because Test::Smoke ignores the values of CC and CFLAGS >>>>
> in >
>>>> your environment. >>>>
>>> Two options here: >>> 1) use the -Dcc= and -Dccflags= options for configure >>> Put these options on a single line in the first section of the >>>
> build >
>>> configurations file (perlcurrent.cfg); or (preferred) create a new >>> configuration with its own build configurations file that has these >>> options in a single section. >>>
I tried this, but it still doesn't work. As a test I created a new cfg file which has only one section: -Duseithreads -Dccflags="-Wall -O2 -pipe" But the logfile says: CCCMD = cc -DPERL_CORE -c -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -std=c89 -O2 -Wall -ansi -pedantic -W -Wextra -Wdeclaration-after-statement -Wendif-labels -Wc++-compat -DPERL_GCC_PEDANTIC Show quoted text
> > PS: These are not really bugs, please just send me e-mail with > questions. >
Unfortunately you forgot to mention what your email is, so I've had to continue to use "reply". Show quoted text
> Good luck, > -- Abe. >
-- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, ICQ#20252325, twitter: @nigelhorne njh@bandsman.co.uk http://www.bandsman.co.uk
CC: njh [...] bandsman.co.uk
Subject: Re: [rt.cpan.org #60857] Ignores CC and CFLAGS
Date: Tue, 07 Sep 2010 11:07:13 +0200
To: bug-Test-Smoke [...] rt.cpan.org
From: Abe Timmerman <abe.timmerman [...] xs4all.nl>
On 7-09-10 10:46, njh@bandsman.co.uk via RT wrote: Show quoted text
> Queue: Test-Smoke > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=60857 > > > On 29/08/10 22:29, Abe Timmerman via RT wrote:
>>>>
>>>>> You can't use Test::Smoke to test whether Perl builds with a >>>>>
>> different >>
>>>>> compiler, because Test::Smoke ignores the values of CC and CFLAGS >>>>>
>> in >>
>>>>> your environment. >>>>>
>>>> Two options here: >>>> 1) use the -Dcc= and -Dccflags= options for configure >>>> Put these options on a single line in the first section of the >>>>
>> build >>
>>>> configurations file (perlcurrent.cfg); or (preferred) create a new >>>> configuration with its own build configurations file that has these >>>> options in a single section. >>>>
> I tried this, but it still doesn't work. > > As a test I created a new cfg file which has only one section: > > -Duseithreads > -Dccflags="-Wall -O2 -pipe"
Ah, it has to be in it's own section: # Begin of .cfg # Single line with all compiler flags -Dccflags='-Wall -O2 -pipe' = -Dusethreads = # Debug section Build configurations are composed by combining all lines from all sections, in the above example: -Dccflags='-Wall -O2 -pipe' -Dccflags='-Wall -O2 -pipe' -Dusethreads checkout the chkbcfg.pl <your.cfg> it'll tell you what configs will be smoked. Show quoted text
>> PS: These are not really bugs, please just send me e-mail with >> questions. >>
> Unfortunately you forgot to mention what your email is, so I've had to > continue to use "reply".
As for all CPAN authors: <cpanid>@cpan.org => abeltje@cpan.org Also to be found in the Test::Smoke docs. Thank you for your interest in Test::Smoke + Good luck, Abe. -- _ | "Are you pondering what I'm pondering?" ( ) | Well, I think so, Brain, but if Jimmy cracks corn, and no one cares, X | why does he keep doing it? (23 Nov 96 - A Little Off the Top) / \ |
From: njh [...] bandsman.co.uk
Fixed by using -Accflags instead of -Dccflags. There seems to be no means to close this bug!!! However it is now resolved.