This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: ITA: gcc-mingw-* gcc-3 -mno-cygwin support packages; ITP: mingw-binutils/mingw-gcc-* cross compiler
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: Mailing List: CygWin-Apps <cygwin-apps at cygwin dot com>
- Date: Mon, 24 Jan 2011 11:54:52 -0500
- Subject: Re: ITA: gcc-mingw-* gcc-3 -mno-cygwin support packages; ITP: mingw-binutils/mingw-gcc-* cross compiler
- References: <4CEC401E.4060506@cwilson.fastmail.fm> <1295843772.348.11.camel@YAAKOV04>
- Reply-to: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
On 1/23/2011 11:36 PM, Yaakov (Cygwin/X) wrote:
> On Tue, 2010-11-23 at 17:28 -0500, Charles Wilson wrote:
>> Updated packages are available by pointing setup.exe here:
>> http://cygutils.fruitbat.org/ITP/mingw-gcc/
>
> Could you sign your setup.ini and post the GPG key (for setup -K)?
Err...not reliably. I'm still confused about GPG and its relationship
with multiple email aliases. I don't really WANT <s>people</s>
automated bots connecting my various aliases together via a shared
keyring, but that appears to be the only way to easily use GPG with
multiple aliases. The alternative is to use completely separate
keyrings...which is a huge pain. So...I've never really bothered to
"get into" the whole GPG thing (*), which means that any key I have is
not hooked into any web-of-trust. So, I could sign it, and post a
public key...but could anybody REALLY trust it?
-----------
(*) About 18 months ago, I tried to sort all this out along with porting
gnupg2 and its prereqs -- and eventually ITP'ed all but gnupg2 itself.
However, I ran into a couple of roadblocks and tabled any further
progress pending...
"Passing file descriptors over a socket"
http://cygwin.com/ml/cygwin/2009-10/msg00397.html
"GNU pth + cygwin + fork [Was: Re: fork failure?]"
http://cygwin.com/ml/cygwin/2009-10/msg00467.html
(cgf: "Let me add a new data point: I'll implement sigaltstack after
1.7.1 is released." -- http://cygwin.com/ml/cygwin/2009-07/msg00859.html )
Also, I had a long message summarizing all these travails, and talking
about the (then-)current state of my gnupg2 port, and asking for advice
as to whether I should ITP it in its not-completely-working state
(gpg-agent no-workee, but everything else seemed to). I never got a
response, so...I tabled everything.
I now know why I never got a response. I misaddressed the message, but
never noticed because I got my Bcc:! I'll revisit in another, more
appropriate thread.
-----------
>> = mingw-zlib-1.2.5-4-src.tar.bz2
>> = mingw-zlib-1.2.5-4.tar.bz2
>> = mingw-zlib-devel-1.2.5-4.tar.bz2
>> = mingw-zlib1-1.2.5-4.tar.bz2
>
> The sharedlibdir variable in zlib.pc needs to be fixed.
Err...why?
exec_prefix=/usr/i686-pc-mingw32/sys-root/mingw
sharedlibdir=$(exec_prefix)/bin
$ ls /usr/i686-pc-mingw32/sys-root/mingw/bin/libbz*
/usr/i686-pc-mingw32/sys-root/mingw/bin/libbz2-1.dll
I thought the installed files were NOT going to reflect paths on the
actual $host, but instead were going to reflect the paths on $build,
with the possible exception of those areas where specialized sysroot
support with the special '=' character ('=/mingw/foo') was available?
Are you suggesting that the $sharedlibdir variable in .pc files is an
appropriate place for '=' substitution?
--
Chuck