unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Germán Arias" <german@xelalug.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: .el files with gnustep
Date: Tue, 22 Nov 2011 12:26:30 -0600	[thread overview]
Message-ID: <53c419519e6dd2f55b9158b69994c799@german-desktop> (raw)
In-Reply-To: <jwv39dgupwj.fsf-monnier+emacs@gnu.org>

On 2011-11-22 09:41:33 -0600 Stefan Monnier <monnier@IRO.UMontreal.CA> 
wrote:

>> Can somebody give me an idea about why some files ".el" compile fine
>> with ./configure & make, but not with: ./configure --with-ns & make?
>> Is annoying that after an update, emacs can compile sometimes with
>> gnustep, and sometimes not.  But if I try with ./configure & make, 
>> all
>> works fine.  And each time the problem is with a different ".el" 
>> file.
> 
> Can't think of any obvious reason.  If you show us some example of
> errors you get with "./configure --with-ns & make", maybe we can help
> a little better.
> 
> 
>         Stefan

With rev 106478 I get (and gcc 4.6.0):

Compiling align.el
Wrote /home/german/Instalados/emacs/lisp/align.elc
Compiling allout-widgets.el
Wrote /home/german/Instalados/emacs/lisp/allout-widgets.elc
Compiling allout.el
Aborted
make[3]: *** [allout.elc] Error 134
make[3]: Leaving directory `/home/german/Instalados/emacs/lisp'
make[2]: *** [compile-main] Error 2
make[2]: Leaving directory `/home/german/Instalados/emacs/lisp'
make[1]: *** [lisp] Error 2
make[1]: Leaving directory `/home/german/Instalados/emacs'
make: *** [bootstrap] Error 2

There isn't enough information. At least to me.




  reply	other threads:[~2011-11-22 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  5:11 .el files with gnustep Germán Arias
2011-11-22 15:41 ` Stefan Monnier
2011-11-22 18:26   ` Germán Arias [this message]
2011-11-22 20:25     ` chad
2011-11-22 22:33     ` Stefan Monnier
2011-11-23  6:43       ` Germán Arias

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=53c419519e6dd2f55b9158b69994c799@german-desktop \
    --to=german@xelalug.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).