Re: 32bit Snow Leopard libc++11 dylibs

in/usr/bin On Monday, 24 June 2024, 5:12:40 pm AEST, Ken Cunningham wrote: there are a set of the required libs in here:http://packages.macports.org/libcxx/libc

Re: 32bit Snow Leopard libc++11 dylibs

there are a set of the required libs in here: http://packages.macports.org/libcxx/libcxx-5.0.1_5+emulated_tls+universal.darwin_10.i386-x86_64.tbz2 You'll need both libc++ and libc++abi,, and probably the symlink too, in your bundle. As you said, use install_name_tool to fix things up. I have

Re: 7zip port - what's the name of the binary?

port contents 7zip will tell you what’s installed by a port. pipe it to grep for a specific path like bin/ > On Jun 23, 2024, at 07:49, Christoph Kukulies via macports-users > wrote: > > 7zip

Re: C++ exception handling on PPC with gcc 6.4.0 doesn't work

do exceptions work with the default gcc7 compiler? K

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

Hi Ken, I’ve updated the port here, just waiting for the CI system to validate on arm, etc before pushing: https://github.com/macports/macports-ports/pull/24159 I don’t know how to use or test those bindings you are asking for, and I

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

c >> [ 91%] Building CXX object CMakeFiles/primesieve.dir/src/app/cmdoptions.cpp.o >> [ 93%] Building CXX object CMakeFiles/primesieve.dir/src/app/help.cpp.o >> [ 95%] Building CXX object CMakeFiles/primesieve.dir/src/app/main.cpp.o >> [ 97%] Building CXX object CMakeFi

Re: New Port Request: Primesieve from https://github.com/kimwalisch/primesieve

Someone can make a port for this, but here you are for a quickie, to show you how this is done: % sudo port install cmake % git clone --depth=1 https://github.com/kimwalisch/primesieve % cd primesieve % mkdir build % cd build % cmake .. % make % ./primesieve 100 --count --print 2 3 5 7 11 13

Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)

> On Nov 4, 2023, at 4:51 PM, Ken Cunningham > wrote: > > So to clean that up: > > sudo port -f uninstall perl5 perl5.36 > > and then: > > sudo port -f install perl5 That last line should have been: sudo port -v install perl5 K

Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)

MacPorts current "default" perl is perl5.34. I tooks like you have manually installed perl5.36 and there is no need for perl 5.36, so you could uninstall that if you care to. Everything else is pegged to perl 5.34 currently, except your "perl5" port which must have manually been installed with

Re: Help with legacysupport PortGroup for building GIMP for older MacOS's

Building and using legacysupport on a newer system to target an older system is tricky to design and implement properly. I think it is possible to do it, but issues will probably arise that only show up at deployment time. If I wanted to deploy gimp to 10.13, I would set up a 10.13 VM in

Re: Help me understand dependents of libgcc-devel vs gcc13?

