X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,TW_RW,TW_WX,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4C2A806F.5010009@redhat.com> Date: Tue, 29 Jun 2010 17:23:27 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100621 Fedora/3.0.5-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.2 Thunderbird/3.0.5 MIME-Version: 1.0 To: cygwin Subject: Re: rebaseall [1.7]: cyggcc_s-1.dll error References: <1277822045 DOT 12015 DOT 1382454075 AT webmail DOT messagingengine DOT com> <4C2A04C9 DOT 5000202 AT redhat DOT com> <20100629144014 DOT GA25176 AT ednor DOT casa DOT cgf DOT cx> <4C2A725A DOT 8030802 AT cygwin DOT com> In-Reply-To: <4C2A725A.8030802@cygwin.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig6749346F8CD23044A8C5CD51" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com --------------enig6749346F8CD23044A8C5CD51 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 06/29/2010 04:23 PM, Larry Hall (Cygwin) wrote: >>>> Or dash could be rebuilt using -static-libgcc. >>> >>> OK, I'm now trying to figure out how to add -static-libgcc into my >>> cygport file. Look for an updated dash later today... >> >> In the meantime, you might want to consider linking dash with >> -static-libgcc. >=20 > You know, I thought of that too but then I thought, it's probably better > that > dash is statically linked with libgcc instead. Or maybe I should just try changing my .cygport file to pass different options to configure so that I do static linking. Like adding one line: export CFLAGS=3D'-O2 -static-libgcc' Interesting observations from that attempt: CYGCONF_ARGS can't accept arguments with whitespace; I had to pass my CFLAGS with whitespace through the environment instead. I guess if cygport were changed to treat CYGCONF_ARGS as an array variable instead: ./configure "$*" "${CYGCONF_ARGS[*]}" then I could have used CYGCONF_ARGS=3D(CC=3Dgcc-4 CFLAGS=3D'-O2 -static-libgcc') but that would be a change to everyone who used CYGCONF_ARGS as a flat variable. Is there a bash shorthand for telling whether a variable is an array instead of flat? And what difference does libgcc really make, anyways? $ ll ./dash-0.5.6.1-?/inst/usr/bin/ash.exe -rwxr-xr-x 2 eblake None 82446 2010-06-28 12:05 ./dash-0.5.6.1-1/inst/usr/bin/ash.exe* -rwxr-xr-x 2 eblake None 82446 2010-06-29 16:48 ./dash-0.5.6.1-2/inst/usr/bin/ash.exe* Identical size executables, but cygcheck confirms that only -1 dynamically sucks in cyggcc_s-1.dll. Is that a shortcoming of the toolchain, in defaulting to the dynamic dependence even when it makes no difference to the final exe size? --=20 Eric Blake eblake AT redhat DOT com +1-801-349-2682 Libvirt virtualization library http://libvirt.org --------------enig6749346F8CD23044A8C5CD51 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.14 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJMKoB1AAoJEKeha0olJ0NqmRYH/RowLM5Mh26Yx69phxu55UnF IEJqOOS6fBxpbWiEMILGpRRmBDq2egxox40IOCQ7ZZBrLUOojsFaoHeBeDtFJfOp pieOFGIl+3LVV/Y3Zlz6ZByAk/819A0942Rdlkyx8LknKRgnpbSFyegx27c3qBJn Mmng7/B4MkG6obb65CJoN/tjlBiXOExmfyDrmOVLspTaSO13LidOclawFAVQILyq eapOK/ibzAjns4vwkw+6a1nNNt12biQT1Gs2mgIcvzSUKMGkc5H+FLPRrZi57hF9 6Tt5K5F/pr5K1QeI6I5wXn3F4Nqf5Tn1H7XjimLuv47zj0OaJOE8zzxSTCusSHs= =Tru/ -----END PGP SIGNATURE----- --------------enig6749346F8CD23044A8C5CD51--