Kevin Horton wrote:
> On 29 Oct 2007, at 21:27, Robert T Wyatt wrote:
> 
>> Building cadabra kind of dies because it doesn't find breqn (which is
>> installed):
>>
>> checking for latex... yes
>> -n checking for breqn package...

The "-n" raises a certain suspicion...

>> ^Z
>> [1]+  Stopped                 fink install cadabra
[]
> I'll look into this as soon as I have Leopard.  But, I'm going to be  
> tied up with a family visit for the next week, so this won't happen  
> quickly.

...and yes, it's that @!#?#@ broken echo command again! The cadabra 
configure script tests for breqn by running a small latex file through 
latex. It produces the latex file using the following command line

echo 
"\nonstopmode\\documentclass{article}\\usepackage{breqn}\\begin{document}\\begin{dmath*}x^2\\end{dmath*}\\end{document}\n"
 
 > conftmp.tex

The result is supposed to be a one-line file containing

\nonstopmode\documentclass{article}\usepackage{breqn}\begin{document}\begin{dmath*}x^2\end{dmath*}\end{document}\n

which then compiles perfectly in latex.

This is, indeed, the output if you run the above command in bash, even 
on Leopard. It is also the output if you run it in sh on earlier Mac OSX 
versions, or in sh on other operating systems. But if you run it in 
Leopard's sh, you get a one-line file absurdly containing a blank line 
and then

onstopmode\documentclass{article}\usepackage{breqn}^Hegin{document}^Hegin{dmath*}x^2^[nd{dmath*}^[nd{document}

That is, it interprets the escaped backslashes plus the following 
character as escape sequences. This is a buggy implementation not of 
POSIX conformance, but of XSI extensions of the POSIX standard, see
<http://www.opengroup.org/onlinepubs/009695399/utilities/echo.html>
It is a pity that Apple went this way. For the moment we can complain 
and file bugs, but we have to live with it.

Several workarounds are possible:
- Replace every "echo " by "/bin/echo " in configure
- Replace in the first line of configure sh by bash
- Change the failing echo command lines so that they don't use 
backslashes as escape sequences, i.e. replace the one-liner by several 
lines.

-- 
Martin







-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to