Subject: What might cause this failure? - msg#00080

Previous Message by Date: click to view message preview

Re: 'fc' program and autoconf

On 17-Aug-2002, Paul Eggert <eggert@xxxxxxxxxxx> wrote: | > Date: Sat, 17 Aug 2002 21:12:33 -0400 (EDT) | > From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxxxxxxx> | | > > Thanks for the suggestion. I think the fc Fortran compiler is long | > > dead, so I installed this patch. | > | > Perhaps I spoke too soon? It turns out that 'fc' is the name of the | > (native) Fortran compiler by Convex (now HP) on the HP Exemplar SPP. | | If that's the only fc we have to worry about, we should be OK. The | Convex Exemplar is obsolete, and other than a hobbyist picking one up | at a salvage auction I don't think we'll ever run into anyone actually | booting one. (Next you'll be finding old copies of manuals for the | Kendall Square KSR-1. :-) | | In the unlikely case that someone still actually uses such a beast, | they'll almost certainly have HP's Fortran as well (called "f77"), and | since f77 preceded fc in the list we can safely omit the fc. I'd guess that the only reason that fc is in the list at all is because when I wrote the original configure code for Octave, I had access to a Convex system (C-110 or something?) at the UT Center for High Performance Computing, and for some reason, I knew that "fc" was the name of the compiler. I remember thinking back then that there might be some conflict with the bash fc builtin, and I don't recall actually ever building Octave on the Convex, but I left fc in the list anyway. I supposed I'd vote to remove it too. jwe -- www.octave.org | Unfortunately we were hopelessly optimistic in 1954 www.che.wisc.edu/~jwe | about the problems of debugging FORTRAN programs. | -- J. Backus

Next Message by Date: click to view message preview

Eiffel language support

Hello All, I'm trying to write a few macro's to have Eiffel support. Checking for stuff worked quite well. However, trying to add Eiffel language support didn't prove to be so easy. For example as soon as I add this: AC_DEFUN([AC_LANG_COMPILER(Eiffel)], [AC_REQUIRE([AC_PROG_EC])]) aclocal aborts with: internal error: /\bAC_LANG_COMPILER(Eiffel\b/: unmatched () in regexp at (eval 6) line 110. It doesn't seem to matter if AC_PROG_EC is defined or not. Can anyone shed some light on this matter? m4 is quite new to me. -- Regards, Berend. (-:

Previous Message by Thread: click to view message preview

Re: Threading support

Philip Willoughby wrote: I generally use AC_SEARCH_LIBS(pthread_create, pthread posix POSIX) for pthread support Unfortunately, this will fail on a number of systems (see the ACX_PTHREAD macro in the macro archive for the large number of incantations that are used.) The ACX_PTHREAD macro doesn't check for -lposix or -lPOSIX, and I'd like to add those if they are necessary; on what systems is this the location of the threads library? Steven

Next Message by Thread: click to view message preview

Re: What might cause this failure?

On Sun, Aug 18, 2002 at 07:55:53PM -0700, Bruce Korb wrote: > No errors, > except for this incomprehensible thing. > [lots of commands] \ > && make distcleancheck > configure: error: cannot find install-sh or install.sh in config ../config > make: *** [distcheck] Error 1 Not sure whether this is relevent or not, but it might offer a clue. I saw something kind of similar in a package I worked on. The package used AC_CONFIG_SUBDIRS(), and it was from one of the subdirectories that the distributions were built: pkg-root/ Makefile.am configure.ac bar/ baz/ distrib/ Makefile.am configure.ac more-stuff One went "cd pkg-root/distrib; make dist" to build a distribution. I can no longer recall why (maybe just because I didn't understand things too well :-), but one had to run automake separately in both pkg-root and pkg-root/distrib. The problem was that, in distrib: - "automake --add-missing" didn't think install-sh was in fact missing, because it could find the copy in pkg-root, because: - its default search path is ($SRCDIR $SRCDIR/.. $SRCDIR/../..) - the file had already been installed in pkg-root by the "automake --add-missing" that had been run there - For the same reason, pathnames in distrib got configured to ../install-sh and the like, which masked the problem for the most part - But install-sh didn't make it into distributions, so trying to build from one of those would blow up (There may have been similar problems with other files that --add-missing is supposed to deal with.) Workaround: add this to pkg-root/distrib/configure.ac: AC_CONFIG_AUX_DIR([.]) That defeats the search path shown above, which keeps automake from seeing ../install-sh etc., and thus forces it to put another copy directly into distrib. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont. erics@xxxxxxxxxxxx | | / Anyone who swims with the current will reach the big music steamship; whoever swims against the current will perhaps reach the source. - Paul Schneider-Esleben