Fwd: Re: Re: Qt 5.10 skipped?

[Jason Liu]

-- Forwarded message -
From: 
Date: Fri, Sep 1, 2023 at 10:21 PM
Subject: Re: Re: Re: Qt 5.10 skipped?
To: Jason Liu 


My email is once again blocked from posting to the mailing lists; please
forward this.




On 9/1/23 at 5:34 PM, Jason Liu wrote:

> Yes, I do have the crash report that gets generated by macOS when the
> application crashes. I haven't reported it anywhere, because this is an
> old, obsolete version of both the software and the version of Qt that's
> involved.


MacPorts’ trac would still be a good place to report this.


> I thought about using the 'symbolicatecrash' tool that comes with Xcode,
> but I've never had any luck getting it to work properly. I suppose I could
> also use 'atos' to symbolicate line by line, but I don't even know where
to
> begin getting my hands on the dSYM build symbols from the MacPorts build
of
> Qt 5.11.


I am not familiar with these tools (mainly since I have not needed to use
them yet), however my impression is that (1) they are not very useful for
certain “release“ builds which do not have debugging symbols to begin with,
and/or (2) they are only needed for a debug build where symbols have been
stripped.

I do not know whether rebuilding the relevant qt511 ports with the +debug
variant enabled works or will help get a more useful crash report, but that
is what I would suggest trying next.

Re: Re: Qt 5.10 skipped?

[Jason Liu]

Yes, I do have the crash report that gets generated by macOS when the
application crashes. I haven't reported it anywhere, because this is an
old, obsolete version of both the software and the version of Qt that's
involved.

I thought about using the 'symbolicatecrash' tool that comes with Xcode,
but I've never had any luck getting it to work properly. I suppose I could
also use 'atos' to symbolicate line by line, but I don't even know where to
begin getting my hands on the dSYM build symbols from the MacPorts build of
Qt 5.11.

-- 
Jason Liu


On Fri, Sep 1, 2023 at 3:33 PM  wrote:

> On 8/31/23 at 6:39 PM, Jason Liu wrote:
>
> > Does anyone have any objections if I were to resurrect Qt 5.10? One of
> the
> > ports that I am working on crashes under certain circumstances when using
> > qt511, which is the newest Qt that works on macOS 10.11. The version of
> Qt
> > that was bundled with the pre-built binary distribution was Qt 5.10.
> > Admittedly, I am also able to compile the port using qt59, and there are
> no
> > crashes. In addition, I can also compile the port using qt513 on macOS
> > 10.13, and there are also no crashes (qt512 also doesn't currently
> exist).
> >
> > I'm not really sure how much Qt changes with each version. So on the one
> > hand, it would be nice to be able to get the port working with the same
> > version of Qt that it originally shipped with, but on the other hand, it
> > seems like overkill to bring back such a large set of ports as qt510-*
> just
> > for the sake of a single port on old versions of macOS.
> >
> > What are everyone's thoughts on this?
> >
> > --
> > Jason Liu
>
>
> I think it would be much better to investigate the crash first. Do you
> have a crash report/have you reported the crash somewhere?
>

Re: Re: Qt 5.10 skipped?

[chrischavez]

On 8/31/23 at 6:39 PM, Jason Liu wrote:

> Does anyone have any objections if I were to resurrect Qt 5.10? One of the
> ports that I am working on crashes under certain circumstances when using
> qt511, which is the newest Qt that works on macOS 10.11. The version of Qt
> that was bundled with the pre-built binary distribution was Qt 5.10.
> Admittedly, I am also able to compile the port using qt59, and there are no
> crashes. In addition, I can also compile the port using qt513 on macOS
> 10.13, and there are also no crashes (qt512 also doesn't currently exist).
>
> I'm not really sure how much Qt changes with each version. So on the one
> hand, it would be nice to be able to get the port working with the same
> version of Qt that it originally shipped with, but on the other hand, it
> seems like overkill to bring back such a large set of ports as qt510-* just
> for the sake of a single port on old versions of macOS.
>
> What are everyone's thoughts on this?
>
> --
> Jason Liu


I think it would be much better to investigate the crash first. Do you have a 
crash report/have you reported the crash somewhere?

Re: Qt 5.10 skipped?

[Jason Liu]

Does anyone have any objections if I were to resurrect Qt 5.10? One of the
ports that I am working on crashes under certain circumstances when using
qt511, which is the newest Qt that works on macOS 10.11. The version of Qt
that was bundled with the pre-built binary distribution was Qt 5.10.
Admittedly, I am also able to compile the port using qt59, and there are no
crashes. In addition, I can also compile the port using qt513 on macOS
10.13, and there are also no crashes (qt512 also doesn't currently exist).

I'm not really sure how much Qt changes with each version. So on the one
hand, it would be nice to be able to get the port working with the same
version of Qt that it originally shipped with, but on the other hand, it
seems like overkill to bring back such a large set of ports as qt510-* just
for the sake of a single port on old versions of macOS.

What are everyone's thoughts on this?

-- 
Jason Liu


On Wed, Aug 30, 2023 at 11:26 PM Ryan Schmidt 
wrote:

>
>
> On Aug 30, 2023, at 19:40, Jason Liu wrote:
>
> I just noticed that Qt 5.9 and Qt 5.11 are available in MacPorts, but not
> Qt 5.10. Was there a specific reason why 5.10 was skipped, or was it just
> that no one got around to it before 5.11 was released?
>
>
> Certainly qt 5.10.x existed in MacPorts. You can find bugs that were filed
> against it:
>
> https://trac.macports.org/query?port=~qt5=~%405.10
>
> I couldn't immediately find the commit in which it was removed. It's a
> little difficult since the qt5 portfile is massive and there are also the
> qt5 portgroups. But I suspect it was deleted because there exists no macOS
> version for which qt 5.10.x is the most recent one available.
>
> And a somewhat tangential question: When using the qt5 PortGroup, is there
> a way to specify a particular version of Qt 5.x that needs to be used? I do
> see plenty of references to ${qt5.version}, but is that something that I am
> allowed to set in my Portfile?
>
>
> Looking near the top of the qt5-1.0 portgroup,
>
>
> https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/qt5-1.0.tcl
>
> the prominent placement of qt5.min_version suggests to me that it is
> intended for portfile authors to override it. 38 ports reference this
> variable.
>
> I don't believe there is any way for you to specify a maximum qt version,
> nor a specific version. The qt5 portgroup will select the blessed qt
> version that is compatible with the user's OS version.
>

Re: Qt 5.10 skipped?

[Ryan Schmidt]

> On Aug 30, 2023, at 19:40, Jason Liu wrote:
> 
> I just noticed that Qt 5.9 and Qt 5.11 are available in MacPorts, but not Qt 
> 5.10. Was there a specific reason why 5.10 was skipped, or was it just that 
> no one got around to it before 5.11 was released?

Certainly qt 5.10.x existed in MacPorts. You can find bugs that were filed 
against it:

https://trac.macports.org/query?port=~qt5=~%405.10 


I couldn't immediately find the commit in which it was removed. It's a little 
difficult since the qt5 portfile is massive and there are also the qt5 
portgroups. But I suspect it was deleted because there exists no macOS version 
for which qt 5.10.x is the most recent one available. 

> And a somewhat tangential question: When using the qt5 PortGroup, is there a 
> way to specify a particular version of Qt 5.x that needs to be used? I do see 
> plenty of references to ${qt5.version}, but is that something that I am 
> allowed to set in my Portfile?

Looking near the top of the qt5-1.0 portgroup,

https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/qt5-1.0.tcl
 


the prominent placement of qt5.min_version suggests to me that it is intended 
for portfile authors to override it. 38 ports reference this variable.

I don't believe there is any way for you to specify a maximum qt version, nor a 
specific version. The qt5 portgroup will select the blessed qt version that is 
compatible with the user's OS version.