From: "Roland Zerek" <rolandz@poczta.fm>
To: "gdb" <gdb@sources.redhat.com>
Subject: Problems with building - part II [gdb 6.0]
Date: Sat, 14 Feb 2004 10:57:00 -0000 [thread overview]
Message-ID: <001801c3f2e9$93b6fa50$ede1573e@DOM> (raw)
Hello again,
At the beginning I would like to tank for your answers on my first letter.
The environment I am workin with is the following:
*) operating system: winXP home edition
*) compiler: gcc 3.2 (CYGWIN 2.249.2.5)
The build process went differently than before
(http://rolandz.fm.interia.pl/gdb/1.html). Then it seemed to be problems
with file names really (spaces within them). However, now these probles
alterred with more real ones: compile or link errors. The full build log is
at http://rolandz.fm.interia.pl/gdb/2.html
I am really not very familiar with GDB internals and it is very hard job for
me to find the problem. So I am asking you for help again. TIA.
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?
--
Roland Żerek
next reply other threads:[~2004-02-14 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 10:57 Roland Zerek [this message]
2004-02-17 18:38 ` Andrew Cagney
2004-02-19 18:20 ` Roland Zerek
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='001801c3f2e9$93b6fa50$ede1573e@DOM' \
--to=rolandz@poczta.fm \
--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