[src/trunk]: src/external/gpl3/gdb/dist/bfd If the shell does not support the...

[apb <apb%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/400a5cdc0db7
branches:  trunk
changeset: 790488:400a5cdc0db7
user:      apb <apb%NetBSD.org@localhost>
date:      Tue Oct 15 07:14:59 2013 +0000

description:
If the shell does not support the $LINENO variable, then use
"bfd_configure.lineno" instead of "configure.lineno" as the name of the
a version of the script that has had all uses of $LINENO converted to
literal line numbers.

Now building tools via "MKCROSSGDB=yes build.sh tools" works again, even
if the shell does not support $LINENO.

The previous problem was caused by an interaction
between the way .../gdb/dist/opcodes/configure executes
"${srcdir}/../bfd/configure --version", and the way both configure
scripts tried to create and then execute configure.lineno scripts.
Both configure.lineno scripts were created in the same OBJDIR,
with the configure.lineno from .../bfd/configure overwriting the
configure.lineno from .../opcodes/configure, while the latter was
still running.

diffstat:

 external/gpl3/gdb/dist/bfd/configure |  1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diffs (11 lines):

diff -r a491b01d431d -r 400a5cdc0db7 external/gpl3/gdb/dist/bfd/configure
--- a/external/gpl3/gdb/dist/bfd/configure      Mon Oct 14 22:23:22 2013 +0000
+++ b/external/gpl3/gdb/dist/bfd/configure      Tue Oct 15 07:14:59 2013 +0000
@@ -428,6 +428,7 @@
   as_lineno_2=$LINENO as_lineno_2a=$LINENO
   eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" &&
   test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || {
+  as_me=bfd_$as_me # XXX don't overwrite our caller's configure.lineno
   # Blame Lee E. McMahon (1931-1989) for sed's syntax.  :-)
   sed -n '
     p