3.5-nightly-compile/link error. (Linux)

[Spacebux]

Yeah, I think that patching that modules list by just inserting a dummy variable wasn't the right idea. Sure it makes the compile error go away, but it doesn't fix the underlying problem that that error was telling you about. You really need to have at least one of USE_X11, USE_SDL, or USE_GCU defined or else the game won't know how to run.

Hmmm... leaving it blank is optimal, but the linker doesn't want to fill it with the appropriate value.

I thought the autogen.sh script specified which module to set.

Time to do more research.

[Blue Baron]

Hmmm... leaving it blank is optimal, but the linker doesn't want to fill it with the appropriate value.

I thought the autogen.sh script specified which module to set.

Time to do more research.

Did you run configure after autogen and before make? something like:
./configure --enable-sdl --with-no-install

[Spacebux]

Did you run configure after autogen and before make? something like:
./configure --enable-sdl --with-no-install

Not with an --enable-xxx flag. Which would be the appropriate flag for Linux, X11? I'm running the Gnome desktop, so I'm quite sure X11 will work.

........suppose I could give it a whirl and see.

[Spacebux]

no X11 libraries installed...

[AnonymousHero]

[root@mb1 angband-dev]# make

I'm afraid I don't have any help for your issue, but the command snippet you pasted seems to indicate that you're logging in and compiling as the "root" user. I just wanted to say: please don't do that -- it's incredibly unsafe and a single bad makefile can compromise your machine or delete all your files.

Btw, love the machine name .

[Spacebux]

Resolved. Thank you.

I'm afraid I don't have any help for your issue, but the command snippet you pasted seems to indicate that you're logging in and compiling as the "root" user. I just wanted to say: please don't do that -- it's incredibly unsafe and a single bad makefile can compromise your machine or delete all your files.

Btw, love the machine name .

Wasn't sure if my being a different user I had access issues to certain libraries or not, so I wanted to compile as 'root'. Yeah, beware the Sys-Admin with a screw driver.

ok - I installed X11 libraries and ncurses just to be safe. Not sure if it was absolutely necessary, but I did. For those that may come after me, compiling/installing in Linux:

yum install ncurses-devel
yum install libXt-devel

(If you are a Debian user, you'll use replace "yum" with "apt-get" above.

Then run ./configure --enable-x11 and angband will compile without that ISO C error & warning. And, best of all, no seg fault when you try to run it.

'Bux.
- thanks for the compliment on the machine name.