Two of the libgccs are stubs, the rest are not.
so it is pretty much as bad as it looks.
Once gcc13 is the default gcc used on older systems, it would be hoped that it
would cover off most needs.
Up to now, though, older systems have used gcc7, and in a few cases gcc5 or
gcc48 are used for specific issues. So those gcc versions may still be needed
... time will tell.
If the whole
verification.
K
> On Mar 27, 2024, at 02:29, Riccardo Mottola
> wrote:
>
> Hi Ken,
>
> Ken Cunningham wrote:
>> the cmake port is very very far behind.
>>
>> cmake-devel has been updated to the newest version currently available
>> (3.29.0) for most sy
I was not aware that supporting the bootleg crippled 10.6 PPC pre-beta had
anything to do with why nobody had gotten around to updating the gcc version
used on older systems.
At least, it was not anywhere on my radar.
Just -- nobody did the legwork.
Ken
On 2024-03-28, at 11:47 AM, Sergio
supporting all the gcc versions between gcc 8 and 12 on older systems will be
quite a bit of work and require a lot of build time for poor users of these
systems.
To have libgcc7, the way it is now, you need to build libgcc13, 12, 11, 10, 9,
8, and then 7.
That is -- a lot of gcc building for
ith me then to move 10.4–10.5 to libgcc13,
> since we should not have a disagreement anymore.
>
>
>> On Mar 29, 2024, at 5:34 AM, Ken Cunningham
>> wrote:
>>
>> I was not aware that supporting the bootleg crippled 10.6 PPC pre-beta had
>> anything to do
the cmake port is very very far behind.
cmake-devel has been updated to the newest version currently available (3.29.0)
for most systems, and then newest supportable (3.28.4) for 10.7 and < 10.6.
Please try out if you care to, as cmake-devel should become cmake soon.
If you are interested in
Some of your macports installations are installed as the root user, instead of
the macports user.
This happened because there is no installer for 10.6-ppc to automatically
create the macports user. You have an open ticket about this too, where I
pointed to the commands to be run to generate
in the master has no support for tests, as of now, so running it gonna fail anyway.)On Sat, Feb 24, 2024 at 11:24 PM Ken Cunningham <ken.cunningham.web...@gmail.com> wrote:Some of your macports installations are installed as the root user, instead of the macports user.
This happened b
On 25/2/2024 03:07, Ken Cunningham wrote:
>> Some of your macports installations are installed as the root user, instead
>> of the macports user.
>> This happened because there is no installer for 10.6-ppc to automatically
>> create the macports user. You have an op
> On Apr 7, 2024, at 11:24 PM, Riccardo Mottola
> wrote:
>
> Hi,
>
> Ken Cunningham wrote:
>> Up to now, though, older systems have used gcc7, and in a few cases gcc5 or
>> gcc48 are used for specific issues. So those gcc versions may still be
>> ne
It's easier to help if we can see the link line you're using, but in short you
need to make sure that lobjc is in the link libs, sometimes by explicitly
adding it:
LDFLAGS="$LDFLAGS -framework Cocoa -lobjc"
K
> On Jun 10, 2024, at 8:08 AM, Gagan Sidhu via macports-dev
> wrote:
>
> hi team,
e same undefined symbol error.
>
> sorry for the duplicate message ken. forgot to send it ot the mailer.
>
>>
>>> On Jun 10, 2024, at 9:45 AM, Ken Cunningham
>>> mailto:ken.cunningham.web...@gmail.com>>
>>> wrote:
>>>
>>> I
> without lobjc
>
> it’s the exact same as below.
>
> Thanks,
> Gagan
>
>> On Jun 10, 2024, at 10:17 AM, Ken Cunningham
>> mailto:ken.cunningham.web...@gmail.com>>
>> wrote:
>>
>> Yes but I still don't see -lobjc on your link line...
>
unified/toolkit/mozapps/update/updater/launchchild_osx.mm
>>>> launchchild_osx.o:(symbol
>>>> OBJC_METACLASS_$_ElevatedUpdateServer+0x0)
>>>> referenced by
>>>> /Users/Gagan/Downloads/mozilla-unified/toolkit/mozapps/update/updater/progres
701 - 715 of 715 matches
Mail list logo
