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=AO8xsc
	gNdKKjKuOFbb8ckNNxexF0IRv1X2nSZQUO2CwLeuBryt9LtwRoiAYTWHRPs2hQsV
	95poQvElANyvRRskY40AmmvSAoEEdqd9qbeH/3BAIB4fi9ZM/uAtyIkZQmWLa+mN
	H5eH1UfUeFTIC5YwZylkN12DVaIsBnjKTFP4U=
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: <51EE7885.1090709@gmail.com>
Date: Tue, 23 Jul 2013 20:35:17 +0800
From: JonY <10walls AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Basic gcc compilation on cygwin64
References: <51EDC591 DOT 40505 AT gmail DOT com>
In-Reply-To: <51EDC591.40505@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2FLJLAEMBMDNWONRVOWWG"

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

On 7/23/2013 07:51, Richard H Lee wrote:
> I'm trying to compile the following basic program on cygwin64:
>=20
> int main() {
>   ;
>   return 0;
> }
>=20
> But I get the following errors:
>=20
> $ gcc test.c
> /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -ladvapi32
> /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -lshell32
> /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -luser32
> /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -lkernel32
> collect2: error: ld returned 1 exit status
>=20
> This is my first time using the 64-bit version of cygwin and I get the
> feeling I am missing some sort of flag or library.
>=20

Try rerunning setup again, there was a mistake in the w32api-runtime -1
release. -2 should have this fixed.


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (MingW32)

iQIcBAEBAgAGBQJR7niMAAoJEHE7X+KcFF1FMZUP/A+T8xbs10VyHPLb1VydM3Ty
zZMsLX6WittC4N2Knl6a1xOnM1CEdo2AUAD2CYxyhGZI4Lz5vf4dND7OWZgmFgb7
mMq93rkVJaRH1k/6KhAppFI9tOLOGj9rueeU33DoWJabcQk4g6RYJ5SBr9xiPSYR
MNSPhEYKKADXSTvUTpRDaHUzYkB+87NwF128T7ELUu2dAIbzbbpsq3IBlI9Lz9pw
CAcL7S6PuVFcceds7Uedr55hyM2EsSO7TokR+MGH7YWbyQAKtTaGsn/IrzKYFIhc
nZzT+Hp/zCmYbBPqg7KZya00roPbnmd2RC8nhmv8Cv9HM1GvFvjFGzWYqSUz6C6u
oQsWoemJfjAS2akYh80JSjROl4o0g5S8ST4pUa/Vuc64ZfcM72HI1qrHRQIMihJI
n6fe8vejytAcuwK4g5elH6fQAALUmPGlbRkYWPWDP1ooNqhL390iBNUxOR/aBTkt
BTgRIk4Ksuh+FSFInaLueStYKBinyeeMlmagcXKsjbDOBeMCS6FlDIGz3xiNuDrI
xj7qOPvVobADsYB+wriS7OttJaQpRaCponYXeniEJiBPR0JM9FgH2Xr9JSzWeQdK
qQ0vlPa+kJimIiuqSruKt2KOQnoXlXxPtvFeegr3hPPf5uWNNiSiNXMnbufzRaVb
AwTf7kIVE3S++7efab47
=KK7i
-----END PGP SIGNATURE-----

------enig2FLJLAEMBMDNWONRVOWWG--