There was a time when the only version of gcc that built on arm64 was gcc-devel/libgcc-devel. So ports put a specific dependency on that on arm. This was a long time ago now. It got things built. Then various gcc versions came out, gcc-12, gcc-13 that would build on arm64 (with extra patches,

Re: Can gcc13 create fat binaries for Intel+ARM in one-liner?

The necessary parts Apple added (driverdriver.c) to enable that have not been updated since gcc-4.2, so one-pass universal is not available since then. People occassionaly talk about updating driverdriver.c, and there are a few shell scripts floating around that do some of it, but that’s as far

Re: best Xcode version for Mojave?

On 2023-06-12, at 7:25 PM, Richard L. Hamilton wrote: > "On macOS 10.14, iTerm2 @3.4.19 requires Xcode 11.0 or later but you have > Xcode 10.3." > > 11.3.1 is the newest Xcode for Mojave. > > Is there any known downside to Xcode 11.3.1 on Mojave rather than the 10.3 I > have on there now?

Re: Exa port dependencies

I have long thought the doc variants should never be the default. Lots of bloat and extra deps and build errors. But I know others feel differently. I know I can set -doc in variants.conf, but then you’re building everything. K > On Jun 9, 2023, at 04:01, Joshua Root wrote: > >  >> >>

Re: Portfile question for 10.6.8

> On Jun 6, 2023, at 6:28 PM, raf via macports-users > wrote: > > On Wed, Jun 07, 2023 at 11:09:13AM +1000, raf via macports-users > wrote: > >> Yay! It worked. Many thanks. I'll fix my Makefile for the upcoming version >> of rawhide and create the Portfile for that. > > I spoke too

Re: Portfile question for 10.6.8

> On Jun 6, 2023, at 6:16 PM, raf via macports-users > wrote: > > On Wed, Jun 07, 2023 at 11:09:13AM +1000, raf via macports-users > wrote: > >> So if I use different macro names (e.g. ALL_CFLAGS and ALL_LDFLAGS), and just >> add $(CFLAGS) and $(LDFLAGS) from the environment to it, then it

Re: Portfile question for 10.6.8

it looks like the legacy support library is not being included in the link. This is common when only scripts are used, as there are many flags that might not be considered. If you run the build on 10.6 using some extra verbosity flags like "-d" it will show you all the ENVVARs and LDFLAGS etc

Re: gcc12 fault?

> On Jun 1, 2023, at 6:18 PM, Joshua Root wrote: > > Ken Cunningham wrote: > >> what you see is difficult to explain, unless the PATH changed between the >> two tests. >> >> if >> >> 'which gcc' gives /opt/local/bin/gcc >> >> t

Re: gcc12 fault?

what you see is difficult to explain, unless the PATH changed between the two tests. if 'which gcc' gives /opt/local/bin/gcc then gcc --version should give exactly the same as /opt/local/bin/gcc --version Now you know that /opt/local/bin/gcc will not actually exist, unless you have

Re: Wine

est version on MacPorts really that old, or am I misunderstanding > something? > > Thanks > > Andre > >> On Apr 30, 2023, at 14:39, Ken Cunningham >> wrote: >> >> You probably won't want to build it, though. >> >> Dean uses MacPorts to bui

Re: Wine

You probably won't want to build it, though. Dean uses MacPorts to build wine, and then makes the binaries available here: https://github.com/Gcenx/macOS_Wine_builds/releases/ Homebrew just downloads and installs the premade binaries that are made by Dean's MacPorts overlay. These are

Re: Cannot build glib2

FYI I have had good luck with opencore legacy patcher on several machines. A macbookpro 9,2 can run the current Ventura, for example, very nicely (upgraded to 16GB Ram). Some machines don't fare as well -- a macbookpro 9,1 I tried to upgrade struggles. K On 2023-04-18, at 11:17 AM, Eldrid

Re: meson and NM

> On Apr 17, 2023, at 4:43 PM, Riccardo Mottola > wrote: > > Hi Ken! > > hmm... somehow your email got garbled? It is without subject and I cannot > relate.. but I think I got it. > > > Ken Cunningham wrote: >> meson is now more picky about unrecogni

Re: Cannot build glib2

if glib2 now links against dbus (and it seems at least one test does) then dbus will need to be added to the build deps of glib2 so that macports can work out the architecture matching needed to prevent this. I can't see any indication that any of the installed glib2 files link against dbus,

Re: compiling ArcticFox on 10.11 - atomic not found, cxx11

$ cat atomic.cxx #include int main(void) { return (0); } $ clang++-mp-9.0 -stdlib=libstdc++ atomic.cxx atomic.cxx:1:10: fatal error: 'atomic' file not found #include ^~~~ 1 error generated. $ clang++-mp-9.0 -stdlib=macports-libstdc++ atomic.cxx h$ clang++-mp-9.0 -stdlib=libc++

[no subject]

meson is now more picky about unrecognized arguments. This will have to be removed, and then making sure it uses the right NM might have to be done another way: lt_cv_path_NM=/opt/local/bin/nm > *info:configure meson: error: unrecognized arguments: >

Re: MacBook broken GPU workarounds

I disassembled my MacBookPro 2,1 and baked the motherboard in the oven for 8 minutes at 350F (IIRC), supported on some pyramids of tinfoil. It worked for another 1.5 years after that, but then died again and that was enough for me. I removed all the useful parts from it and moved on, giving it

Re: Setting environment and support of older OS/arch

You can also look into how to use pkgconfig and cmake to find needed libraries. They can suffice for simpler header and library path additions, and often that might be all you need for a simpler project with just one or two things needed. K

Re: Setting environment and support of older OS/arch

If you are doing your own compilation using the compilers and libraries from MacPorts, you need to direct your build to use the specified tools, headers, and libraries. You can look at what MacPorts sets up itself for each build for a clue, for example this is setup for a generic build of

Re: libgcc11 failed build failed on macOS 13.0.1

On Ventura arm64, libgcc11 is not part of the youtube-dl dependency tree. You can use: port rdeps youtube-dl so see what is on the tree. I can install youtube-dl without any trouble. % port -v installed youtube-dl The following ports are currently installed: youtube-dl

Re: GIMP Quartz broken on 10.7, perhaps gtk

; > On 2023-01-12 14:12:38 +0100 Ken Cunningham > wrote: > >> My guess would be to look at harfbuzz…make sure our patches there still >> make sense, run the test suite. It can be touchy, different compilers can >> change test results, etc. >> >>

Re: GIMP Quartz broken on 10.7, perhaps gtk

n gtk3 is built with the quartz backend (on 10.7 at least), so that is unfortunate. Ken > On Jan 12, 2023, at 5:12 AM, Ken Cunningham > wrote: > > My guess would be to look at harfbuzz…make sure our patches there still make > sense, run the test suite. It can be touchy, differe

Re: GIMP Quartz broken on 10.7, perhaps gtk

My guess would be to look at harfbuzz…make sure our patches there still make sense, run the test suite. It can be touchy, different compilers can change test results, etc. To disable one port in an overlay with minimal fuss, rename to Portfile to something else (I use Portfile.disabled), and

Re: GIMP Quartz broken on 10.7, perhaps gtk

The default x11 installation of gimp works perfectly. I know that is not the version you want, you want the +quartz version. But there’s a data point, at least, and a likely clue as to where to look for the issue with font rendering. Ken > On Jan 8, 2023, at 2:24 PM, Ken Cunning

Re: GIMP Quartz broken on 10.7, perhaps gtk

I see the same thing on a fresh gimp2 install +quartz on 10.7 (one very tiny patch needed to gimp2 to change NULL -> 0 to keep clang-15 happy, otherwise a no-touch build). However, there is no text drawn on any gimp2 windows or dialog boxes, as you noted. Installing pan2 +quartz +gtk3, I see

Re: a2ps fails to install (compressed log attached)

> On Dec 20, 2022, at 8:12 AM, Ken Cunningham > wrote: > > , or we generate another port that provides Apple’s older makeinfo version > from Ventura. Monterey I meant

Re: a2ps fails to install (compressed log attached)

% uname -a Darwin MacBookPro-2012 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64 % ls -la /usr/bin/makeinfo ls: /usr/bin/makeinfo: No such file or directory The makeinfo in the makeinfo port was too new to build this, so once you

Re: iInstall denemo failed due to failure to configure qt5-qtbase

Oh, I’m sorry, you already did that. My apologies, I didn’t read that closely enough. I don’t know for sure what is happening to you now then. K > On Oct 29, 2022, at 7:24 PM, Ken Cunningham > wrote: > > Probably you need to go to the developer.apple.com > <http://d

Re: iInstall denemo failed due to failure to configure qt5-qtbase

t;> sudo port -v -t clean denemo >>> sudo port -v -t install denemo >>> >>> failed as above. >>> >>> sudo port selfupdate >>> sudo port upgrade outdated >>> >>> sudo port clean qt5-qtbase >>> sudo port clean denemo >>> sudo port -v -t install qt5-qtbase >>> >>> failed as above. >>> >>> Attached is the most recent log. >>> >>> Thanks, >>> Ken Wolcott >>> >>> On Sat, Oct 29, 2022 at 10:04 AM Ken Cunningham >>> wrote: >>>> >>>> should be fixed now, after you update >>>> >>>> thx K

Re: macports-users Digest, Vol 194, Issue 22 ==> py-jupyter won't install

I just tried to install py-jupyter on a clean machine, and got the same error: g-info/dependency_links.txt Error: Failed to activate py310-jupyter: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/__pycache__/jupyter.cpython-310.pyc is being

Re: iInstall denemo failed due to failure to configure qt5-qtbase

should be fixed now, after you update thx K

Re: problems recompiling ports for Ventura

> On Oct 28, 2022, at 8:16 PM, Andreas Skarlatoudis wrote: > > :notice:patch ---> Applying patches to aquaterm > :info:patch ---> Applying no-NSMailDelivery.patch > :debug:patch Environment: > :debug:patch CC_PRINT_OPTIONS='YES' > :debug:patch >

Re: iInstall denemo failed due to failure to configure qt5-qtbase

The qt5 issue is a pain, something as yet unexplained to do with xcrun not recognizing an SDK that is sitting right there. please see the relevant ticket: https://trac.macports.org/ticket/65853

Re: problems recompiling ports for Ventura

Aquaterm was fixed yesterday: https://github.com/macports/macports-ports/commit/32c5c1e4a77f9a7437e74be6fb25551fd2e17e6e k

Re: Cannot build graphene (fwd)

somehow, you *are* compiling it +universal, clearly, or it wouldn’t be showing this isdue. So clean it, then look through all your installed ports to see what is forcing it universal and get rid of that, assuming you don’t want it universal. It might be some port that only builds 32 bit that

Re: Cannot build DOSBOX

use dosbox-x instead. I added it to MP largely because it is 64bit and maintained actively. It’s been updated a number of times lately I see. K K

Re: What happens when a port fails to compile (+universal) and there is no maintainer?

it builds OK universal on Monterey Intel: % port -v installed jemalloc The following ports are currently installed: jemalloc @5.3.0_2+universal (active) requested_variants='+universal' platform='darwin 21' archs='arm64 x86_64' date='2022-08-22T17:31:05-0700’ There are many combinations and

Re: problem compiling libzzip (PPC, Sorbet Leopard)

> Hello, > > somewhere in the dependencies for some package I have to compile > libzzip. That's less easy than it sounds: > > The libzzip package seems to enforce gcc-4.2 (there's /usr/bin/gcc-4.0 > and /opt/local/bin/ppc-apple-darwin9-gcc-7.5.0 == /opt/local/bin/gcc > too) and tries to use it

