Re: Build problem on 64 bit Linux

Thanks for the help!!

Every time I run it with bash -vx the whole thing works and I can build.
Every time I run ./configure without bash -xv it fails as I described.

Even with just "bash ./configure with-gcc" it works.  The bash command
creates a new environment.  There must be something in my regular
environment that is causing the problem.

How else can I figure out the problem?

Thanks.

Blake


On Mon, Dec 11, 2017 at 8:59 AM, Sam Steingold <[email protected]> wrote:

> > * Blake McBride <[email protected]> [2017-12-10 18:04:51 -0600]:
> >
> > Still a problem.  Here you go:
> >
> > $ rm -rf *
> > $ ls -l
> > total 0
> > $ hg update -C
> > 1383 files updated, 0 files merged, 0 files removed, 0 files unresolved
> > $ ls
> > ANNOUNCE    DEPENDENCIES  HACKING          Makefile.in  SUMMARY
> version.sh
> > benchmarks  doc           INSTALL          modules      tests
> win32msvc
> > configure   emacs         INSTALL.windows  sacla-tests  unix
> > COPYRIGHT   GNU-GPL       Makefile.devel   src          utils
> > $ ./configure build-with-gcc
> > ...
> > config.status: executing depfiles commands
> > config.status: executing libtool commands
> > config.status: executing po-directories commands
> > config.status: creating po/POTFILES
> > config.status: creating po/Makefile
> > Configure findings:
> >   FFI:        yes (user requested: default)
> >   readline:   yes (user requested: default)
> >   libsigsegv: yes
> > $ cd build-with-gcc
> > $ make
> > make: *** No targets specified and no makefile found.  Stop.
> > $ ls
> > config.cache  config.log     floatparam.h  intparam.h  makemake  stamp-h1
> > config.h      config.status  gllib         libtool     po
>
> When I repeat what you did, my output ended with
>
> --8<---------------cut here---------------start------------->8---
> ...
> Configure findings:
>   FFI:        no, consider installing GNU libffcall (user requested:
> default)
>   readline:   yes (user requested: default)
>   libsigsegv: yes
> ./makemake  > Makefile
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> cp -p ../src/cfgunix.lisp config.lisp
> chmod +w config.lisp
> echo '(setq *clhs-root-default* "http://www.ai.mit.edu/
> projects/iiip/doc/CommonLISP/HyperSpec/")' >> config.lisp
>
> To continue building CLISP, the following commands are recommended
>   (cf. unix/INSTALL step 4 ff):
>     cd build-with-gcc
>     /Users/sds/src/emacs/trunk/build/lib-src/emacsclient config.lisp
>     make
> # CLISP self-test:
>     make check
> # Test non-portable features and modules
>     make extracheck mod-check
> --8<---------------cut here---------------end--------------->8---
>
> IOW, your "./configure" probably failed (try "./configure || echo failed").
> The question is why.
> Could you please run it as "bash -vx configure"?
> You will see a lot of output, and the end will, hopefully, shed some
> light on what the problem is.
>
> Thanks.
>
> --
> Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
> http://steingoldpsychology.com http://www.childpsy.net
> http://think-israel.org
> http://www.memritv.org http://islamexposedonline.com
> http://www.dhimmitude.org
> The more project management you do, the less likely your project is to
> succeed.
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel