all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Odd problem with GNU/Emacs CVS
@ 2008-01-23 15:38 Adolfo De Unanue
  2008-01-23 20:04 ` Peter Dyballa
  0 siblings, 1 reply; 7+ messages in thread
From: Adolfo De Unanue @ 2008-01-23 15:38 UTC (permalink / raw)
  To: help-gnu-emacs

Hi everyone!

I am a big fan of GNU/Emacs, and since some years ago I always get the
cvs version, compile it and, obviously, use it :-)

Yesterday I made a "cvs up" in my source dir, I got the
GNU/Emacs 23.0.50 version (the file README said it, 23.0.50.4 if after
building I execute M-x emacs-version), so I followed the classical
steps:

./compile

but wait the console answered me with this

[...]


Configured for `i686-pc-linux-gnu'.

  Where should the build process find the source
code?    /home/nano/software/emacs
  What operating system and machine description files should Emacs use?
        `s/gnu-linux.h' and `m/intel386.h'
  What compiler should emacs be built with?               gcc -g -O2
-Wno-pointer-sign 
  Should Emacs use the GNU version of malloc?             yes
      (Using Doug Lea's new malloc from the GNU C Library.)
  Should Emacs use a relocating allocator for buffers?    yes
  Should Emacs use mmap(2) for buffer allocation?         no
  What window system should Emacs use?                    x11
  What toolkit should Emacs use?                          GTK
  Where do we find X Windows header files?                Standard dirs
  Where do we find X Windows libraries?                   Standard dirs
  Does Emacs use -lXaw3d?                                 no
  Does Emacs use -lXpm?                                   no
  Does Emacs use -ljpeg?                                  no
  Does Emacs use -ltiff?                                  no
  Does Emacs use a gif library?                           no 
  Does Emacs use -lpng?                                   no
  Does Emacs use -lrsvg-2?                                no
  Does Emacs use -lgpm?                                   no
  Does Emacs use X toolkit scroll bars?                   yes


[...]

The weird thing is I have libxaw3d, libxpm4 (3.5.6-3), libjpeg (6b-14),
libtiff (3.8.2-7),libungif (4.1.4-5), librsvg-2 (2.18.2-1) and libgpm
(1.19.6-25) installed! (Including the -dev)

What is the problem? Maybe I have to update all the libs? By the way I
am running a Ubuntu Gutsy.


Thanks in advance


Adolfo 


PS. Here is the full output  of ./configure:


checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for AIX... no
checking whether gcc understands -Wno-pointer-sign... yes
checking whether ln -s works... yes
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for install-info... /usr/sbin/install-info
checking for install-info... (cached) /usr/sbin/install-info
checking for install-info... (cached) /usr/sbin/install-info
checking for gzip... /bin/gzip
checking for makeinfo... /usr/bin/makeinfo
checking for -znocombreloc... yes
configure: checking the machine- and system-dependent files to find out
 - which libraries the lib-src programs will want, and
 - whether the GNU malloc routines are usable...
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking machine/soundcard.h usability... no
checking machine/soundcard.h presence... no
checking for machine/soundcard.h... no
checking sys/soundcard.h usability... yes
checking sys/soundcard.h presence... yes
checking for sys/soundcard.h... yes
checking soundcard.h usability... no
checking soundcard.h presence... no
checking for soundcard.h... no
checking for _oss_ioctl in -lossaudio... no
checking for pkg-config... /usr/bin/pkg-config
checking for alsa >= 1.0.0... yes
checking ALSA_CFLAGS... -I/usr/include/alsa  
checking ALSA_LIBS... -lasound  
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking linux/version.h usability... yes
checking linux/version.h presence... yes
checking for linux/version.h... yes
checking sys/systeminfo.h usability... no
checking sys/systeminfo.h presence... no
checking for sys/systeminfo.h... no
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for string.h... (cached) yes
checking for stdlib.h... (cached) yes
checking termcap.h usability... yes
checking termcap.h presence... yes
checking for termcap.h... yes
checking stdio_ext.h usability... yes
checking stdio_ext.h presence... yes
checking for stdio_ext.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for strings.h... (cached) yes
checking coff.h usability... no
checking coff.h presence... no
checking for coff.h... no
checking pty.h usability... yes
checking pty.h presence... yes
checking for pty.h... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/vlimit.h usability... yes
checking sys/vlimit.h presence... yes
checking for sys/vlimit.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking sys/_mbstate_t.h usability... no
checking sys/_mbstate_t.h presence... no
checking for sys/_mbstate_t.h... no
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking if personality LINUX32 can be set... yes
checking for term.h... yes
checking for ANSI C header files... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking whether sys_siglist is declared... no
checking whether __sys_siglist is declared... no
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for struct utimbuf... yes
checking return type of signal handlers... void
checking for speed_t... yes
checking for struct timeval... yes
checking for struct exception... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for net/if.h... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct tm.tm_zone... yes
checking for struct tm.tm_gmtoff... yes
checking for struct ifreq.ifr_flags... yes
checking for struct ifreq.ifr_hwaddr... yes
checking for struct ifreq.ifr_netmask... yes
checking for struct ifreq.ifr_broadaddr... yes
checking for struct ifreq.ifr_addr... yes
checking for function prototypes... yes
checking for working volatile... yes
checking for an ANSI C-conforming const... yes
checking for void * support... yes
checking whether make sets $(MAKE)... yes
checking for long file names... yes
checking for X... libraries , headers 
checking Carbon/Carbon.h usability... no
checking Carbon/Carbon.h presence... no
checking for Carbon/Carbon.h... no
checking for malloc_get_state... yes
checking for malloc_set_state... yes
checking whether __after_morecore_hook exists... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking for dnet_ntoa in -ldnet... no
checking for main in -lXbsd... no
checking for cma_open in -lpthreads... no
checking for XFree86 in /usr/X386... no
checking whether X on GNU/Linux needs -b to link... no
checking for Xkb... yes
checking for XrmSetDatabase... yes
checking for XScreenResourceString... yes
checking for XScreenNumberOfScreen... yes
checking for XSetWMProtocols... yes
checking X11 version 6... 6 or newer
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for gtk+-2.0 >= 2.6 glib-2.0 >= 2.6... yes
checking GTK_CFLAGS... -I/usr/include/gtk-2.0
-I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/freetype2
-I/usr/include/libpng12 checking GTK_LIBS... -lgtk-x11-2.0
-lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0
-lfontconfig -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor
-lXcomposite -lXdamage -lpango-1.0 -lcairo -lX11 -lXfixes -lgobject-2.0
-lgmodule-2.0 -ldl -lglib-2.0 checking for gtk_main... yes checking for
gdk_display_open... yes checking for gtk_file_selection_new... yes
checking for gtk_file_chooser_dialog_new... yes checking pthread.h
usability... yes checking pthread.h presence... yes checking for
pthread.h... yes checking for pthread_self in -lpthread... yes checking
maybe dbus... checking for pkg-config... (cached) /usr/bin/pkg-config
checking for dbus-1 >= 1.0... yes checking DBUS_CFLAGS...
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include checking
DBUS_LIBS... -ldbus-1 yes checking for pkg-config...
(cached) /usr/bin/pkg-config checking for xft >= 0.13.0... yes checking
XFT_CFLAGS... -I/usr/include/freetype2 checking XFT_LIBS... -lXft
-lfontconfig checking X11/Xft/Xft.h usability... yes
checking X11/Xft/Xft.h presence... yes
checking for X11/Xft/Xft.h... yes
checking for XftFontOpen in -lXft... yes
checking malloc/malloc.h usability... no
checking malloc/malloc.h presence... no
checking for malloc/malloc.h... no
checking X11/SM/SMlib.h usability... yes
checking X11/SM/SMlib.h presence... yes
checking for X11/SM/SMlib.h... yes
checking for SmcOpenConnection in -lSM... yes
checking whether netdb declares h_errno... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for sqrt in -lm... yes
checking for maillock in -lmail... no
checking for maillock in -llockfile... no
checking for liblockfile.so... no
checking for touchlock... no
checking maillock.h usability... no
checking maillock.h presence... no
checking for maillock.h... no
checking for gethostname... yes
checking for getdomainname... yes
checking for dup2... yes
checking for rename... yes
checking for closedir... yes
checking for mkdir... yes
checking for rmdir... yes
checking for sysinfo... yes
checking for getrusage... yes
checking for get_current_dir_name... yes
checking for random... yes
checking for lrand48... yes
checking for bcopy... yes
checking for bcmp... yes
checking for logb... yes
checking for frexp... yes
checking for fmod... yes
checking for rint... yes
checking for cbrt... yes
checking for ftime... yes
checking for setsid... yes
checking for strerror... yes
checking for fpathconf... yes
checking for select... yes
checking for mktime... yes
checking for euidaccess... yes
checking for getpagesize... (cached) yes
checking for tzset... yes
checking for setlocale... yes
checking for utimes... yes
checking for setrlimit... yes
checking for setpgid... yes
checking for getcwd... yes
checking for getwd... yes
checking for shutdown... yes
checking for getaddrinfo... yes
checking for __fpending... yes
checking for mblen... yes
checking for mbrlen... yes
checking for mbsinit... yes
checking for strsignal... yes
checking for setitimer... yes
checking for ualarm... yes
checking for index... yes
checking for rindex... yes
checking for sendto... yes
checking for recvfrom... yes
checking for getsockopt... yes
checking for setsockopt... yes
checking for getsockname... yes
checking for getpeername... yes
checking for gai_strerror... yes
checking for mkstemp... yes
checking for getline... yes
checking for getdelim... yes
checking for mremap... yes
checking for memmove... yes
checking for fsync... yes
checking for sync... yes
checking for bzero... yes
checking for memset... yes
checking for memcmp... yes
checking for difftime... yes
checking for memcpy... yes
checking for mempcpy... yes
checking for mblen... (cached) yes
checking for mbrlen... (cached) yes
checking for posix_memalign... yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking for sys/time.h... (cached) yes
checking for unistd.h... (cached) yes
checking for alarm... yes
checking for working mktime... yes
checking for getloadavg... yes
checking for pstat_getdynamic... no
checking for kstat_open in -lkstat... no
checking for getloadavg... yes
checking whether getloadavg requires setgid... no
checking for _LARGEFILE_SOURCE value needed for large files... no
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking for getopt_long_only... yes
checking whether optreset is declared... no
checking for working GNU getopt function... yes
checking whether getpgrp requires zero arguments... yes
checking for strftime... yes
checking for grantpt... yes
checking for getpt... yes
checking for tparm in -lncurses... yes
checking for com_err in -lcom_err... no
checking for mit_des_cbc_encrypt in -lk5crypto... no
checking for mit_des_cbc_encrypt in -lcrypto... no
checking for krb5_init_context in -lkrb5... no
checking krb5.h usability... no
checking krb5.h presence... no
checking for krb5.h... no
checking com_err.h usability... no
checking com_err.h presence... no
checking for com_err.h... no
checking for dgettext in -lintl... no
checking whether localtime caches TZ... no
checking for gettimeofday... yes
checking whether gettimeofday can accept two arguments... yes
checking for socket... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking whether system supports dynamic ptys... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for nl_langinfo and CODESET... yes
checking for size_t... yes
checking for mbstate_t... yes
checking for C restrict keyword... __restrict
checking for C restricted array declarations... yes

Configured for `i686-pc-linux-gnu'.

  Where should the build process find the source
code?    /home/nano/software/emacs What operating system and machine
description files should Emacs use? `s/gnu-linux.h' and `m/intel386.h'
  What compiler should emacs be built with?               gcc -g -O2
-Wno-pointer-sign Should Emacs use the GNU version of
malloc?             yes (Using Doug Lea's new malloc from the GNU C
Library.) Should Emacs use a relocating allocator for buffers?    yes
  Should Emacs use mmap(2) for buffer allocation?         no
  What window system should Emacs use?                    x11
  What toolkit should Emacs use?                          GTK
  Where do we find X Windows header files?                Standard dirs
  Where do we find X Windows libraries?                   Standard dirs
  Does Emacs use -lXaw3d?                                 no
  Does Emacs use -lXpm?                                   no
  Does Emacs use -ljpeg?                                  no
  Does Emacs use -ltiff?                                  no
  Does Emacs use a gif library?                           no 
  Does Emacs use -lpng?                                   no
  Does Emacs use -lrsvg-2?                                no
  Does Emacs use -lgpm?                                   no
  Does Emacs use X toolkit scroll bars?                   yes

configure: creating ./config.status
config.status: creating Makefile
config.status: creating lib-src/Makefile.c
config.status: creating oldXMenu/Makefile
config.status: creating doc/emacs/Makefile
config.status: creating doc/misc/Makefile
config.status: creating doc/lispintro/Makefile
config.status: creating doc/lispref/Makefile
config.status: creating src/Makefile.c
config.status: creating lwlib/Makefile
config.status: creating lisp/Makefile
config.status: creating leim/Makefile
config.status: creating src/config.h
config.status: executing default commands
creating src/epaths.h
src/epaths.h is unchanged
creating lib-src/Makefile
creating src/Makefile

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Odd problem with GNU/Emacs CVS
  2008-01-23 15:38 Odd problem with GNU/Emacs CVS Adolfo De Unanue
@ 2008-01-23 20:04 ` Peter Dyballa
  2008-01-23 21:08   ` Adolfo De Unanue
  0 siblings, 1 reply; 7+ messages in thread
From: Peter Dyballa @ 2008-01-23 20:04 UTC (permalink / raw)
  To: Adolfo De Unanue; +Cc: help-gnu-emacs


Am 23.01.2008 um 16:38 schrieb Adolfo De Unanue:

> Yesterday I made a "cvs up" in my source dir, I got the
> GNU/Emacs 23.0.50 version (the file README said it, 23.0.50.4 if after

You should delete the DOC-* files in etc. Do the same, except of  
DOC-23.0.50.1, also in the install area, i.e. /usr/local/share/emacs/ 
23.0.50/etc – only after you've installed the update. Otherwise GNU  
Emacs would complain about not finding its doc strings.

> building I execute M-x emacs-version), so I followed the classical
> steps:
>
> ./compile


Never knew this would work! Except for the Mac OS X Cocoa/NeXTStep/ 
OPENSTEP variant Emacs.app ...

The change seems to be that most add-ons are now set to off (or no),  
i.e. you have to configure actively with --with-this --with-that -- 
with-something-else!

--
Greetings

   Pete

There's no sense in being precise when you don't even know what  
you're talking about.
				– John von Neumann

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Odd problem with GNU/Emacs CVS
       [not found] <mailman.6445.1201109436.18990.help-gnu-emacs@gnu.org>
@ 2008-01-23 20:09 ` Sven Joachim
  2008-01-23 21:09   ` Adolfo De Unanue
  2008-01-23 21:18   ` Adolfo De Unanue
  0 siblings, 2 replies; 7+ messages in thread
From: Sven Joachim @ 2008-01-23 20:09 UTC (permalink / raw)
  To: help-gnu-emacs

On 2008-01-23 16:38 +0100, Adolfo De Unanue wrote:

> I am a big fan of GNU/Emacs, and since some years ago I always get the
> cvs version, compile it and, obviously, use it :-)
>
> Yesterday I made a "cvs up" in my source dir, I got the
> GNU/Emacs 23.0.50 version (the file README said it, 23.0.50.4 if after
> building I execute M-x emacs-version), so I followed the classical
> steps:
>
> ./compile

You mean ./configure, I guess.

> but wait the console answered me with this
>
> [...]
>
>
> Configured for `i686-pc-linux-gnu'.
>
>   Where should the build process find the source
> code?    /home/nano/software/emacs
>   What operating system and machine description files should Emacs use?
>         `s/gnu-linux.h' and `m/intel386.h'
>   What compiler should emacs be built with?               gcc -g -O2
> -Wno-pointer-sign 
>   Should Emacs use the GNU version of malloc?             yes
>       (Using Doug Lea's new malloc from the GNU C Library.)
>   Should Emacs use a relocating allocator for buffers?    yes
>   Should Emacs use mmap(2) for buffer allocation?         no
>   What window system should Emacs use?                    x11
>   What toolkit should Emacs use?                          GTK
>   Where do we find X Windows header files?                Standard dirs
>   Where do we find X Windows libraries?                   Standard dirs
>   Does Emacs use -lXaw3d?                                 no
>   Does Emacs use -lXpm?                                   no
>   Does Emacs use -ljpeg?                                  no
>   Does Emacs use -ltiff?                                  no
>   Does Emacs use a gif library?                           no 
>   Does Emacs use -lpng?                                   no
>   Does Emacs use -lrsvg-2?                                no
>   Does Emacs use -lgpm?                                   no
>   Does Emacs use X toolkit scroll bars?                   yes

It's a bug that was introduced today, see the thread starting at
http://permalink.gmane.org/gmane.emacs.devel/87377.

You might want to subscribe to the emacs-devel mailinglist to see the
potential breakages in time.

Sven

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Odd problem with GNU/Emacs CVS
  2008-01-23 20:04 ` Peter Dyballa
@ 2008-01-23 21:08   ` Adolfo De Unanue
  0 siblings, 0 replies; 7+ messages in thread
From: Adolfo De Unanue @ 2008-01-23 21:08 UTC (permalink / raw)
  To: help-gnu-emacs

Hi Peter!

El Wed, 23 Jan 2008 21:04:23 +0100
Peter Dyballa <Peter_Dyballa@Web.DE> escribió:

> 
> Am 23.01.2008 um 16:38 schrieb Adolfo De Unanue:
> 
> > Yesterday I made a "cvs up" in my source dir, I got the
> > GNU/Emacs 23.0.50 version (the file README said it, 23.0.50.4 if
> > after
> 
> You should delete the DOC-* files in etc. Do the same, except of  
> DOC-23.0.50.1, also in the install area, i.e. /usr/local/share/emacs/ 
> 23.0.50/etc – only after you've installed the update. Otherwise GNU  
> Emacs would complain about not finding its doc strings.
> 
> > building I execute M-x emacs-version), so I followed the classical
> > steps:
> >
> > ./compile

You are absolutly right, I mean ./configure :-), Sorry for the
brain-hand mixup!
> 
> 
> Never knew this would work! Except for the Mac OS X Cocoa/NeXTStep/ 
> OPENSTEP variant Emacs.app ...
> 
> The change seems to be that most add-ons are now set to off (or no),  
> i.e. you have to configure actively with --with-this --with-that -- 
> with-something-else!
> 
> --
> Greetings
> 
>    Pete
> 
> There's no sense in being precise when you don't even know what  
> you're talking about.
> 				– John von Neumann
> 
> 
> 
> 
> 
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Odd problem with GNU/Emacs CVS
  2008-01-23 20:09 ` Sven Joachim
@ 2008-01-23 21:09   ` Adolfo De Unanue
  2008-01-23 21:18   ` Adolfo De Unanue
  1 sibling, 0 replies; 7+ messages in thread
From: Adolfo De Unanue @ 2008-01-23 21:09 UTC (permalink / raw)
  To: help-gnu-emacs

Hi Sven,

El Wed, 23 Jan 2008 21:09:49 +0100
Sven Joachim <svenjoac@gmx.de> escribió:

> On 2008-01-23 16:38 +0100, Adolfo De Unanue wrote:
> 
> > I am a big fan of GNU/Emacs, and since some years ago I always get
> > the cvs version, compile it and, obviously, use it :-)
> >
> > Yesterday I made a "cvs up" in my source dir, I got the
> > GNU/Emacs 23.0.50 version (the file README said it, 23.0.50.4 if
> > after building I execute M-x emacs-version), so I followed the
> > classical steps:
> >
> > ./compile
> 
> You mean ./configure, I guess.

You are right :-)
> 
> > but wait the console answered me with this
> >
> > [...]
> >
> >
> > Configured for `i686-pc-linux-gnu'.
> >
> >   Where should the build process find the source
> > code?    /home/nano/software/emacs
> >   What operating system and machine description files should Emacs
> > use? `s/gnu-linux.h' and `m/intel386.h'
> >   What compiler should emacs be built with?               gcc -g -O2
> > -Wno-pointer-sign 
> >   Should Emacs use the GNU version of malloc?             yes
> >       (Using Doug Lea's new malloc from the GNU C Library.)
> >   Should Emacs use a relocating allocator for buffers?    yes
> >   Should Emacs use mmap(2) for buffer allocation?         no
> >   What window system should Emacs use?                    x11
> >   What toolkit should Emacs use?                          GTK
> >   Where do we find X Windows header files?                Standard
> > dirs Where do we find X Windows libraries?
> > Standard dirs Does Emacs use
> > -lXaw3d?                                 no Does Emacs use
> > -lXpm?                                   no Does Emacs use
> > -ljpeg?                                  no Does Emacs use
> > -ltiff?                                  no Does Emacs use a gif
> > library?                           no Does Emacs use
> > -lpng?                                   no Does Emacs use
> > -lrsvg-2?                                no Does Emacs use
> > -lgpm?                                   no Does Emacs use X
> > toolkit scroll bars?                   yes
> 
> It's a bug that was introduced today, see the thread starting at
> http://permalink.gmane.org/gmane.emacs.devel/87377.
> 
Thank's I am checkin' it out

> You might want to subscribe to the emacs-devel mailinglist to see the
> potential breakages in time.
> 
> Sven

Thank's for the tip, I will do that!
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Odd problem with GNU/Emacs CVS
  2008-01-23 20:09 ` Sven Joachim
  2008-01-23 21:09   ` Adolfo De Unanue
@ 2008-01-23 21:18   ` Adolfo De Unanue
  2008-01-23 21:43     ` Peter Dyballa
  1 sibling, 1 reply; 7+ messages in thread
From: Adolfo De Unanue @ 2008-01-23 21:18 UTC (permalink / raw)
  To: help-gnu-emacs

Hi again,

I modify the configure.in, so now the lib images are in ON (i.e.
OPTION_DEFAULT_ON) but I am getting the same response after
the ./compile. The same thing happens if I use ./configure --with-ljpeg
--with-ltiff etc...

Any ideas?

Adolfo


El Wed, 23 Jan 2008 21:09:49 +0100
Sven Joachim <svenjoac@gmx.de> escribió:

> On 2008-01-23 16:38 +0100, Adolfo De Unanue wrote:
> 
> > I am a big fan of GNU/Emacs, and since some years ago I always get
> > the cvs version, compile it and, obviously, use it :-)
> >
> > Yesterday I made a "cvs up" in my source dir, I got the
> > GNU/Emacs 23.0.50 version (the file README said it, 23.0.50.4 if
> > after building I execute M-x emacs-version), so I followed the
> > classical steps:
> >
> > ./compile
> 
> You mean ./configure, I guess.
> 
> > but wait the console answered me with this
> >
> > [...]
> >
> >
> > Configured for `i686-pc-linux-gnu'.
> >
> >   Where should the build process find the source
> > code?    /home/nano/software/emacs
> >   What operating system and machine description files should Emacs
> > use? `s/gnu-linux.h' and `m/intel386.h'
> >   What compiler should emacs be built with?               gcc -g -O2
> > -Wno-pointer-sign 
> >   Should Emacs use the GNU version of malloc?             yes
> >       (Using Doug Lea's new malloc from the GNU C Library.)
> >   Should Emacs use a relocating allocator for buffers?    yes
> >   Should Emacs use mmap(2) for buffer allocation?         no
> >   What window system should Emacs use?                    x11
> >   What toolkit should Emacs use?                          GTK
> >   Where do we find X Windows header files?                Standard
> > dirs Where do we find X Windows libraries?
> > Standard dirs Does Emacs use
> > -lXaw3d?                                 no Does Emacs use
> > -lXpm?                                   no Does Emacs use
> > -ljpeg?                                  no Does Emacs use
> > -ltiff?                                  no Does Emacs use a gif
> > library?                           no Does Emacs use
> > -lpng?                                   no Does Emacs use
> > -lrsvg-2?                                no Does Emacs use
> > -lgpm?                                   no Does Emacs use X
> > toolkit scroll bars?                   yes
> 
> It's a bug that was introduced today, see the thread starting at
> http://permalink.gmane.org/gmane.emacs.devel/87377.
> 
> You might want to subscribe to the emacs-devel mailinglist to see the
> potential breakages in time.
> 
> Sven
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Odd problem with GNU/Emacs CVS
  2008-01-23 21:18   ` Adolfo De Unanue
@ 2008-01-23 21:43     ` Peter Dyballa
  0 siblings, 0 replies; 7+ messages in thread
From: Peter Dyballa @ 2008-01-23 21:43 UTC (permalink / raw)
  To: Adolfo De Unanue; +Cc: help-gnu-emacs


Am 23.01.2008 um 22:18 schrieb Adolfo De Unanue:

> The same thing happens if I use ./configure --with-ljpeg
> --with-ltiff


Check with './configure --help' the correct syntax! For me GNU Emacs  
tells:

	--with-tiff
	--with-jpeg

etc.

--
Greetings

   Pete

These are my principles and if you don't like them... well, I have  
others.
				- Groucho Marx

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2008-01-23 21:43 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-23 15:38 Odd problem with GNU/Emacs CVS Adolfo De Unanue
2008-01-23 20:04 ` Peter Dyballa
2008-01-23 21:08   ` Adolfo De Unanue
     [not found] <mailman.6445.1201109436.18990.help-gnu-emacs@gnu.org>
2008-01-23 20:09 ` Sven Joachim
2008-01-23 21:09   ` Adolfo De Unanue
2008-01-23 21:18   ` Adolfo De Unanue
2008-01-23 21:43     ` Peter Dyballa

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.