#1044: Configure.pl relies too heavily on perl5 ccflags settings.
-----------------------+----------------------------------------------------
 Reporter:  doughera   |       Owner:  jkeenan 
     Type:  bug        |      Status:  assigned
 Priority:  normal     |   Milestone:          
Component:  configure  |     Version:  1.6.0   
 Severity:  medium     |    Keywords:          
     Lang:             |       Patch:          
 Platform:             |  
-----------------------+----------------------------------------------------
Changes (by jkeenan):

  * owner:  => jkeenan
  * status:  new => assigned


Comment:

 Replying to [comment:16 nwellnhof]:
 > I didn't get any further feedback on the compiler_flags branch. I still
 think it's the right approach but we will need a lot of testing on all
 kinds of platforms.

 Thanks for responding to the cage cleaner's inquiry.

 1. In order to continue work on this, I will take the ticket.  I have
 merged master into the branch in order to capture what has been done in
 master since you originally created the branch.

 2. I had merge conflicts in three files during that merge.  The ones I'm
 most worried about are in ''config/init/hints/mswin32.pm''.  I fear I may
 have deleted work that was done after the branch point which should be
 retained.  So more eyeballs would be helpful here.

 3. I have tested the branch on linux/i386 with an all-gcc build and an
 all=g++ build.  `make test` completes successfully in both cases.  I am
 currently testing the branch on darwin/ppc with my customary mixed build,
 gcc for the compiler and g++ for `ld` and `link`.  I expect all tests will
 pass except the one in ''t/dynpmc/select.t'' that is currently failing.

 4. I agree with you that we will need to get this branch tested on other
 OSes before we can merge it, particularly MSWin32 and the Cygwin/Msys
 variants that are now getting some attention.

 Thank you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1044#comment:17>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to