From mint-bounce@lists.fishpool.fi Mon Jan 11 18:25:40 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=V478KnS/TzM1358dmpf7rVaQns2QKGnAaj0aZKjCMbI=; b=CuRPhBly4Kfw9ZpKjQPjv941hjbIKlA5u1rwqLCzpUfXLbLgausyhDg0+VcnoH66hp HI07i9K1GFzYyl5mbS+l4EncTJfBxtBLS7Q7lDIa3llDLrsFOcbch/Eb7lt1N3dKY04d n6YT/4mD+5y0iQAWDr2TjR/8p3nFELw1EzFTM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ErukBf2ZM69rvz5ouRrJjafAHT99xkQcO9JFSopbDm7aGMmQwK958wbSlTG3r3c94Y ZXaFP+rBvoITjMp1Vim4E4whKHXzIbgsyyclDJ4EgomTcIfPzBHMCgIc0MesIEilJcyi j+4SrzqAS4P7sJybJSiH0gbEcl/VsKAoQ2js8= MIME-Version: 1.0 In-Reply-To: <4B4BA685.1060806@freesbee.fr> References: <4B4B7E78.9090703@freesbee.fr> <4B4B8ACD.4080109@freesbee.fr> <11a6f2b11001111354g26fd21abp68d47b1010455765@mail.gmail.com> <4B4BA685.1060806@freesbee.fr> Date: Tue, 12 Jan 2010 10:23:00 +1100 Message-ID: <11a6f2b11001111523x399af4hff946f5f2d11c93b@mail.gmail.com> Subject: Re: [MiNT] how to compile stik/sting stuff with gcc4 From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o0BNPdlK021719 2010/1/12 Vincent Rivière : > Paul Wratt wrote: >> >> One last question, does "It is defined in include/compiler.h" imply >> there are more changes to be made elsewhere? > > No, include/compiler.h is a header provided by the MiNTLib, where the > __CLOBBER_RETURN macro is defined. > > For instance: > > /* Convenience macros to test the versions of glibc and gcc. >   Use them like this: >   #if __GNUC_PREREQ (2,8) >   ... code requiring gcc 2.8 or later ... >   #endif >   Note - they won't work for gcc1 or glibc1, since the _MINOR macros >   were not defined then.  */ > #if defined __GNUC__ && defined __GNUC_MINOR__ > # define __GNUC_PREREQ(maj, min) \ >        ((__GNUC__ << 16) + __GNUC_MINOR__ >= ((maj) << 16) + (min)) > #else > # define __GNUC_PREREQ(maj, min) 0 > #endif > > #if __GNUC_PREREQ(3, 3) > # define __CLOBBER_RETURN(a) > #else > # define __CLOBBER_RETURN(a) a, > #endif > > -- > Vincent Rivière > and this reflects some knowledge I gained elsewhere that 3.3.x is a bit of a special case in gcc development history, does it not. If so, would I be right in thinking that certain packages that were or do build with 3.3.6 may be restrictive in there source, concerning the use of other gcc versions, both older and newer Paul