[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#880851: marked as done (libva: FTBFS on non-Linux: __NR_gettid undeclared)

Your message dated Mon, 07 Dec 2020 00:06:15 +0100
with message-id <20882883.EfDdHjke4D@thyrus>
and subject line Fixed in libva 2.10.0
has caused the Debian Bug report #880851,
regarding libva: FTBFS on non-Linux: __NR_gettid undeclared
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 owner@bugs.debian.org
immediately.)


-- 
880851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880851
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libva
Version: 1.8.3-2
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-bsd@lists.debian.org
Usertags: kfreebsd

Builds of libva for kfreebsd-* (admittedly not release architectures)
have been failing lately:

  va_trace.c: In function 'add_trace_config_info':
  va_trace.c:294:28: error: '__NR_gettid' undeclared (first use in this function); did you mean '__getpgid'?
       pid_t thd_id = syscall(__NR_gettid);

(plus a few more uses further down in va_trace.c).  Builds for
hurd-i386 (not a release architecture) are blocked on the
unavailability of libdrm-dev there, but will presumably encounter the
same error if and when it ever becomes available.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu

--- End Message ---
--- Begin Message --- 
Source: libva
Source-Version: 2.10.0-1
Done: Sebastian Ramacher <sramacher@debian.org>

This was fixed upstream before 2.10.0:
https://github.com/intel/libva/commit/9ab7db37d11dcec840475933a8721672f02bff79
https://github.com/intel/libva/commit/0ed447df56fe14f9a83886c955365b6d13f972de
and indeed it libva 2.10.0-1 built successfully on non-Linux
architectures. Hence, closing appropriately.

-- 
Pino Toscano

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: