Am 10. Juli 2020 um 03:36 Uhr schrieb "Kai Torben Ohlhus":
> You are right, with the "--with-pkg-dir" option you specify a custom
> location for the default "/pkg" directory, thus you have to download
> everything all over again.
I might be misunderstanding what your wrote. But to maybe clear up a bit where setting the pkg-dir can be useful, please let me give an example:
Assume you would have several local MXE Octave repositories that are configured for incompatible builds (e.g. win64, win32 and native linux). In this case, you could point the pkg-dir of all of these repositories to a common location. That way you *won't* have to download everything all over again for each of the repositories...
Thank you for your fast response! Thanks Markus for the clarification regarding the optional
separate pkg-directory. In fact I was indoubt after the problems I face, if I need to have separate
pkg-directory for the different versions (default, stable, release).
And I understood one error I made, I just downloaded the file an copied it into the pkg-folder,
but had not taken care to rename the file that I had downloaded from
"mexbiosig-2.0.4.src.tar.gz" --> "biosig-2.0.4.src.tar.gz"
Is there anyone who succeeded building an octave-stable during the last week?
I have now tried to compile it for more than a week, for at least 7 times.
I tried both, new clone and removal of the old make folder and update clone and clean
It always stops after or during the compilation of "libbiosig", attached you can find the log-file.
Here is what I do:
1.) clone repository or update
2.) build ./configure
3.) Clean Build Directory, if makefile exist inside the build-folder
4.) Generate Makefile inside of build directory
4.) Compile Octave-stable inside the build directory
make all 7z-dist JOBS=4 --trace --keep-going