unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [ich@frank-schmitt.net: Build failure under Suse 10.0]
Date: Mon, 06 Nov 2006 08:53:19 +0100	[thread overview]
Message-ID: <454EE9EF.4090205@swipnet.se> (raw)
In-Reply-To: <E1Ggwci-0000PM-D5@fencepost.gnu.org>

Can you do:

gcc -dD -E -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 > x.i

and sen med x.i (no need to send it to the whole list, it might be big).

Thanks,

	Jan D.


Richard Stallman skrev:
> Has this been fixed?
> 
> ------- Start of forwarded message -------
> To: emacs-devel@gnu.org
> From: Frank Schmitt <ich@frank-schmitt.net>
> Date: Mon, 30 Oct 2006 10:53:40 +0100
> Organization: Hamme net, kren mer och nimmi
> Mime-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Subject: Build failure under Suse 10.0
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
> 	version=3.0.4
> 
> 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
> 
> [inverness:~d/cvs/emacs]$ rpm -q giflib giflib-devel
> giflib-4.1.3-7.2
> giflib-devel-4.1.3-7.2
> 
> 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: 
> 
> /* This is the in-core version of an extension record */
> typedef struct {
>     int ByteCount;
>     char *Bytes;    /* on malloc(3) heap */
>     int Function;   /* Holds the type of the Extension block. */
> } ExtensionBlock;
> 
> - -- 
> 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.
> 
> 
> 
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
> ------- End of forwarded message -------
> 
> 
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2006-11-06  7:53 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 [this message]
2006-11-06  8:04   ` Jan Djärv
2006-11-06  8:40 ` Frank Schmitt
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

  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=454EE9EF.4090205@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).