Re: port:audacity up for grabs

Rene, our loss. Thanks so much for all that you have contributed over the years! Ken

Re: Should I expect a +quartz variant to propagate to dependencies, and overrule existing variants?

> Should I expect a +quartz variant to propagate to dependencies, and > overrule existing variants? propagate to dependencies? Yes. You demonstrated that already when you tried to install gimp +quartz and it passed that down to deps. overrule existing variants? No. If you already have a

Re: Is there a well-defined way to do "bleeding edge" ports? Should there be one?

You can (for yourself) just change the github commit to HEAD and you’ll get the latest commit. Disable the checksum phase if you do that. I often do that in some of my local portfile overlay repos for my own uses, but you can’t do that for macports in general as Ryan points out as the builds

Re: A simple request (MkHexGrid) turned into ...

> On May 14, 2022, at 1:21 PM, Mojca Miklavec wrote: > > See: > > https://github.com/macports/macports-ports/blob/master/multimedia/dav1d/Portfile#L47-L50 > suggesting that this looks like a workaround for a bug in the meson > build system that has been ignored for more than a year: >

Re: A simple request (MkHexGrid) turned into ...

It was a couple of years ago I fixed up ICU — so I don’t recall just now a specific python 2.7 reason. Bootstrapping maybe. Sorry, Ken > On May 14, 2022, at 9:27 AM, Mojca Miklavec wrote: > > On Sat, 14 May 2022 at 16:20, Michael wrote: >> >> So I thought I'd install a simple little hex

