Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Jan 2020 06:21:53 +0000
From:      bugzilla-noreply@freebsd.org
To:        gnome@FreeBSD.org
Subject:   [Bug 242533] devel/libgtop: error: no member named 'next' in 'struct vm_map_entry
Message-ID:  <bug-242533-6497-QuOJdewIZ3@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-242533-6497@https.bugs.freebsd.org/bugzilla/>
References:  <bug-242533-6497@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242533

Tomoaki AOKI <junchoon@dec.sakura.ne.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |junchoon@dec.sakura.ne.jp

--- Comment #16 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> ---
Created attachment 210610
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D210610&action=
=3Dedit
Updated patch for r356432 and later

r356432 on head [1] broke this again by eliminating v_tag from struct vnode.
r356437 on head [2] fixes by replacing v_tag with v_lock.lock_object.lo_nam=
e.

Attached patch is the update for the one on phablicator D22929.
Unfortunately, I'm not enough familiar with phablicator to update diff ther=
e.

Beware! Not enogh confirmed whether additional __FreeBSD_version checking is
required or not.

[1] https://lists.freebsd.org/pipermail/svn-src-head/2020-January/132472.ht=
ml

[2] https://lists.freebsd.org/pipermail/svn-src-head/2020-January/132477.ht=
ml

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242533-6497-QuOJdewIZ3>