Your message dated Fri, 14 Jul 2023 18:23:12 +0200
with message-id <ZLF2cP/v5mvc+...@aurel32.net>
and subject line Closing kfreebsd specific bugs
has caused the Debian Bug report #775710,
regarding libc0.1-dev: mcontext.h incomplete for kfreebsd-amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
775710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:glibc
version: 2.19-13
severity: important
control: block 767048 by -1

Hi, I was working on building wine for kfreebsd-amd64 and found that
glibc's x86_64 mcontext.h is not in sync with the upstream code that
it is derived from (kfreebsd's amd64 ucontext.h).

One example is that mc_fs is not defined in glibc's mcontext_t struct
but is in kfreebsd's __mcontext struct (well there is a definion of
mc_fs in a second definition of the mcontext_t struct behind an #ifdef
__i386__ which will be false on amd64).  There are many other
differences like this.

Since wine uses mc_fs and some of the other bits missing from the
non-i386 mcontext_t struct, it fails to build using glibc.

Files to compare are:

src:kfreebsd-10 sys/x86/include/ucontext.h (the #ifdef __amd64__ section)
src:glibc ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/x86_64/bits/mcontext.h
(the #else section)

Thanks for looking into this.

Best wishes,
Mike

--- End Message ---
--- Begin Message ---
Starting with glibc 2.37-6 the support for kfreebsd has been dropped for
the packaging (it has been broken for many years). Let's close the
corresponding bugs.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                     http://aurel32.net

--- End Message ---

Reply via email to