On 2016-05-22 23:20:33 [+0200], Kurt Roeckx wrote:
> On Sun, May 22, 2016 at 11:13:50PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2015-09-20 15:52:34 [-0400], Jeffrey Walton wrote:
> > > This could be a problem with the include paths for the standard
> > > library. Examining features.h and what's going on around the cdefs.h
> > > include:
> >
> > Jeffrey, can this be closed? The overview page for x32 shows 1.0.2h-1 as
> > `Installed' but if I click on the log then I see a segfault in the
> > testsuite. Whatever it is, it is a different issue, right?
>
> My understanding is of this bug report is that the default
> upstream ./config does not support x32. I haven't looked at what
> the status of this is in the upstream branches.
From Configurations/10-main.conf:
|…
| "linux-x32" => {
| inherit_from => [ "linux-generic32", asm("x86_64_asm") ],
| cflags => add("-mx32 -DL_ENDIAN"),
| bn_ops => "SIXTY_FOUR_BIT",
| perlasm_scheme => "elf32",
| shared_ldflag => "-mx32",
| multilib => "x32",
| },
|…
there is a linux-x32 target. The debian patch has
|"debian-x32","gcc:-mx32 -DL_ENDIAN ${debian_cflags}
|-DMD32_REG_T=int::-D_REENTRANT::-ldl:SIXTY_FOUR_BIT RC4_CHUNK DES_INT
DES_UNROLL:
|${x86_64_asm}:elf:dlfcn:linux-shared:-fPIC:-mx32:.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR):::x32",
so it is not that different.
> The buildd log segfault is something unrelated, and as far as I
> understand it can only be reproduced on the buildd.
fun.
> Kurt
Sebastian
