Tiny Core Linux

Tiny Core Extensions => TCE Q&A Forum => Topic started by: spillz on July 13, 2009, 11:47:59 PM

Title: Building Code::Blocks -- RTTI required + other issues
Post by: spillz on July 13, 2009, 11:47:59 PM

I'm trying to compile Code::Blocks IDE but running into a few issues.

Show stopper:

* Seems that the default setting of gcc in tinycore is -fno-rtti. Is it possible to switch rtti back on? If so, how?

Resolved issues (potential bugs in tc/tces?)

* I had to touch all files in the source directory as make complained that Makefile.am was dated in the future

* freetype2.pc installed to wrong directory (/usr instead of /usr/local) had to export PKG_CONFIG_PATH=/usr/lib/pkgconfig

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: Juanito on July 13, 2009, 11:54:36 PM

Quote from: spillz on July 13, 2009, 11:47:59 PM

* I had to touch all files in the source directory as make complained that Makefile.am was dated in the future

I've seen some errors of this nature - I was lazily using emelfm and busybox tar to untar source packages (which works most of the time, but messes up dates/times), but now only use the full tar to do this

Quote

* freetype2.pc installed to wrong directory (/usr instead of /usr/local) had to export PKG_CONFIG_PATH=/usr/lib/pkgconfig

Since the base-devs are in /usr, it would probably be better to use "PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/local/lib/pkgconfig", no?

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: spillz on July 14, 2009, 12:08:44 AM

Quote from: Juanito on July 13, 2009, 11:54:36 PM

Quote

* freetype2.pc installed to wrong directory (/usr instead of /usr/local) had to export PKG_CONFIG_PATH=/usr/lib/pkgconfig

Since the base-devs are in /usr, it would probably be better to use "PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/local/lib/pkgconfig", no?

yes, but /usr/local/lib/pkgconfig seemed to be implicit.

any idea on the -fno-rtti?

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: Juanito on July 14, 2009, 12:15:32 AM

The "standard" tinycore flags are:

CFLAGS="-march=i486 -mtune=i686 -Os -pipe"
CXXFLAGS="-march=i486 -mtune=i686 -Os -pipe -fno-exceptions -fno-rtti"
export

but, as I recall, gcc would not compile with "-fno-rtti" so I omitted this.

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: spillz on July 14, 2009, 07:22:10 AM

Quote from: Juanito on July 14, 2009, 12:15:32 AM

The "standard" tinycore flags are:

CFLAGS="-march=i486 -mtune=i686 -Os -pipe"
CXXFLAGS="-march=i486 -mtune=i686 -Os -pipe -fno-exceptions -fno-rtti"
export

but, as I recall, gcc would not compile with "-fno-rtti" so I omitted this.

I did the same (but without -march and -mtune), but I get error message along the lines of "cannot use type information with compiler option -fno-rtti" on the first templated class declaration in Code::Blocks. i.e. -fno-rtti is being set anyway (I can tell because the -fno-rtti appears in the gcc command line).

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: robc on July 14, 2009, 12:39:58 PM

have you tried using -frtti instead?

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: spillz on July 14, 2009, 02:42:37 PM

Quote from: robc on July 14, 2009, 12:39:58 PM

have you tried using -frtti instead?

well that would be the easy way  :P. almost have it built now (hopefully just missing one or two minor build tools)

nonetheless I'd still like to understand where "-fno-rtti" is getting set in tc.

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: spillz on July 14, 2009, 03:57:15 PM

aargh... seems wxWidgets wasn't built with rtti. Now I have to rebuild it too. (Or am I just cooked, as potentially this goes all the way up the dependency chain?)

Title: Re: Building Code::Blocks -- RTTI required + other issues
Post by: spillz on July 15, 2009, 12:30:05 AM

Thankfully the wxWidgets rebuild was enough. I've made nice tces out my rtti-enabled wx build and code::blocks (4mb and 11mb respectively). I haven't tested thoroughly but they seem to work.

Question is: should I send them for upload into the repos?