unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [OSX] G4 compiled binary fails on G5
Date: Wed, 02 Feb 2005 12:21:34 -0500	[thread overview]
Message-ID: <jwvwttqc2hc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2lla7j5ij.fsf@seki.fr> ( Sébastien Kirche's message of "Wed, 02 Feb 2005 17:22:44 +0100")

> > You should recompile and either run
> > make CC=gcc
> > or
> > make-package -M,CC=gcc
> 
> I have compiled a  version with «make-package --self-compiled -M,CC=gcc» and
> now wait for feedback.
> 
> I also made an OS9 version with the USE_LSB_TAG and i wonder if it should be
> given also to OSX ?

How did you set the USE_LSB_TAG ?  What compiler did you use?

> That symbol seems to be defined on  mac if __MRC__ is defined. IIRC MrC used
> to be the OS9 compiler from Apple/MPW.

I must say I have no clue under which circumstance are the mac/inc/*
files used.  Is that for Mac OS 9 only?

While I'm looking at them, couls someone tell me what the following comment
(in mac/inc/config.h) refers to:

   /* Use low-bits for tags.  If ENABLE_CHECKING is turned on together
      with USE_LSB_TAG, optimization flags should be explicitly turned
      off.  */

what's the problem with optimization flags and ENABLE_CHECKING and
USE_LSB_TAG?

Also in s-mac.h, would it be correct to add to the code

   #ifdef __MRC__
   #define DECL_ALIGN(type, var) type var
   #endif

a little comment saying something like "MrC always aligns structures larger
than 8bytes on 8byte boundaries".  If not, what is the justification for
defining DECL_ALIGN as a nop?

> If so,  looking dumb  I did not  figured the  syntax to provide  both CC=gcc
> *and* USE_LSB_TAG or maybe -DUSE_LSB_TAG...

If you tell me how you set USE_LSB_TAG, I may be able to tell you how to
combine the two.


        Stefan

  reply	other threads:[~2005-02-02 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 10:15 [OSX] G4 compiled binary fails on G5 Sébastien Kirche
2005-01-31 16:40 ` Steven Tamm
2005-01-31 17:06   ` Sébastien Kirche
2005-01-31 21:45   ` Kim F. Storm
2005-02-02 16:22   ` Sébastien Kirche
2005-02-02 17:21     ` Stefan Monnier [this message]
2005-02-02 18:09       ` Steven Tamm
2005-02-02 18:48         ` Stefan Monnier
     [not found]           ` <85wttqwwv5.fsf@obelix.seki.fr>
2005-02-02 20:25             ` Stefan Monnier
     [not found]         ` <85sm4ewwqo.fsf@obelix.seki.fr>
2005-02-02 22:50           ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2004-10-16  7:28 Mac OS 9 support YAMAMOTO Mitsuharu
2004-10-16 18:37 ` Stefan Monnier
2004-10-17  9:23   ` YAMAMOTO Mitsuharu
2005-02-03 11:28     ` [OSX] G4 compiled binary fails on G5 YAMAMOTO Mitsuharu
2004-12-24  8:52 ` Mac OS 9 support (and some enhancements for Carbon Emacs) YAMAMOTO Mitsuharu
2004-12-27 17:42   ` Steven Tamm
2005-01-18 10:46   ` Sébastien Kirche

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvwttqc2hc.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).