> If you are referring to C:\Users\username\ then there are no such folder or files. > I've created the folder but still no luck.
No, not your Windows profile directory. You need to work out where the MSYS2 environment has put your MinGW home directory that appears as /home/username in the MSYS2 environment and check permissions on that.
Sorry to trouble you further, but I need some more help with this. I've being compiling MAME for many years, but I'm not a technical IT person and not had this problem before.
Everything is installed at c:\msys64.
Having searched my entire c: drive, there's a gitconfig file under C:\msys64\home\THENGAMES. There are no other directories under C:\msys64\home
I'd say delete evything and start over with downloading the entire package again from MAMEDev Development tools. I put that in it's own msys64 directory with all my MAME stuff. Everyhting from the package is found inside the msys64 directory as it's root. Run all the commands, done. Easy peasy.
> > If you are referring to C:\Users\username\ then there are no such folder or files. > > I've created the folder but still no luck. > > No, not your Windows profile directory. You need to work out where the MSYS2 > environment has put your MinGW home directory that appears as /home/username in the > MSYS2 environment and check permissions on that.
A directory C:\msys64\home\THENGAMES is created, but a directory C:\msys64\home\%username% is not. If I copy the THENGAMES folder, then rename it to my username, I am able to continue with the step "git config --global core.autocrlf true"
But... updating the tools is also broken, due to MSYS2 issue reported here for 6/29:
After the initial learning curve of using some tools I hadn't used before, I successfully finished compiling a version last night.
Side question:
When using command from the easy package to download source... "git clone https://github.com/mamedev/mame.git" ... source is downloaded to C:\msys64\src\mame
When using same command from the "hard[?]" version of tools... source is downloaded to C:\msys64\home\%username%\mame.
Which is correct?
(Might be time to update the "easy package tools?").
RELAX and just have fun. Remember, it's all about the games.
You know the instructions always said if you are installing somewhere else other that default you have to run autorebase.bat. I think you actually need to run the autorebase.bat no matter where you set it up. I set up mine in D:\MAME\msys64. When I download the source it goes to D:\MAME\msys64\src.
> You know the instructions always said if you are installing somewhere else other that > default you have to run autorebase.bat. I think you actually need to run the > autorebase.bat no matter where you set it up. I set up mine in D:\MAME\msys64. When I > download the source it goes to D:\MAME\msys64\src.
Yup... tried all that... I did a fresh install three different ways... I couldn't get past the step of updating the tools... known issue here:
I followed the steps in the last post in that thread, and still got the unknown trust error (though I did not follow the last step of trying to ignore the signatures... I didn't want to go that route).
I ended up being okay, following the other directions... , plus I learned a bit more in the process, so... bonus?
I just wish I had a better PC. Last time I "had" to compile something was more than a few years ago... I remember it taking less than 30min. I've been laptop only for a few years now (work laptop doubles as my home laptop... separate hard drives), and I just got it replaced in January. 8 cores, but speed when all eight are running is 1.90, I think... took just over two hours to complete.
RELAX and just have fun. Remember, it's all about the games.
> Yup... tried all that... I did a fresh install three different ways... I couldn't get > past the step of updating the tools... known issue here:
I had similar trouble. Long story short, I unpacked the prepackaged installer to C: instead of to my removeable drive and skipped updating the build tools. That avoided the errors I kept running into. git clone and make completed without any trouble. Make took a really long time though and my executable wound up being twice as large as the official one. I didn't add any switches to the commandline.
Frank's walkthrough was very helpful. I hope he posts more hand-holding videos.
--
A story of one man and his obsession with the female anatomy.
Previous 
Index 
Next 
Threaded 
gitconfig?
Reply
[Re: 
