From: Christopher Faylor <cgf@redhat.com>
To: gdb <gdb@sources.redhat.com>
Cc: Roland Zerek <rolandz@poczta.fm>
Subject: Re: Problems with building [gdb 6.0]
Date: Wed, 11 Feb 2004 05:22:00 -0000 [thread overview]
Message-ID: <20040211052236.GA9887@redhat.com> (raw)
In-Reply-To: <20040211051509.GA22903@nevyn.them.org>
[reply-to set]
On Wed, Feb 11, 2004 at 12:15:09AM -0500, Daniel Jacobowitz wrote:
>On Tue, Feb 10, 2004 at 10:43:09AM +0100, Roland Zerek wrote:
>>I am writting this letter after few times I was trying to build gdb 6.0
>>from sources. The environment is as follows:
>>*) operating system: winXP home edition
>>*) compiler: gcc 3.2 (CYGWIN 2.249.2.5)
>>
>>It goes quite well for some time and then throws problems. Although I
>>understand messages, I have no idea of how to solve problems reported.
>>The log of gdb build can be found at
>>http://rolandz.fm.interia.pl/gdblog.html
>>
>>Please anyone help me... TIA
>
>Try building in a directory with no spaces in the pathname. I don't
>konw if that's supposed to work, but judging from the error messages,
>it looks like it doesn't.
It should work but it is a frequent cause for complaint on cygwin, not
for anything to do with cygwin, but because most people on UNIX don't use
directories with spaces and so there are unknown assumptions in the build
process. Of course, Windows loves to use directories with spaces in them.
And, btw, that's not a valid cygwin version number. You can find the
version by typing 'uname -s'.
cgf
next prev parent reply other threads:[~2004-02-11 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 9:43 Roland Zerek
2004-02-11 5:15 ` Daniel Jacobowitz
2004-02-11 5:22 ` Christopher Faylor [this message]
2004-02-11 5:50 ` Eli Zaretskii
2004-02-11 10:27 ` Output the filename ,the function name and the line number after returning from a function call murugesan
2004-02-11 13:08 ` Bob Rossi
2004-02-11 16:38 ` murugesan
2004-02-11 16:43 ` murugesan
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=20040211052236.GA9887@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=rolandz@poczta.fm \
/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