From: Bernhard Walle <bernhard@bwalle.de>
To: "Andreas Bießmann" <andreas@biessmann.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using PTXdist on Mac OS
Date: Mon, 9 Apr 2012 20:59:43 +0200 [thread overview]
Message-ID: <20120409185943.GB7410@regiomontanus.bwalle.de> (raw)
In-Reply-To: <4F832414.2090800@biessmann.de>
Hi,
* Andreas Bießmann <andreas@biessmann.de> [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 with:
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 5658) (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 faults.
But we will see.
> c) you forget Fink package names (patches follow ;)
Patch is applied, thanks. But I will wait for Jürgens comments until I
upload a new PDF.
Regards,
Bernhard
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-04-09 18:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 17:11 Bernhard Walle
2012-04-09 17:48 ` Juergen Beisert
2012-04-10 9:37 ` Bernhard Walle
2012-04-09 18:01 ` Andreas Bießmann
2012-04-09 18:59 ` Bernhard Walle [this message]
2012-04-09 19:47 ` Juergen Beisert
2012-04-09 20:04 ` Andreas Bießmann
2012-04-09 20:48 ` Andreas Bießmann
2012-04-10 9:04 ` Bernhard Walle
2012-04-10 18:35 ` Bernhard Walle
2012-04-17 11:08 ` Daniel Kriesten
2012-04-17 11:24 ` Michael Olbrich
2012-04-17 11:45 ` Bernhard Walle
2012-04-17 11:59 ` Daniel Kriesten
2012-04-17 12:03 ` Bernhard Walle
2012-04-17 12:32 ` Daniel Kriesten
2012-04-18 8:29 ` Michael Olbrich
2012-04-18 11:25 ` Daniel Kriesten
2012-04-18 14:16 ` Michael Olbrich
2012-04-18 14:28 ` Daniel Kriesten
2012-04-19 10:41 ` Daniel Kriesten
2012-04-19 11:29 ` Andreas Bießmann
2012-04-19 12:04 ` Daniel Kriesten
2012-04-19 12:25 ` Andreas Bießmann
2012-04-19 13:12 ` Daniel Kriesten
2012-04-19 13:27 ` Michael Olbrich
2012-04-19 14:03 ` Andreas Bießmann
2012-04-19 20:13 ` Bernhard Walle
2012-12-08 15:31 ` Daniel Kriesten
2012-12-08 15:43 ` [ptxdist] Using PTXdist on Mac OS 10.7 Daniel Kriesten
2012-12-10 8:48 ` Michael Olbrich
2012-12-10 8:46 ` [ptxdist] Using PTXdist on Mac OS Michael Olbrich
2012-12-11 15:00 ` Daniel Kriesten
2012-12-12 11:00 ` Michael Olbrich
2012-04-17 11:48 ` Bernhard Walle
2012-04-17 12:04 ` Daniel Kriesten
2012-04-17 12:18 ` Bernhard Walle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120409185943.GB7410@regiomontanus.bwalle.de \
--to=bernhard@bwalle.de \
--cc=andreas@biessmann.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox