Mail Archives: djgpp/1999/07/02/11:34:50
Hi Eli,
Yesterday I could spend some time in the sed thing and found the root
of the problem. The problem was not with my configuration but with the
script you sent me. I have no idea why it works for you but the problem
is in the fragment below:
# po2tbl.sed.in is invalid on MSDOS
s|po2tbl\.sed\.in|po2tbl-sed.in|g
# Additional editing of Makefiles
/ac_given_INSTALL=/,/^CEOF/ {
/^s%@l@%/a\
/TEXINPUTS=/s,:,\\\\\\\\\\\\\\;,g\
/PATH=/s,:,\\\\\\\;,g\
s,po2tbl\\.sed\\.in,po2tbl-sed.in,g\
s,config\\.h\\.in,config.h-in,g\
s,Makefile\\.in\\.in,Makefile.in-in,g\
s,Makefile\\.am\\.in,Makefile.am-in,g\
}
I tried this in three different machines( Dos/DJGPP, Solaris & Linux)
and got the same result. The problem starts in the line :
/TEXINPUTS=/s,:,\\\\\\\\\\\\\\;,g\
Sed complains about the last char "\" in this line and in the lines
after it. The error is something like "Unsupported s/ extension". Is
this a gnu extension? I browsed the info files and man pages in all
three machines and couldn't find the reason for the "\". My hypothesis
is that all this lines are arguments for the first line (/^s%@l@%/a\) so
they are appended to the sed script (in the autoconf config file) that
edits the TCL makefile.
BUT there are no occurrences of "ac_given_INSTALL=" in the configure
script. There is something close, that is "ac_given_source=" and between
this and a ^CEOF the is a sed script that is applied in the makefile.
Eli, could you comment about the "\\" present in the sed code above? I
didn't understood the "\\." and the "\\\\\\\\\\;" parts. To be more
specific why the 2nd line (s|po2tbl\.sed\.in|po2tbl-sed.in|g) and the
9th line (s,po2tbl\\.sed\\.in,po2tbl-sed.in,g\) are so different ( \\.
vs \.)
Thank you,
Edevaldo
- Raw text -