Hi,
yes, portmap failed here, too - maybe due to recent glibc update or something.
I fixed it by updating it:
Committed revision 43204.
René
On Sep 11, 2014, at 2:10, scsijon <[email protected]> wrote:
>
> This leaves just the 5-portmap and 5-aufs packages with problems
>
> Haven't looked at Portmap yet. I will have a quick look later today in case
> it's something simple to fix.
>
> The aufs problem is a version problem as it needs aufs3 for kernel 3.16.x,
> aufs2 is out of date for kernel 3.9 +.
> I shall have a go at working this out using packages/filesystems/aufs or
> aufs2 as a template to create aufs3-util and aufs3. It should then only need
> the list ammending, or do we also ammend aufs which has both combined (maybe
> later) itself?
>
> ----------------------------------------------------
>
> The stage 2 building problem has been sorted.
>
> It has it's own thread if you want to follow.
>
> ------------------------------------------------------------
> Thanks
>
> On 09/06/2014 10:15 PM, ExactCODE wrote:
>> Hi,
>>
>> I added libel to the 00-minimal list for wpa_supplicant:
>>
>> Committed revision 43169.
>>
>> René
>>
>> On Aug 22, 2014, at 12:33, scsijon <[email protected]> wrote:
>>
>>> try2, sorry
>>> ----------------
>>>
>>> I think i may have ?sorted out the wpa_supplicant problem.
>>>
>>> It has a patch that wants libnl-3.0 in the packages list directory, and
>>> as I read the error file, the build is failing because the package is
>>> not installed.
>>>
>>> 00-minimal doesn't have libnl set to be included to start with.
>>>
>>> libnl in the mirror and packages list is version 3.2.24.
>>>
>>> Does this mean that I should remove the patch or add libnl to 00-minimal?
>>>
>>> ----------
>>>
>>> For portmap, it seems to want ld -lwrap, but I can't find any -lwrap in
>>> any of the ld's I have access too, so i'm not sure where to go from here.
>>>
>>> -----------
>>>
>>> For aufs and aufs3, I need guidance please, can I use existing patches
>>> or what, or do I build without patches?
>>>
>>> thanks
>>>
>>> On 08/17/2014 02:37 PM, scsijon wrote:
>>>> so there are 4 problem packages left for a 00-minimal.
>>>>
>>>> Also as i said in my last email, I wonder if 1-man is required as it
>>>> builds ok at 5-man?
>>>>
>>>> However problems still exist with 5-aufs, 5-portmap and
>>>> 5-wpa_supplicant, I have attached their error files.
>>>>
>>>> As you said last time for aufs, I also wonder if it's time to move to
>>>> aufs3 as aufs2 has no support for 3.16 and later. It lost it for 3.x
>>>> kernels back in oct 2012 according to the coders website.
>>>>
>>>> Is it worth me manually building these failed packages and building a T2
>>>> v9 from that or is it best to await fixes?
>>>>
>>>> My next step would be the xorg build, from that it becomes puppy
>>>> integration.
>>>>
>>>> As I said when I first started worrying you, I really want to build the
>>>> puppy packages that I will use, and make available, from a working T2
>>>> V9.0 Trunk system, so I then know that any problems that appear are most
>>>> likely puppy related and not T2 related.
>>>>
>>>> I also noticed a number of packages are giving warnings about 'the use
>>>> of custmain is depreciated, please use hooks instead'. I remember that
>>>> linux-header was the first it appeared in during building but there were
>>>> quite a few others. Not sure if your interested.
>>>>
>>>> regards
>>>>
>>>> On 08/15/2014 06:35 PM, ExactCODE wrote:
>>>>> Hi,
>>>>>
>>>>> as per earlier email I personally fixed some of those shared file
>>>>> (coreutils, mktemp, …) some days ago.
>>>>>
>>>>> 1-man was trying to install files outside of the new system root.
>>>>>
>>>>> aufs may need an update
>>>>>
>>>>> On Aug 15, 2014, at 1:33, scsijon <[email protected]> wrote:
>>>>>
>>>>>> I should have waited a few more minutes.....
>>>>>>
>>>>>> The minimal build has completed building it's packages with these
>>>>>> final package errors, so it's not useable yet!
>>>>>>
>>>>>> aufs
>>>>>> coreutils
>>>>>> mktemp
>>>>>> portmap
>>>>>> procps
>>>>>> shadow
>>>>>> wpa_supplicant
>>>>>>
>>>>>> Interesting that man was ok under 5-man
>>>>>>
>>>>>> All error logs from packages of this build are attached. I haven't
>>>>>> added the overall build logs due to size. I will if you need it, but
>>>>>> i'd like to fix a few first and rerun the build. And yes I shall have
>>>>>> a look when free later today for obvious problems I can fix.
>>>>>>
>>>>>> regards
>>>>>> scsijon
>>>>>>
>>>>>> -------- Original Message --------
>>>>>> Subject: Re: [t2] T2 problems - part d) building
>>>>>> Date: Fri, 15 Aug 2014 08:49:09 +1000
>>>>>> From: scsijon <[email protected]>
>>>>>> To: [email protected]
>>>>>>
>>>>>> Update: I eventually got T2 V8 minimal loaded on one of my testing
>>>>>> computers by blowing everything away and starting it as a raw
>>>>>> (unpartitioned or formatted) system but even that wouldn't build
>>>>>> anything so I went another path by using another puppy called slacko and
>>>>>> are using it as a base to build from.
>>>>>>
>>>>>> I am currently building a minimal and when it's working I intend to use
>>>>>> that for further building, but I need to get there first.
>>>>>>
>>>>>> I have set the following config changes for now as it at least runs and
>>>>>> should give useable logs for fixing.
>>>>>>
>>>>>> Generic
>>>>>> minimal
>>>>>> pkgdist
>>>>>>
>>>>>> /root/t290minpkg
>>>>>> -
>>>>>> -
>>>>>>
>>>>>> -Build system configuration
>>>>>> Continue on package error after stage 0 (toolchain)
>>>>>> Retry building broken packages
>>>>>> Do not try building packages if deps failed
>>>>>> Keep src dirs on build errors
>>>>>> Create debug information (xtrace) for builds
>>>>>>
>>>>>>
>>>>>>
>>>>>> Problems to date:
>>>>>>
>>>>>> 1- Shouldn't the Kernel-Headers package use the same version of the
>>>>>> kernel as the actual Kernel Package? It is in puppy and in fact they are
>>>>>> both created, plus a kernel-?.src package also needed with the header
>>>>>> package for additional driver package building, at the same time.
>>>>>>
>>>>>> 2- Building Generic>Toolchain
>>>>>> The package Man fails to build until 5-man.log. I have attached the
>>>>>> errorfile 1-man.err for your perusal. This is from a generic, toolchain
>>>>>> only build.
>>>>>>
>>>>>> 3- Building Generic>minimal
>>>>>> I shall send you the results from the minimal build when it's
>>>>>> completed
>>>>>> however I already have error logs showing for 1-man, 1-mktemp, 1-procps,
>>>>>> 3-coreutils, 3-mktemp and 3-procps, so there are serious problems
>>>>>> here also.
>>>>>>
>>>>>> regards
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> <1-man.err><1-mktemp.err><1-procps.err><3-coreutils.err><3-mktemp.err><5-aufs.err><3-procps.err><5-coreutils.err><5-mktemp.err><5-portmap.err><5-shadow.err><5-wpa_supplicant.err>-----------------------------------------------------------
>>>>>>
>>>>>> If you wish to unsubscribe from this mailing, send mail to
>>>>>> [email protected] with a subject of: unsubscribe t2
>>>>>
>>>
>>>
>>>
>>
--
ExactCODE GmbH, Jaegerstr. 67, 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
