Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] fix config.rpath for cygwin/mingw
Date: Wed, 20 Jul 2011 20:29:00 -0000	[thread overview]
Message-ID: <20110720192506.GB2455@ednor.casa.cgf.cx> (raw)
In-Reply-To: <1311145448.7796.40.camel@YAAKOV04>

On Wed, Jul 20, 2011 at 02:04:06AM -0500, Yaakov (Cygwin/X) wrote:
>The gettext macros use config.rpath to determine the link library name
>of libiconv and libintl (on non-glibc platforms); the import library
>suffix is of importance, not the runtime library suffix.  On PE
>platforms, these differ, and by using the latter in config.rpath, the
>gettext macros think shared import libraries aren't available, and
>forces linking with the static library instead.
>
>(FWIW, gettext itself has already been fixed in this regard, but
>updating to the latest version of those files is much more invasive.)
>
>The attached patch fixes linking with the shared import libraries.  We
>have been using this patch for over a year on i686-pc-cygwin hosted
>toolchains (both native- and cross-target).
>
>
>Yaakov
>Cygwin Ports
>
>

>2011-07-20  Yaakov Selkowitz  <yselkowitz@users.sourceforge.net>
>
>	* config.rpath [cygwin|mingw*|pw32] (shrext): Change to .dll.a,
>	to match the import library suffix.

Looks ok.  Do you have a CVS tree checked out which would enable you to
check this in?  You probably have privileges since gdb overlaps with Cygwin.

cgf


  reply	other threads:[~2011-07-20 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 11:02 Yaakov (Cygwin/X)
2011-07-20 20:29 ` Christopher Faylor [this message]
2011-07-20 21:03   ` Yaakov (Cygwin/X)
2011-07-21  7:03     ` Christopher Faylor

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=20110720192506.GB2455@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=yselkowitz@users.sourceforge.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