* Re: New texinfo still breaks `make bootstrap` [not found] <Pine.GSO.3.96.980328115215.14742A-100000@markab.dbai.tuwien.ac.at> @ 1998-03-31 0:46 ` Jim Wilson 1998-04-04 11:01 ` Jeffrey A Law 0 siblings, 1 reply; 3+ messages in thread From: Jim Wilson @ 1998-03-31 0:46 UTC (permalink / raw) To: law; +Cc: egcs A lot texinfo related problems could be fixed simply by not building the stuff we don't need. For instance, this gets me past the texinfo build problems others are reporting, though I don't know yet whether the resulting makeinfo program works, my build is still going. There was a similar change in the old EGCS texinfo sources. Fri Oct 31 09:39:31 1997 Jeffrey A Law (law@cygnus.com) * Makefile.in (install targets): Add a dummy target for sunos make. (SUBDIR): Remove 'info'. It's unneeded. Index: Makefile.am =================================================================== RCS file: /egcs/carton/cvsfiles/egcs/texinfo/Makefile.am,v retrieving revision 1.4 diff -p -r1.4 Makefile.am *** Makefile.am 1998/03/24 19:40:22 1.4 --- Makefile.am 1998/03/31 02:26:47 *************** EXTRA_DIST = INTRODUCTION dir-example *** 14,16 **** --- 14,19 ---- # Do doc/ last so makeinfo will be built when we get there. # Others are alphabetical. SUBDIRS = intl lib info makeinfo po util doc + # ??? For EGCS, only build the stuff we actually need. This eliminates the + # need for xgettext that exists in the po subdirectory. + SUBDIRS = intl lib makeinfo Index: Makefile.in =================================================================== RCS file: /egcs/carton/cvsfiles/egcs/texinfo/Makefile.in,v retrieving revision 1.9 diff -p -r1.9 Makefile.in *** Makefile.in 1998/03/24 19:40:23 1.9 --- Makefile.in 1998/03/31 02:26:47 *************** EXTRA_DIST = INTRODUCTION dir-example *** 97,102 **** --- 97,105 ---- # Do doc/ last so makeinfo will be built when we get there. # Others are alphabetical. SUBDIRS = intl lib info makeinfo po util doc + # ??? For EGCS, only build the stuff we actually need. This eliminates the + # need for xgettext that exists in the po subdirectory. + SUBDIRS = intl lib makeinfo ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = config.h ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: New texinfo still breaks `make bootstrap` 1998-03-31 0:46 ` New texinfo still breaks `make bootstrap` Jim Wilson @ 1998-04-04 11:01 ` Jeffrey A Law 1998-04-06 2:35 ` Manfred Hollstein 0 siblings, 1 reply; 3+ messages in thread From: Jeffrey A Law @ 1998-04-04 11:01 UTC (permalink / raw) To: Jim Wilson; +Cc: egcs In message < 199803310231.SAA11043@rtl.cygnus.com >you write: > A lot texinfo related problems could be fixed simply by not building the > stuff we don't need. For instance, this gets me past the texinfo build > problems others are reporting, though I don't know yet whether the resulting > makeinfo program works, my build is still going. > > There was a similar change in the old EGCS texinfo sources. > Fri Oct 31 09:39:31 1997 Jeffrey A Law (law@cygnus.com) > * Makefile.in (install targets): Add a dummy target for sunos make. > (SUBDIR): Remove 'info'. It's unneeded. Part of the original idea behind not building certain things was because our texinfo was horribly out of date and we didn't want to build anything except the bare bones necessary to format the docs. Similarly we tweaked make install to do nothing to avoid overwriting a previously installed texinfo (which would probably have been newer than the one egcs would install). So the question at had is do we want to continue the the practice of not building stuff we don't need and not installing texinfo? I don't care much either way. jeff ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: New texinfo still breaks `make bootstrap` 1998-04-04 11:01 ` Jeffrey A Law @ 1998-04-06 2:35 ` Manfred Hollstein 0 siblings, 0 replies; 3+ messages in thread From: Manfred Hollstein @ 1998-04-06 2:35 UTC (permalink / raw) To: law; +Cc: wilson, egcs On Thu, 2 April 1998, 22:54:05, law@cygnus.com wrote: > > In message < 199803310231.SAA11043@rtl.cygnus.com >you write: > > A lot texinfo related problems could be fixed simply by not building the > > stuff we don't need. For instance, this gets me past the texinfo build > > problems others are reporting, though I don't know yet whether the resulting > > makeinfo program works, my build is still going. > > > > There was a similar change in the old EGCS texinfo sources. > > Fri Oct 31 09:39:31 1997 Jeffrey A Law (law@cygnus.com) > > * Makefile.in (install targets): Add a dummy target for sunos make. > > (SUBDIR): Remove 'info'. It's unneeded. > Part of the original idea behind not building certain things was > because our texinfo was horribly out of date and we didn't want to > build anything except the bare bones necessary to format the docs. > Similarly we tweaked make install to do nothing to avoid overwriting > a previously installed texinfo (which would probably have been newer > than the one egcs would install). > > So the question at had is do we want to continue the the practice > of not building stuff we don't need and not installing texinfo? Last Saturday I did a `make install' and got pretty surprised when I saw, it did not only install the usual `gcc', `c++', `g++' ... but `info', `makeinfo', `texi2dvi', ... and even the texinfo related locale files. Unnecessary to say, it completely overwrote my previous texinfo-3.12 installation :-) > > I don't care much either way. I'd prefer not to build and/or install anything which doesn't actually belong to egcs. > > jeff manfred ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1998-04-06 2:35 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <Pine.GSO.3.96.980328115215.14742A-100000@markab.dbai.tuwien.ac.at> 1998-03-31 0:46 ` New texinfo still breaks `make bootstrap` Jim Wilson 1998-04-04 11:01 ` Jeffrey A Law 1998-04-06 2:35 ` Manfred Hollstein
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).