From: 김범수 <kbs@swc.sec.samsung.co.kr>
To: "'fortinj@ibm.net'" <fortinj@ibm.net>
Cc: "'mailing@okclub.communitech.net'"
<mailing@okclub.communitech.net>,
"'gdb@cygnus.com'" <gdb@cygnus.com>
Subject: RE: how to build gdb with cygnus?
Date: Mon, 19 Apr 1999 19:50:00 -0000 [thread overview]
Message-ID: <003928C86BDDD211BC8000A0C98A6129031752@SWC> (raw)
Thank you very much.
It worked as you said.
best regards,
Bumsoo Kim
kbs@swc.sec.samsung.co.kr
> -----Original Message-----
> From: fortinj@ibm.net [SMTP:fortinj@ibm.net]
> Sent: Monday, April 12, 1999 9:18 PM
> To: PARK JONG PORK
^[$)C
> Cc: \x0e!>\x0fe\x0e)v\x0fu\x0e(y\x0fo; gdb@cygnus.com
> Subject: Re: how to build gdb with cygnus?
>
> 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.
> >
> > ----- \x0e"/)*(,!m ",(-(v\x0fAAo -----
> > \x0e(,",)x(v !m\x0fc\x0e"R!@\x0f: \x0e!>\x0fe\x0e)v\x0fu\x0e(y\x0fo <kbs@swc.sec.samsung.co.kr>
> > \x0e)v(-"%\x0fA \x0e!m\x0fc\x0e"R!@\x0f: <gdb@cygnus.com>
> > \x0e(,",)x(v )x\x0f?A\x0e!M\x0f: 1999\x0e)x\x0fa 4\x0e"/\x0fu 12AI \x0e"/\x0fu\x0e"/\x0faAI \x0e"/\x0fAEA 3:46
> > A|\x0e",\x0fn: 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
> > >
> > >
WARNING: multiple messages have this Message-ID
From: 김범수 <kbs@swc.sec.samsung.co.kr>
To: "'fortinj@ibm.net'" <fortinj@ibm.net>
Cc: "'mailing@okclub.communitech.net'"
<mailing@okclub.communitech.net>,
"'gdb@cygnus.com'" <gdb@cygnus.com>
Subject: RE: how to build gdb with cygnus?
Date: Mon, 19 Apr 1999 20:37:00 -0000 [thread overview]
Message-ID: <003928C86BDDD211BC8000A0C98A6129031752@SWC> (raw)
Message-ID: <19990419203700.MHD5U1GEPEr-11RlIDlWZ2nKqC5Ed0P8kGloXiWSsTw@z> (raw)
Thank you very much.
It worked as you said.
best regards,
Bumsoo Kim
kbs@swc.sec.samsung.co.kr
> -----Original Message-----
> From: fortinj@ibm.net [SMTP:fortinj@ibm.net]
> Sent: Monday, April 12, 1999 9:18 PM
> To: PARK JONG PORK
^[$)C
> Cc: \x0e!>\x0fe\x0e)v\x0fu\x0e(y\x0fo; gdb@cygnus.com
> Subject: Re: how to build gdb with cygnus?
>
> 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.
> >
> > ----- \x0e"/)*(,!m ",(-(v\x0fAAo -----
> > \x0e(,",)x(v !m\x0fc\x0e"R!@\x0f: \x0e!>\x0fe\x0e)v\x0fu\x0e(y\x0fo <kbs@swc.sec.samsung.co.kr>
> > \x0e)v(-"%\x0fA \x0e!m\x0fc\x0e"R!@\x0f: <gdb@cygnus.com>
> > \x0e(,",)x(v )x\x0f?A\x0e!M\x0f: 1999\x0e)x\x0fa 4\x0e"/\x0fu 12AI \x0e"/\x0fu\x0e"/\x0faAI \x0e"/\x0fAEA 3:46
> > A|\x0e",\x0fn: 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
> > >
> > >
From jauming@yahoo.com Tue Apr 20 04:49:00 1999
From: JauMing Tseng <jauming@yahoo.com>
To: gdb gdb <gdb@cygnus.com>
Subject: source of cygmon
Date: Tue, 20 Apr 1999 04:49:00 -0000
Message-id: <19990420103539.6905.rocketmail@send102.yahoomail.com>
X-SW-Source: 1999-04/msg00052.html
Content-length: 238
[source of cygmon]
[?]is source of CygMon freely available?
thx in advanced!:)
==
--
Regards,
Kevin.:)
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
next reply other threads:[~1999-04-19 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 19:50 김범수 [this message]
1999-04-19 20:37 ` 김범수
-- strict thread matches above, loose matches on Subject: below --
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
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=003928C86BDDD211BC8000A0C98A6129031752@SWC \
--to=kbs@swc.sec.samsung.co.kr \
--cc=fortinj@ibm.net \
--cc=gdb@cygnus.com \
--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