Running ./configure --with-no-install ends up using (and breaking) the savefile of my vanilla installation at ~/.angband/Angband/save/. The config, lib, and var paths reported at the end of the configure script all say ~/angbandv4/lib/, but when I run the game, it loads in my savefile from ~/.angband/Angband/save/ and obviously breaks it if I save it. Not really sure how to avoid this.
breaking stable vanilla's saves
Collapse
X
-
Running ./configure --with-no-install ends up using (and breaking) the savefile of my vanilla installation at ~/.angband/Angband/save/. The config, lib, and var paths reported at the end of the configure script all say ~/angbandv4/lib/, but when I run the game, it loads in my savefile from ~/.angband/Angband/save/ and obviously breaks it if I save it. Not really sure how to avoid this.
1. Your entire configure command line
2. The final output of configure (i.e. the modules and paths stuff)
3. The git rev you're building
4. A unified diff of any local changes you've made to that revision"Been away so long I hardly knew the place, gee it's good to be back home" - The Beatles -
My entire config command line is `./configure --with-no-install --disable-sdl-mixer`.
Configure reports:
Configuration:
Install path: (not used)
binary path: ..
config path: /home/dionysian/angbandv4/lib/
lib path: /home/dionysian/angbandv4/lib/
var path: /home/dionysian/angbandv4/lib/
-- Frontends --
- Curses Yes
- GTK 2.x Disabled
- X11 Yes
- SDL Disabled
- Windows Disabled
- Test No
- Stats No
- SDL sound Disabled
I haven't made any changes.Oh, Mr. Speaker, I had underestimated the tenderness of the feelings of the members opposite.
--Barney FrankComment
-
Can we just check the entire sequence of commands?
git pull official/master (or however you update your source code)
make distclean
./autogen.sh
./configure --with-no-install --disable-sdl-mixer
make
./angband -mgcu -- -b
Is that right? And you're doing all this in ~? Or in ~/angbandv4?"Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Yep, that's right. Doing it in ~/angbandv4... the only difference is that I cd into the src directory because that's where the binary is.Oh, Mr. Speaker, I had underestimated the tenderness of the feelings of the members opposite.
--Barney FrankComment
-
If your machine is on the net, do you fancy PMing me a login to it? If you don't fancy that, login as a completely new user yourself and see if the problem still occurs. i.e. clone the repo and build v4 with a user that has never played V (and has therefore never created ~/.angband/Angband). I'm curious as to whether you are somehow building v4 with the wrong PRIVATE_USER_DIR, or whether something is going wrong at run-time."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
At the moment, I don't have anything installed for remote access. I'm also using wifi and I'm not sure how the access point is set up... So, I'll try it on a fresh user, and see what happens.Oh, Mr. Speaker, I had underestimated the tenderness of the feelings of the members opposite.
--Barney FrankComment
-
Oh, Mr. Speaker, I had underestimated the tenderness of the feelings of the members opposite.
--Barney FrankComment
-
So, I created a new user... cloned the git, compiled with --with-no-install, and it used ~/.angband/Angband
http://pastebin.com/hGgbB86V
Just for completeness, can you tell me the versions you're running of
autoconf/automake
gcc
make"Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Looks like that's exactly what I've been doing wrong. Haven't tried it yet, but I'm pretty sure that will do it. Kind of embarassing, actually.
Magnate, sorry to have wasted your time. But thanks for the help!Oh, Mr. Speaker, I had underestimated the tenderness of the feelings of the members opposite.
--Barney FrankComment
-
Good luck!Comment
Comment