Tiny Core Linux

Tiny Core Extensions => TCE Q&A Forum => Topic started by: jpeters on May 22, 2009, 04:09:12 AM

Title: compiling
Post by: jpeters on May 22, 2009, 04:09:12 AM

Seems like sometimes there's an endless chain of pkgconfig requests when compiling. If I build libgnome_dev, then it wants libbonobo_dev, which needs libORbit_dev, etc, etc.  I don't know if there's an easier way when the libs already exist.  

Title: Re: compiling
Post by: Juanito on May 22, 2009, 04:27:52 AM

I guess it depends on what you're trying to compile - several bloat-o-gnome applications seem to require many, many deps, gnu cash being a good example. Xorg does quite well in this respect too...

Title: Re: compiling
Post by: jpeters on May 22, 2009, 04:40:52 AM

I was hoping I could just do some CFLAG  to bypass the whole pkgconfig thing......but maybe not.

Title: Re: compiling
Post by: curaga on May 22, 2009, 08:29:13 AM

Welcome to the concept of Dependency Hell ;)

Trying to build anything that depends on 30+ Gnome or KDE packages is rather bad. Because they in order depend on more G/K packages, and so on.

Disabling pkg-config wouldn't help much, then your compile would only error out at the linking phase when it can't find those libs.

Title: Re: compiling
Post by: jpeters on May 22, 2009, 02:04:16 PM

I could find and compile source for ORBit.pc  (for gnome-1 apps) , but finding source for ORBit-2.0 is another matter.  The only sources I found were rpm that didn't convert with rpm2targz:

Code: [Select]

tc@box:~/Desktop$ rpm2targz ORBit2-2.14.9-1mdv2008.0.src.rpm
ERROR:  rpm2cpio failed.  (maybe ORBit2-2.14.9-1mdv2008.0.src.rpm is not an RPM?

Edit: I see there's a package at BLFS  (which requires libIDL-2.0  :)  )

Title: Re: compiling
Post by: jpeters on May 22, 2009, 09:09:27 PM

Anybody else come across a similar error using bison?   The configuration seemed to go well, but when trying to "make" :

Code: [Select]

...
config.status: creating libIDL.spec
config.status: creating libIDL-2.0.pc
config.status: creating libIDL-2.0-uninstalled.pc
config.status: executing depfiles commands

libIDL 0.8.8 configuration complete

  C Preprocessor: "gcc -E"
  Standard input supported.

tc@box:~/libIDL-0.8.8$ make
bison -y -d -v 2>/dev/null ./parser.y
make: *** [stamp-parser] Error 1
tc@box:~/libIDL-0.8.8$


Title: Re: compiling
Post by: Jason W on May 22, 2009, 09:12:07 PM

Also the latest Orbit if you haven't found it:

http://ftp.gnome.org/pub/GNOME/sources/ORBit2/2.14/ORBit2-2.14.17.tar.bz2

Title: Re: compiling
Post by: jpeters on May 22, 2009, 11:05:43 PM

..have to be able to compile libIDL-2.0 first....Any idea re the parser error? 

Title: Re: compiling
Post by: Jason W on May 22, 2009, 11:15:03 PM

I've read it is a bison bug, but I haven't looked too far into it:

http://www.mail-archive.com/bug-bison@gnu.org/msg01226.html

Title: Re: compiling
Post by: jpeters on May 22, 2009, 11:47:52 PM

I built my own bison extension, and that solved it.  I had to build M4 first...I used the source from LFS...

Title: Re: compiling
Post by: Juanito on May 23, 2009, 01:22:07 AM

From Jason's link, I can see there might be a problem with the bison (2.4.1) extension, but didn't the m4 extension work either?

Title: Re: compiling
Post by: jpeters on May 23, 2009, 03:13:04 AM

I didn't know what was causing the error, so I just built both extensions.   (M4 was needed to build it).

Title: Re: compiling
Post by: curaga on May 23, 2009, 07:33:12 AM

There's libIDL.tcel already? (and it's a newer version, 0.8.11)

Title: Re: compiling
Post by: jpeters on May 23, 2009, 12:39:43 PM

Quote from: curaga on May 23, 2009, 07:33:12 AM

There's libIDL.tcel already? (and it's a newer version, 0.8.11)

I didn't see it because there's apparently no tcz version.