Hello Waldek, *
Ok, you mention SVN and the problem came from that software on Cygwin, or
how it operates. I just updated all my Cygwin installation last week.
Surprisingly when I update my FriCAS SVN tree, merging one or two weeks of
change in the FriCAS source leads the error spotted (remake ptyout.clisp).
Even if I never touch this tree, I always do a copy of it in my home
directory of MinGW/MSYS.
I just did a fresh checkout of r2100 and everything went fine except line
754-762 :
===================================================
#+:sbcl
(defun OBEY (S)
#-:win32 (sb-ext::process-exit-code
(sb-ext::run-program "/bin/sh"
(list "-c" S) :input t :output t :error t))
#+:win32 (sb-ext::process-exit-code
(sb-ext::run-program (make-absolute-filename "/lib/obey.bat")
(list S) :input t :output t :error t))
)
===================================================
As in the past the OBEY command with the offending obey.bat file is
problematic on Windows. Personally, since the bin directory of MSYS is in
the PATH, I use :
=====================================================
(defun OBEY (S)
#-:win32 (sb-ext::process-exit-code
(sb-ext::run-program "/bin/sh"
(list "-c" S) :input t :output t :error t))
#+:win32 (sb-ext::process-exit-code
(sb-ext::run-program "sh.exe" (list "-c" S) :input t :output t
:error t :search t))
)
======================================================
Of course there isn't any "legacy" path for executables on Windows so I use
the ':search t' option. This is not a big problem for information, this to
sort temp.text in br-data.boot.
I will not exhaustively search where and why OBEY routine is used in FriCAS
to see which shell command it use, I think this routine should be removed
of FriCAS.
Hope that helps if needed.
In any case, thanks!
--
Greg
2016-09-06 21:11 GMT+02:00 Waldek Hebisch <[email protected]>:
> > Ok, will look deeper into that issue when time permits but right now I
> just
> > checked out the SVN tree (rev. 2100) and the build process stops directly
> > at an earlier stage :
> >
> > ============================================================
> =================
> <snip>
> > make[2]: Leaving directory `/home/gvanuxem/fricas_build/src/lisp'
> > make[2]: Entering directory `/home/gvanuxem/fricas_build/src/boot'
> > Building stage 0
> > [ -d stage0 ] || ../../../fricas/config/mkinstalldirs stage0
> > mkdir -p -- stage0
> > rm -rf prev-stage
> > rm -f stage0/ptyout.fasl stage0/btincl2.fasl stage0/btscan2.fasl
> > stage0/typrops.fasl stage0/btpile2.fasl stage0/typars.fasl
> > stage0/tytree1.fasl
> > rm -f stage0/ptyout.clisp stage0/btincl2.clisp stage0/btscan2.clisp
> > stage0/typrops.clisp stage0/btpile2.clisp stage0/typars.clisp
> > stage0/tytree1.clisp
> > make OBJECTS="stage0/ptyout.fasl stage0/btincl2.fasl stage0/btscan2.fasl
> > stage0/typrops.fasl stage0/btpile2.fasl stage0/typars.fasl
> > stage0/tytree1.fasl" stage0/bootsys.exe
> > make[3]: Entering directory `/home/gvanuxem/fricas_build/src/boot'
> > /home/gvanuxem/fricas_build/../fricas/src/scripts/build_helper
> > --translate_boot --debug=no --use=./prev-stage/bootsys
> > --output=../../../fricas/src/boot/compiled/ptyout.clisp
> > ../../../fricas/src/boot/compiled/../../../fricas/src/boot/ptyout.boot
> > /home/gvanuxem/fricas_build/../fricas/src/scripts/build_helper: line 4:
> > ./prev-stage/bootsys: No such file or directory
> <snip>
> > Reading the output, it *seems* the build machinery removes the prev-stage
> > directory ('rm -rf prev-stage') and after tries to use a file in it
> > 'build_helper --translate_boot --debug=no --use=./prev-stage/bootsys'.
> > That's cryptic to me.
>
> Well, make is using wrong rule. More precisely,
> '../../../fricas/src/boot/compiled/ptyout.clisp' is part of
> source tree and make should not try to remake it. ATM I do
> not see how make decided that it should re-make
> '../../../fricas/src/boot/compiled/ptyout.clisp'
> It seems that
> ../../../fricas/src/boot/compiled/../../../fricas/src/boot/ptyout.boot
> points to nonexistent file...
>
> > So I quickly tried to see which revision modified the build machinery
> > without success.
>
> This part of build machinery did not change for long time.
> Actually, this part works the same when you use release tarball
> and when you fetch from SVN. OK, using SVN you may get
> different timestamps. But for stage0 build shoud just use
> .clisp files from surced directory. In particular,
> regardless of timestaps build should not try to remake
> them.
>
> --
> Waldek Hebisch
>
> --
> You received this message because you are subscribed to the Google Groups
> "FriCAS - computer algebra system" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/fricas-devel.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
