If there's a big enough call for it, I can grab the snippet from MudBytes, plug it into a stock FUSS 1.9 and clean it up and release a fixed version of the snippet. But I'm not going to do it if just one person wants it, especially with simple errors like you have reporting.
A large chunk of those errors appears to be improper bit use. Likely trying to use Bitvector macros on an Extended bitvector field. A lot of them are too many arguments or too few arguments which means you need to check the FUSS 1.9 defines and make the calls match the prototypes for the functions being used.
house.c:1718: error: no match for 'operator&=' in '
location->room_index_data::room_flags &= -21'
house.c:1719: error: no match for 'operator&=' in '
location->room_index_data::room_flags &= -22'
house.c:1720: error: no match for 'operator&=' in '
location->room_index_data::room_flags &= -4'
house.c:1721: error: no match for 'operator&=' in '
location->room_index_data::room_flags &= -11'
These are all bitwise errors, check to see whether room_flags is defined as int or EXT_BV. If it's an int make sure the calls are using IS_SET etc. If it's EXT_BV make sure the calls use xIS_SET etc.
house.c:2106: error: invalid conversion from `const char*' to `char*'
house.c:2122: warning: too many arguments for format
house.c: In function `void save_accessories()':
house.c:2179: warning: too many arguments for format
house.c: In function `void load_accessories()':
house.c:2215: warning: too many arguments for format
house.c:2234: warning: too many arguments for format
house.c:2249: warning: too many arguments for format
These are likely bug statements with a , 0 ); on the end or something inane like that.
house.c:1946: error: `fpReserve' undeclared (first use this function)
house.c:1946: error: (Each undeclared identifier is reported only once for each
function it appears in.)
Did Smaug ever use the fpReserve deal? I don't ever remember using it. Find a function that does somthing similar to what he's attempting to do here, and emulate it.
house.c:1957: error: invalid conversion from `const char*' to `char*'
This is a string thing. You're passing something as a char * into a function expecting a const char*. Or whatever you've declared as a char* should be a const char*. GCC has decided we all need to be forced to learn proper constness. Get used to these, you'll see them a lot while installing old snippets in FUSS 1.9.
house.c:1972: error: `NULL_FILE' undeclared (first use this function)
You got me here. I've never seen this before.