https://bugzilla.mindrot.org/show_bug.cgi?id=2590
--- Comment #7 from Darren Tucker <[email protected]> --- (In reply to Joshua Kinard from comment #3) > I believe there's a known/defined CHOST tuple to specify an N32 Debian seems to document "mips64-linux-gnuabin32": https://wiki.debian.org/Multiarch/Tuples (In reply to Joshua Kinard from comment #6) [...] > Per the MIPS N32 handbook, you can tell O32/N32 apart from N64 (full > 64-bit) by checking the size of a pointer, which should be 8 bytes > on N64. But it'll be 4 bytes under both O32/N32, so this approach > won't work either. I know nothing about this other than what I've read in the last few minutes, but isn't O32 for purely 32 bit machines? ie isn't config.guess is going to say "mips-"? or can you run O32 userspace even on a 64 bit kernel? > Is it possible to have configure compile a test binary using the > provided C compiler and flags, then check the file magic of the > output binary? It's possible but seems pretty icky. I think the first thing to do is fix the case statement which will allow you to at least specify the right thing via configure --target. -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
