This transaction appears to have no content
> the attached patch against r7825 suppresses stderr output during 'bc'
> step in configure
I was thinking along similar lines, but got stuck wondering: "Why is
Configure.pl looking for bc in the first place? It doesn't do anything
with the result."
The problem is complicated because there are significant differences among
bc(1) commands. For example, Solaris has a traditional bc(1) command. It
does not accept the '-v' option, and Configure.pl currently sets
has_bc='no'. The GNU version of bc(1) has many extensions beyond
traditional bc(1). It does accept a '-v' option, and Configure.pl
currently sets has_bc='yes'.
A reasonable Configure.pl plan, then, would be to construct a bc input
file representative of the sorts of things we actually use bc for, run the
system bc (if there is one), and check that the output is as it should be.
Since bc isn't used anywhere yet, I wasn't able to construct such a
"typical" bc input file.
--
Andy Dougherty doug...@lafayette.edu
> On Wed, 13 Apr 2005, Jerry Gay wrote:
>
> > the attached patch against r7825 suppresses stderr output during 'bc'
> > step in configure
>
> I was thinking along similar lines, but got stuck wondering: "Why is
> Configure.pl looking for bc in the first place? It doesn't do anything
> with the result."
bernhard, (r7757), notes:
r7757 | bernhard | 2005-04-02 03:00:05 -0800 (Sat, 02 Apr 2005) | 4 lines
Changed paths:
M /trunk/MANIFEST
A /trunk/config/auto/bc.pl
M /trunk/config/auto/perldoc.pl
M /trunk/lib/Parrot/Configure/RunSteps.pm
Check for existence of 'bc', the basic calculator, on the system.
When running tests for 'Parrot bc', I'd like to doublecheck
with the standard 'bc'.
so it seems he's using it for testing against parrot. perhaps there's some
basic functionality that 'bc' shares in its many incarnations, including a
method of detection that can be used reliably during configure. since i
can't find 'Parrot bc', i'll wait for bernhard to weigh in.
> Andy Dougherty doug...@lafayette.edu
~jerry
> The problem is complicated because there are significant differences among
> bc(1) commands. For example, Solaris has a traditional bc(1) command. It
> does not accept the '-v' option, and Configure.pl currently sets
> has_bc='no'. The GNU version of bc(1) has many extensions beyond
> traditional bc(1). It does accept a '-v' option, and Configure.pl
> currently sets has_bc='yes'.
'Parrot bc' is planned to support only the POSIX standard. GNU bc has a
'-s', standard, option. So it is a good target for verifying 'Parrot bc'.
For now it might be the easiest thing to check only for 'has_gnu_bc'.
Ultimatively the bc test should end up in 'languages/bc', but AFAIK,
there is no language specific config yet.
CU, Bernhard
--
**************************************************
Dipl.-Physiker Bernhard Schmalhofer
Senior Developer
Biomax Informatics AG
Lochhamer Str. 11
82152 Martinsried, Germany
Tel: +49 89 895574-839
Fax: +49 89 895574-825
eMail: Bernhard.S...@biomax.com
Website: www.biomax.com
**************************************************
I suggest to use the new "capture_output" (from
lib/Parrot/Configure/Step.pm)...
BTW: the same problem is in
- config/inter/progs.pl
- config/init/hints/mswin32.pl
- config/auto/antlr.pl
- config/auto/python.pl
On Win98/VC6, there is a file "&1" after Configure.pl ran.
jens