DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=ZK6fc7
	xV8Yyu6h1FcHKAbDV2+P0p0/vPLEX7W+G6EWDkV/4E8j0JPFJ62Ug0+4JNXQW14A
	elyR835dVjp08ceFckOsJJxLiCXcUL5CFlewA5H40WSuh7bS2GqjN0AAVupOIjFI
	OJYEGudEN5gj0fwTKiPQtAMZd9wfQw55/YG4Y=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <57C41FCE.8040304@gmail.com>
Date: Mon, 29 Aug 2016 19:43:10 +0800
From: JonY <10walls AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:25.4) Gecko/20150524 FossaMail/25.1.5
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: x86_64-w64-mingw32-ld lib dir configuration issue
References: <CACDsba3MD78H+zLsAR336OwUB4rSa6xr9MDBigqRHK=qaXvNNQ AT mail DOT gmail DOT com>
In-Reply-To: <CACDsba3MD78H+zLsAR336OwUB4rSa6xr9MDBigqRHK=qaXvNNQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3JTCrkOOlgngG3EHx98cAwEcIgeLu1Urp"

--3JTCrkOOlgngG3EHx98cAwEcIgeLu1Urp
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 8/29/2016 10:06, Whek rin wrote:
> The utility x86_64-w64-mingw32-ld from package mingw-x86_64-binutils
> cannot by default find libraries from the path
> /usr/x86_64-w64-mingw32/sysroot/mingw/lib, where the package
> mingw64-x86_64-runtime installs them. I believe this is a build
> configuration issue. I've attached a zip file which contains a test
> case which illustrates the issue. Inspect and run
> build_hellotest_mingw.sh and it's output, in particular how it can't
> find e.g. libkernel32 without a -L argument to the correct location.
> I renamed the .zip to .z__ to get around the spam filters, you may
> need to rename it to open it.
> Thanks, Matt
>=20

Though I agree that this is a path search bug that should be fixed,
please do not abuse ld by using it directly. Use the frontend driver
instead.


--3JTCrkOOlgngG3EHx98cAwEcIgeLu1Urp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJXxB/VAAoJEHE7X+KcFF1FrycP/iG8KnslBuKFlyGuJcNK7nSU
p60bTlMzJibQGMTH2ZppX1Q0ffgbpec6SifR+xyvzOGbfEMW73XnZbHx/0HON1ZL
dXmdsygi01o+bxhYbpEPnGJIbTxpV0XtZ82ZaZ/znN8cMt77p06oPEDpALlQ+lv8
iZaAaC3x9A4HYucDhuTcUjJ7u3WxlgNuNZm3MNQn2D3RSrawToOCPhbrrxnXK1yU
9DG8VwE4yIlgY54FlxNNzKjbkOBK5kVmRUfE5sFzE+5IoaM6a6rM0LjpG12B+nll
eyOyqrAkG2sajqkpz4A/40VNAxCUsEEp/9FEgVzVl0tfeauw/oI6mL1tweC0rXHR
D9ZvKbWms3p/vqZlkanSqxZrslhjUN3AnRqingic2hyKThmbWzUtmq3CS4hiUebH
CWttLnefWgUad2ASLaOSqMVm86BqBlV1RPcdO7POayomSyXjtC7iV60jeikfFL39
FVBmkZIbQ378YzwbH1EOlYv+cUcMXRXpPoHqFKmNwS3pRYIfzLM3ev3/3KkOfuHZ
rh08zpDLU2TcUIjRlqXCVyoefuIXYTtwQcioc576nQlkU5/lG06pRMNldwk5SEkB
hgchnXeo6/cUDDBNG6vbs6mppwXy1HqRKWJfJDj56nepydefEor9fyw/PCDugd/j
KN9Sk9uEEYrqTk3n0K5D
=iRz3
-----END PGP SIGNATURE-----

--3JTCrkOOlgngG3EHx98cAwEcIgeLu1Urp--