develooper Front page | perl.perl5.porters | Postings from February 2008

RE: Change 33049: Fix the misplaced warnings and failing tests caused by the precision

Thread Previous
Steve Hay
February 22, 2008 10:19
RE: Change 33049: Fix the misplaced warnings and failing tests caused by the precision
Message ID:
Steve Hay wrote:
> Nicholas Clark wrote:
>> On Wed, Jan 23, 2008 at 01:30:15AM -0800, Nicholas Clark wrote:
>> Is there an automatic way to propagate these:
>>> ==== //depot/perl/win32/config.bc#177 (text) ====
>>> Index: perl/win32/config.bc
>>> --- perl/win32/config.bc#176~32953~	2008-01-11 05:36:54.000000000
>>> -0800 +++ perl/win32/config.bc	2008-01-23 01:18:41.000000000
>>>  @@ -802,6 +802,7 @@ nvFUformat='"F"'
>>>  nvGUformat='"G"'
>>>  nv_preserves_uv_bits='32'
>>>  nveformat='"e"' nvfformat='"f"'
>>>  nvgformat='"g"'
>> to their relevant headers?
>> (Better still, was there an automatic way to generate those diffs,
>> that would have saved me doing it by hand?)
> Not that I'm aware of. (If anyone knows different I'd love to know:
> I've played catch-up plenty of times in the past for these Win32
> files, and always manually.)  
> I did have the Win32 config.* and config_H.* files in sync with the
> sample files in Porting/ at one time, but I'm sure they've crept out
> of sync again, not least since #33047. I once had in mind writing a
> script to generate them automatically, perhaps using those sample
> files, and having logic in the script for what (relatively few)
> things need to change for each Win32 compiler, but (of course) I've
> never quite got round to it...      

I still don't have a fully automatic way of doing this (if that's even
possible), but I have found that the Win32 makefiles contain a
regen_config_h target for regerating the config_H.* files (the config.*
files still need hand-editing, but Porting/ at least makes
it easy to see what needs editing).

As of #33349 the makefile targets should work again, and #33350 syncs up
the config_H.* files using those targets. Hopefully I haven't broken too
much. The smoke signals should tell... (Speaking of which, I've added a
VC2008 (VC9) smoke to my schedules. It should run for the first time

Thread Previous Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About