Date: Fri, 16 Jul 2010 12:29:10 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: pluknet <pluknet@gmail.com> Cc: Dimitry Andric <dimitry@andric.com>, FreeBSD Hackers <hackers@freebsd.org> Subject: Re: strange problem with int64_t variables Message-ID: <4C403476.4020704@FreeBSD.org> In-Reply-To: <AANLkTikX8kYatUT2pwbUbkd2HY9ISFlIJx5bVgJ7Os2D@mail.gmail.com> References: <4C39D92F.4050605@FreeBSD.org> <4C39DB09.6010808@andric.com> <4C39DBFF.2000307@FreeBSD.org> <AANLkTilqEfe_EL_3ExodMgqfmU-DubIdlRs-5NXXT4dO@mail.gmail.com> <4C3AF87B.3030707@FreeBSD.org> <AANLkTinwsNqH19LF7CAc6uC2NZuh2CdCkfEtsv6yM2Bt@mail.gmail.com> <4C3F80D3.8080809@FreeBSD.org> <AANLkTikX8kYatUT2pwbUbkd2HY9ISFlIJx5bVgJ7Os2D@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 2010.07.16. 12:17, pluknet escreveu: > Almost the same (#__jid_t#jid_t#). > > Did you have to include any header for that? IIRC, I used __jid_t because it didn't compile with jid_t. > The difference (and probably a trigger of bug elsewhere) might be in > that this lives > on amd64 arch (while yours on i386 afair). Just a food for thoughts. > Yes, and now I also added the entries to sys/compat/freebsd32/syscalls.master, although I think it's just for 32-bit binaries on 64-bit systems but let's see if that helps. Thanks for your help. Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C403476.4020704>