From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: MetaPost 1.004 announcement
Date: Sun, 4 May 2008 10:52:39 +0200 [thread overview]
Message-ID: <6faad9f00805040152r46faa439hb91324df7b784942@mail.gmail.com> (raw)
In-Reply-To: <481D7601.9000703@elvenkind.com>
On Sun, May 4, 2008 at 10:38 AM, Taco Hoekwater wrote:
> Thomas A. Schmitz wrote:
> >
> > 1. general architecture specification: CFLAGS -arch ppc (for
> > powerpc) CFLAGS -arch ppc64 (for the new 64bit binaries on
> > powerpc) CFLAGS -arch i386 (for intel) I did not check the ppc64
> > (not needed) and i386 (not having one) options.
> >
> > 2. more specific architecture specification affecting instruction set
> > and scheduling if one wants to tune the generated code to ones
> > processor: CFLAGS -mcpu=G4 (-mcpu=G5 etc. whichever ones machine has)
> >
> >
> > It would be most natural, I think, if the -arch switch is added
> > standard through the autoconf scripts. Taco could see to that for
> > metapost and luatex, I trust. Can someone mail this experience to the
> > maintainers of pdftex? (I could not ascertain why pdftex compiles
> > without problems).
I might be missing the point, but I would be glad if -arch would not
be set automatically if there is some better solution. Now it's really
easy to cross-compile metapost, pdfTeX and LuaTeX for ppc on intel. If
configure script would set the -arch unconditionally, then I would
probably run into problems. But again - I might be misunderstanding
the problem.
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-05-04 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48198C57.4000304@elvenkind.com>
2008-05-03 18:56 ` Thomas A. Schmitz
2008-05-03 21:18 ` luigi scarso
2008-05-04 5:46 ` Peter Münster
2008-05-04 8:20 ` luigi scarso
2008-05-04 8:38 ` Taco Hoekwater
2008-05-04 8:52 ` Mojca Miklavec [this message]
2008-05-04 16:04 ` Thomas A. Schmitz
2008-05-06 6:50 ` Metapost on OS X 10.5 Taco Hoekwater
2008-05-06 7:40 ` Thomas A. Schmitz
2008-05-06 15:53 ` Thomas A. Schmitz
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=6faad9f00805040152r46faa439hb91324df7b784942@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/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;
as well as URLs for NNTP newsgroup(s).