From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: I can't build from cvs sources on cygwin for some time now
Date: Mon, 13 Nov 2006 00:45:34 +0100 [thread overview]
Message-ID: <f7ccd24b0611121545j377aefdvc730a30a11e660a4@mail.gmail.com> (raw)
In-Reply-To: <ej8af0$poj$2@sea.gmane.org>
On 11/13/06, Eric Lilja <mindcooler@gmail.com> wrote:
> The steps I described in my OP are more or less
> the same I have used for two years now. And now it wont work, possibly
> due to how make is told to build emacsclient.c?
Possibly.
But you're the one that can really research what's happening and
propose a fix. I have no cygwin environment in my computer.
/L/e/k/t/u
next prev parent reply other threads:[~2006-11-12 23:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 22:17 I can't build from cvs sources on cygwin for some time now Eric Lilja
2006-11-12 22:23 ` Juanma Barranquero
2006-11-12 22:29 ` Eric Lilja
2006-11-12 22:34 ` Juanma Barranquero
2006-11-12 22:46 ` Eric Lilja
2006-11-12 22:56 ` Eric Lilja
2006-11-12 23:05 ` Juanma Barranquero
2006-11-12 23:22 ` Eric Lilja
2006-11-12 23:44 ` Juanma Barranquero
2006-11-12 23:52 ` Eric Lilja
2006-11-13 0:07 ` Jason Rumney
2006-11-13 0:49 ` Juanma Barranquero
2006-11-13 2:13 ` Juanma Barranquero
2006-11-13 8:21 ` Eric Lilja
2006-11-13 11:37 ` Jason Rumney
2006-11-13 12:25 ` Juanma Barranquero
2006-11-13 11:41 ` emacsclientw Jason Rumney
2006-11-13 12:23 ` emacsclientw Juanma Barranquero
2006-11-13 16:19 ` emacsclientw Lennart Borgman
2006-11-13 12:36 ` emacsclientw dhruva
2006-11-13 12:39 ` emacsclientw Juanma Barranquero
2006-11-13 13:14 ` emacsclientw dhruva
2006-11-13 13:31 ` emacsclientw Juanma Barranquero
2006-11-13 22:43 ` emacsclientw Jason Rumney
2006-11-13 22:56 ` emacsclientw Lennart Borgman
2006-11-14 3:32 ` emacsclientw dhruva
2006-11-14 7:18 ` emacsclientw Mathias Dahl
2006-11-14 7:34 ` emacsclientw Jason Rumney
2006-11-14 8:44 ` emacsclientw Mathias Dahl
2006-12-05 23:15 ` emacsclientw Stuart D. Herring
2006-11-14 8:39 ` emacsclientw dhruva
2006-11-14 7:30 ` emacsclientw Jason Rumney
2006-11-13 14:11 ` emacsclientw Lennart Borgman
2006-11-13 14:40 ` emacsclientw Juanma Barranquero
2006-11-13 19:36 ` emacsclientw Stefan Monnier
2006-11-13 20:08 ` emacsclientw Juanma Barranquero
2006-11-13 21:33 ` emacsclientw Stefan Monnier
2006-11-13 22:23 ` emacsclientw Lennart Borgman
2006-11-13 22:40 ` emacsclientw Juanma Barranquero
2006-11-13 22:54 ` emacsclientw Lennart Borgman
2006-11-13 23:10 ` emacsclientw Juanma Barranquero
2006-11-14 0:45 ` emacsclientw Lennart Borgman
2006-11-13 23:20 ` emacsclientw Jason Rumney
2006-11-13 20:12 ` emacsclientw Eli Zaretskii
2006-11-12 23:01 ` I can't build from cvs sources on cygwin for some time now Juanma Barranquero
2006-11-12 23:24 ` Eric Lilja
2006-11-12 23:45 ` Juanma Barranquero [this message]
2006-11-13 12:21 ` Eric Lilja
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=f7ccd24b0611121545j377aefdvc730a30a11e660a4@mail.gmail.com \
--to=lekktu@gmail.com \
--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).