#1044: Configure.pl relies too heavily on perl5 ccflags settings.
-----------------------+----------------------------------------------------
Reporter: doughera | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: configure | Version: 1.6.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-----------------------+----------------------------------------------------
Comment(by jkeenan):
This is part of our long-term technical debt. Excerpts from the
discussion in the original RT:
Leopold Toetsch on Mar 31 2006:
{{{
I've tried:
$ perl Configure.pl --cc=gcc --link=gcc --ld=gcc --cxx=gcc
--verbose-step=gcc
and got:
Determining if your C compiler is actually gcc...gcc
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xarch=v8 -D_TS_ERRNO
-I./include -c test.c
gcc: language arch=v8 not recognized
From perl -V:
Compiler:
cc='cc', ccflags ='-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-xarch=v8 -D_TS_ERRNO',
optimize='-xO3 -xspace -xildoff',
That is, our config system is still using perl5 config vars blindly w/o
further inspection and ignores commandline option at least partially.
$ uname -a
SunOS z1.t2000.develooper.com 5.10 Generic_118833-03 sun4v sparc
SUNW,Sun-Fire-T200
$ perl -v
This is perl, v5.8.4 built for sun4-solaris-64int
$ cc -V
cc: Sun C 5.8 2005/10/13
$ gcc --version
gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
}}}
Andy Dougherty subsequently explained that this is not a Solaris-specific
problem:
{{{
...[B]ut Solaris is probably one of the more
popular platforms where this is appears. (The usual issue is that the
vendor supplies a perl compiled with the vendor's compiler, but an end
user wishes to use gcc.)
}}}
Andy also noted:
{{{
Anyone can check [for the existence of this problem] by editing
their perl Config settings and seeing that they get passed through
unquestioningly to parrot.
}}}
So, the problem with `ccflags` is really a subset of our larger dependency
on the Perl t `%Config` with which we begin our configuration in the
second configuration step: `init::defaults`. The problem will go away
whenever we can figure out a way to extract ourselves from that
dependency. TT #619 is a long-term roadmap ticket covering this issue and
then some.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1044#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