Re: Replacement Options for Discontinued macOS Server

I took an old, useless-for-macOS Intel system and installed Ubuntu 20.04 on it. A Core2 Duo with 2GB ram is fine for this. letsencrypt manages all the certificate renewals automatically for all my ssl domains every 90 days or so. I installed it a few years ago and never thought about it again.

Re: What is up with perl5.26 on Snow Leo?

> On Nov 27, 2021, at 8:09 PM, Ryan Schmidt wrote: > > On Nov 27, 2021, at 19:58, Ken Cunningham wrote: > >>> Ok... the significance of this is...?? >> Well in your case, the significance of appears overwhelming — in that it is >> an excellent clue as to the

Re: What is up with perl5.26 on Snow Leo?

> Ok... the significance of this is...?? Well in your case, the significance of appears overwhelming — in that it is an excellent clue as to the cause of your problem, I believe. ie - there is nothing wrong on your system, it is nothing you did, it is not your fault, indeed something has

Re: What is up with perl5.26 on Snow Leo?

all the perl ports were specifically changed to use /usr/bin/cc in the commit below, but something in this plan seems to be not working out:

Re: multi-ask

Yeah, I guess that website name is a little bit too close to "emasculation" for my memory to bring it forward :> K > On Nov 21, 2021, at 9:40 AM, chilli.names...@gmail.com wrote: > > I think you meant > > https://www.emaculation.com/forum/viewtopic.php?t=7361 >

