Dan Nicholson wrote:
> Hey, Jeremy, just a little nit. The new specs readjustment will fail
> because we're piping input to perl, but then using the -i parameter to
> work on the `dirname ...`/specs file. This fails if that file doesn't
> exist. Probably, we should drop -i and redirect the output:
It doesn't fail. I've tested it again here and it's fine. Try directing
it to a temporary location that you know doesn't exist, and look at the
finished product.
gcc -dumpspecs | \
perl -pi -e 's@/tools/lib/ld@/lib/[EMAIL PROTECTED];' \
-e '[EMAIL PROTECTED]:[EMAIL PROTECTED]/usr/lib/ @g;' > \
/tmp/specs
Of course, it also appears to work just fine without the -i, too.
> Or do the -dumpspecs > first, using SPECFILE=... like before. In
> fact, it might not be a bad idea to leave the SPECFILE=... stuff in
> there anyway so we can use the variable. That command is getting to
> be quite a handful, and we don't want the noobs re-running the perl
> command.
Re-running the command shouldn't hurt anything, right? Especially since
we're piping the output and then using '>' to create a new file. Am I
missing something?
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
