We build Tcl 8.4 at work, among many other things. It fails to build on one HPUX machine when built from the overnight build infrastructure; when built manually it worked fine. The error was a parse error from sed, somewhere in the depths of config.status. The actual offending command was identical though there was some slight difference further up the script (just path names). Moving the command itself further up the script identified a point (not obviously related to those differences) where it all started behaving (but that's no good as a solution of course as it's automatically generated). I'd already managed to eliminate environmental differences.
I gave up and installed GNU sed and it just worked.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2003-07-08 12:55 am (UTC)We build Tcl 8.4 at work, among many other things. It fails to build on one HPUX machine when built from the overnight build infrastructure; when built manually it worked fine. The error was a parse error from sed, somewhere in the depths of config.status. The actual offending command was identical though there was some slight difference further up the script (just path names). Moving the command itself further up the script identified a point (not obviously related to those differences) where it all started behaving (but that's no good as a solution of course as it's automatically generated). I'd already managed to eliminate environmental differences.
I gave up and installed GNU sed and it just worked.