Re: multi-ask

When I last updated the basiliskii and sheepshaver ports I was still fairly new to macports and took them on as a challenge. They had some interesting wrinkles I was looking to understand. At that time, both of them did not run well when built as 64-bit versions; the JIT code, that really

Re: mango linking question

Nothing important, we think. When we first started building ports with the buildbot using BigSur, we built with the system of the time which was BigSur 11.2, so some of the builds were marked with that system as a floor. We later decided hat it would be better to build against the lowest

Re: What version of Xcode for which macOS ?

One thing that may not be clear from our table is that in several cases the buildbot (and therefore our recommended) Xcode has been held back from the latest available version. This was done to have an SDK version that matches the OS version. This is somewhat problematic as the App store prompts

Re: MacPorts for High Sierra?

> On Aug 15, 2021, at 6:43 PM, Dave Horsfall wrote: > https://everymac.com/mac-answers/macos-11-big-sur-faq/macos-big-sur-macos-11-compatbility-list-system-requirements.html > >System Requirements > >In marketing and technical documentation and elsewhere, Apple >specifies that

Re: MacPorts for High Sierra?

> On Aug 15, 2021, at 6:25 PM, Dave Horsfall wrote: > > I had to upgrade this old MacBook Pro (mid 2010) from Sierra to High Sierra > to run some software that I needed, and now I find that MacPorts wants Big > Sur which this thing won't run (and I can't afford a new one). > > So, is there

Re: Building icu port on macos x tiger

s.1.dylib or /opt/local/lib/libgcc/libgcc_s.1.dylib since >> the symbols used would be in both (by explicitly not using ___divmoddi4 >> optimization during compilation). >> >> I'll see about sorting out where Trac is and recreating the issue as time >> permits. >&

Re: Building icu port on macos x tiger

ms to be looking in the wrong libgcc_s for this particular > symbol. How would I force the OS to look in the right place instead of just > adjusting the compiler to not use this optimization? > > Thanks. > > On Sat, Jun 26, 2021 at 7:12 PM Ken Cunningham < > ken.cunningham

Re: Building icu port on macos x tiger

> dlopen(/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/libxml2mod.so, > 2): Symbol not found: ___divmoddi4 Referenced from: /opt/local/lib/libicui18n.67.dylib > resulting from the default build configuration of macports icu on Tiger? Assuming you

Re: unexpected warning from dylib

> My MacOS version is fully up to date 11.4, and my Xcode is fully up to date > (12.5) and I’m seeing these warnings: > > ld: warning: dylib (/opt/local/lib/libidn2.dylib) was built for newer macOS > version (11.3) than being linked (11.0) > ld: warning: dylib (/opt/local/lib/libzstd.dylib) was

Re: Why don't p5-* ports mark their dependencies?

I think Bill perhaps then you really want to open a thread with the title: “I would like to suggest we move MacPorts default perl to 5.30 now”. And then let the conversation happen, and if the outcome is “Yes” then that will happen. Or 5.32. Whatever you care to suggest. But trying to fight

Re: Why don't p5-* ports mark their dependencies?

macports recommended perl is still 5.28 $ port info perl5 perl5 @5.28.3 (lang) Sub-ports:perl5.16, perl5.18, perl5.20, perl5.22, perl5.24, perl5.26, perl5.28, perl5.30, perl5.32 Variants: perl5_26, [+]perl5_28, perl5_30 so that is supposed to be the default perl for

Re: Error building "gq"

> error: incomplete definition of type 'struct x509_st' would most likely mean the software needs to either use the older openssl 1.0 (via PG perhaps) or be updated to use the newer openssl 1.1 (look upstream or elsewhere for patches). These build issues are best managed via tickets, of

Re: MacPorts 2.7.0 has been released

my SnowLeopard macports-base built and installed just fine. As Chris says, post up your config log and we might see the error. Or — simpler perhaps -- just try to build any “hello_world.c” program at all with your llvm-gcc-4.2 compiler and you might find out how it is broken. I seem to

Re: Reclaim was not 'safe'

> Isn't that just sudo port setrequested installed That’s what I’ve always done to avoid this, also having been burned by it once years ago: sudo port setrequested installed sudo port -v reclaim K

Re: OpenMPI Users - Is Anyone Using openmpi-clang33 or openmpi-clang34?

