On May 27, 2023 8:42:27 AM GMT+02:00, "Flávio Cruz"
wrote:
>On Fri, May 26, 2023 at 9:42 AM Guy-Fleury Iteriteka
>wrote:
>
>> On May 26, 2023 2:00:00 PM GMT+02:00, "Flávio Cruz"
>> wrote:
>> >Hi Sergey
>> >
>> >On Fri, May 19, 2023 at 4:02 AM Sergey Bugaev wrote:
>> >
>> >> Hi,
>> >>
>> >> On
On Fri, May 26, 2023 at 9:42 AM Guy-Fleury Iteriteka
wrote:
> On May 26, 2023 2:00:00 PM GMT+02:00, "Flávio Cruz"
> wrote:
> >Hi Sergey
> >
> >On Fri, May 19, 2023 at 4:02 AM Sergey Bugaev wrote:
> >
> >> Hi,
> >>
> >> On Fri, May 19, 2023 at 9:43 AM Flávio Cruz
> wrote:
> >> > I have made cha
On Fri, May 26, 2023 at 10:43 AM Sergey Bugaev wrote:
> On Fri, May 26, 2023 at 3:00 PM Flávio Cruz wrote:
> > Hi Sergey
>
> Hi,
>
> > Thanks for the instructions. I was able to make it work and pushed my
> changes to Github.
>
> That's awesome news -- thank you!
>
> (Well, I figured as much fro
On Fri, May 26, 2023 at 3:00 PM Flávio Cruz wrote:
> Hi Sergey
Hi,
> Thanks for the instructions. I was able to make it work and pushed my changes
> to Github.
That's awesome news -- thank you!
(Well, I figured as much from looking at the GitHub, but it's nice to
get a confirmation.)
What we
On May 26, 2023 2:00:00 PM GMT+02:00, "Flávio Cruz"
wrote:
>Hi Sergey
>
>On Fri, May 19, 2023 at 4:02 AM Sergey Bugaev wrote:
>
>> Hi,
>>
>> On Fri, May 19, 2023 at 9:43 AM Flávio Cruz wrote:
>> > I have made changes so that it does daily builds and I'm able to boot
>> small programs. However,
Hi Sergey
On Fri, May 19, 2023 at 4:02 AM Sergey Bugaev wrote:
> Hi,
>
> On Fri, May 19, 2023 at 9:43 AM Flávio Cruz wrote:
> > I have made changes so that it does daily builds and I'm able to boot
> small programs. However, I haven't had the time to boot programs built
> against Glibc. How do
Hi,
On Fri, May 19, 2023 at 9:43 AM Flávio Cruz wrote:
> I have made changes so that it does daily builds and I'm able to boot small
> programs. However, I haven't had the time to boot programs built against
> Glibc. How do you package and boot the static binaries using a ramdisk? I've
> been
Hi Sergey
Sorry for the late reply, I have been busy with work and also traveling.
On Tue, May 16, 2023 at 8:41 AM Sergey Bugaev wrote:
> On Tue, May 16, 2023 at 6:02 PM Flávio Cruz wrote:
> > Yes, I meant this when I said "generate code to call the server reply
> routine
> > in case of errors
On Tue, May 16, 2023 at 6:02 PM Flávio Cruz wrote:
> Yes, I meant this when I said "generate code to call the server reply routine
> in case of errors".
Ah, I see.
> Take the example of the term translator, it forces TypeCheck to be 0 so that
> it can still receive replies in the error case (oth
On Mon, May 15, 2023 at 2:19 AM Sergey Bugaev wrote:
> Hi,
>
> On Mon, May 15, 2023 at 7:09 AM Flávio Cruz wrote:
> > If we want
> > ./configure to check if MiG generates code to call the server reply
> routine
> > in case of errors (it doesn't :() then we will need to build a different
> check.
On Mon, May 15, 2023 at 9:19 AM Sergey Bugaev wrote:
> On Mon, May 15, 2023 at 7:09 AM Flávio Cruz wrote:
> > If we want
> > ./configure to check if MiG generates code to call the server reply routine
> > in case of errors (it doesn't :() then we will need to build a different
> > check.
>
> Huh
Hi,
On Mon, May 15, 2023 at 7:09 AM Flávio Cruz wrote:
> If we want
> ./configure to check if MiG generates code to call the server reply routine
> in case of errors (it doesn't :() then we will need to build a different
> check.
Huh? Why would MIG call that? Maybe I'm missing some context. Her
Hi Sergey
On Wed, May 10, 2023 at 1:36 AM Sergey Bugaev wrote:
> Hello,
>
> On Wed, May 10, 2023, 08:21 Flavio Cruz wrote:
> > HAVE_MIG_RETCODE is removed completely since this will be a no-op either
> > way (compiling against old Hurd headers will work the same, new Hurd
> > headers will resul
Applied, thanks!
Flavio Cruz, le mer. 10 mai 2023 01:20:34 -0400, a ecrit:
> We already did the same change for Hurd
> (https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=ef5924402864ef049f40a39e73967628583bc1a4)
>
> Due to MiG requiring the subsystem to be defined early in order to know
Hello,
On Wed, May 10, 2023, 08:21 Flavio Cruz wrote:
> HAVE_MIG_RETCODE is removed completely since this will be a no-op either
> way (compiling against old Hurd headers will work the same, new Hurd
> headers will result in the same stubs since retcode is a no-op).
It is a no-op currently, but
We already did the same change for Hurd
(https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=ef5924402864ef049f40a39e73967628583bc1a4)
Due to MiG requiring the subsystem to be defined early in order to know the
size of a port, this was causing a division by zero error during ./configure.
We
16 matches
Mail list logo
