More compile errors. Yay!

NOTICE: This forum is archived as read only.
Please use the Github Discussions at https://github.com/exult/exult/discussions
Forum rules
NOTICE: This forum is archived as read only.
Please use the Github Discussions at https://github.com/exult/exult/discussions
Locked
Wizardry Dragon
Posts: 1241
Joined: Thu May 14, 2020 1:34 pm

More compile errors. Yay!

Post by Wizardry Dragon »

I went to build from the snapshot to try and see if some of these problems are resolved in them, and I ran into more compile errors, except these aren't dependancies, these are programming related. The shell was actually nice enough to let me use 2> to capture std_err this time, so here's a pasty:

In file included from /usr/lib/gcc/i686-redhat-linux/4.5.1/../../../../include/c++/4.5.1/backward/hash_map:60:0,
from ../hash_utils.h:41,
from font.h:20,
from font.cc:23:
/usr/lib/gcc/i686-redhat-linux/4.5.1/../../../../include/c++/4.5.1/backward/backward_warning.h:28:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated.
In file included from font.cc:23:0:
font.h:110:2: error: 'hash_map' does not name a type
font.cc: In destructor 'FontManager::~FontManager()':
font.cc:873:2: error: 'fonts' was not declared in this scope
font.cc: In member function 'void FontManager::add_font(const char*, const File_spec&, int, int, int)':
font.cc:897:2: error: 'fonts' was not declared in this scope
font.cc: In member function 'void FontManager::add_font(const char*, const File_spec&, const File_spec&, int, int, int)':
font.cc:923:2: error: 'fonts' was not declared in this scope
font.cc: In member function 'void FontManager::remove_font(const char*)':
font.cc:928:5: error: 'fonts' was not declared in this scope
font.cc: In member function 'Font* FontManager::get_font(const char*)':
font.cc:936:9: error: 'fonts' was not declared in this scope
font.cc: In member function 'void FontManager::reset()':
font.cc:942:2: error: 'hash_map' was not declared in this scope
font.cc:942:16: error: expected primary-expression before 'const'
font.cc:942:16: error: expected ';' before 'const'
font.cc:947:7: error: 'i' was not declared in this scope
font.cc:947:9: error: 'fonts' was not declared in this scope
make[3]: *** [font.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

----------
Peter M Dodge
aka Wizardry Dragon
www.thefeudallands.ca
Cheers, Wizardry Dragon
Lead Designer, Ultima VII: The Feudal Lands
www.thefeudallands.ca
Dominus
Site Admin
Posts: 5656
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Dominus »

Let me get back on this tomorrow. I ran into this when I tried setting up my development environment and installing some package fixed that. Just don't know which it was.
Libpng, bison, flex, freetype all installed with devel? Maybe gcc-objectc?
--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Dominus
Site Admin
Posts: 5656
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Dominus »

Again a problem of a not very good and easy setting up a development environment on F14...
--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Malignant Manor
Site Admin
Posts: 985
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Malignant Manor »

You may have to compile with HAVE_TR1_UNORDERED_MAP if you have and configure isn't adding it.

You could install a GCC version that is lower than 4.3.
Wizardry Dragon
Posts: 1241
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Wizardry Dragon »

Yeah, and its frustrating to me because RHL was historically a pretty solid build, but it seems the more modern Fedora isn't quite as slick.

Ill make sure all those libraries are installed and that I have the devel versions. Odd that I got it to compile all and working and such and then this shows up though. Just more fun, I guess.
----------
Peter M Dodge
aka Wizardry Dragon
www.thefeudallands.ca
Cheers, Wizardry Dragon
Lead Designer, Ultima VII: The Feudal Lands
www.thefeudallands.ca
Wizardry Dragon
Posts: 1241
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Wizardry Dragon »

"You could install a GCC version that is lower than 4.3."

Its possible that could be the problem, since Fedoras packagekit recently updated GCC/et al. I'll look into it. (Though Im unsure why it would compile on older tools and not newer ones, you should think they'd want to maintain backwards compatability, when we're dealing with compiler tools)
----------
Peter M Dodge
aka Wizardry Dragon
www.thefeudallands.ca
Cheers, Wizardry Dragon
Lead Designer, Ultima VII: The Feudal Lands
www.thefeudallands.ca
Malignant Manor
Site Admin
Posts: 985
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Malignant Manor »

If you updated your compiler and didn't make clean, you really should. Then run configure before compiling again.
Wizardry Dragon
Posts: 1241
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Wizardry Dragon »

I always make clean before rebuilding when I encounter build errors.
----------
Peter M Dodge
aka Wizardry Dragon
www.thefeudallands.ca
Cheers, Wizardry Dragon
Lead Designer, Ultima VII: The Feudal Lands
www.thefeudallands.ca
Dominus
Site Admin
Posts: 5656
Joined: Thu May 14, 2020 1:34 pm

Re: More compile errors. Yay!

Post by Dominus »

the problem was fixed on my F14 side with installing either:
- libpng-devel (though I don'T think that makes a dent, Exult isn't dependent on that I thought).
-libtool devel
-gcc-objc
-gcc-objc++
-libobj
- flex
(this is from the package manager log)

OR running ./configure again :)

gcc 4.5.x was not the problem.
--
Read the documentation and the FAQ! There is no excuse for not reading them! RTFM
Read the Rules!
We do not support Piracy/Abandonware/Warez!
Locked