X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 7E2CBDC03AF for ; Fri, 17 May 2013 17:50:47 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 789A2206EA for ; Fri, 17 May 2013 13:50:46 -0400 (EDT) Received: from web3.nyi.mail.srv.osa ([10.202.2.213]) by compute2.internal (MEProxy); Fri, 17 May 2013 13:50:46 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=7hfI2Hcp9kRd7/9w80Kd7V83km4=; b=s7L zTncKMWRPsoXTTA7fzu6bBcgMAxgbyU+1VMChLJ6I0y1V7qiIbh2tc8HzhLZLUlY LAiH/p38+h0sCFV11d8AXa9uOzt7j1EzsWNkpUkmKLn4c4fjEMr3ibIjJiZdRNB5 oBsjP66eJt+sIREySQ5Si1Jytw3C9kfLLS+JbgsE= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 5456AB202AA; Fri, 17 May 2013 13:50:46 -0400 (EDT) Message-Id: <1368813046.22124.140661232401945.6B54D8D7@webmail.messagingengine.com> X-Sasl-Enc: CHqxMdMEoJLmkCIy95XNDWc1KybUl1oXWYfNr0D6Fs4T 1368813046 From: Dubiousjim To: Alpine X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - html In-Reply-To: <1368810440.11585.140661232362869.109C2D3D@webmail.messagingengine.com> References: <1368810440.11585.140661232362869.109C2D3D@webmail.messagingengine.com> Subject: Re: [alpine-devel] Bunch of questions about Alpine's gcc package Date: Fri, 17 May 2013 13:50:46 -0400 I can answer two of my questions: On Fri, May 17, 2013, at 01:07 PM, Dubiousjim wrote: > Our sources has: > ... > boehem-gc-uclibc.patch > ... > ... > What about the patches available at > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/gcc/4.7.3/uclibc/? > Buildroot includes all of those patches, but at a first glance, it seems > like we don't include them? Are first appearances misleading here? > > What about the rest of the patches in our sources list: where do those > come from? Were they generated by Alpine devs, or do they come from > miscellaneous places? If anyone can venture a recommendation as to > whether I should apply those patches (and also the earlier block of > patches) to my cross-compiling gcc, I'd welcome the advice. The boehem-gc-uclibc.patch turns out to be the same as http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/gcc/4.7.3/uclibc/90_all_301-missing-execinfo_h.patch. But the rest of the patches in that folder on sources.gentoo.org seem not to be used by our APKBUILD, and I'm not sure where the rest of the patches in our APKBUILD are coming from. > These are options that Alpine uses when configuring gcc that I wasn't > able to find documentation on (for instance, at > http://gcc.gnu.org/install/configure.html). Might some of these options > now be obsolete? Or could anyone offer any explanation of these, and > suggestions about whether I should also apply them to the > cross-compiler. (I will continue to research these, as well.) > > --disable-altivec # from what I could see, gcc's -maltivec > option is only relevant for RS/6000 and PowerPC > --disable-build-with-cxx > --disable-libstdcxx-pch > --enable-esp > --without-system-libunwind I found info on one of these, --enable-esp. This is used for the PIE patchset, which I'm not using. See http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/gcc/4.7.3/pie/README?revision=1.1&view=markup. --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---