From: "Roland Zerek" <rolandz@poczta.fm>
To: "Andrew Cagney" <cagney@gnu.org>
Cc: "gdb" <gdb@sources.redhat.com>
Subject: Re: Problems with building - part II [gdb 6.0]
Date: Thu, 19 Feb 2004 18:20:00 -0000 [thread overview]
Message-ID: <001d01c3f715$41b60e50$54b7573e@DOM> (raw)
In-Reply-To: <40325FAB.8070201@gnu.org>
> > A'propos spaces in file names: I think this problem does not exist in
> > unix-like systems anymore. So why it does here. The matter of notation?
> If I try to build GDB in a directory with spaces on a UNIX system,
> similar problems occure.
> $ pwd
> /tmp/sp ce
> $ .../configure && make
> ...
> creating calc.h
> cd: can't cd to /tmp/sp
> $
> The immediate problem here isn't with windows. Rather its with the
> existing build system which is just not tooled up to handle spaces in
> file names.
Yes, I agree. I've forgotten that the build environment might be
incorrect...
> The only reason that this appears to be windows specific
> is because only windows systems tend to have spaces in files (on windows
> creating a file with a space is easy, on UNIX it's pain).
Anyway, it looks the makefile is not perfect. In most cases (unix/linux) it
works, but if something is not quite standard then problems come.
> However, also note that, for similar reasons, once GDB is built it will
> have problems: GDB will not open symbol files if there is a space in the
> filename or path
(Un)fortunatelly, I've already noticed it. It costed me few hours ;-( Only I
wonder, what if file names being put into quotations...
Roland
prev parent reply other threads:[~2004-02-19 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 10:57 Roland Zerek
2004-02-17 18:38 ` Andrew Cagney
2004-02-19 18:20 ` Roland Zerek [this message]
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='001d01c3f715$41b60e50$54b7573e@DOM' \
--to=rolandz@poczta.fm \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/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