All,
I just formally subscribed to this mailing list.
I'm interested in fpc on FreeBSD/PowerPC, however, I don't want to
create any additional work nor break something that's not broken. That
being said, I'm willing to work on this alone or with anyone who is also
interested. My personal work
Hi,
On Wed, 9 Aug 2017, Curtis Hamilton wrote:
> I just formally subscribed to this mailing list.
>
> I'm interested in fpc on FreeBSD/PowerPC, however, I don't want to
> create any additional work nor break something that's not broken. That
> being said, I'm willing to work on this alone or with
In our previous episode, Curtis Hamilton said:
> I just formally subscribed to this mailing list.
>
> I'm interested in fpc on FreeBSD/PowerPC, however, I don't want to
> create any additional work nor break something that's not broken.
Just try to keep your patches small (no major restructuring
In our previous episode, Karoly Balogh (Charlie/SGR) said:
> > organic process, but unfortunately it doesn't happen in all of the BSDs at
> > the same time or even at all.
>
> The questions is, can I just go in and upgrade our syscall interface to
> the newer calls (where makes sense), or do we in
Hi,
On Thu, 10 Aug 2017, Marco van de Voort wrote:
> > The questions is, can I just go in and upgrade our syscall interface to
> > the newer calls (where makes sense), or do we intend to support older
> > systems too?
>
> To my knowledge there is no universal "newer" and "older" BSD syscall
> set
In our previous episode, Karoly Balogh (Charlie/SGR) said:
> > To my knowledge there is no universal "newer" and "older" BSD syscall
> > set. Are you talking about something NetBSD specific? So the first thing
> > would be to qualify that, and/or verify in how much the other BSDs
> > follow.
>
> W