; Chris > >> On 7 May 2021, at 8:11 pm, Ken Cunningham >> wrote: >> >> Yes, gcc7 works down to 10.4, both PPC and Intel and is the primary >> compiler there. I can see no need for openMPI to support any older gcc. >> >> clang-3.3, clang-3.4, an

Re: OpenMPI Users - Is Anyone Using openmpi-clang33 or openmpi-clang34?

Yes, gcc7 works down to 10.4, both PPC and Intel and is the primary compiler there. I can see no need for openMPI to support any older gcc. clang-3.3, clang-3.4, and clang-3.7 should not be used for anything other than bootstrapping to newer clangs now. Ken

Re: Using macports-libcxx to build a non-MacPorts cmake project

; going to take to mean I was doing it right all along, and Dolphin just isn't > going to be amenable to building this way. My shared_mutex-free build mostly > works anyway. > > > On May 3, 2021, at 5:46 PM, Ken Cunningham <mailto:ken.cunningham.web...@gmail.com>> wrote:

Re: Error: Failed to build source-highlight: command execution failed

> That log shows that you are back at the original problem, whose proposed > solution was to force the use of a newer version of the clang compiler > by running these: At least we can get source-highlight off this table, and then if there is some other problem with clang-9.0, fix that.

Re: Error: Failed to build source-highlight: command execution failed

I believe this should be fixed now (fix works for me on 10.7). please wait a bit for the commits to propagate through (couple of hours) and then try your build again and I hope this brings you success. best, K

Re: Issue compiling simple code with clang++-mp-11

this should be fixed now, for clang-11 at least, courtesy of @landonf finding the relevant upstream commit in the llvm tree and backporting it to clang-11. Ken

Re: Using macports-libcxx to build a non-MacPorts cmake project

what you did actually might have worked, I think, ideally… too bad it didn’t. Can you do this perhaps? export CXXFLAGS="-nostdinc++ -I/opt/local/include/libcxx/v1” export LDFLAGS="-L/opt/local/lib/libcxx" or maybe this: CXX=/path/to/clang-9.0 CXXFLAGS="-nostdinc++

Re: Error: Failed to build source-highlight: command execution failed

To hopefully solve your browser spinning-beachball problem at developer.apple.com, the browsers-for-older-systems market has had a lot of activity lately. For 10.7 (and probably 10.7 to 10.9) the nicest, most capable one I have seen lately is a legacy version of Chromium that seems to work really

Re: Installing universal binaries on Apple M1 using macports

. Thank you for your responses and sorry for the noise. On Wed, Mar 31, 2021 at 12:30 AM Ken Cunningham <mailto:ken.cunningham.web...@gmail.com>> wrote: and the command I used is: *% sudo port install llvm-10 +universal* But, what I see is: *% otool -l /opt/local/libexe

Re: Installing universal binaries on Apple M1 using macports

> and the command I used is: > *% sudo port install llvm-10 +universal* > > But, what I see is: > *% otool -l /opt/local/libexec/llvm-10/lib/libLLVM.dylib| grep "minos\|sdk"* > minos 11.0 > sdk 11.1 > > The sdk version looks fine, but why the minos is 11.0? shouldn't it be > 10.14 as

Re: Class wxDisclosureNSButton is implemented in both … One of the two will be used. Which one is undefined.

wxWidgets-3.0 on the buildbot was built back in January when install_name_tool had a bug in it. That bug has since been fixed. sudo port -f uninstall wxWidgets-3.0 sudo port -v -s install wxWidgets-3.0 should get you fixed up. Someone might

Re: cMP w/ 256 GB RAM

My own pair of classic MacPros are set up in a similar way. I find it a very impressive and flexible setup indeed. I have the MacPros running the current BigSur, and they can multi-boot to 10.15, 10.14, 10.6, and 10.5. The more powerful system also boots into Windows10, where the new FlightSim

Re: Writing a Portfile for the Zig language / lld

right now... Best, K On Thursday, March 25, 2021, wrote: > 2021. 3. 26. 오전 6:07, Ken Cunningham 작성: > > > > People are invited to kick the tires on this PR. > > > > I put this lld addition to the clang-11 port together for some early > testers <https://github

Re: Writing a Portfile for the Zig language / lld

People are invited to kick the tires on this PR. I put this lld addition to the clang-11 port together for some early testers feedback appreciated.

Writing a Portfile for the Zig language / lld

