AW: AW: problem compiling emacs with suse 10.1

[C.Strobl]

> -----Ursprüngliche Nachricht-----
> Von: Nelson H. F. Beebe [mailto:beebe@math.utah.edu] 
> Gesendet: Dienstag, 19. September 2006 20:48
> An: Strobl, Christian
> Cc: beebe@math.utah.edu
> Betreff: Re: AW: problem compiling emacs with suse 10.1
> 
> >> ...
> >> it didn't work, maybe because im not experienced with 
> linux at all. 
> >> could you write the commands below line for line. i don't 
> also know 
> >> what the LDFLAGS are for and i didn't find anything in 
> google about 
> >> it.  i set also a softlink to the folder /usr/X11R6/lib 
> but it didn't 
> >> help neither.
> >> ...
> 
> OK.  The && is an AND-THEN shell operator: A && B means run 
> command A, an if-and-only-if it succeeds then run command B.
> 
> You could write my example like this, with separate commands:
> 
>       env LDFLAGS=-L/usr/X11R6/lib CC=gcc4 ./configure 
> --with-x-toolkit=athena --with-gcc=yes --with-x11
>       make bootstrap
> 
> I used the date command, because I like to record dates in my 
> build logs, so that I can easily measure how long the build 
> takes.  However, for your needs, they can be omitted.
> 
> The env command takes a list of VARIABLE=VALUE assignments, 
> and adds them to the environment passed to the command that 
> follows the assignments.  It is a good way to set variables 
> that apply only to a single command, and it has no effect on 
> any values that those variables have in the current shell.
> 
> The CC=gcc4 assignment says to use gcc4 as the C compiler, 
> instead of the default gcc.  Several of my machines have 
> multiple compilers, and gcc is usually a version 3.x 
> compiler, while gcc4 is a version 4.x one.
> 
> The LDFLAGS variable is a long-time Unix, POSIX, and GNU 
> standard in Makefiles to define the initial flags passed on 
> the compiler command lines to the loader/linker.  The 
> configure script generally adds to it.  It is needed on most 
> current Unix systems because of the bug in autoconf that 
> fails to list /usr/X11R6/lib as one of the places that
> X11 Window System libraries should be looked for.  One 
> exception is recent Fedora Core 5 systems, which have moved 
> the X11 libraries into /usr/lib, the standard library 
> directory that is always searched.  It does not matter if the 
> directory does not exist.
> 
> The --with-x-toolkit=athena option selects the lowest-level, 
> and thus, most portable and likely to be found everywhere, 
> X11 toolkit.  By choosing the least common denominator, I can 
> assure my users that an emacs window always looks the same, 
> no matter what machine they login to.  I've tried builds with 
> the motif toolkit in the past, but that just led to visual confusion.
> 
> The --with-gcc=yes option says that the build will be with a 
> gcc-compatible compiler.  It can likely be omitted.
> 
> The final --with-x11 option is the critical one: it says that 
> emacs should be built with X11 support.  Since emacs runs on 
> a huge number of different platforms, including some embedded 
> systems on tiny devices, it does not default to building with 
> X11 support.  Older Mac OS X systems, before version 10.4, 
> won't support emacs with X11.
> 
> In emacs 21.x and earlier, after the configure run, all that 
> you had to do was type "make".  In emacs 22.x, you have to 
> use "make bootstrap".  In either case, that command starts 
> the make utility, which then uses the Makefile and its 
> dependencies to figure out what needs to be compiled, linked, 
> and otherwise done to get a complete emacs built.
> 
> When I build a new version, I always install it like this:
> 
>       make install EMACS=nemacs
> 
> That way, the existing emacs executable remains intact, and 
> the new version is available for people to try out as "nemacs".
> 
> --------------------------------------------------------------
> -----------------
> - Nelson H. F. Beebe                    Tel: +1 801 581 5254  
>                 -
> - University of Utah                    FAX: +1 801 581 4148  
>                 -
> - Department of Mathematics, 110 LCB    Internet e-mail: 
> beebe@math.utah.edu  -
> - 155 S 1400 E RM 233                       beebe@acm.org  
> beebe@computer.org -
> - Salt Lake City, UT 84112-0090, USA    URL: 
> http://www.math.utah.edu/~beebe/ -
> --------------------------------------------------------------
> -----------------
> 



hello nelson,

thanks for your very good explanation, i did it exactly that way. the problem 
was that it looked like that nothing has changed. config gives always the same 
output.
the hint from andreas schwab (see below) solved the problem finally. i deleted 
the whole folder and extracted the archive once again 

thanks also to andreas and reiner

regards
christian



###################################################################################

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> [ Please copy the mailing list <bug-gnu-emacs@gnu.org> in replies. ]
>
> On Tue, Sep 19 2006, C.Strobl@dlr.de wrote:
>
>> hello reiner,
>>
>> thanks for your help, but it didn't work. the line
>>
>> checking for X... (cached) no
>>
>> remains also after installing the xorg-x11-devel. also a symbolic 
>> link to the /usr/X11R6/lib doesn't work. do you know any further 
>> hint?
>
> Hm, it says "cached".  Does it help to remove "config.status" before

ITYM config.cache.

Andreas.

--
Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, 
Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 
942B 1756  01D3 44D5 214B 8276 4ED5 "And now for something completely 
different."

############################################################################