5:38 a.m.
Hi Allin, if you can hold off the release for one more day I could
probably test the current situation of the windows build again, starting
from a clean environment. I know the relevant updates occurred with
2019d and not so much with 2020a, but I never properly re-checked
whether we have reached a working steady state.
But of course not super important, so if you already ran your test suite
etc. I'd say just go ahead.
thanks
sven
5:30 p.m.
Am 03.03.2020 um 11:38 schrieb Sven Schreiber:
Hi Allin, if you can hold off the release for one more day I could
probably test the current situation of the windows build again, starting
from a clean environment. I know the relevant updates occurred with
2019d and not so much with 2020a, but I never properly re-checked
whether we have reached a working steady state.
Hm, I'm getting a weird error when I want to build current git (on
Windows) with addons enabled:
make -C SVAR
make[2]: Verzeichnis „/home/fantomas/src/build/addons/SVAR“ wird betreten
../../cli/gretlcli -t pkg.inp
Error reading
C:\msys64\home\fantomas\src\build\addons\SVAR\./../../gretl-git/addons/SVAR\../../../gretl-git/addons/SVAR/SVAR_boot.inp
Windows says: Das System kann die angegebene Datei nicht finden.
(= cannot find the given file)
But AFAICT the file is there alright. Any ideas?
If I build without addons, everything runs smoothly, but haven't tested
yet to actually start it up.
BTW, in section 3.6 of the windows building guide there's an example
conf.sh which doesn't match the one that's online, although it says it does.
thanks
sven
8:29 p.m.
On Tue, 3 Mar 2020, Sven Schreiber wrote:
Am 03.03.2020 um 11:38 schrieb Sven Schreiber:
> Hi Allin, if you can hold off the release for one more day I could
> probably test the current situation of the windows build again, starting
> from a clean environment. I know the relevant updates occurred with
> 2019d and not so much with 2020a, but I never properly re-checked
> whether we have reached a working steady state.
Hm, I'm getting a weird error when I want to build current git (on
Windows) with addons enabled:
make -C SVAR
make[2]: Verzeichnis „/home/fantomas/src/build/addons/SVAR“ wird betreten
../../cli/gretlcli -t pkg.inp
Error reading
C:\msys64\home\fantomas\src\build\addons\SVAR\./../../gretl-git/addons/SVAR\../../../gretl-git/addons/SVAR/SVAR_boot.inp
Windows says: Das System kann die angegebene Datei nicht finden.
(= cannot find the given file)
But AFAICT the file is there alright. Any ideas?
Apart from the path being a horrible mash-up? I'll try taking a look
at that tomorrow.
If I build without addons, everything runs smoothly, but haven't
tested
yet to actually start it up.
BTW, in section 3.6 of the windows building guide there's an example
conf.sh which doesn't match the one that's online, although it says it does.
OK, I'll take a look at that too.
Allin
3:07 a.m.
Am 04.03.2020 um 02:29 schrieb Allin Cottrell:
On Tue, 3 Mar 2020, Sven Schreiber wrote:
...
\src\build\addons\SVAR\./../../gretl-git/addons/SVAR\../../../gretl-git/addons/SVAR/SVAR_boot.inp
> Windows says: Das System kann die angegebene Datei nicht finden.
>
> (= cannot find the given file)
> But AFAICT the file is there alright. Any ideas?
Apart from the path being a horrible mash-up?
Well, I don't really understand this first part with the single dot
myself: ___addons\SVAR\./../../gretl___
while the second part should be OK: ___addons/SVAR\../../../gretl__
But the thing is that there are many other files in addons/SVAR, not
just SVAR_boot.inp, and it seems to work with (some of) them. Plus other
addons have the same file layout and I've verified that some of them got
built alright. That's why I'm puzzled.
cheers
sven
3:55 p.m.
On Wed, 4 Mar 2020, Sven Schreiber wrote:
Am 04.03.2020 um 02:29 schrieb Allin Cottrell:
> On Tue, 3 Mar 2020, Sven Schreiber wrote:
...
\src\build\addons\SVAR\./../../gretl-git/addons/SVAR\../../../gretl-git/addons/SVAR/SVAR_boot.inp
>> Windows says: Das System kann die angegebene Datei nicht finden.
>>
>> (= cannot find the given file)
>> But AFAICT the file is there alright. Any ideas?
>
> Apart from the path being a horrible mash-up?
Well, I don't really understand this first part with the single dot
myself: ___addons\SVAR\./../../gretl___
while the second part should be OK: ___addons/SVAR\../../../gretl__
But the thing is that there are many other files in addons/SVAR, not
just SVAR_boot.inp, and it seems to work with (some of) them. Plus other
addons have the same file layout and I've verified that some of them got
built alright. That's why I'm puzzled.
Fair enough. I tried today on Windows 10 and (somehow or other) the
SVAR addon built OK. But "extra" failed: after thinking about it I
see why, and maybe the issue you saw with SVAR is similar.
For building gretl outside of the source tree (recommended) we've
been symlinking certain files we need from the source tree into the
out-of-source directory (for example, the ".spec" files for addons).
This works fine on *nix, but MS Windows doesn't do symlinks. So when
MSYS encounters an instruction to create a symlink, it just copies
the file in question to the "make a link here" location.
Perhaps you can see what's coming: a proper symlink will always
point to the current file in the source tree, but a physical copy,
as on Windows, will go stale whenever the source file is updated!
What's needed, then, to support building on Windows, is a wholesale
conversion in the addons Makefiles from "If the file doesn't exist
at the required location, symlink it" to "if the file doesn't exist
OR is older than the file it's supposed to be a link to, symlink
it". This is a PITA but I've started work on it.
Allin
1719
days inactive
1720
days old
4 comments
2 participants
participants (2)
-
Allin Cottrell -
Sven Schreiber