help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: still failing to "make" almost-cvs 21.3


From: David Combs
Subject: Re: still failing to "make" almost-cvs 21.3
Date: Sat, 24 Jul 2004 00:38:02 +0000 (UTC)

In article <address@hidden>,
Eli Zaretskii <address@hidden> wrote:
>> From: address@hidden (David Combs)
>> Newsgroups: gnu.emacs.help
>> Date: 16 Jul 2004 21:08:07 -0400
>> 
>> STILL trying to compile "almost-cvs" 21.3
>
>This is the wrong place to discuss problems with building the CVS
>code.  Please in the future write to address@hidden

OOPS -- just noticed the above after filling-in a reply.
Hmmm.  Look, I'll shoot this back to the group, just in
case someone has a sudden "ah-ha"; then I'll have to
merge these n-posts, and shoot *that* off to the pretest-people.

Thanks for having a look at this!

David


>
>> ------- Repeating that code that caught me:
>> 
>> maybe_bootstrap:
>>      @bar="`echo $(srcdir)/lisp/*.elc`"; \
>>      if [ \( "$$bar" = '$(srcdir)/lisp/*.elc' \) -o \( "$$bar" = '' \) ]; 
>> then \
>>        echo "Your tree does not include the compiled Lisp files."; \
>>        echo "You need to do \`make bootstrap' to build Emacs."; \
>>        echo "Emacs now requires Texinfo version 4.2."; \
>>        exit 1;\
>>      fi
>
>That's right: the first time you build the CVS code after checking it
>out, you need to say "make bootstrap".
>
>> I've now gone and installed texinfo 4.2, and it's on $PATH.
>> 
>> No, no .elc-files.  Why didn't they get built?  Beats me!
>
>They are not in the CVS tree, and since your previous bootstrap
>failed, they were not built.
>
>> And, as instructed, I tried to do the "make bootstrap"; got this:
>> 
>> 275 ==/big7.1/sources-stuff-2/emacs-21.3==> 
>> 275 ==/big7.1/sources-stuff-2/emacs-21.3==> make bootstrap
>> (cd src;      make  mostlyclean)
>> [Please ignore a syntax error on the next line - it is intentional]
>
>Where did that message come from?  The only place I can find it in the
>CVS is in the nt/gmake.defs file, which should be only used on

No, not windows, but sparc: sunblade 100.  Weird...  Here's a piece of
the ./configure-created Makefile (I use "|" instead of ">"):


 | # ==================== Things `configure' Might Edit ====================
 | 
 | CC=gcc
 | CPP=gcc -E
 | C_SWITCH_SYSTEM= 
 | ALLOCA=
 | LN_S=ln -s
 | CFLAGS=-O2 -pipe -mcpu=ultrasparc
 | LDFLAGS=-L/usr/openwin/lib -R/usr/openwin/lib -L/usr/sfw/lib -R/usr/sfw/lib  
  -L/opt/sfw/lib -R/opt/sfw/lib -L/usr/openwin/lib
 | CPPFLAGS=    
 | C_SWITCH_X_SITE=-I/usr/openwin/include
 | LD_SWITCH_X_SITE=-L/usr/openwin/lib
 | EXEEXT=
 | 
 | ### These help us choose version- and architecture-specific directories
 | ### to install files in.
 | 
 | ### This should be the number of the Emacs version we're building,
 | ### like `18.59' or `19.0'.
 | version=21.3.50
 | 
 | ### This should be the name of the configuration we're building Emacs
 | ### for, like `mips-dec-ultrix' or `sparc-sun-sunos'.
 | configuration=sparc-sun-solaris2.9                 <<<================ SPARC
 | 
 | # ==================== Where To Install Things ====================




