Jason schrieb:

>>> So, if it doesn't see zlib.h in /usr/include/, it's going to try to
>>> install sys-libs/zlib in '/'.  If sys-libs/zlib is also an RDEPEND for
>>> your pkg, it will need to be installed to $ROOT also.  Most likely you
>>> only need the shared libraries in ROOT, eg 'libz.so*'.  You should be
>>> able to delete the includes and static libs from $ROOT (*.h,*.a,*.la)
>>> since those are only used for building.  At least, that works for me :-)
>> I will try this and clean up my system. I will see, if this works.
> 
> You should be able to use your BINDDIR trick on usr/{include,src},
> however, static libs are in the same directories as shared libs.  I
> usually do a:
> 
> find ${TGTROOT}/ -name "*.a" -print >>${file_list}
> find ${TGTROOT}/ -name "*.la" -print >>${file_list}
> 
> You could also replace '-print' with '-exec rm -f {} ';'' but I like to
> print out the list first, and hit a key to confirm.
> 

Nice tip. But could please help me out again. I need some clarification
about static libs and how they are used. AFAIK you can compile binaries
either static, which would include all needed libs into the binary, or
you compile with shared libs, which are pulled in at runtime. Could you
explain why, why there are static libs? Are they needed as build time
dependencies, when you compile static bins?

Regards,
Marc

-- 
gentoo-embedded@g.o mailing list