AudaciousTUX Posted April 4, 2018 Report Share Posted April 4, 2018 (edited) faced this same issue... added using namespace icu exactly the way mapkoc said.. but now i'm facing this error (screenshot): /usr/include/c++/7.3.1/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next <stdlib.h> Edited April 4, 2018 by AudaciousTUX Quote Link to comment Share on other sites More sharing options...
mapkoc Posted April 6, 2018 Report Share Posted April 6, 2018 Hi, yeah happened to me too. Aparently is some bug on gcc's side. As a very nasty hack you can replace the #include_next for a plain #include, you have to do that like 4 times, just run make each time to get the file and line. Hopefully it will go away with next update. 1 Quote Link to comment Share on other sites More sharing options...
psypherium Posted April 21, 2018 Report Share Posted April 21, 2018 On 20/04/2018 at 9:45 PM, elexis said: @Morrd @AudaciousTUX you still had failures when compiling, right? Can you post the errors? In file included from ../../../source/lib/sysdep/stl.h:32:0, from ../../../source/lib/precompiled.h:68, from ../../../source/pch/scriptinterface/precompiled.h:19: /usr/include/c++/7.3.1/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next <stdlib.h> It is still failing :(. Quote Link to comment Share on other sites More sharing options...
elexis Posted April 22, 2018 Report Share Posted April 22, 2018 @Hannibal_Barca got it too. Quote Link to comment Share on other sites More sharing options...
Hannibal_Barca Posted April 22, 2018 Report Share Posted April 22, 2018 (edited) Guess it's irrelevant from a certain point of view. Don't think it influences anything. Also I managed to fix it by running clean-workspaces and make clean Edited April 22, 2018 by Hannibal_Barca 1 Quote Link to comment Share on other sites More sharing options...
mapkoc Posted April 23, 2018 Report Share Posted April 23, 2018 How is that error 0ad's fault? I already said, change in /usr/include/c++/7.3.1/cstdlib line 75 #include_next <stdlib.h> for #include <stdlib.h> run make again and change next error until it compiles 1 Quote Link to comment Share on other sites More sharing options...
elexis Posted April 23, 2018 Report Share Posted April 23, 2018 0AD should be compatible with most recent and the most recent c++ standards and compilers ideally. But if I recall correctly, @Hannibal_Barca could fix the issue by executing "make clean" in the gcc directory, or was it the `clean-workspaces.sh` script? Quote Link to comment Share on other sites More sharing options...
psypherium Posted April 23, 2018 Report Share Posted April 23, 2018 Hey @mapkoc, you don't understand, I know what you already said, I'm just answering a question that elexis was wondering about. Confusions are annoying but I'm not bothered. I hope you have a nice day. It's confusing because I jumped from thread to thread, but I think that these are separate issues, just closely related. I haven't tried changing the line personally, because: On 03/04/2018 at 2:35 AM, elexis said: @AudaciousTUX is also experiencing the issue, but adding the line mentioned above by itself doesn't fix it: ../../../source/i18n/L10n.cpp:517:24: error: expected type-specifier before ?Locale? Locale* locale = new Locale(Locale::createCanonical(localeCode.c_str())); I don't think I would try anyway, I don't like changing default system stuff if I can avoid it. Running clean-workspaces and make clean didn't change the outcome. It's possible my software is misconfigured in some way, and that it's not a problem with the game or icu. All of the other things I've been compiling are working fine though. 1 Quote Link to comment Share on other sites More sharing options...
mapkoc Posted April 26, 2018 Report Share Posted April 26, 2018 Maybe your svn is not updated, I think they changed those lines to icu::Locale ... Quote Link to comment Share on other sites More sharing options...
mapkoc Posted April 26, 2018 Report Share Posted April 26, 2018 and the problem with gcc was with gcc 7.3.1+20180312-2 try compiling int main(){} , I got the same errors 1 Quote Link to comment Share on other sites More sharing options...
s0600204 Posted May 18, 2018 Report Share Posted May 18, 2018 Links to a couple of tickets that have been opened on the topic of the stdlib error: https://trac.wildfiregames.com/ticket/5152 https://trac.wildfiregames.com/ticket/5157 (Just to keep things cross-referenced, and people apprised.) Quote Link to comment Share on other sites More sharing options...
s0600204 Posted June 18, 2018 Report Share Posted June 18, 2018 And a phabricator revision with a potential fix: https://code.wildfiregames.com/D1582 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.