From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: Langella Raphael <raphael.langella@steria.cnes.fr>,
507@emacsbugs.donarmstrong.com
Subject: bug#507: compilation problem under Solaris
Date: Mon, 07 Jul 2008 17:26:12 -0700 [thread overview]
Message-ID: <200807080026.m680QCQo019650@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <18542.32370.506572.312639@fencepost.gnu.org> (Glenn Morris's message of "Fri, 4 Jul 2008 15:48:02 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Langella Raphael wrote (on Fri, 4 Jul 2008 at 10:40 +0200):
>
> > > By far the easiest way for you to fix this is just to edit your
> > > src and lib-src Makefile by hand.
> >
> > That's exactly what I did even before reporting the bug. I just
> > thought I should report this. And I didn't have to edit
> > lib-src/Makefile, only src/Makefile.
>
> I know. Thanks for taking the time to report it.
>
> If you like, you could check that the configure patch, plus changing
> files in src/ to use __sparc__ rather than sparc, works:
>
> src/m/sparc.h:
>
> /* Say this machine is a sparc */
>
> #ifndef __sparc__
> #define __sparc__
> #endif
This should not be needed, the compiler defines __sparc__ by default.
next prev parent reply other threads:[~2008-07-08 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 8:40 bug#507: compilation problem under Solaris Langella Raphael
2008-07-04 19:48 ` Glenn Morris
2008-07-08 0:26 ` Dan Nicolaescu [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-03 14:40 Langella Raphael
2008-07-03 20:00 ` Glenn Morris
2008-07-03 21:22 ` Stefan Monnier
2008-07-02 7:59 Langella Raphael
2008-07-02 19:52 ` Glenn Morris
[not found] <092785B790DCD043BA45401EDA43D9B503276D9D@cst-xch-003.cnesnet.ad.cnes.fr>
2008-07-01 20:08 ` Glenn Morris
2008-06-30 12:41 Langella Raphael
2008-06-30 20:30 ` Glenn Morris
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=200807080026.m680QCQo019650@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=507@emacsbugs.donarmstrong.com \
--cc=raphael.langella@steria.cnes.fr \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.