Re: GNU/Hurd portability patches

2025-07-01 Thread Michael Paquier
On Tue, Jul 01, 2025 at 10:01:37PM +0200, Michael Banck wrote: > On Tue, Jul 01, 2025 at 12:41:50PM -0400, Tom Lane wrote: >> Pushed, after some fooling with the comments and commit messages. > > Thanks! Also for back-patching them. Catching up on this thread after-the-fact, specifically looking

Re: GNU/Hurd portability patches

2025-07-01 Thread Tom Lane
Michael Banck writes: > On Tue, Jul 01, 2025 at 12:41:50PM -0400, Tom Lane wrote: > | * If didn't define IOV_MAX, define our own. X/Open requires at > | * least 16. (GNU Hurd apparently feel that they're not bound by X/Open, > | * because they don't define this symbol at all.) > I personally d

Re: GNU/Hurd portability patches

2025-07-01 Thread Michael Banck
Hi, On Tue, Jul 01, 2025 at 12:41:50PM -0400, Tom Lane wrote: > Michael Banck writes: > > please find attached the current patches required to get master built > > and the testsuites run on Debian's hurd-i386 port. I have not had the > > time to test the hurd-amd64 port in the same fashion, but w

Re: GNU/Hurd portability patches

2025-07-01 Thread Tom Lane
Michael Banck writes: > please find attached the current patches required to get master built > and the testsuites run on Debian's hurd-i386 port. I have not had the > time to test the hurd-amd64 port in the same fashion, but will do so > next. Pushed, after some fooling with the comments and com