public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paavola@skycomputers.com
To: gcc-gnats@gcc.gnu.org
Subject: java/9677: File not found if spaces in file name
Date: Wed, 12 Feb 2003 20:26:00 -0000 [thread overview]
Message-ID: <20030212202058.17150.qmail@sources.redhat.com> (raw)
>Number: 9677
>Category: java
>Synopsis: File not found if spaces in file name
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 12 20:26:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Steve Paavola
>Release: 3.2.1
>Organization:
>Environment:
PowerPC Linux 2.4.19-4a
>Description:
The eclipse sources use directory names with spaces in them. If gcj is called with quotes around the file names, gcj determines that the files exist and calls jc1. The quotes get lost going to jc1, and jc1 complains that it can't open the source files.
$ cd /tmp
$ mkdir 'foo bar'
$ touch 'foo bar/foo.java'
$ gcj -v -save-temps -c '/tmp/foo bar/foo.java'
Reading specs from /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.2.1/specs
Reading specs from /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.2.1/../../../libgcj.spec
rename spec lib to liborig
Configured with: ../gcc-3.2.1/configure
Thread model: posix
gcc version 3.2.1
/usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/3.2.1/jc1 /tmp/foo bar/foo.java -fhash-synchronization -fuse-divide-subroutine -fuse-boehm-gc -fnon-call-exceptions -fkeep-inline-functions -quiet -dumpbase foo.java -g1 -version -o foo.s
GNU Java version 3.2.1 (powerpc-unknown-linux-gnu)
compiled by GNU C version 2.95.4 20010319 (prerelease/franzo/20011204).
Class path starts here:
./
/usr/local/share/java/libgcj-3.2.1.jar/ (system) (zip)
jc1: No such file or directory: can't open /tmp/foo
>How-To-Repeat:
See instructions in Description:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2003-02-12 20:26 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=20030212202058.17150.qmail@sources.redhat.com \
--to=paavola@skycomputers.com \
--cc=gcc-gnats@gcc.gnu.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).