found the problem.
line 215 in graphviz/cmd/smyrna/main.c
char *path is not defined for macos.
after defining, build works. will post upstrema
thanks lads.
btw this new (“old” cause APPARENTLY an 8 core i9 w/ 64 gigs sucks compared to
an M1 [lulz]) is DOPE
wish i had dashboard though. so the
i agree with this.
i’m still pissed i can’t merge my legacy trac with the new git system. the fact
they were separate in the first place is like, the antithesis of what the APPUL
mantra USED to mean.
but whatever. mobile rulz. 2fa, mfa, gfy
tethered to a cancer box no matter what it seems, or
every time i see valerio’s name, i’m reminded of the scene from night at the
roxbury referencing emilio estevez
i don’t know why it comes to mind, nor why i felt this was worth sharing, but
whatever.
Thanks,
Gagan
> On Jan 27, 2024, at 5:00 PM, Dave Allured - NOAA Affiliate via macports-dev
>
dear fred,
i understand this is the dev mailing list and politeness does not supersede
correctness given the topical nature of this mailing list.
i am the last one to be pedantic, but serge *did* qualify his statement with a
“should” (i.e. expectation), meaning it was not absolute.
let us not
do we got it?
tried a few a week ago and it seems like we don’t, as the firefox mach build
system would fail at the webassembly checks for clang.
Thanks,
Gagan
… let’s just say… um, imaginative.
🤘
Thanks,
Gagan
> On May 24, 2024, at 10:08 AM, Gagan Sidhu via macports-dev
> wrote:
>
> do we got it?
>
> tried a few a week ago and it seems like we don’t, as the firefox mach build
> system would fail at the webassembly checks for
… let’s just say… um, imaginative.
\m/
Thanks,
Gagan
i see you valerio! be ready dawg!
> On May 24, 2024, at 10:08 AM, Gagan Sidhu via macports-dev
> wrote:
>
> do we got it?
>
> tried a few a week ago and it seems like we don’t, as the firefox mach build
> system would fa
hi marcus
i’m working on making a firefox that works all the way back to 10.9
right now i am using it on 10.14 without issue, and i think the only thing left
is ensuring rust honours my macosx_deployment_target
it seems rustc from macports (1.77.1) honours this variable for the most part,
but
ery difficult to answer this question without having a
> much greater insight into Firefox builds.
> I am not quite sure what libgkrust.a is, but if it is copying files from the
> Rust supplied libcompiler_builtins-xxx.rlib, then it would make sense that
> there would be a discrepanc
hi team,
first of all, i just built the clang-18 properly and wow am i amazed. here i
was asking about wasm and stuff, i should have been a little more thorough, my
bad.
-really this thing is a work of art. great yob
now to my question, which i also posted to
stackexchange(https://stac
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 1
progressui_osx.o:(symbol OBJC_METACLASS_$_UpdaterUI+0x8)
>>> referenced 1 more times
with or without -lobjc
Thanks,
Gagan
> On Jun 10, 2024, at 10:14 AM, Ken Cunningham
> wrote:
>
> I can't see lobjc on the link line.
>
> Could you show us a failed
>>>>>> referenced by
>>>>>> /Users/Gagan/Downloads/mozilla-unified/toolkit/mozapps/update/updater/launchchild_osx.mm
>>>>>> launchchild_osx.o:(symbol
>>>>>> OBJC_METACLASS_$_ElevatedUpdateServer+0x0)
>>>>>> referenced
;
>> 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...
>>>
>>> K
>
(sorry for the dupe email ryan)
“how do i do that?” (submit a pull request) lol i remember our beloved ppc
crank barracuda told me to do the same thing for folly and i didn’t know how.
i’m just kidding on expecting you to answer that here though, as i
know/hope/suspect bing will tell me how to
tensions running high lads!
it’s like APPUL’s (now) piece of shit operating system and kit (SDK) problems
have finally had the proper effect on the endless abuse over the past decade
plus.
let’s cool ‘er down and not talk about Napster (linux), shall we?
i’d rather us flog the stupid brand th
anyone else get this?
and it just is stuck at the assembly file:
> /usr/bin/clang -I. -Iinclude -Iproviders/common/include
> -Iproviders/implementations/include -DAES_ASM -DBSAES_ASM -DCMLL_ASM
> -DECP_NISTZ256_ASM -DGHASH_ASM -DKECCAK1600_ASM -DMD5_ASM
> -DOPENSSL_BN_ASM_GF2m -DOPENSSL_BN_A
at 7:57 PM, Fred Wright wrote:
>>
>>
>> On Mon, 23 Sep 2024, Gagan Sidhu via macports-dev wrote:
>>
>>> anyone else get this?
>>>
>>> and it just is stuck at the assembly file:
>> [...]
>>
>> I don't see that on 10.7 here,
found the issue fred! it’s my kext that was attempting to patch the fdexec
issue from 10.7 that doesn’t exist in 10.8
it needs a little more work!
sorry about this!
Thanks,
Gagan
> On Sep 23, 2024, at 9:44 PM, Gagan Sidhu via macports-dev
> wrote:
>
> i guess my victory decla
again to install all the dependencies for lldb-5.0, it
arose on openssl-3.20.
- doesn’t seem to be a specific port. something up with 11g63, ports,
and bsdtar.
strange i know, but i thought i should share this.
Thanks,
Gagan
> On Sep 23, 2024, at 9:12 PM, Gagan Sidhu via macports-
the mach_kernel that i
replaced) that needed restoration.
but perhaps this caused an issue.
will look into it. thanks.
Thanks,
Gagan
> On Sep 23, 2024, at 7:57 PM, Fred Wright wrote:
>
>
> On Mon, 23 Sep 2024, Gagan Sidhu via macports-dev wrote:
>
>> anyone else ge
ports.macports.org/port/macports-libcxx/
>
>
>> On Sep 25, 2024, at 12:22 PM, Gagan Sidhu via macports-dev
>> wrote:
>>
>> … but i guess we’re shorthanded.
>>
>> today i built nodejs18 with a couple of flags anyone could find if they
>> attempted it
hi all,
so with a little effort (not too much, mind you), i did manage to get
lldb-mp-5.0 built/installed in my vm.
the changes were very small, like:
- removing the .sdk member in one of the files,
- changing the @YES @NO definitions to @true @false since the 10.7.5
SDK uses d
does anyone know why the APPUL gdb resolves the symbols in the binary, but the
newer GDB from ports does not?
i thought maybe it was because i didn’t have the universal binary, but now i
have that too (lol).
it’s way better, and my eyes have been opened to its realtime display of thread
spawni
package manager and, at one time, this operating system.
nice job man.
Thanks,
Gagan
> On Sep 25, 2024, at 2:14 PM, Gagan Sidhu via macports-dev
> wrote:
>
> thanks ken. i am aware of this library, but i’ve never used it outside of
> building clang with the +libstdcxx flag.
>
>
> On Sep 28, 2024, at 11:14 PM, Ken Cunningham
> wrote:
>
>
>
>> On Sep 28, 2024, at 8:47 PM, Gagan Sidhu via macports-dev
>> wrote:
>>
>
>> in my opinion, and while it’s clear the lack of weak references and thread
>> local storage in
systems to
build macports-libcxx.
i get that libcxx is a dependency for macports-libcxx on 10.5 and 10.6, but
those systems are far smaller than the rest that require a newer libcxx (and
presumably macports-libcxx) and thus i think the names should reflect their
current popularity.
>
&g
mine and it’s like such a shock we’re letting those
BREWsers (brew losers) just take our spot.
something must be done about this. they are losers. yes i did just “ad hominem”
them (i bet they like richard dawkins too, like real losers do)
>
> K
>
>
>
>
>> On Sep 2
will also look at after i get this firefox to behave on 10.7
>
>
>
>> On Sep 29, 2024, at 07:56, Gagan Sidhu via macports-dev
>> wrote:
>>
>> thanks for the thoughtful response. just before i follow-up, i wanted to
>> make clear it wasn’t my intention
… but i guess we’re shorthanded.
today i built nodejs18 with a couple of flags anyone could find if they
attempted it (after removing the OS check via sudo port edit), and then
hard-coding (lol it was a test) -L/opt/local/libexec/llvm-17/lib/libc++
it works completely fine if i put that path on
sorry to sound impatient, but would someone mind running the buildbot on my
pull request (nodejs) again?
it should check out fine this time. i had no idea newer OS X versions had
issues with without these flags as well.
Thanks,
Gagan
> On Sep 29, 2024, at 2:44 PM, Gagan Sidhu wrote:
>
> (sor
there’s nothing to suggest i didn’t follow the code of conduct given below.
i engaged the individual multiple times and corrected them, where they
deliberately (this is the key thing) ignored my responses.
as time went on they would pivot to this multiple times, in spite of me
correcting them.
barracuda is correct about libstdc++ being the default on 10.6 for both x86_64
and ppc.
ryan even said this in a bugticket that our beloved self-anointed sage
responded to:
https://trac.macports.org/ticket/56042
`` 10.7 and later ship with libc++, but 10.6 doesn’t ‘'
to criticise others as yo
took you how long to think of a recovery, which is embedded with lies?
rootie, are you going to do something about this pathological liar? should i
dig up the tickets where he makes baseless accusations and never responds
because he likes to abuse his power?
anyways let’s revisit his post, whic
ate me.
> On Jan 26, 2025, at 4:58 PM, Gagan Sidhu via macports-dev
> wrote:
>
> took you how long to think of a recovery, which is embedded with lies?
>
> rootie, are you going to do something about this pathological liar? should i
> dig up the tickets where he makes bas
does anyone notice that, ken seems to think he can attack others because he
undertakes a larger role than anyone wants?
as we see below, he gets upset when someone shares their own opinion and
threatens to stop contributing.
and who’s to say that the month-plus he spent on gcc-14 wasn’t a night
where i’m from, you treat others the way they treat you.
instead of admitting when he is wrong, he attacks others, puts words in their
mouth and says they’re at fault.
your response is not encouraging at all. it feels like you are condoning the
antagonistic behaviour of the person you’re defend
it’s the scripts or macro check for xcrun are causing a problem:
>
> vms-Mac-2:MacOS vm$ cat /opt/local/bin/clang++-mp-17
> #!/bin/bash
>
> if [ -x /usr/bin/xcrun ] ; then
> exec /usr/bin/xcrun /opt/local/libexec/llvm-17/bin/clang++ "${@}"
> else
> exec /opt/local/libexec/llvm-17/bin/clan
i think it’s an old and unneeded workaround for newer clangs. could someone
look into this?
i know that it’s not needed for newer clangs and, if anything, will frustrate
any potential users from staying with our package manager.
in my experience i’ve found this macro to be more of a hindrance t
>>> These scripts have worked perfectly for years.
>>>
>>> They work fine for me now, and on all the buildbots.
>>>
>>> Please explain or demonstrate exactly what problem you believe you are
>>> experiencing. The problem is most likely in your
i noticed that when building with older xcodes (the ones that can build a lion
kernel on lion), that the scripts for newer clangs in /opt/local/bin interfere
with compiling gdb.
i assume this issue can arise in other situations too. has anyone thought to
tackle the problem?
as it stands gdb ne
jimmy this isn’t twitter. you act like these shit processors are worth wasting
breath over.
save me with your benchmarks. i have no time for enthusiasm over inferior
architectures.
i tolerate powerpc, but this? i will not.
> On Jan 8, 2025, at 4:05 PM, Jimmy Yuen Ho Wong wrote:
>
> That's go
with the time and
> inclination should look into that first I would say.
>
> cheers Chris
>
> On 31/03/2025 2:40 pm, Gagan Sidhu via macports-dev wrote:
>> any thoughts on this?
>> i think it’s time.
>> Thanks,
>> Gagan
>
any thoughts on this?
i think it’s time.
Thanks,
Gagan
trying to see if i can conjure a new libuv with the existing patches.
i found that i could fetch the release on my brojave machine no problem:
> ---> libuv-v1.51.0-dist.tar.gz does not exist in
> /opt/local/var/macports/distfiles/libuv
> ---> Attempting to fetch libuv-v1.51.0-dist.tar.gz from
is there any way to do this in the portfile?
-fuse-ld=ld-latest ain't enough for clang.
didn't ken say that we should be moving away from ld127 on 10.6 anyways? what's
the harm in upping ld's symlink to ld-latest for 10.6?
Thanks,
Gagan
ote:
>>
>> Off-list, and please note that I'm not really active / not much time
>> myself, so please don't expect answers from me.
>>
>> Please open merge requests with your patches.
>> Does clang-19 also build on Snow Leopard (10.6 is still relatively
&g
is there a way i can edit the files after configure, before build?
like, i need to edit the files after ninja creates teh cmake files
Thanks,
Gagan
ld process is well-underway. like 6083/6945.
will the build system automatically call pre-build at each phase?
Thanks,
Gagan
> On Jul 5, 2025, at 5:44 PM, Gagan Sidhu via macports-dev
> wrote:
>
> is there a way i can edit the files after configure, before build?
>
> li
each phase?
>
> Thanks,
> Gagan
>
>> On Jul 5, 2025, at 5:44 PM, Gagan Sidhu via macports-dev
>> wrote:
>>
>> is there a way i can edit the files after configure, before build?
>>
>> like, i need to edit the files after ninja creates teh cmake files
>>
>> Thanks,
>> Gagan
>>
>
Miklavec
> wrote:
>
> Off-list, and please note that I'm not really active / not much time
> myself, so please don't expect answers from me.
>
> Please open merge requests with your patches.
> Does clang-19 also build on Snow Leopard (10.6 is still relative
ng the update of macports-libcxx to
clang-19?
we need to do this asap so i can try to push out fixes for node
hoping someone on the team is ready to receive and test a "patch" (as much of a
joke as the patch is)
Thanks,
Gagan
> On Mar 31, 2025, at 9:05 AM, Gagan Sidhu via ma
https://github.com/macports/macports-ports/pull/28834
https://github.com/macports/macports-ports/pull/28819
need someone to review these PRs.
clang doesn't finish within the 6 hour timer, but will build and work properly
on 10.6+ for intel macs if someone decides to evaluate it.
-it take
Anybody? Please?
Thanks,
Gagan
Sent from my (Inferior Android) BlackBerry—the (second-)most secure mobile
device—via the Rogers Network. Long Live QNX
Original Message
From: macports-dev@lists.macports.org
Sent: July 23, 2025 8:35 PM
To: macports-dev@lists.macports.org
Rep
> machine, being pushed into the macports distribution.
>
> -Frank
>
>> On Jul 30, 2025, at 4:45 AM, Gagan Sidhu via macports-dev
>> wrote:
>>
>>
>> Anybody? Please?
>>
>>
>> Thanks,
>> Gagan
>>
>> Sent
55 matches
Mail list logo
