Re: AW: Re-port Intent for HPE NonStop (a.k.a. Tandem)

[Florian Weimer <fweimer@redhat.com>]

* Joachim Schmitz:

> No idea whether that port had ever been send back upstream, it must have
> been done in 2007 or before.
> Not sure what you mean by "stable kernel interface"?

In general, Linux does not remove any interfaces for entering the kernel
once they have been added.  The system call numbers that identify the
entry points also does not change over time.  For example, on x86-64,
there is still a fstat system call, even though it has been superseded
by newfstatat first, and then by statx.

Other operating systems treat libc has the stable binary interface (if
they have one at all), and remove the old system calls from their
kernels once libc has been upgraded.  This means it is not feasible to
maintain libc as a separate project.

> No, sorry, unfortunately no gcc available nor possible to cross-compile, it
> is actually the assembler part that is missing IIRC

You will have to release that first, preferably as a new target for
binutils or LLVM, and then a compiler.  But again, even if you do all
that, it is unlikely that we would accept a glibc port.  But without the
toolchain, there is simply no way that it can happen.  I think glibc
stopped supporting proprietary toolchains some time in the 90s, before
the glibc 2.0 release, and we are definitely not going back.  Sorry.

If you need a glibc compatibility layer, maybe you should look at gnulib
instead.

Thanks,
Florian