Source MUD
Source MUDNewsWikiBugsForumFilesSource LoginRegister
HomeBugsBug #0011
Compile of 0.26.20090405 fails with "Error 1"
Bug #0011
Reported by James Penketh
May 18th, 2009 at 7:10pm UTC
Version ... 0.26.20090405
$ make
Generating src/generated/commands.cc
Pre-compiling include/common.h
Compiling src/common/base64.cc
Compiling src/common/error.cc
Compiling src/common/fdprintf.cc
Compiling src/common/file.cc
Compiling src/common/imanager.cc
Compiling src/common/log.cc
Compiling src/common/md5.cc
Compiling src/common/rand.cc
Compiling src/common/strbuf.cc
Compiling src/common/strings.cc
Compiling src/common/time.cc
Compiling src/generated/commands.cc
Compiling src/lua/core.cc
In file included from src/lua/core.cc:10:
include/lua/core.h:11:20: error: calling fdopen: Bad file descriptor
make: *** [.build/src/lua/core.o] Error 1

Comment from Elanthis
May 19th, 2009 at 10:45am
Which version of GCC are you using?

Comment from James Penketh
May 19th, 2009 at 11:12am
gcc version 4.3.3 (Gentoo 4.3.3-r2 p1.1, pie-10.1.5)

It also breaks with 4.1.2, but a lot later in the build process. (http://furryhelix.webhop.org/sites/default/files/make.log if you're interested.)

Comment from Elanthis
May 19th, 2009 at 12:27pm
Looks like it could be an issue with pre-compiled headers.

I pushed a change to git head that allows you to pass --disable-pch to ./configure. Clone the git tree and try running:

./bootstrap && ./configure --disable-pch && make clean all

Let me know if that works or not.

Comment from James Penketh
May 19th, 2009 at 12:38pm
That has indeed fixed it on both 4.3.3 and 4.1.2. Thank-you very much. :)

Comment from Elanthis
May 19th, 2009 at 1:38pm
Not a problem. I do wish I knew how to make PCH just work for your setup though. :) It is working correctly for me on both GCC 4.2 on Ubuntu and 4.4 on Fedora, so I wonder if perhaps it's a Gentoo thing? Only thing a quick Google check found was that it may be a kernel issue conflicting with PCH, but that was with much older versions of the kernel and GCC.

Either way, I don't think there's much I can do to get PCH to work for you, so closing this out. Thanks for the report, I'm sure the --disable-pch will come in handy for others in the future. :)

Additional Comments:
or Login
Exception - Source MUD
Source MUD
Source MUDNewsWikiBugsForumFilesSource LoginRegister

Exception

_execute: [Error message: Unable to execute statement] [Last executed query: UPDATE session SET session_stamp=NOW(),session_vars=? WHERE session_id=?] [Native code: 0]