View Single Post
Old 04-26-2015, 10:51 AM   #7
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@abbaspour:

Yup, -static-libstdc++

But, again, that should be the default (https://github.com/koreader/koreader...file.defs#L193 && https://github.com/koreader/koreader...efile.defs#L86).
And it's explicitly always done for cre, AFAICT (https://github.com/koreader/koreader.../Makefile#L288 && https://github.com/koreader/koreader.../Makefile#L187).

So, err, again, make sure nothing in your env is polluting *FLAGS or that you're not overriding them by passing them to make on the CLI.

As you can see, the Makefiles are a house of cards tailored to the buildbot and the envs of a few developers, I've always directly messed w/ Makefiles.defs when I needed to adapt stuff to my TC, that's the safest move.

(Also, you shouldn't have had to mess with cmake's rules for cre).

Last edited by NiLuJe; 04-26-2015 at 10:59 AM.
NiLuJe is offline   Reply With Quote