On 28/10/2015 05:25 μμ, Michael Havens wrote:
On Wed, Oct 28, 2015 at 11:00 AM, Pierre Labastie <[email protected] <mailto:[email protected]>> wrote: Two solutions: - Use ln -sf (force) - remove the link command from your script... Thank you Pierre force option it is. As for my first run having already created it not really. It ran for lie 10 seconds and then barfed up the rest of the script in errors followed with the link error. Wait.... it is just a link! It is linking to the program. It is linking to the recompiled program if I recompile it. I get it!
If I got it right, a command in your script failed and the script continued. If that's the case, the rest commands naturally failed,
because each one depends on the previous to be executed with no errors. Thus it is desirable in build scripts and scripts in general to exit when a command fails, so that the rest commands are not executed just to through out errors who make it harder to track down the first one that failed. To accomplish that you can make the first line #!/bin/bash -e or add the line "set -e" under #!/bin/bash and your scripts will exit when a command fails. -- Thanos -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
