From: fortinj@ibm.net
To: PARK JONG PORK <mailing@okclub.communitech.net>
Cc: ñèùüüö <kbs@swc.sec.samsung.co.kr>, gdb@cygnus.com
Subject: Re: how to build gdb with cygnus?
Date: Mon, 12 Apr 1999 05:17:00 -0000 [thread overview]
Message-ID: <3711E486.D8499C9F@ibm.net> (raw)
In-Reply-To: <000b01be84d3$f3004680$207471d2@okc1>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
What I did is went into each directory individually and ran configure.
Some of them didn't work correctly, some of them did. I then copied the
largest config.cache without errors to the base directory and ran
configure again. I believe I had one or two small errors, but ignored
them. I checked the config.cache after the errors and the correct
values were there. I don't remember which they were.
gdb then compiled, though without thread support.
regards,
John Fortin
fortinj@ibm.net
PARK JONG PORK wrote:
>
> I had same problem.
> and, new snapshot(04/xx) can't compile Perl 5.005_03 better.
>
> ----- ¿øº» ¸Ã½ÃÃö -----
> º¸³½ »ç¶÷: ±è¹ü¼ö <kbs@swc.sec.samsung.co.kr>
> ¹Ã´à »ç¶÷: <gdb@cygnus.com>
> º¸³½ ³¯ÃÂ¥: 1999³â 4¿ù 12Ãà ¿ù¿äÃà ¿ÃÃà 3:46
> æ¸ñ: how to build gdb with cygnus?
>
> > John Fortin told us:
> >
> > > All, I compiled the newest snapshot of gdb using cygwin ( after
> > fighting
> > > with the configuration. Doesn't seem to work well recursively. )
> >
> > I have the same problem with gdb-4.17 and gdb-4.18.
> > Could you tell me how you worked it out?
> >
> > Thanks,
> > Bumsoo Kim
> > kbs@swc.sec.samsung.co.kr
> >
> >
next prev parent reply other threads:[~1999-04-12 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-11 23:50 김범수
1999-04-12 4:06 ` PARK JONG PORK
1999-04-12 4:56 ` PARK JONG PORK
1999-04-12 5:17 ` fortinj [this message]
1999-04-19 19:50 김범수
1999-04-19 20:37 ` 김범수
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=3711E486.D8499C9F@ibm.net \
--to=fortinj@ibm.net \
--cc=gdb@cygnus.com \
--cc=kbs@swc.sec.samsung.co.kr \
--cc=mailing@okclub.communitech.net \
/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