[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-tickets
Subject:    Re: [MacPorts] #67307: glib2 compilation issues with clang
From:       "MacPorts" <noreply () macports ! org>
Date:       2023-04-29 18:53:38
Message-ID: 060.cd3d87c7e3558822d99ea319f3348a2b () macports ! org
[Download RAW message or body]

--===============2186958416707438700==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#67307: glib2 compilation issues with clang
-----------------------+----------------------
  Reporter:  rmottola  |      Owner:  mascguy
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  leopard
      Port:  glib2     |
-----------------------+----------------------

Comment (by mascguy):

 Riccardo, it might be better to install/fix `glib2-upstream` instead, as
 that will ultimately be the basis for `glib2`.

 For your awareness, `glib2` will be updated to the next major release -
 matching `glib2-devel` - within the next few weeks.

 After that, we'll probably wait another 30-ish days, and finally update
 `glib2` to the latest-and-greatest (matching `glib2-upstream`).

 So to avoid having to repeat all of this again two more times, I'd suggest
 working with `glib2-upstream`.

 Does that make sense?

-- =

Ticket URL: <https://trac.macports.org/ticket/67307#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS

--===============2186958416707438700==--
[prev in list] [next in list] [prev in thread] [next in thread]