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

Comment(by nwellnhof):

 First of all, it's a long term goal to reduce the dependency on Perl 5 in
 Parrot's config, build and test system.

 Then, as I described above, using basically random compiler and linker
 flags from another project breaks if Perl was compiled with a different
 compiler.

 Even if you use the same compiler, there are some compiler and linker
 flags in Perl's Config hash that Parrot simply doesn't need. Even worse,
 some of them cause build failures with Parrot. Have a look at all the code
 in the configuration system that removes certain conflicting flags. It
 seems that this has caused numerous build failures in that past and it
 might cause build failures with every new or untested Perl version.

 I had a look at many configs from Smolder builds, and sometimes Parrot is
 linked against completely unneeded libraries just because Perl happens to
 use them. Do we want to special case every one of them?

 If we are building with a supported compiler on a supported platform, it
 isn't very hard to determine the correct compiler and linker flags. So I
 don't see what information we are throwing away. IMO, the whole thing has
 been a hack from the beginning that was probably nice to get the config
 system started but should have been fixed a long time ago.

 And as I said above, I can offer to add an option to use the Perl flags as
 default.

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1044#comment:11>
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