From: Bob Rossi <bob_rossi@cox.net>
To: Fahd Abidi <fabidi@ultsol.com>
Cc: gdb@sourceware.org
Subject: Re: trying to build gdb with renamed cygwin1.dll
Date: Mon, 30 Apr 2007 15:10:00 -0000 [thread overview]
Message-ID: <20070430150955.GO3759@cox.net> (raw)
In-Reply-To: <071DB0C788671B48940BC79F8B4930691181F4@ultsol01.tewks.ultsol.local>
On Mon, Apr 30, 2007 at 11:09:12AM -0400, Fahd Abidi wrote:
> Hello,
>
> I was trying to build a gdb version that would use a renamed version of
> cygwin1.dll and some of the other dll's that gdb seem to depend on. I
> determined all the dll's that gdb relies on using the "cygcheck" command
>
> My purpose is to try and build a gdb that so I can move it across
> different windows platforms with out worrying about newer or older
> versions of the cygwin dll interfering. I already looked at the MinGW
> option but the newer versions of gdb do not build against mingw32.
IMO, this is a really bad idea. The cygwin1.dll uses shared memory
at a fixed location. So, renaming the dll won't help. You will still
get the same old errors.
> My procedure was something like so, copied and renamed the dll's
> cygwin1, cygiconv-2,cygitl-3,cygcurses-8,tcl84,tk84 into another
> directory. Then tried to compile gdb against these renamed dll's by
> using the --libdir configure option. Unfortunately the resulting gdb
> executable totally ignores these renamed libraries and still links
> against the original dlls.
>
> Is this going to be possible to do?
No, don't do it. Stop where you are.
Bob Rossi
next prev parent reply other threads:[~2007-04-30 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 15:05 Fahd Abidi
2007-04-30 15:10 ` Bob Rossi [this message]
2007-04-30 15:13 ` Bob Rossi
2007-04-30 15:18 ` Andrew STUBBS
2007-04-30 15:32 ` Brian Dessent
2007-04-30 15:38 Fahd Abidi
2007-04-30 15:49 ` Andrew STUBBS
2007-04-30 15:57 ` Brian Dessent
2007-04-30 16:15 ` Andrew STUBBS
2007-04-30 16:38 Fahd Abidi
2007-04-30 17:04 ` Andrew STUBBS
2007-04-30 20:12 ` Dave Korn
2007-04-30 20:18 ` Daniel Jacobowitz
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=20070430150955.GO3759@cox.net \
--to=bob_rossi@cox.net \
--cc=fabidi@ultsol.com \
--cc=gdb@sourceware.org \
/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