>Windows.  Are you building this on Windows?  If so, you need to follow
>the Windows installation instructions in nt/INSTALL, except that you
>should say "make bootstrap" instead of just "make".
>
>> Huh?:  "make[1]: *** No rule to make target `mostlyclean'.  Stop."
>
>Probably because you didn't run nt/configure.bat, and so there's no
>Makefile in the `src' directory.

But there is one, and here's the mostlyclean part of it ("src/Makefile"):

 | intervals.o: intervals.c buffer.h $(INTERVAL_SRC) keyboard.h puresize.h 
$(config_h)
 | composite.o: composite.c buffer.h  charset.h $(INTERVAL_SRC) $(config_h)
 | sunfns.o: sunfns.c buffer.h window.h dispextern.h $(config_h)
 | ${libsrc}emacstool${EXEEXT}: ${libsrc}emacstool.c
 |      cd ${libsrc}; ${MAKE} ${MFLAGS} emacstool${EXEEXT}
 | bootstrapclean:
 |      rm -f bootstrap-emacs${EXEEXT}
 | mostlyclean:
 |      rm -f temacs${EXEEXT} prefix-args${EXEEXT} core *.core \#* *.o 
libXMenu11.a liblw.a
 |      rm -f ../etc/DOC
 |      rm -f bootstrap-emacs${EXEEXT}
 | clean: mostlyclean
 |      rm -f emacs-*${EXEEXT} emacs${EXEEXT}
 | distclean: clean
 |      rm -f epaths.h config.h Makefile Makefile.c config.stamp stamp-oldxmenu 
../etc/DOC-*
 |      mv ./.gdbinit ./.gdbinit.save
 |      if test -f "${srcdir}/.gdbinit"; then rm -f ./.gdbinit.save;    else mv 
./.gdbinit.save ./.gdbinit; fi



In fact, at least these Makefiles got created on the day
I did the .configure:



This from the top-level Makefile:

 | SUBDIR = lib-src src
 | 
 | # The makefiles of the directories in $SUBDIR.
 | SUBDIR_MAKEFILES = lib-src/Makefile man/Makefile lispref/Makefile 
lispintro/Makefile src/Makefile oldXMenu/Makefile lwlib/Makefile leim/Makefile
 | 
 | # Subdirectories to install, and where they'll go.





And this from doing (as dired "!"-cmd (the "# *" to fool "!")):

 |   ls -lsAt lib-src/Makefile man/Makefile lispref/Makefile lispintro/Makefile 
src/Makefile oldXMenu/Makefile lwlib/Makefile leim/Makefile  # *


 |   44 -r--r--r--   1 dkc      other      21799 Jul 16 15:50 src/Makefile
 |   26 -r--r--r--   1 dkc      other      12545 Jul 16 15:50 lib-src/Makefile
 |   16 -rw-r--r--   1 dkc      other       7350 Jul 16 15:50 leim/Makefile
 |    6 -rw-r--r--   1 dkc      other       2153 Jul 16 15:50 lispintro/Makefile
 |    8 -rw-r--r--   1 dkc      other       3878 Jul 16 15:50 lispref/Makefile
 |    4 -rw-r--r--   1 dkc      other       1865 Jul 16 15:50 lwlib/Makefile
 |   20 -rw-r--r--   1 dkc      other       9428 Jul 16 15:50 man/Makefile
 |    6 -rw-r--r--   1 dkc      other       3031 Jul 16 15:50 oldXMenu/Makefile






>
>> Hey, cvs-maintainers, do I *really* have to hack this Makefile,
>
>No, you don't.
>
>>   fix bugs in it?
>
>What bugs? ;-)
>
>


------ dup from above:

>This is the wrong place to discuss problems with building the CVS
>code.  Please in the future write to address@hidden

OOPS -- just noticed the above after filling-in a reply.
Hmmm.  Look, I'll shoot this back to the group, just in
case someone has a sudden "ah-ha"; then I'll have to
merge these n-posts, and shoot *that* off to the pretest-people.

Thanks for having a look at this!

David



reply via email to

[Prev in Thread] Current Thread [Next in Thread]