Did those pull requests ever get accepted? I am trying to build it right now, also, but I get the same errors as originally mentioned.
Andrew Jackman [email protected] On Thu, Feb 11, 2016 at 1:01 PM, Gapry Un <[email protected]> wrote: > Thank you for your hints > > I don't execute `make kzm_release_defconfig` before `make`. For now, it > can compile and execute. > > Thank you very much ! > > -- Gapry > > 2016-02-12 3:14 GMT+08:00 HyperNewbie <[email protected]>: > >> That's kernel code. Looks rather easy to fix though. >> Might be that you're using a slightly different compiler version than >> what the seL4 team is testing with. >> >> - Xi >> >> On 11 February 2016 at 03:51, Gapry Un <[email protected]> wrote: >> >>> Hi Xi, >>> >>> Thank for your help. >>> >>> For now, it occurs other error messages as following so I still can not >>> compile RefOS. >>> >>> ~/refos/kernel/src/fastpath/fastpath.c:17:1: *error: conflicting types >>> for ‘fastpath_call’* >>> fastpath_call(word_t cptr, word_t msgInfo) >>> ^ >>> In file included from ~/refos/kernel/src/arch/x86/c_traps.c:15:0: >>> ~/refos/kernel/include/arch/x86/arch/fastpath/fastpath.h:184:6: note: >>> previous declaration of ‘fastpath_call’ was here >>> void fastpath_call(word_t cptr, word_t r_msgInfo) >>> ^ >>> ~/refos/kernel/src/plat/pc99/machine/intel-vtd.c: In function >>> ‘vtd_process_faults’: >>> ~/refos/kernel/src/plat/pc99/machine/intel-vtd.c:236:13: error: format >>> ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type >>> ‘uint32_t’ [-Werror=format=] >>> printf("from bus/dev/fun 0x%lx ", source_id); >>> ^ >>> cc1: all warnings being treated as errors >>> make[1]: *** [kernel_final.s] Error 1 >>> make: *** [kernel_elf] Error 2 >>> >>> Thanks for any help or suggestion, >>> >>> - Gapry >>> >>> 2016-02-11 16:12 GMT+08:00 HyperNewbie <[email protected]>: >>> >>>> Hi, >>>> >>>> With these pull requests I can compile RefOS. >>>> >>>> https://github.com/seL4/refos/pull/3 >>>> https://github.com/seL4/libsel4utils/pull/4 >>>> https://github.com/seL4/libsel4vka/pull/1 >>>> >>>> - Xi >>>> >>>> On 10 February 2016 at 19:03, Adrian Danis <[email protected]> >>>> wrote: >>>> >>>>> Hi Xi, >>>>> >>>>> AEP's got renamed to Notification's. So in this example >>>>> seL4_TCB_BindAEP got renamed to seL4_TCB_BindNotification. >>>>> >>>>> Adrian >>>>> >>>>> >>>>> On Thu 11-Feb-2016 1:08 PM, HyperNewbie wrote: >>>>> >>>>> I'm trying to update RefOS. >>>>> I see seL4_TCB_BindAEP is gone; is there anything similar to replace >>>>> this? Or do we have to use a separate thread to emulate this behaviour? >>>>> >>>>> - Xi >>>>> >>>>> On 10 February 2016 at 17:33, Kevin Elphinstone < >>>>> [email protected]> wrote: >>>>> >>>>>> RefOS was a student project that is now no longer actively >>>>>> maintained. It would make an ideal community or personal project for >>>>>> somebody to pick up, albeit one with a steep initial learning curve. >>>>>> >>>>>> >>>>>> >>>>>> Yes, you are hitting API changes. The best way forward would be to >>>>>> port RefOS to the newer API. Downgrading would be a temporary solution at >>>>>> best. >>>>>> >>>>>> >>>>>> >>>>>> - Kevin >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Assoc. Prof. Kevin Elphinstone, Trustworthy Systems >>>>>> >>>>>> *DATA61 | CSIRO* >>>>>> >>>>>> *E *[email protected] *T* +61 2 8306 0573 >>>>>> <%2B61%202%208306%200573> >>>>>> >>>>>> <http://www.data61.csiro.au/>www.data61.csiro.au >>>>>> >>>>>> >>>>>> >>>>>> *CSIRO’s Digital Productivity business unit and NICTA have joined >>>>>> forces to create digital powerhouse Data61* >>>>>> >>>>>> [image: cid:[email protected]] >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *From:* Devel [mailto: <[email protected]> >>>>>> [email protected]] *On Behalf Of *Gapry Un >>>>>> *Sent:* Sunday, 24 January 2016 9:31 PM >>>>>> *To:* [email protected] >>>>>> *Subject:* [seL4] Can not build RefOS >>>>>> >>>>>> >>>>>> >>>>>> Dear all, >>>>>> >>>>>> I follow the official step ( <https://github.com/seL4/refos-manifest> >>>>>> https://github.com/seL4/refos-manifest) to build RefOS and it occurs >>>>>> the following error message. >>>>>> >>>>>> >>>>>> >>>>>> In file included from >>>>>> /home/chi-wai/Workspaces/microkernel/RefOS/libs/librefos/src/sync.c:16:0: >>>>>> >>>>>> ~/Workspaces/RefOS/stage/arm/imx31/include/refos/refos.h:73:1: *error: >>>>>> unknown type name ‘uint32_t’* >>>>>> >>>>>> ~/Workspaces/RefOS/stage/arm/imx31/include/refos/refos.h:73:23: *error: >>>>>> unknown type name ‘uint32_t’* >>>>>> >>>>>> In file included from >>>>>> /home/chi-wai/Workspaces/microkernel/RefOS/libs/librefos/src/sync.c:18:0: >>>>>> >>>>>> ~/Workspaces/RefOS/stage/arm/imx31/include/refos-util/cspace.h:44:72: >>>>>> *error: >>>>>> unknown type name ‘uint32_t’* >>>>>> >>>>>> ~/Workspaces/RefOS/libs/librefos/src/sync.c: In function >>>>>> ‘sync_create_mutex’: >>>>>> >>>>>> ~/Workspaces/RefOS/libs/librefos/src/sync.c:49:5: *warning*: >>>>>> ‘seL4_Notify’ is deprecated (declared at >>>>>> /home/chi-wai/Workspaces/microkernel/RefOS/stage/arm/imx31/include/sel4/deprecated.h:23): >>>>>> use seL4_Signal [-Wdeprecated-declarations] >>>>>> >>>>>> ~/Workspaces/RefOS/libs/librefos/src/sync.c: In function >>>>>> ‘sync_acquire’: >>>>>> >>>>>> ~/Workspaces/RefOS/libs/librefos/src/sync.c:65:5: *error: invalid >>>>>> initializer* >>>>>> >>>>>> ~/Workspaces/RefOS/libs/librefos/src/sync.c: In function >>>>>> ‘sync_release’: >>>>>> >>>>>> ~/Workspaces/RefOS/libs/librefos/src/sync.c:74:5: *warning*: >>>>>> ‘seL4_Notify’ is deprecated (declared at >>>>>> /home/chi-wai/Workspaces/microkernel/RefOS/stage/arm/imx31/include/sel4/deprecated.h:23): >>>>>> use seL4_Signal [-Wdeprecated-declarations] >>>>>> >>>>>> >>>>>> make[1]: *** [src/sync.o] Error 1 >>>>>> >>>>>> make: *** [librefos] Error 2 >>>>>> >>>>>> >>>>>> Does RefOS use the old seL4 API ? If it is, which version I need to >>>>>> downgrade? >>>>>> >>>>>> Thanks for any help or suggestion, >>>>>> >>>>>> Gapry. >>>>>> https://gapry.wordpress.com/ >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> The information in this e-mail may be confidential and subject to >>>>>> legal professional privilege and/or copyright. National ICT Australia >>>>>> Limited accepts no liability for any damage caused by this email or its >>>>>> attachments. >>>>>> >>>>>> _______________________________________________ >>>>>> Devel mailing list >>>>>> [email protected] >>>>>> https://sel4.systems/lists/listinfo/devel >>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing >>>>> [email protected]https://sel4.systems/lists/listinfo/devel >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> [email protected] >>>>> https://sel4.systems/lists/listinfo/devel >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Devel mailing list >>>> [email protected] >>>> https://sel4.systems/lists/listinfo/devel >>>> >>>> >>> >> > > _______________________________________________ > Devel mailing list > [email protected] > https://sel4.systems/lists/listinfo/devel > >
_______________________________________________ Devel mailing list [email protected] https://sel4.systems/lists/listinfo/devel
