From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Build failure under Suse 10.0
Date: Mon, 30 Oct 2006 19:26:32 -0500 [thread overview]
Message-ID: <87hcxlnxdz.fsf@stupidchicken.com> (raw)
In-Reply-To: <17734.36719.594533.108256@kahikatea.snap.net.nz> (Nick Roberts's message of "Tue\, 31 Oct 2006 12\:49\:03 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> > > I don't have any strange gif_lib.h files lying around and the
> > > relevant lines in /usr/include/gif_lib.h look ok to me
> >
> > What configure options did you use? Does an ordinary ./configure &&
> > make work?
>
> Working out why a build fails for someone else's system is way over my head
> but the tarball currently seems to be a pre-pretest. If we made the next
> one a pretest i.e announced it on other mailing lists/websites, isn't it
> more likely that fixes will be posted for these failures?
True. The most glaring building/distribution bugs have been ironed
out, so unless something else comes up, I'll roll a 22.0.91 tarball
tomorrow and we can make the pretest announcement.
next prev parent reply other threads:[~2006-10-31 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 9:53 Build failure under Suse 10.0 Frank Schmitt
2006-10-30 23:16 ` Chong Yidong
2006-10-30 23:24 ` Frank Schmitt
2006-10-30 23:49 ` Nick Roberts
2006-10-31 0:26 ` Chong Yidong [this message]
2006-10-31 4:25 ` Eli Zaretskii
2006-10-31 15:25 ` Chong Yidong
2006-11-04 13:20 ` Eli Zaretskii
2006-10-31 9:29 ` Juanma Barranquero
2006-10-31 22:15 ` Eli Zaretskii
2006-10-31 23:06 ` Chong Yidong
2006-11-01 4:17 ` Eli Zaretskii
2006-11-02 4:42 ` Richard Stallman
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=87hcxlnxdz.fsf@stupidchicken.com \
--to=cyd@stupidchicken.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 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.