X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49CF2163.3060602@gmail.com> Date: Sun, 29 Mar 2009 08:21:07 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gcc4: missing atomic builtins? References: <49CD325C DOT 5030109 AT users DOT sourceforge DOT net> In-Reply-To: <49CD325C.5030109@users.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 Yaakov (Cygwin/X) wrote: > Building djvulibre-3.5.21 with gcc4, while linking libdjvulibre: > > .libs/atomic.o:atomic.cpp:(.text+0x3b): undefined reference to > `___sync_bool_compare_and_swap_4' > .libs/atomic.o:atomic.cpp:(.text+0x65): undefined reference to > `___sync_add_and_fetch_4' > > Some googling shows that the culprit *may be* gcc4: > > http://sourceware.org/ml/crossgcc/2008-06/msg00022.html > > Any ideas? Well, I guess the question is, what's the minimum level of CPU we want to support, and I can configure the next version --with-arch that level, and as long as it's >=486 we'll be ok. I think the question is mainly "686, or is there any reason to have 586 as the minimum supported CPU"? (Not that < [56]86 users couldn't add the -march= flag to their builds, but this will determine what minimum level of cpu all the default code is generated for, and as most packages will be built with the default, we run the risk of having things in the distro that they can't install and run successfully from binaries.) cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/