From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtprelay01.ispgateway.de ([80.67.31.28]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1SHJoX-0000PA-Cy for ptxdist@pengutronix.de; Mon, 09 Apr 2012 20:59:46 +0200 Date: Mon, 9 Apr 2012 20:59:43 +0200 From: Bernhard Walle Message-ID: <20120409185943.GB7410@regiomontanus.bwalle.de> References: <4F831846.3060203@bwalle.de> <4F832414.2090800@biessmann.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4F832414.2090800@biessmann.de> Subject: Re: [ptxdist] Using PTXdist on Mac OS Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Andreas =?iso-8859-1?Q?Bie=DFmann?= Cc: ptxdist@pengutronix.de Hi, * Andreas Bie=DFmann [2012-04-09 20:01]: > = > a) Fink is _not_ Debian based but uses the great Debian package format > (*.deb ;) Well, depends on what you call 'Debian-based'. I didn't say that the packages are from Debian (the MacPorts packages are also not from Free/Open/NetBSD). finkproject.org says "Fink uses Debian tools like dpkg and apt-get to provide powerful binary package management. " So is the wording Is following acceptable? ------------------------------------ 8< ------------------------------------ \item \textbf{Fink} (\url{http://www.finkproject.org}) uses the package management tools and the package format from Debian. Contrary to MacPorts, it has both binaries and can be built from source (but as far= as I know, the binaries are less up-to-date compared the source packages). ------------------------------------ >8 ------------------------------------ > b) FSF GCC is _not_ required for GNU Toolchain bootstrap, I did compile > my arm-cortexa8, arm-v4t, arm-v5te, x86_64 and avr32 OSELAS.Toolchain wit= h: This experience is from the time when I used Xcode 4.2 (I had to wait for the update until MacPorts got support for it). I got llvm-gcc segmentation faults and this was also "documented" in the bug tracker of FSF GCC. And I think that in LLVM bugtracker was a fix already in SVN of LLVM GCC. I'm just running a build of a toolchain with Xcode 4.3(.2) LLVM GCC and if that build succeeds then I will remove the restriction to FSF GCC and mention Xcode 4.3 somewhere in the requirements. bwalle@euler % gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 565= 8) (LLVM build 2336.9.00) > (But maybe there are some Fink stuff leaking in and let it build on my > system? Did not investigate it further ...) I don't think that some Fink environment settings fixes GCC segmentation fa= ults. But we will see. > c) you forget Fink package names (patches follow ;) Patch is applied, thanks. But I will wait for J=FCrgens comments until I upload a new PDF. Regards, Bernhard -- = ptxdist mailing list ptxdist@pengutronix.de