public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29473] New: [gdb/build] gdb/gdb_buildall.sh: No such file or directory: /usr/local/share/gdb/guile/gdb/boot.scm
Date: Thu, 11 Aug 2022 15:33:31 +0000	[thread overview]
Message-ID: <bug-29473-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29473

            Bug ID: 29473
           Summary: [gdb/build] gdb/gdb_buildall.sh: No such file or
                    directory: /usr/local/share/gdb/guile/gdb/boot.scm
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I tried out gdb/gdb_buildall.sh:
...
$ bash ./src/gdb/gdb_buildall.sh -j 5 $(pwd -P)/src $(pwd -P)/build.tmp
./src/gdb/gdb_buildall.sh: line 27: warning: setlocale: LC_ALL: cannot change
locale (c)
Starting gdb_buildall.sh ...
... /home/vries/gdb_versions/devel/binutils-gdb.git/configure
--enable-targets=all
... make -j 5
maint print architecture for
... No such file or directory:
"/usr/local/share/gdb/guile/gdb/boot.scm"./src/gdb/gdb_buildall.sh: line 229:
$log_file: ambiguous redirect
./src/gdb/gdb_buildall.sh: line 231: test: too many arguments
grep: No: No such file or directory
grep: such: No such file or directory
grep: file: No such file or directory
grep: or: No such file or directory
grep: directory_: No such file or directory
grep: "/usr/local/share/gdb/guile/gdb/boot.scm".log: No such file or directory
 OK
sed: can't read No: No such file or directory
sed: can't read such: No such file or directory
sed: can't read file: No such file or directory
sed: can't read or: No such file or directory
sed: can't read directory_: No such file or directory
sed: can't read "/usr/local/share/gdb/guile/gdb/boot.scm".log: No such file or
directory
sed: can't read No: No such file or directory
sed: can't read such: No such file or directory
sed: can't read file: No such file or directory
sed: can't read or: No such file or directory
sed: can't read directory_: No such file or directory
sed: can't read "/usr/local/share/gdb/guile/gdb/boot.scm".log: No such file or
directory
mv: target '"/usr/local/share/gdb/guile/gdb/boot.scm".log' is not a directory
done.
...

So, we do:
...
$ ./build.tmp/ALL/gdb/gdb -ex "set architecture"
Exception caught while booting Guile.
Error in function "open-file":
No such file or directory: "/usr/local/share/gdb/guile/gdb/boot.scm"
./build.tmp/ALL/gdb/gdb: warning: Could not complete Guile gdb module
initialization from:
/usr/local/share/gdb/guile/gdb/boot.scm.
Limited Guile support is available.
Suggest passing --data-directory=/path/to/gdb/data-directory.
Requires an argument. Valid arguments are ARC600, ... , tilegx32, auto.
...
and conclude that 'No such file or directory:
"/usr/local/share/gdb/guile/gdb/boot.scm"' is a target, and then bail out when
we try to redirect to $target.log (because there's a space in the file name and
log_file is not quoted in cat > $log_file).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2022-08-11 15:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29473-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).