5th September Nightly builds available

[Magnate]

could it be possible that he reloaded on a level with an active angel in LoS. That would probably create some problems, right?

It shouldn't, as the code would just look up the r_idx of the monster in LOS and return the details of the maiar which has replaced the original angel.

I think d_m is right and the lib/ path is ending up with an old monster.txt from before the change.

@Napsterbater: you're building this yourself, right? Since the nightlies are only published as pre-built for Windows and OSX, you must be compiling from source on Ubuntu. So how are you compiling it? Presumably something like

./autogen.sh
./configure --with-some-options
make
make install

?

I think the problem is quite likely to be the interaction of your configure options with your previous install. It's also possible that you fell foul of a bug that I committed which broke the buildsystem on Linux (especially if you use --enable-setgid).

[Napsterbater]

It shouldn't, as the code would just look up the r_idx of the monster in LOS and return the details of the maiar which has replaced the original angel.

I think d_m is right and the lib/ path is ending up with an old monster.txt from before the change.

@Napsterbater: you're building this yourself, right? Since the nightlies are only published as pre-built for Windows and OSX, you must be compiling from source on Ubuntu. So how are you compiling it? Presumably something like

./autogen.sh
./configure --with-some-options
make
make install

?

I think the problem is quite likely to be the interaction of your configure options with your previous install. It's also possible that you fell foul of a bug that I committed which broke the buildsystem on Linux (especially if you use --enable-setgid).

Yeah, that's how I do it. I don't use --enable-setgid. I think I even tried deleting the entire build folder and re-cloning from git, and it didn't work.

[Magnate]

Yeah, that's how I do it. I don't use --enable-setgid. I think I even tried deleting the entire build folder and re-cloning from git, and it didn't work.

Ok, you didn't say what configure options you use, but the ultimate test is to configure --with-no-install and just type src/angband after make. That ought to work. Having said that, the build system has been partially fixed (I suspect not all the --with-foopath options will work properly, but a normal prefix ought to install ok).

[Napsterbater]

Sorry, I didn't put it down, because I rarely have to configure. I usually just git pull, then make clean and make. Whatever it is, it's just graphics options. Probably just --enable-sdl

So I can git pull and try again? Are the fixes in the main tree?

[Magnate]

Sorry, I didn't put it down, because I rarely have to configure. I usually just git pull, then make clean and make. Whatever it is, it's just graphics options. Probably just --enable-sdl

So I can git pull and try again? Are the fixes in the main tree?

Yes, the fixes are now in the main tree. But you should try to get into the habit of doing make distclean; ./autogen.sh; ./configure --with-your-options; make. It adds about 90 seconds to your build but guarantees that you will have no more problems than those actually present upstream ...