[Top][All Lists]

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

Re: [Bug-mit-scheme] [bug #34689] [9.1] Build failure on x86_64-linux-gn

From: Chris Hanson
Subject: Re: [Bug-mit-scheme] [bug #34689] [9.1] Build failure on x86_64-linux-gnu
Date: Wed, 9 Nov 2011 01:15:20 -0800

I've put out a new release that supports "./configure && make".

I still have to deal with the info files and will replace the README
with a more relevant one; that README is intended for someone building
from source, when they have a working Scheme compiler already
installed on their system.  I'll get around to that before the next
release, or I'll generate 9.1.2 if I have enough time.

On Mon, Nov 7, 2011 at 1:53 PM, Ludovic Courtès <address@hidden> wrote:
> Hi,
> Matt Birkholz <address@hidden> skribis:
>>> From: address@hidden (Ludovic Courtès)
>>> Date: Sun, 30 Oct 2011 12:50:45 +0100
>>> [...]
>>> I actually read the fine src/README.txt, which led me to think that
>>> ‘make’ alone would work.  Perhaps it should be updated to reflect that?
>> How?
> I was referring to the table and text under “Building from source on
> unix systems”:
>  The following table shows the commands used to transition the build
>  tree from one build state to another.  All of the commands must be run
>  in the "src" directory.
>          From          To              Command
>          ------------  ------------    ---------------------
>          fresh         distribution    ./Setup.sh
>          distribution  configured      ./configure
>          configured    compiled        make
>          compiled      configured      make clean
>          compiled      distribution    make distclean
>          compiled      fresh           make maintainer-clean
>          configured    distribution    make distclean
>          configured    fresh           make maintainer-clean
>>> Would it be an option for you to have a top-level configure and
>>> makefile that would allow ‘./configure && make’ to do the right
>>> thing (info "(standards) Managing Releases")?
>> I would like to see that, but I never learned to use VPATH, and do not
>> use proprietary operating systems.  I dare not muck about in the build
>> process more than I have already.  I tried to KISS it with something
>> like
>>       #! /bin/sh
>>       (cd src; ./configure $*)
>>       (cd doc; ./configure $*)
>> But that does not do justice to `./configure --help'...
> There could be a top-level configure.ac with:
>  AC_INIT([MIT/GNU Scheme], [9.1], address@hidden, [mit-scheme])
>  AC_CONFIG_SUBDIRS([src doc])
> It should DTRT.  As a bonus, configure runs will use a shared cache.
> The top-level makefile could be improved to support more targets.
> Automake could be used for that, but since it’s not used for the rest of
> the system, I guess you may be reluctant to using it for a single
> convenience makefile.
> Thanks,
> Ludo’.
> _______________________________________________
> Bug-MIT-Scheme mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-mit-scheme

reply via email to

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