Hi,

On Nov 28, 2014, at 15:13, Barry Kauler <[email protected]> wrote:

> On 11/28/14, René Rebe <[email protected]> wrote:
> 
>> 
>> On Nov 27, 2014, at 2:51, Barry Kauler <[email protected]> wrote:
>> 
>>> 
>>> Hi,
>>> I reported today that Quirky 6.1.4 is "T2 compatible".
>>> 
>>> Apart from failure at stage-1 with 'man', that I fixed, compiling
>>> raced ahead and failed next at stage-5 with the base/kmod 18 package.
>>> 
>>> Configure fails, says it can't find 'zlib'.
>>> 
>>> i manually copied build/wary6....linux/lib/pkgconfig/zlib.pc to
>>> usr/lib/pkgconfig/
>>> 
>>> Kmod then built successfully.
>>> 
>>> Hmmm, so what is the best permanent fix?
>>> 
>>> A pre-configure hook in 'zlib.conf' to copy zlib.pc as I have done?
>>> 
>>> That would probably be the easiest solution, otherwise a patch would
>>> be required?
>>> 
>>> I am an end-user, and will leave it to you T2-developer guys to
>>> implement the fix.
>> 
>> 
>> Yes, the zlib package should install the zlib.pc if some packages need one.
>> 
>> Patch welcome.
>> 
> 
> Ok, patch attached.

Oh cool, proper patches, great!

> It is a preconf hook to copy zlib.pc to usr/lib/pkgconfig/
>
> I don't think it is the most elegant solution, but it works.

So we had a .pc in /lib, but pkg-config would not find it there? So we either 
should fix pkg-config to use /lib/…pc files or move the file there permanently 
(not moving sometimes) to the usr/lib location, ...

> Notice that I took "[F] CROSS DIETLIBC" out of kmod.desc.
> 
> I don't see why that was there. kmod creates a shared library,
> libkmod, that other apps link against, for example the udevd from
> eudev and systemd.

I guess at least the CROSS should there there, as this means we can cross 
compile it, … ?

-- 
 ExactCODE GmbH, Lietzenburger Str. 42, DE-10117 Berlin
 http://exactcode.com | http://exactscan.com | http://ocrkit.com | 
http://t2-project.org | http://rene.rebe.de

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to