From: Frank Schmitt <ich@frank-schmitt.net>
Subject: Re: [ich@frank-schmitt.net: Build failure under Suse 10.0]
Date: Mon, 06 Nov 2006 09:40:59 +0100 [thread overview]
Message-ID: <m3ac35j7c4.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: E1Ggwci-0000PM-D5@fencepost.gnu.org
Richard Stallman <rms@gnu.org> writes:
> Has this been fixed?
>
> From: Frank Schmitt <ich@frank-schmitt.net>
> Subject: Build failure under Suse 10.0
> Date: Mon, 30 Oct 2006 10:53:40 +0100
>
> Hello
>
> I get a build failure with current CVS-Head:
>
> gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -DUSE_LUCID -I. -I/export/inverness/cvs/emacs/src -D_BSD_SOURCE -I/usr/X11R6/include -I/usr/
> include/alsa -g -O2 -Wno-pointer-sign image.c
> image.c: In function ?gif_load?:
> image.c:7874: error: ?struct <anonymous>? has no member named ?Function?
> make[2]: *** [image.o] Error 1
> make[2]: Leaving directory `/export/inverness/cvs/emacs/src'
> make[1]: *** [bootstrap-build] Error 2
> make[1]: Leaving directory `/export/inverness/cvs/emacs'
> make: *** [bootstrap] Error 2
No, I still get the same error with a fresh checkout of todays CVS
head. I also tried compiling under a fresh user account to prevent
strange settings of environment variables hindering compilation but this
didn't change anything, too.
--
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.
next prev parent reply other threads:[~2006-11-06 8:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 5:02 [ich@frank-schmitt.net: Build failure under Suse 10.0] Richard Stallman
2006-11-06 7:53 ` Jan Djärv
2006-11-06 8:04 ` Jan Djärv
2006-11-06 8:40 ` Frank Schmitt [this message]
2006-11-06 9:19 ` Jan Djärv
2006-11-06 9:51 ` Frank Schmitt
2006-11-06 10:49 ` Jan Djärv
2006-11-06 21:00 ` Richard Stallman
2006-11-06 22:28 ` Reiner Steib
2006-11-06 22:49 ` Andreas Schwab
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=m3ac35j7c4.fsf@mid.gehheimdienst.de \
--to=ich@frank-schmitt.net \
/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.