I was wondering if this might be a better fit then <execute command="sed"> <PARAM>-e '[EMAIL PROTECTED](^CROSS_SYSTEM_HEADER_DIR =\)[EMAIL PROTECTED] /tools/[EMAIL PROTECTED]'</param> <param>-i gcc/Makefile.in</param> </execute>
I see you have it slightly differently why put -i by its self? and no -e? i see its a cross compile insted of hlfs but was wondering. <execute command="sed"> <param>-i</param> <param>"[EMAIL PROTECTED](^CROSS_SYSTEM_HEADER_DIR =\)[EMAIL PROTECTED] /tools/[EMAIL PROTECTED]"</param> <param>gcc/Makefile.in</param> </execute> Thomas Pegg <[EMAIL PROTECTED]> wrote .. > The syntax is right, but you won't get the result you would expect, the > search_replace element does not interface to sed in any way, therefore > for a sed like that it's best to use an execute element. > > > echo " > > #undef STARTFILE_PREFIX_SPEC > > #define STARTFILE_PREFIX_SPEC \"/tools/lib/\"" >> gcc/config/linux.h > > For that it's best to use a textdump element for this. > > For an example of both cases see here: http://tinyurl.com/8nl86 > > -- > Thomas > LFS User : 4729 / Linux User : 298329 > kitt - Powered by: Linux 2.6.11 > 09:06:08 up 8 days, 17:11, 7 users, load average: 1.05, 0.87, 0.65
-- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
