On Fri, Feb 17, 2023 at 6:26 AM Sergey Bugaev wrote:
> On Fri, Feb 17, 2023 at 9:02 AM Flávio Cruz wrote:
> > Thanks for the instructions. I discovered that mach_msg_type_long_t does
> not align to 8 bytes so it also needs a bit of padding just like
> mach_msg_type_t. See my last patch. I was ab
On Fri, Feb 17, 2023 at 9:02 AM Flávio Cruz wrote:
> Thanks for the instructions. I discovered that mach_msg_type_long_t does not
> align to 8 bytes so it also needs a bit of padding just like mach_msg_type_t.
> See my last patch. I was able to compile most of the glibc and all the stubs
> afte
On Thu, Feb 16, 2023 at 4:19 AM Sergey Bugaev wrote:
> On Thu, Feb 16, 2023 at 10:27 AM Flávio Cruz wrote:
> >> On that note: right now, MIG-generated stubs are broken on x86_64. MIG
> >> built from master complains about time_value_t (which GCC says is 16
> >> bytes-, but MIG expects to be 12 b
On Thu, Feb 16, 2023 at 10:27 AM Flávio Cruz wrote:
>> On that note: right now, MIG-generated stubs are broken on x86_64. MIG
>> built from master complains about time_value_t (which GCC says is 16
>> bytes-, but MIG expects to be 12 bytes- sized). If I set
>> desired_max_alignof to 8 (which it mu
On Wed, Feb 15, 2023 at 4:05 AM Sergey Bugaev wrote:
> On Wed, Feb 15, 2023 at 8:51 AM Flávio Cruz wrote:
> >> This would be trivial to fix by flipping the line order in aclocal.m4
> >> (in each repo that vendors it...), but maybe MIG should actually
> >> support this? What does it need the subs
On Wed, Feb 15, 2023 at 8:51 AM Flávio Cruz wrote:
>> This would be trivial to fix by flipping the line order in aclocal.m4
>> (in each repo that vendors it...), but maybe MIG should actually
>> support this? What does it need the subsystem for anyway, when parsing
>> type defs? Apple's MIG suppor
Hey Sergey
On Tue, Feb 14, 2023 at 8:49 AM Sergey Bugaev wrote:
> This line in configure logs has always bugged me; of course GNU MIG
> supports "retcode" (as in, does not report an error upon seeing it).
> Today I happened to have journalctl -f opened at the time I ran
> ../configure, and accid
This line in configure logs has always bugged me; of course GNU MIG
supports "retcode" (as in, does not report an error upon seeing it).
Today I happened to have journalctl -f opened at the time I ran
../configure, and accidentally found out why this happens:
kernel: traps: x86_64-gnu-migc[177175]