lld would best be an addition to our existing llvm tree build, when added. (libomp builds separately for historical reasons going back many years, but that should be folded in too at some point.) It's not particularly difficult to add to our llvm build, as I mentioned yesterday. But it's not a

clang++ and libc++

I undertook some further refinements and put together a port for this. The "macports-libcxx" port will install the needed libc++ libraries and the matching headers, with the needed minor tweak to disable the availability test you ran across. The port notes explain how to use it, and there is more

Re: Forcing python39 on M1

> Having heard that python39 is the only one (so far) to compile natively on > M1, I’m trying to force the python ports I use to python39 Hello Peter, FYI, an arm64 version of python38 appears to be available: http://packages.macports.org/python38/python38-3.8.8_0.darwin_20.arm64.tbz2 and is

Re: Apple notarisation process - LC_VERSION_MIN_MACOSX

Both versions of the load command are still in use. The cutoff for which load command gets used appears to be based on the deployment target that has been set. The clang driver (and ld64) then uses the right one, depending on that. A deployment target of 10.14+ will set LC_BUILD_VERSION. A

Re: Apple notarisation process - LC_VERSION_MIN_MACOSX

here. K On Friday, March 5, 2021, Rainer Müller wrote: > On 05/03/2021 04.43, Ken Cunningham wrote: > > Apple is not using LC_VERSION_MIN_MACOSX any longer, as at least one > helpful > > person pointed out. So — we will never “fix” the problem of this not > being >

Re: Apple notarisation process - LC_VERSION_MIN_MACOSX

> On Mar 3, 2021, at 11:50 AM, Ken Cunningham > wrote: > The LC_VERSION_MIN_MACOSX issue is interesting. > > There is lots of code in ld64 that appears designed to add this, and to fall > back on the DEPLOYMENT_TARGET to set it if it's not on the command line, and >

Fwd: Apple notarisation process - LC_VERSION_MIN_MACOSX

sent this to the dev list due to finger slip on ipad buttons... -- Forwarded message -- From: *Ken Cunningham* Date: Wednesday, March 3, 2021 Subject: Apple notarisation process - LC_VERSION_MIN_MACOSX To: macports-dev We really should have MacPorts libs be utilizable

re: clang++ and libc++

As of clang-11, the most current libc++ is installed tucked away in the llvm-11 libs dir. There is both a dylib (rpathed) and a static libc++ there. I set this up for now for people like you to use for exactly this. You will have to force it (DYLD_LIBRARY_PATH, possibly static link it, or some

Re: Building Clang 8/9 in El Capitan

typo, of course. I meant compiler.cxx_standard 2017 compiler.thread_local_storage yes I'm typing this in TenFourFox right now on Tiger ;> K On Sat, Feb 13, 2021 at 3:25 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > To try to make bootstrapping clang and llvm

Re: Building Clang 8/9 in El Capitan

by upending what amounts to many hours of work first by Jeremy and then by me to make this work properly. Ken On Sat, Feb 13, 2021 at 2:35 AM Ryan Schmidt wrote: > > > On Feb 13, 2021, at 03:42, Ken Cunningham wrote: > > > Thread local includes __thread, Thread_local, and thread_l

Re: Building Clang 8/9 in El Capitan

> On Feb 13, 2021, at 1:27 AM, Ryan Schmidt wrote: > > > I would consider it unreasonable to ask users to be aware of the existence of > our buildbot infrastructure or what versions of Xcode we have installed on > the buildbot workers and to ask them to duplicate it. > > I didn't mention

Re: Building Clang 8/9 in El Capitan

I would suggest you install Xcode 8.2.1 to match the buildbots. Don’t forget that in almost all cases, MacPorts will use the SDK installed in “/“ when building software. That SDK is the 10.11 SDK, so it is the one that matches your system, and is the one you want. Virtually all standard “open

Re: Building Clang 8/9 in El Capitan

Both clang-8.0 and clang-9.0 having been building properly for us on the buildbots and (when I last did it) locally for me, on ElCap. See and the one for clang-8.0. But your logic is flawed about why you want it, as no clang version provides

Re: stdlib.h compilation error for macports gcc9.

Our fix changed the baked-in gcc SDK reference from using the MacOSX11.x  and above  to MacOSX.sdk. that fixes a number of broken systems, but not all it appears. Perhaps we should find a way to broaden that down to including MacOSX10.15+ as well, if Catalina is going to be using the

  1   2   3   4   5   6   >