Hi, I just filled a bug for the stack installer : https://github.com/commercialhaskell/stack/issues/5626
I was wondering, how is the installer built ? I see a build-stack-installer.hsfile which uses a nsis package to generate a nsis installer, but does it happen on a windows machine or a linux machine ? These days the recommended way of making windows installer is by making msi file for instance with WiX toolset, which is an xml based format. But this means that the installer can only be built on a Windows machine. So that's why I'm asking the question, are installer put on the release page generated on a Windows machine or VM ?
here is the log : build.log
I don't understand what ghc is trying to do at the beginning, addLibrarySearchPath fails but it doesn't tell what is the path
There is however another issue, the first time you install stack on Windows 11, shis complaining about a base address not being the same as some reference. It suffers from the same problem as the installer, and if I disable ASRL it works.
I can get stack executable installed via setup but the sh issue is more annoying to me, and I don't know how to fix it. I suspect it's some binary package which is trailing behing. Do you know where these binaries are compiled and uploaded and who I can send a bug report to ?
Hi, I just filled a bug for the stack installer : https://github.com/commercialhaskell/stack/issues/5626
I was wondering, how is the installer built ? I see a
build-stack-installer.hsfile which uses a nsis package to generate a nsis installer, but does it happen on a windows machine or a linux machine ? These days the recommended way of making windows installer is by making msi file for instance with WiX toolset, which is an xml based format. But this means that the installer can only be built on a Windows machine. So that's why I'm asking the question, are installer put on the release page generated on a Windows machine or VM ?By the way how can I build stack on windows ? I'm trying to launch
stack .\etc\scripts\release.hs buildbut it failshere is the log :
build.log
I don't understand what ghc is trying to do at the beginning, addLibrarySearchPath fails but it doesn't tell what is the path
I found out what's happening, nevermind !
Would it be worth sharing what you did to solve the issue?
Maybe it could help the next person running into the same situation...
I had to install nsis on my machine so that the executable is discoverd
There is however another issue, the first time you install stack on Windows 11,
shis complaining about a base address not being the same as some reference. It suffers from the same problem as the installer, and if I disable ASRL it works.I can get stack executable installed via setup but the
shissue is more annoying to me, and I don't know how to fix it. I suspect it's some binary package which is trailing behing. Do you know where these binaries are compiled and uploaded and who I can send a bug report to ?