From noreply at macports.org Thu Dec 1 00:11:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 00:11:27 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.07bf9cf25ff3a6e7df8ceda3a98dba77@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by kencu): I have the stock path setup, for both user and root: {{{ PATH=/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin }}} I am not sure what, if anything, is in your path that may or may not cause trouble, but it is a 10 second fix to check if the stock path fixes you up, and then you'll know. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 00:58:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 00:58:13 -0000 Subject: [MacPorts] #66273: gnutls @3.6.16_4 does not build on PPC Tiger, Mac OS X 10.4.11, because a configure script hangs in an endless loop? In-Reply-To: <046.e16508a5b2a332ccdb03cba6976587c5@macports.org> References: <046.e16508a5b2a332ccdb03cba6976587c5@macports.org> Message-ID: <061.349bd2075c410167a864f3f554bf9d62@macports.org> #66273: gnutls @3.6.16_4 does not build on PPC Tiger, Mac OS X 10.4.11, because a configure script hangs in an endless loop? -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: gnutls | -------------------------+----------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: Yes, mine installs fine without any trouble: {{{ $ port -v installed gnutls The following ports are currently installed: gnutls @3.6.16_4 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-11-30T16:49:43-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 01:59:44 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 01:59:44 -0000 Subject: [MacPorts] #66274: jdupes @1.21.0 does not build on PPC Tiger, Mac OS X 10.4.11, because Makefile seems to need a more up-to-date make In-Reply-To: <046.f9685e30fe3d2086d8a2b309f8aff7f9@macports.org> References: <046.f9685e30fe3d2086d8a2b309f8aff7f9@macports.org> Message-ID: <061.631e2755634da288172f4a10e8f4fb52@macports.org> #66274: jdupes @1.21.0 does not build on PPC Tiger, Mac OS X 10.4.11, because Makefile seems to need a more up-to-date make ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: jdupes | ------------------------+----------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"dbffcd4651c2575fde245c750589eea74ea20321/macports-ports" dbffcd4651c2575fde245c750589eea74ea20321/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dbffcd4651c2575fde245c750589eea74ea20321" jdupes: use a newer make command on Tiger closes: https://trac.macports.org/ticket/66274 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 02:27:53 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 02:27:53 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.a2b9b7bdfd4edc6a23c1ab62213d7a8a@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by kencu): confirmed this issue on clean TIgerPPC system. Fix is not presently obvious to me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 02:32:50 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 02:32:50 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.ab6db2ba9509d8b894e969713e053061@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by kencu): same issue on 3.84 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 04:48:20 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 04:48:20 -0000 Subject: [MacPorts] #66373: beets-full @1.6.0: Failed to mirror beets-full: The requested URL returned error: 404 Not Found In-Reply-To: <047.589ff3e76037bd696b1d99cf36178055@macports.org> References: <047.589ff3e76037bd696b1d99cf36178055@macports.org> Message-ID: <062.4bf0e2e97be286d579a2a084cf3713fc@macports.org> #66373: beets-full @1.6.0: Failed to mirror beets-full: The requested URL returned error: 404 Not Found -------------------------+-------------------- Reporter: ryandesign | Owner: catap Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: beets-full | -------------------------+-------------------- Changes (by catap): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"368de35a6115367a263fc7986fe577675100a032/macports-ports" 368de35a6115367a263fc7986fe577675100a032/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="368de35a6115367a263fc7986fe577675100a032" beets-full: fix mirroring Closes: https://trac.macports.org/ticket/66373 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 08:10:01 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 08:10:01 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.3ab40e077f336b11cd426570337ac3fd@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by coolstars21): > /opt/local/bin/python3.10 -c "import numpy ; print(numpy.__version__)" 1.23.5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 09:27:04 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 09:27:04 -0000 Subject: [MacPorts] #66352: clang-15: unable to locate default SDK In-Reply-To: <043.dd7d4114c232db35c8b48d405978fe84@macports.org> References: <043.dd7d4114c232db35c8b48d405978fe84@macports.org> Message-ID: <058.0c0a1e5bef449058d3d1be636c6f9ca7@macports.org> #66352: clang-15: unable to locate default SDK -----------------------+----------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura, x86_64 Port: clang-15 | -----------------------+----------------------------- Comment (by judaew): Thank you for taking the time for me. After rebuilding this port with Xcode installed, the issue disappeared. Currently, Clang finds SDKs both with and without Xcode. P.S. If anyone gets this issue, then the best workaround without Xcode is the SDKROOT variable. It should help Clang find a path to the SDK. {{{ export SDKROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk" # or export SDKROOT=$(xcrun --show-sdk-path) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 09:27:23 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 09:27:23 -0000 Subject: [MacPorts] #66352: clang-15: unable to locate default SDK In-Reply-To: <043.dd7d4114c232db35c8b48d405978fe84@macports.org> References: <043.dd7d4114c232db35c8b48d405978fe84@macports.org> Message-ID: <058.8b824861c159392047f3121869dbf958@macports.org> #66352: clang-15: unable to locate default SDK -------------------------+----------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura, x86_64 Port: clang-15 | -------------------------+----------------------------- Changes (by judaew): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 11:04:30 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 11:04:30 -0000 Subject: [MacPorts] #66376: brightness @1.2: failed to get brightness of display 0x1 (error -536870201) (was: "brightness @1.2" fails on my M1 macbook pro) In-Reply-To: <051.58ab50aa178dff4e1cd2395cf3992bec@macports.org> References: <051.58ab50aa178dff4e1cd2395cf3992bec@macports.org> Message-ID: <066.c41dd72a8f10106c3e9d1a38f8e6f38c@macports.org> #66376: brightness @1.2: failed to get brightness of display 0x1 (error -536870201) -----------------------------+-------------------- Reporter: MaurizioLoreti | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: arm64 Port: brightness | -----------------------------+-------------------- Changes (by ryandesign): * keywords: => arm64 Comment: This was fixed in the brightness repository last year: https://github.com/nriley/brightness/pull/36 But the developer has not yet released a new version containing the fix: https://github.com/nriley/brightness/issues/38 Nobody maintains this port. Feel free to submit pull requests to improve it, for example to include a patch based on the upstream PR (taking note that one changed line in the PR was not intentional, was reverted later, and should not be included in a port patch). The ideal solution would be for the developer to release a new version containing the fix so that we can simply update to that version. You could encourage the developer to do that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 11:10:34 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 11:10:34 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.920c41196a7cfca2f7cf7652db1d85c5@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by ryandesign): The log you attached is very short. Please attach the entire main.log file, compressing it first if it is large. The log says it was determined that `-latomic` was needed. I would be interested in seeing how that determination was reached, because it may be wrong. (Hopefully, the full log file will tell us.) The log says you are on arm64. `-latomic` is needed on some other operating systems on ARM processors but in my experience it is not needed on macOS. The log shows that items within the path /Users/kaufmannm/Library/R are being used. I wonder why that is. Surely we don't want that. Maybe that is the cause of the problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 11:11:45 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 11:11:45 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.f64280584d0961fe15bf4850c1351dec@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by ryandesign): Replying to [comment:1 ryandesign]: > ~~The log you attached is very short. Please attach the entire main.log file, compressing it first if it is large.~~ Never mind; the error is not when installing the R port, but when using R to install something else. > > The log says it was determined that `-latomic` was needed. I would be interested in seeing how that determination was reached, because it may be wrong. ~~(Hopefully, the full log file will tell us.)~~ The log says you are on arm64. `-latomic` is needed on some other operating systems on ARM processors but in my experience it is not needed on macOS. > > The log shows that items within the path /Users/kaufmannm/Library/R are being used. I wonder why that is. Surely we don't want that. Maybe that is the cause of the problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 12:24:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 12:24:09 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.0c2e713d6f0d9ed2e2d20f02bf703fa6@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by MarcKaufmann): Yes, sorry I didn't make it even clearer that the R install worked fine, but the package did not.Should I attach something else or what should I try next? I am a Mac with Apple M1, Ventura 13.0.1. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 12:28:00 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 12:28:00 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.0e88cd042dee258066183d3b63aec80b@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): I think I fixed the PATH issue. Particularly GNU Emacs, in which I work with MacPorts, has a proper process environment. It's "tested" by logging out and in and by rebooting. Final proof: icu built ? without the balign patch in icu-devel. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 13:28:03 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 13:28:03 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.cc31152a4fb17b317fed265aed84ce79@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by kencu): that?s great! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 13:53:29 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 13:53:29 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.9f2c98f461a1c2c7c5dd85fd7d6e308c@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by michaelld): OK; that's good. What about `python3.10 -c "import numpy ; print(numpy.version)"` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 14:08:11 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 14:08:11 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.49e851e4f2caf9c3ba2543e996bc9ef2@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by coolstars21): > /opt/local/bin/python3.10 -c "import numpy ; print(numpy.version)" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 14:19:54 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 14:19:54 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.5bcf58496b4da70b77cd23d2517dc0d2@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by michaelld): OK that looks good too -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 14:21:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 14:21:09 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.7cfbcc35783557da359582676d44068e@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by michaelld): I'll note that the [https://ports.macports.org/all_builds/?port_name=py310-scipy MP builders succeed with `py310-numpy` for all OSX >= 10.7] ... but that there is no macOS 13 builder up yet. It builds for me on my macOS 13.1-beta Intel computer: {{{ % mp_host_info macOS 13.1 22C5050e Xcode 14.1 14B47b % port -v installed py310-scipy The following ports are currently installed: py310-scipy @1.9.3_0+gfortran+openblas (active) requested_variants='' platform='darwin 22' archs='x86_64' date='2022-11-17T18:14:48-0500' }}} I don't have a macOS 13 ARM64 computer up right now, but at least one log shows building for Intel. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 14:22:00 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 14:22:00 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.b1084cbd35f9d9857eebcab28e8171f3@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by michaelld): Comparing build logs (mine versus the one here), there are no real differences. Just for some reason it fails for folks here but it doesn't for me or the MP builders. So strange! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 15:25:29 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 15:25:29 -0000 Subject: [MacPorts] #66369: qt5-qtwebengine @5.15.11_1 build failure: 'CoreFoundation/CFSocket.h' file not found In-Reply-To: <043.e5040f8ab7aa9bc5166e8e54aba626d0@macports.org> References: <043.e5040f8ab7aa9bc5166e8e54aba626d0@macports.org> Message-ID: <058.8e0366805b06c5ebcf868f570bd43b98@macports.org> #66369: qt5-qtwebengine @5.15.11_1 build failure: 'CoreFoundation/CFSocket.h' file not found ------------------------------+--------------------------------- Reporter: dbl001 | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: qt5-qtwebengine | ------------------------------+--------------------------------- Comment (by dbl001): It's working now ... not sure what's changed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 16:24:17 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 16:24:17 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.33bff4b2ec4d50ddef963615bfb81eff@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): When will GCC 1x test work start? In case this has some time I would boot into Leopard and clean it from Python 3.9 and old stuff. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 17:50:40 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 17:50:40 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.4eefb6de96a76a177d40e68267bc2942@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by ballapete): There is an easy patch available: {{{ --- mesonbuild/scripts/symbolextractor.py~ 1970-01-01 01:00:00.000000000 +0100 +++ mesonbuild/scripts/symbolextractor.py 2022-12-01 18:32:05.000000000 +0100 @@ -146,8 +146,7 @@ break result = [arr[match + 2], arr[match + 5]] # Libreoffice stores all 5 lines but the others seem irrelevant. # Get a list of all symbols exported - output = call_tool('nm', ['--extern-only', '--defined-only', - '--format=posix', libfilename]) + output = call_tool('nm', ['-a', '-U', '-P', libfilename]) if not output: dummy_syms(outfilename) return }}} Comparing the output of `llvm-nm` as an example of a modern version of `nm` with that of old standard `nm` I get on the command line: {{{ /opt/local/lib/libcharset.1.dylib(single module): 00000000 U ____mb_cur_max_l U ____mb_cur_max_l 00000b9c t ___initialize_Cplusplus 00000b9c t ___initialize_Cplusplus 00000b7c t __dyld_func_lookup 00000b7c t __dyld_func_lookup 00000000 T __mh_dylib_header 00000000 t __mh_dylib_header 00000da6 s _alias_table 00000da6 s _alias_table 00000ce4 T _libcharset_set_relocation_prefix 00000ce4 T _libcharset_set_relocation_prefix 00000bf8 T _locale_charset 00000bf8 T _locale_charset 00000000 U _nl_langinfo U _nl_langinfo 00000000 U _strcmp U _strcmp 00000000 U _uselocale U _uselocale 00000b74 t cfm_stub_binding_helper 00000b74 t cfm_stub_binding_helper 0000101c s dyld__mach_header 0000101c d dyld__mach_header 00000b44 t dyld_stub_binding_helper 00000b44 t dyld_stub_binding_helper pete 256 /\ llvm-nm --defined-only /opt/local/lib/libcharset.1.dylib pete 257 /\ nm -U /opt/local/lib/libcharset.1.dylib /opt/local/lib/libcharset.1.dylib(single module): 00000b9c t ___initialize_Cplusplus 00000b9c t ___initialize_Cplusplus 00000b7c t __dyld_func_lookup 00000b7c t __dyld_func_lookup 00000000 T __mh_dylib_header 00000000 t __mh_dylib_header 00000da6 s _alias_table 00000da6 s _alias_table 00000ce4 T _libcharset_set_relocation_prefix 00000ce4 T _libcharset_set_relocation_prefix 00000bf8 T _locale_charset 00000bf8 T _locale_charset 00000b74 t cfm_stub_binding_helper 00000b74 t cfm_stub_binding_helper 0000101c s dyld__mach_header 0000101c d dyld__mach_header 00000b44 t dyld_stub_binding_helper 00000b44 t dyld_stub_binding_helper pete 258 /\ llvm-nm --format=posix /opt/local/lib/libcharset.1.dylib pete 259 /\ nm -P /opt/local/lib/libcharset.1.dylib /opt/local/lib/libcharset.1.dylib(single module): ____mb_cur_max_l U 00000000 ____mb_cur_max_l U 0 0 ___initialize_Cplusplus t 00000b9c ___initialize_Cplusplus t b9c 0 __dyld_func_lookup t 00000b7c __dyld_func_lookup t b7c 0 __mh_dylib_header T 00000000 __mh_dylib_header t 0 0 _alias_table s 00000da6 _alias_table s da6 0 _libcharset_set_relocation_prefix T 00000ce4 _libcharset_set_relocation_prefix T ce4 0 _locale_charset T 00000bf8 _locale_charset T bf8 0 _nl_langinfo U 00000000 _nl_langinfo U 0 0 _strcmp U 00000000 _strcmp U 0 0 _uselocale U 00000000 _uselocale U 0 0 cfm_stub_binding_helper t 00000b74 cfm_stub_binding_helper t b74 0 dyld__mach_header s 0000101c dyld__mach_header d 101c 0 dyld_stub_binding_helper t 00000b44 dyld_stub_binding_helper t b44 0 }}} I had to insert two empty lines into the output of `llvm-nm` in order to get matching lines, because `nm` first outputs an empty line and then the path name of the shared library. Alas, to see before an after I tried to build `libepoxy` before patching `meson` ? and ran into a problem: {{{ Library dl found: YES Checking for function "dlvsym" with dependency -ldl: NO Run-time dependency appleframeworks found: NO (tried framework) test/meson.build:164:2: ERROR: Dependency "appleframeworks" not found, tried framework }}} Have to git there a bit? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 19:52:10 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 19:52:10 -0000 Subject: [MacPorts] #66379: onetbb fails to build as +universal on 10.6.8 (i386+x86_64): error: unused function 'impl_zone_enable_discharge_checking' In-Reply-To: <049.79abdc933203116287962171b077fa27@macports.org> References: <049.79abdc933203116287962171b077fa27@macports.org> Message-ID: <064.79f853411278aaabbd9b73c822f15451@macports.org> #66379: onetbb fails to build as +universal on 10.6.8 (i386+x86_64): error: unused function 'impl_zone_enable_discharge_checking' ---------------------------+------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: onetbb | ---------------------------+------------------------- Comment (by catap): Sergey, https://github.com/macports/macports-ports/pull/16866 should fix it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 20:23:52 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 20:23:52 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.5bae3dd3808f456eec212f72f85b6196@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by tomio-arisaka): Replying to [comment:3 ballapete]: > > {{{ > Library dl found: YES > Checking for function "dlvsym" with dependency -ldl: NO > Run-time dependency appleframeworks found: NO (tried framework) > > test/meson.build:164:2: ERROR: Dependency "appleframeworks" not found, tried framework > }}} > > Have to dig there a bit? see : https://github.com/macports/macports- ports/commit/9eaac52d45e052d7ed33e6c493fd47893107695b#comments -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:14:55 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 22:14:55 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 Message-ID: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 -----------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: libepoxy -----------------------+---------------------- In the last two weeks I started to upgrade my ports from `Python 3.9 to Python 3.10`: {{{ libepoxy @1.5.9_2+python38 (active) requested_variants='+python38' platform='darwin 8' archs='ppc' date='2022-01-23T11:34:00+0100' libepoxy @1.5.9_2+python39 requested_variants='' platform='darwin 8' archs='ppc' date='2022-05-14T22:59:07+0200' libepoxy @1.5.10_0+python39 (active) requested_variants='+python39' platform='darwin 8' archs='ppc' date='2022-05-15T21:52:11+0200' libepoxy @1.5.10_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-11-27T00:04:33+0100' -- meson @0.55.3_1 (active) requested_variants='' platform='darwin 8' archs='noarch' date='2020-10-22T16:38:21+0200' meson @0.58.2_0 (active) requested_variants='' platform='darwin 8' archs='noarch' date='2022-01-15T17:53:45+0100' meson @0.58.2_0 (active) requested_variants='' platform='darwin 8' archs='noarch' date='2022-05-14T13:27:31+0200' meson @0.58.2_0 (active) requested_variants='' platform='darwin 8' archs='noarch' date='2022-11-27T09:45:01+0100' }}} Today I tried to fix `meson`s `wrong handling of nm arguments` or `handling of wrong nm arguments` (the use of `llvm-nm` would be an alternative): {{{ --- mesonbuild/scripts/symbolextractor.py~ 1970-01-01 01:00:00.000000000 +0100 +++ mesonbuild/scripts/symbolextractor.py 2022-12-01 18:32:05.000000000 +0100 @@ -146,8 +146,7 @@ break result = [arr[match + 2], arr[match + 5]] # Libreoffice stores all 5 lines but the others seem irrelevant. # Get a list of all symbols exported - output = call_tool('nm', ['--extern-only', '--defined-only', - '--format=posix', libfilename]) + output = call_tool('nm', ['-a', '-U', '-P', libfilename]) if not output: dummy_syms(outfilename) return }}} Since I recorded some time ago that `meson` has a problem with `nm` when `building libepoxy` I first tried to build this port again to see whether the fault persists with `Python 3.10`. But the build stops during configuration phase: {{{ Checking for function "dlvsym" with dependency -ldl: NO Run-time dependency appleframeworks found: NO (tried framework) test/meson.build:164:2: ERROR: Dependency "appleframeworks" not found, tried framework A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_graphics_libepoxy/libepoxy/work/build /meson-logs/meson-log.txt }}} This log file has at the end: {{{ Run-time dependency appleframeworks found: NO (tried framework) test/meson.build:164:2: ERROR: Dependency "appleframeworks" not found, tried framework }}} The test in `test\meson.build` is: {{{ 162 # Apple 163 if host_machine.system().contains('darwin') 164 opengl_dep = dependency('appleframeworks', modules: ['OpenGL', 'Carbon'], required: true) 165 166 cgl_tests = [ 167 [ 'cgl_core', [ 'cgl_core.c' ] ], 168 [ 'cgl_epoxy_api', [ 'cgl_epoxy_api.c' ] ], 169 ] 170 171 foreach t: cgl_tests 172 test_name = t[0] 173 test_sources = t[1] 174 175 test(test_name, 176 executable( 177 test_name, test_sources, 178 c_args: test_cflags, 179 include_directories: libepoxy_inc, 180 dependencies: [ libepoxy_dep, opengl_dep ], 181 ), 182 ) 183 endforeach 184 endif }}} Is the cause of failure due to building `libepoxy without Python support`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:16:05 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 22:16:05 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> References: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> Message-ID: <061.4c98d74612d58bf0cb4e3a6feafb39a4@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: libepoxy | ------------------------+----------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Tiger, Mac OS X 10.4.11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:17:47 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 22:17:47 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> References: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> Message-ID: <061.f933c85a9e363edc6298de534e9f8b43@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: libepoxy | ------------------------+----------------------- Changes (by ballapete): * Attachment "meson-log.txt" added. The mentioned meson-log.txt -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:24:29 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 22:24:29 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> References: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> Message-ID: <061.af0f301884f34f646d805ed409ae1384@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: libepoxy | ------------------------+----------------------- Comment (by ballapete): These `Apple Mac OS X Frameworks` are installed: {{{ AGL: Version: 2.5.6 Zuletzt ge?ndert: 27.04.13 22:14 Informationen: OpenGL Carbon compatibility dylib for Mac OS X Ort: /System/Library/Frameworks/AGL.framework Carbon: Version: 10.4 Zuletzt ge?ndert: 27.04.13 22:12 Ort: /System/Library/Frameworks/Carbon.framework GLUT: Version: 3.3.8 Zuletzt ge?ndert: 27.04.13 22:12 Informationen: 3.3.8, Copyright (c) 2001-2005 Apple Computer Inc., All Rights Reserved Ort: /System/Library/Frameworks/GLUT.framework OpenGL: Version: 1.4.7 Zuletzt ge?ndert: 27.04.13 22:14 Informationen: OpenGL 1.4.7.14.0 Ort: /System/Library/Frameworks/OpenGL.framework }}} and they have some content: {{{ pete 281 /\ gdu -sh /System/Library/Frameworks/{AGL,Carbon,GLUT,OpenGL}.framework/Versions 336K /System/Library/Frameworks/AGL.framework/Versions 127M /System/Library/Frameworks/Carbon.framework/Versions 868K /System/Library/Frameworks/GLUT.framework/Versions 8,6M /System/Library/Frameworks/OpenGL.framework/Versions }}} and `mesa` is installed as well: {{{ mesa @22.1.7_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-11-28T12:37:46+0100' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:30:19 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 22:30:19 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> References: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> Message-ID: <061.f21a6f560c9433a643a5eb4fad089097@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: libepoxy | ------------------------+----------------------- Comment (by ballapete): {{{ -rw-r--r-- 1 root x11 2177 15 Mai 2022 /opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/graphics/libepoxy/Portfile }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 22:39:50 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 22:39:50 -0000 Subject: [MacPorts] #66332: R @4.2.2_1: error when trying to install.packages possibly due to port/rpath configuration In-Reply-To: <049.95b055d4821921b36e9d80de1acc65cb@macports.org> References: <049.95b055d4821921b36e9d80de1acc65cb@macports.org> Message-ID: <064.010ef9fd178bd44113417ca01bb9736a@macports.org> #66332: R @4.2.2_1: error when trying to install.packages possibly due to port/rpath configuration ---------------------------+------------------------ Reporter: MarcKaufmann | Owner: i0ntempest Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: R | ---------------------------+------------------------ Changes (by i0ntempest): * owner: (none) => i0ntempest * status: new => closed * resolution: => fixed Comment: In [changeset:"cd25817fe917d2b042a63e4b8d1bf5633c8d499d/macports-ports" cd25817fe917d2b042a63e4b8d1bf5633c8d499d/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="cd25817fe917d2b042a63e4b8d1bf5633c8d499d" R: fix broken ldflag Closes: https://trac.macports.org/ticket/66332 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 23:06:15 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 23:06:15 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated Message-ID: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated -------------------------+--------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: TeXShop -------------------------+--------------------- So, 2 separate bugs here: 1 is TeXShop using Sparkle, which MacPorts has tried to remove from other ports when possible, 2 is the update, which is confirmed by livecheck: {{{ $ port -v livecheck TeXShop TeXShop seems to have been updated (port version: 4.79, new version: 5.04) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 23:06:58 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 23:06:58 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.589af07720a18e3f67e2d7da29641134@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: TeXShop | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "Screen Shot 2022-12-01 at 18.04.13.png" added. screenshot of TeXShop Sparkle updater prompt -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 1 23:39:31 2022 From: noreply at macports.org (MacPorts) Date: Thu, 01 Dec 2022 23:39:31 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.e35c05cbfc416bad25948ee891910442@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by ballapete): Replying to [comment:4 tomio-arisaka]: > Replying to [comment:3 ballapete]: > see : https://github.com/macports/macports- ports/commit/9eaac52d45e052d7ed33e6c493fd47893107695b#comments When will a `correct Portfile` be available? (I have no idea how to deal with the texts on that github pge.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 00:29:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 00:29:13 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.9a9f7fed7018efd75a1ef04653a32f0f@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: TeXShop | --------------------------+-------------------- Comment (by Schamschula): Two things: 1) I'll have to disable livecheck for older macOS versions that are incompatible with TeXShop 5 2) TeXShop is the second GUI app I've run across to use Sparkle (owncloud- client is the other). I'll see if I can fix that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 01:06:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 01:06:37 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.9f31bcb95cfa7acc8a48bd0b70e862c0@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: TeXShop | --------------------------+-------------------- Comment (by cooljeanius): Another app where Sparkle had to be disabled/removed that you can look at for reference would be GitUp; see #63684 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 01:33:26 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 01:33:26 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.dd8b5cff346d51d0475dea38f9209726@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: TeXShop | --------------------------+-------------------- Comment (by Schamschula): If it were only this easy. I got rid of Sparkle in owncloud-client using cmake. TeXShop is an Xcode project. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 02:03:07 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 02:03:07 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 Message-ID: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> #66383: WIP new port: snac2 ------------------------+---------------------- Reporter: artkiver | Owner: (none) Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ------------------------+---------------------- I've been making some headway with creating a Portfile for snac2 (https://codeberg.org/grunfink/snac2/) a minimal ActivityPub/FediVerse/Mastodon implemented in C. With much thanks to jmr and neverpanic for getting it this far. It now builds and I see a binary under the work/snac2/ subdirectory when I run port -v install, but the install portion errors out. Creating a ticket here to attach the Portfile as well as Makefile.patch and main.log for reference to the errors generated in hopes that some additional eyeballs may be able to assist. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 02:04:44 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 02:04:44 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.fc29412513d998ec505368ad99fc5182@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: (none) Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Portfile" added. Preliminary Portfile for WIP snac2 MacPort -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 02:05:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 02:05:18 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.d91bef2273ce0592c279548a195c5173@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: (none) Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Makefile.patch" added. Makefile diff patch for WIP snac2 MacPort -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 02:06:07 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 02:06:07 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.abe7d7bf4565bcaa268b1260f87f4a26@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: (none) Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "main.log" added. main.log output with errors from port -v install (seems to build OK and create a binary, but errors out during the install phase?) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 02:06:30 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 02:06:30 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.95e3aff9970c8320bb530ba2304e893e@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * owner: (none) => artkiver -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:33:05 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:33:05 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Makefile.patch" removed. Makefile diff patch for WIP snac2 MacPort -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:33:06 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:33:06 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.7ceba38e647a409c2ffcb0035d752b17@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Makefile.patch" added. Makefile patch for CFLAGS parameters simplified due to modified Portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:35:17 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:35:17 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Portfile" removed. Preliminary Portfile for WIP snac2 MacPort -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:35:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:35:18 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.0ae729d9e06b99ef93a6df60250b3bb3@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Portfile" added. port lint --nitpick cleaned up Portfile with some other minor modifications -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:40:57 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:40:57 -0000 Subject: [MacPorts] #60273: mail-server installs /Library/LaunchDaemons/org.macports.logrotate.plist not registered to port In-Reply-To: <047.e23745bb2842e11dd1040e937ca73a4f@macports.org> References: <047.e23745bb2842e11dd1040e937ca73a4f@macports.org> Message-ID: <062.f1bfb35d6c6302aebea927b324f3a5b5@macports.org> #60273: mail-server installs /Library/LaunchDaemons/org.macports.logrotate.plist not registered to port --------------------------+----------------------- Reporter: ryandesign | Owner: essandess Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: Port: mail-server | --------------------------+----------------------- Changes (by essandess): * status: reopened => closed * resolution: => fixed Comment: In [changeset:"3cda5d271a22d5d33849caa255dba94a804ce14f/macports-ports" 3cda5d271a22d5d33849caa255dba94a804ce14f/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3cda5d271a22d5d33849caa255dba94a804ce14f" mail-server: Update to version 1.5 * Fixes: https://trac.macports.org/ticket/60273 * Fix logrotate permission issue * Migrate to EC P-384 default x509 certificates }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:43:51 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:43:51 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "main.log" removed. main.log output with errors from port -v install (seems to build OK and create a binary, but errors out during the install phase?) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 04:43:51 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 04:43:51 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.c38fe1e9e98f4dc118b2cddad5c74567@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "main.log" added. main.log of port -v install from most recent version seems to be an issue with destroot? running make install manually from the working directory functions OK -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 05:28:07 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 05:28:07 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Portfile" removed. port lint --nitpick cleaned up Portfile with some other minor modifications -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 05:28:08 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 05:28:08 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.0f76ca134739adc0fe970df2bfabd839@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Portfile" added. Portfile minorly changed, seems to function correctly mostly thanks to some additional changes to Makefile.patch -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 05:29:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 05:29:20 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Makefile.patch" removed. Makefile patch for CFLAGS parameters simplified due to modified Portfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 05:29:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 05:29:20 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.3ecb51e8f110dc4155967c65b4f2aad8@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * Attachment "Makefile.patch" added. Added some $(DESTDIR) parameters as suggested by Eric Borisch @eborisch at fosstodon.org which seems to have done the trick to get install functioning! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 07:20:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 07:20:55 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.6d240ae82740d7e73dd51e8a4bfa5dfa@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by barracuda156): Replying to [comment:20 kencu]: > here is my port of mpich-default 4.0.3. Passes all tests. Thank you! Any idea why was it even disabled? I looked through the existing `mpich` port, and it takes little to enable `mpich-default` from there. Also, it appears that `mpich-default` is technically non-different from `mpich-gcc12` (or whatever is the default system compiler). The only thing required is blacklist old GCCs, like you have done, or otherwise set C++11 standard (TBH, I did not check if that is required, but given that `gcc-4.2` does not build it, failing immediately at configure, I guess yes), so that correct GCC is used. P. S. Also `+native` needs a fix for PPC, like I did for `folly` or smth alike (`-march=native` is not supported with PPC). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 07:26:46 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 07:26:46 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.679de09d1979cc2d5dc520b7093feaed@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by barracuda156): Replying to [comment:18 kencu]: > OK, please post up the actual proven build successes you have (in the PR, or some other place than this scalapack ticket). > > No committer will be able to take anyone's word for this as there are too many opportunities for errors and too many systems to cover off. In fact you should be able to see that from statistics. For example, you can see `libgcc9` installed for PPC: https://ports.macports.org/port/libgcc9/stats/ TBH, I do not get why you doubt that so much, given that we know for the fact that `gcc11` and `gcc12` build and work on PPC across three systems, starting from Leopard. Moreover, all GCCs are supported by upstream ??so they must build, unless Macports break something on its side. There is nothing surprising in that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 07:46:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 07:46:37 -0000 Subject: [MacPorts] #66376: brightness @1.2: failed to get brightness of display 0x1 (error -536870201) In-Reply-To: <051.58ab50aa178dff4e1cd2395cf3992bec@macports.org> References: <051.58ab50aa178dff4e1cd2395cf3992bec@macports.org> Message-ID: <066.7c22238355a2a29d0d2fb9ccee537e85@macports.org> #66376: brightness @1.2: failed to get brightness of display 0x1 (error -536870201) -----------------------------+-------------------- Reporter: MaurizioLoreti | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: arm64 Port: brightness | -----------------------------+-------------------- Comment (by MaurizioLoreti): Solved. {{{ 1) go to https://github.com/nriley/brightness , download and unpack the software 2) cd brightness-master 3) CC=clang make 4) mv brightness.arm64 to brightness in your $PATH 5) enjoy }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 08:18:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 08:18:24 -0000 Subject: [MacPorts] #66384: py27-openssl: Please downgrade to 21.0.0 Message-ID: <047.76e3cd8af4225a1f3bbf773f8632d336@macports.org> #66384: py27-openssl: Please downgrade to 21.0.0 ------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-openssl ------------------------+--------------------------------- After upgrading ports on the [https://build.macports.org MacPorts buildmaster], I could not start the buildmaster anymore: {{{ Unhandled Error Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/application/app.py", line 674, in run runApp(config) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/scripts/twistd.py", line 25, in runApp runner.run() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/application/app.py", line 381, in run self.application = self.createOrGetApplication() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/application/app.py", line 453, in createOrGetApplication application = getApplication(self.config, passphrase) --- --- File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/application/app.py", line 464, in getApplication application = service.loadApplication(filename, style, passphrase) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/application/service.py", line 416, in loadApplication application = sob.loadValueFromFile(filename, 'application') File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/persisted/sob.py", line 177, in loadValueFromFile eval(codeObj, d, d) File "buildbot.tac", line 4, in from buildbot.master import BuildMaster File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/buildbot/master.py", line 23, in from twisted.internet import reactor File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/reactor.py", line 38, in from twisted.internet import default File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/default.py", line 56, in install = _getInstallFunction(platform) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/default.py", line 50, in _getInstallFunction from twisted.internet.selectreactor import install File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/selectreactor.py", line 18, in from twisted.internet import posixbase File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/posixbase.py", line 18, in from twisted.internet import error, udp, tcp File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/tcp.py", line 31, in from twisted.internet._newtls import ( File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/internet/_newtls.py", line 21, in from twisted.protocols.tls import TLSMemoryBIOFactory, TLSMemoryBIOProtocol File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/twisted/protocols/tls.py", line 41, in from OpenSSL.SSL import Error, ZeroReturnError, WantReadError File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import SSL, crypto File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/OpenSSL/SSL.py", line 9, in from OpenSSL._util import ( exceptions.SyntaxError: invalid syntax (_util.py, line 21) Failed to load application: invalid syntax (_util.py, line 21) }}} Downgrading py27-openssl from 22.1.0_0 to 21.0.0_0 fixed it. All [changeset:0c80f6b154e81936e780b9ed497f2ca20ad05526/macports-ports py- openssl subports were upgraded to 22.1.0] but [https://pyopenssl.org/en/stable/changelog.html#id4 version 22.0.0 dropped support for Python 2.7] so py27-openssl should be pinned to version 21.0.0. The epoch for py27-openssl should be increased when this is done so that users who already upgraded to 22.1.0 will receive the downgrade. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 11:38:03 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 11:38:03 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.47619c9b7ca04d1a247fa29db75478b3@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by tomio-arisaka): I said "see : https://github.com/macports/macports- ports/commit/9eaac52d45e052d7ed33e6c493fd47893107695b#comments". It means that meson port has been broken since commit 9eaac52d45e052d7ed33e6c493fd47893107695b.\\ So we need the previous version of it. For example, I got it as follows: {{{ $ git clone https://github.com/macports/macports-ports.git $ cd ./macports-ports/ $ git checkout 9eaac52d45e052d7ed33e6c493fd47893107695b $ git log -n 2 commit 9eaac52d45e052d7ed33e6c493fd47893107695b (HEAD) Author: barracuda156 Date: Fri May 13 07:53:47 2022 +0800 meson: update to 0.62.1, add cross-files for ppc & ppc64 commit 2fd08a21f3008e8d8f6a2901bf74da1a4471cf05 Author: usersxx <97012123+usersxx at users.noreply.github.com> Date: Sun May 15 21:34:46 2022 +0530 openjdkXX: fix builds $ git checkout 2fd08a21f3008e8d8f6a2901bf74da1a4471cf05 $ find . -iname 'meson' -type d ./devel/meson }}} Then I think you can also get the previous version of the patch file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 14:22:01 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 14:22:01 -0000 Subject: [MacPorts] #62977: Build noarch ports on 11_arm64 builder In-Reply-To: <043.b4006bb99a45ff144ae4365fc8576c59@macports.org> References: <043.b4006bb99a45ff144ae4365fc8576c59@macports.org> Message-ID: <058.fe761592b8e8d53fbd0e730f15c6b454@macports.org> #62977: Build noarch ports on 11_arm64 builder ----------------------------+--------------------- Reporter: jmroot | Owner: admin@? Type: enhancement | Status: closed Priority: Normal | Milestone: Component: buildbot/mpbb | Version: Resolution: fixed | Keywords: Port: | ----------------------------+--------------------- Comment (by ryandesign): This change is finally deployed to the buildmaster. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 14:49:32 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 14:49:32 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.e43464ff56a202621850e3b2ad7cac72@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by ballapete): I found on macOS High Sierra, Version 10.13 or Darwin 17, and macOS Monterey, Version 12 or Darwin 21, that /usr/bin/nm understands both, BSD "-a" and Linux "--extern-only". Presumingly some more versions behave like them so that the following patch, in Attachments, can be used on Macs? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 14:51:08 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 14:51:08 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.8c090f20e75446224a0ee8d998276c2f@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Changes (by ballapete): * Attachment "patch-meson-BSD-nm.diff" added. Patch to convert Linux style arguments into BSD styles arguments for nm (/usr/bin/nm) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:15:11 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 15:15:11 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.82a9ed1b92c615862ee7cb430ab1eb08@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by kencu): Replying to [comment:22 barracuda156]: > TBH, I do not get why you doubt that so much I doubt it so much because I've been watching well-meaning PRs fail for many years now, and I have in particular seen how fragile building gcc can be, especially in the "non-sterile" MacPorts environment. How do you think I got to know Iain so well in the first place ;> Anyway, if it builds so easily, folks should have no trouble showing that. I can't get anything useful off of the stats website for this question as I would have no idea how they built it, if they did build it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:46:21 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 15:46:21 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.f5ddc05055213eb11b2d2fa630c7a26e@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by barracuda156): Replying to [comment:23 kencu]: > Anyway, if it builds so easily, folks should have no trouble showing that. Well, I have no trouble showing that, but what would you consider the evidence? :) P. S. But again, ''we do not need any of libgccs aside of libgcc12 in order to move to gcc12.'' -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 15:48:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 15:48:24 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.2d793ef6ca9dc20c0b5290421916cc12@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by barracuda156): On a side-note, I have built `mpich-default` on 10.6 by simply allowing it in the portfile. Wonder why at all it was banned in the first place. It does not seem to need any kind of hacks whatsoever. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 16:11:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 16:11:40 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.49d2e9e7a0db797aa0bd1b79982bcbb9@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by ballapete): Nice surprise on PPC Leopard, Mac OS X 10.5.8: {{{ leopard pete 223 /\ /usr/bin/nm -U /opt/local/lib/libcharset.dylib /usr/bin/nm: invalid argument -U Usage: /usr/bin/nm [-agnoprumxjlfAP[s segname sectname] [-] [-t format] [[-arch ] ...] [file ...] leopard pete 224 /\ /usr/bin/nm --defined-only /opt/local/lib/libcharset.dylib /usr/bin/nm: invalid argument -- Usage: /usr/bin/nm [-agnoprumxjlfAP[s segname sectname] [-] [-t format] [[-arch ] ...] [file ...] }}} The man page describes -U? `llvm-nm` works correctly. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 17:57:08 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 17:57:08 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.ac3be4ed464837bf9d432ef498a480f4@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by kencu): the older appleframeworks patchfile was restored here: https://github.com/macports/macports- ports/commit/439761774952ff3cc28fb3ce336bc94f1de71bea and pango builds again on tiger with this change. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 17:59:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 17:59:19 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.7c4f713db5f63440740f090df772cd0e@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by kencu): Replying to [comment:24 barracuda156]: > P. S. But again, ''we do not need any of libgccs aside of libgcc12 in order to move to gcc12.'' P.S. But again, gcc7 and all older gccs will then be broken :> -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 17:59:35 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 17:59:35 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.7492dbff36e56ac82dfe13454cecd971@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by ballapete): Interestingly versions 3.84 and 3.85 both build on PPC Leopard? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:00:36 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 18:00:36 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.0f24d6d289e4340976cadb790aad3714@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by kencu): Replying to [comment:24 barracuda156]: > Well, I have no trouble showing that, but what would you consider the evidence? :) Somebody putting their name down beside verification that the given gcc did indeed build on the given system with the given PR. So that later, if/when the build fails, we know who to ask. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:12:45 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 18:12:45 -0000 Subject: [MacPorts] #66348: logrotate: doesn't install default startitem In-Reply-To: <042.894e49dd09e4098f944a6f4d04dc3c36@macports.org> References: <042.894e49dd09e4098f944a6f4d04dc3c36@macports.org> Message-ID: <057.0ce02e7a56a991a213d9a5f6104f36eb@macports.org> #66348: logrotate: doesn't install default startitem ------------------------+------------------------ Reporter: catap | Owner: ctreleaven Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: logrotate | ------------------------+------------------------ Changes (by ctreleaven): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:14:56 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 18:14:56 -0000 Subject: [MacPorts] #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default In-Reply-To: <049.6cea1f4702984048c25e24fb39a71452@macports.org> References: <049.6cea1f4702984048c25e24fb39a71452@macports.org> Message-ID: <064.024874ecea3685655a763477eb857de9@macports.org> #66307: Scalapack: will not configure properly on PPC since mpi PG cannot handle mpich-gcc* but wants mpich-default ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: scalapack | ---------------------------+------------------------------------------- Comment (by kencu): Anyway, I think it's time to stop talking about hypotheticals in this scalapack ticket, and put the effort into the actual PR. So no more responses about libgcc/gcc from me here. Re: mpich-default -- that was a project I undertook 18 months ago that I eventually gave up on and wrote my own. If you can sell a PR to the maintainers, feel free to float one. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 18:57:51 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 18:57:51 -0000 Subject: [MacPorts] #66383: WIP new port: snac2 In-Reply-To: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> References: <045.3ad68e57b85152c71c8a7536894cbe61@macports.org> Message-ID: <060.18256b563c550617bd23e607f3634c40@macports.org> #66383: WIP new port: snac2 -------------------------+---------------------- Reporter: artkiver | Owner: artkiver Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: | -------------------------+---------------------- Changes (by artkiver): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"dd77cc1ae6d4fe757efc8f0710da5c433b988482/macports-ports" dd77cc1ae6d4fe757efc8f0710da5c433b988482/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dd77cc1ae6d4fe757efc8f0710da5c433b988482" snac: new Portfile for a minimalistic ActivityPub instance in C. (#16871) * version 2.12 closes: https://trac.macports.org/ticket/66383 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:39:06 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:39:06 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.d2a95721ff5ae2ec0023a0b1dd08a21d@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by kencu): the problem here is the gmake port, currently at version 4.4, is too new to build this, but the make on Tiger is too old. So, we need a new plan. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:43:39 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:43:39 -0000 Subject: [MacPorts] #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined Message-ID: <049.1d82130b540711fe530066891970425e@macports.org> #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined --------------------------+------------------------- Reporter: barracuda156 | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: SoapyRTLSDR --------------------------+------------------------- {{{ [100%] Linking CXX shared module librtlsdrSupport.so /opt/local/bin/cmake -E cmake_link_script CMakeFiles/rtlsdrSupport.dir/link.txt --verbose=ON /opt/local/bin/g++-mp-12 -pipe -Os -DNDEBUG -I/opt/local/include -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++11 -std=c++11 -Wc++11-extensions -O3 -DNDEBUG -arch ppc -mmacosx-version-min=10.6 -bundle -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names -o librtlsdrSupport.so CMakeFiles/rtlsdrSupport.dir/Registation.cpp.o CMakeFiles/rtlsdrSupport.dir/Settings.cpp.o CMakeFiles/rtlsdrSupport.dir/Streaming.cpp.o CMakeFiles/rtlsdrSupport.dir/Version.cpp.o -Wl,-rpath,/opt/local/lib /opt/local/lib/librtlsdr.dylib -pthread /opt/local/lib/libSoapySDR.0.8.1.dylib -Wl,--no-undefined -pthread -flat_namespace ld: unknown option: --no-undefined collect2: error: ld returned 1 exit status make[2]: *** [librtlsdrSupport.so] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_SoapyRTLSDR/SoapyRTLSDR/work/build' make[1]: *** [CMakeFiles/rtlsdrSupport.dir/all] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_SoapyRTLSDR/SoapyRTLSDR/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_SoapyRTLSDR/SoapyRTLSDR/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_SoapyRTLSDR/SoapyRTLSDR/work/build" && /usr/bin/make -j6 -w all VERBOSE=ON Exit code: 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:44:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:44:40 -0000 Subject: [MacPorts] #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined In-Reply-To: <049.1d82130b540711fe530066891970425e@macports.org> References: <049.1d82130b540711fe530066891970425e@macports.org> Message-ID: <064.2bc1fe89ed1bc471437db36f6f08a7ea@macports.org> #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined ---------------------------+---------------------- Reporter: barracuda156 | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: SoapyRTLSDR | ---------------------------+---------------------- Changes (by barracuda156): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:44:51 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:44:51 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.aa8c13488b484feaeb0b9d8a9199b897@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"0022160d24a12bf9018a501b7ae34c4f2b22be51/macports-ports" 0022160d24a12bf9018a501b7ae34c4f2b22be51/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0022160d24a12bf9018a501b7ae34c4f2b22be51" nss: use gmake-apple on Tiger the make in the gmake port is too new for this build closes: https://trac.macports.org/ticket/66270 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:46:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:46:34 -0000 Subject: [MacPorts] #66386: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable Message-ID: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> #66386: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable --------------------+-------------------- Reporter: dbl001 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: R --------------------+-------------------- Building 'R' on MacOS Ventura 13.0.1 {{{ % xcrun --show-sdk-path /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk }}} {{{ :info:build /opt/local/bin/clang-mp-14 -I"../../../../include" -DNDEBUG -I../../../include -I../../../../src/include -DHAVE_CONFIG_H -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -fPIC -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64 -fobjc-exceptions -c qdCocoa.m -o qdCocoa.o :info:build qdBitmap.c:61:39: warning: 'CFURLCreateStringByAddingPercentEscapes' is deprecated: first deprecated in macOS 10.11 - Use [NSString stringByAddingPercentEncodingWithAllowedCharacters:] instead, which always uses the recommended UTF-8 encoding, and which encodes for a specific URL component or subcomponent (since each URL component or subcomponent has different rules for what characters are valid). [-Wdeprecated- declarations] :info:build CFStringRef pathEscaped = CFURLCreateStringByAddingPercentEscapes(kCFAllocatorDefault, pathString, NULL, NULL, kCFStringEncodingUTF8); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFURL.h:408:13: note: 'CFURLCreateStringByAddingPercentEscapes' has been explicitly marked deprecated here :info:build CFStringRef CFURLCreateStringByAddingPercentEscapes(CFAllocatorRef allocator, CFStringRef originalString, CFStringRef charactersToLeaveUnescaped, CFStringRef legalURLCharactersToBeEscaped, CFStringEncoding encoding) API_DEPRECATED("Use [NSString stringByAddingPercentEncodingWithAllowedCharacters:] instead, which always uses the recommended UTF-8 encoding, and which encodes for a specific URL component or subcomponent (since each URL component or subcomponent has different rules for what characters are valid).", macos(10.0,10.11), ios(2.0,9.0), watchos(2.0,2.0), tvos(9.0,9.0)); :info:build ^ :info:build devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable :info:build atsFont = ATSFontFindFromName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:811:1: note: 'ATSFontFindFromName' has been explicitly marked unavailable here :info:build ATSFontFindFromName( :info:build ^ :info:build devQuartz.c:662:27: error: 'ATSFontFindFromPostScriptName' is unavailable :info:build atsFont = ATSFontFindFromPostScriptName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:828:1: note: 'ATSFontFindFromPostScriptName' has been explicitly marked unavailable here :info:build ATSFontFindFromPostScriptName( :info:build ^ :info:build devQuartz.c:689:27: error: 'ATSFontFindFromName' is unavailable :info:build atsFont = ATSFontFindFromName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:811:1: note: 'ATSFontFindFromName' has been explicitly marked unavailable here :info:build ATSFontFindFromName( :info:build ^ :info:build devQuartz.c:690:41: error: 'ATSFontFindFromPostScriptName' is unavailable :info:build if (!atsFont) atsFont = ATSFontFindFromPostScriptName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:828:1: note: 'ATSFontFindFromPostScriptName' has been explicitly marked unavailable here :info:build ATSFontFindFromPostScriptName( :info:build ^ :info:build devQuartz.c:696:35: error: 'ATSFontFindFromName' is unavailable :info:build atsFont = ATSFontFindFromName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:811:1: note: 'ATSFontFindFromName' has been explicitly marked unavailable here :info:build ATSFontFindFromName( :info:build ^ :info:build devQuartz.c:702:39: error: 'ATSFontFindFromName' is unavailable :info:build atsFont = ATSFontFindFromName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:811:1: note: 'ATSFontFindFromName' has been explicitly marked unavailable here :info:build ATSFontFindFromName( :info:build ^ :info:build devQuartz.c:710:35: error: 'ATSFontFindFromName' is unavailable :info:build atsFont = ATSFontFindFromName(cfFontName, kATSOptionFlagsDefault); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Headers/ATSFont.h:811:1: note: 'ATSFontFindFromName' has been explicitly marked unavailable here :info:build ATSFontFindFromName( :info:build ^ :info:build devQuartz.c:729:12: warning: 'CGFontCreateWithPlatformFont' is deprecated: first deprecated in macOS 10.6 - No longer supported [-Wdeprecated-declarations] :info:build return CGFontCreateWithPlatformFont(&atsFont); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/CoreGraphics.framework/Headers/CGFont.h:64:32: note: 'CGFontCreateWithPlatformFont' has been explicitly marked deprecated here :info:build CG_EXTERN CGFontRef __nullable CGFontCreateWithPlatformFont( :info:build ^ :info:build devQuartz.c:1012:5: warning: 'CGContextShowGlyphsWithAdvances' is deprecated: first deprecated in macOS 10.9 - No longer supported [-Wdeprecated-declarations] :info:build CGContextShowGlyphsWithAdvances(ctx,glyphs, g_adv, len); :info:build ^ :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/System/Library/Frameworks/CoreGraphics.framework/Headers/CGContext.h:1070:16: note: 'CGContextShowGlyphsWithAdvances' has been explicitly marked deprecated here :info:build CG_EXTERN void CGContextShowGlyphsWithAdvances(CGContextRef cg_nullable c, :info:build ^ :info:build 2 warnings and 7 errors generated. :info:build 1 warning generated. :inf }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:46:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:46:53 -0000 Subject: [MacPorts] #66386: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable In-Reply-To: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> References: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> Message-ID: <058.ecec563c1b96a213cb17ea16d7b12ba3@macports.org> #66386: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable ---------------------+-------------------- Reporter: dbl001 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------+-------------------- Changes (by dbl001): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 21:48:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 21:48:40 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.08378c8dda03ad3bfaae404ce1ccd417@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by ballapete): Did `nss` build for you on `Tiger with gmake`? I think I tried it myself and also reached the fault. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:00:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:00:19 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.d2cb5d48af882906baa601d53f19e0f3@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by kencu): gmake in the gmake port is too new. this fixes it -- give a while to come you're way and enjoy! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:03:29 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:03:29 -0000 Subject: [MacPorts] #66386: R @4.2.2_2 build failure: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable (was: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable) In-Reply-To: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> References: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> Message-ID: <058.d69f44dfd18901c8758aaae16e20686f@macports.org> #66386: R @4.2.2_2 build failure: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable ---------------------+------------------------ Reporter: dbl001 | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------+------------------------ Changes (by jmroot): * cc: kjellpk (added) * status: new => assigned * owner: (none) => i0ntempest -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:03:30 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:03:30 -0000 Subject: [MacPorts] #66386: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable In-Reply-To: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> References: <043.bac97a1af19eab6bba8b03156f6d3adb@macports.org> Message-ID: <058.aee5ff46ddd54bf2ac6d6992a96644eb@macports.org> #66386: devQuartz.c:660:23: error: 'ATSFontFindFromName' is unavailable ------------------------+-------------------- Reporter: dbl001 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: R | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => duplicate Comment: #66095 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:04:27 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:04:27 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.d3b15adc0e259d574ffe235db1ecb9ce@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+---------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------------------+---------------------- Comment (by kencu): perhaps someone might plug this into the current portfile, until a new version comes out? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:11:00 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:11:00 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.1803b8429e4388a076527ea736bbd6fb@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+---------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------------------+---------------------- Comment (by kencu): This worked in qt4-mac: {{{ platform darwin 22 { macosx_deployment_target 12.0 } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:11:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:11:37 -0000 Subject: [MacPorts] #66187: Error: Failed to build R: command execution failed In-Reply-To: <043.a0b0096939574148b1cc6012fd166bb1@macports.org> References: <043.a0b0096939574148b1cc6012fd166bb1@macports.org> Message-ID: <058.3643d5dec5c363a9baebd469e8bfba39@macports.org> #66187: Error: Failed to build R: command execution failed ------------------------+------------------------ Reporter: dbl001 | Owner: i0ntempest Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: R | ------------------------+------------------------ Comment (by kencu): This worked in qt4-mac: {{{ platform darwin 22 { macosx_deployment_target 12.0 } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:58:35 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:58:35 -0000 Subject: [MacPorts] #66096: libevent @2.12.12_1: Fails when libressl @3.6.0 installed, due to BIO_get_init In-Reply-To: <048.d33c032d557b6cfd8afb1c57fbcb27e6@macports.org> References: <048.d33c032d557b6cfd8afb1c57fbcb27e6@macports.org> Message-ID: <063.76b5e9362147c208c926bd787db3e273@macports.org> #66096: libevent @2.12.12_1: Fails when libressl @3.6.0 installed, due to BIO_get_init ---------------------------------+----------------------- Reporter: daphnediane | Owner: jerryyhom Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: haspatch Port: libevent, libressl | ---------------------------------+----------------------- Comment (by artkiver): Tested the patch locally and it seems to function OK. Added notes to: https://github.com/macports/macports- ports/pull/16681/files but I do not have commit access, so someone else will need to merge this PR. Regardless, it looks OK to me! Thank you for your contributions and sorry for the delay in replying. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 22:58:47 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 22:58:47 -0000 Subject: [MacPorts] #66031: selfupdate throws error changing directory permissions on Monterey and Big Sur In-Reply-To: <048.0de81a973a47b4e4a4f6cea869adbe58@macports.org> References: <048.0de81a973a47b4e4a4f6cea869adbe58@macports.org> Message-ID: <063.0f60f2a0ac86ed83c644787646973315@macports.org> #66031: selfupdate throws error changing directory permissions on Monterey and Big Sur --------------------------+-------------------------------------- Reporter: petermichor | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: catalina bigsur monterey Port: | --------------------------+-------------------------------------- Comment (by ballapete): The same is true for `macOS High Sierra, Version 10.13.6` ? it works all from `~root`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:08:45 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:08:45 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.ffebf5473ccd26f044aa8942483c57be@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+--------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: R | ---------------------------------+--------------------- Changes (by i0ntempest): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"de78e1b2bf3fc86d66ae4a0d4c036981f30d8067/macports-ports" de78e1b2bf3fc86d66ae4a0d4c036981f30d8067/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="de78e1b2bf3fc86d66ae4a0d4c036981f30d8067" R: temporary fix for building on macOS 13 Closes: https://trac.macports.org/ticket/66095 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:26:46 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:26:46 -0000 Subject: [MacPorts] #66346: meson @0.58.2 seems to have a flaw with "nm" In-Reply-To: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> References: <046.6bc6d0d2836b5d3a40b6e0635145626e@macports.org> Message-ID: <061.8ddea621adc19a9c07cedb0a93c76166@macports.org> #66346: meson @0.58.2 seems to have a flaw with "nm" ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: meson | ------------------------+----------------------- Comment (by ballapete): Somewhere else on Github I am "discussing" meson using faulty options: https://github.com/mesonbuild/meson/discussions/11131. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:37:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:37:13 -0000 Subject: [MacPorts] #66269: mesa @22.1.7 does not build on PPC Tiger, Mac OS X 10.4.11, because of inappropriate format specifiers In-Reply-To: <046.f35ebbc129a163e9256268d8f01c84a0@macports.org> References: <046.f35ebbc129a163e9256268d8f01c84a0@macports.org> Message-ID: <061.01a8025c3d96daf4a5c3074df4c186b5@macports.org> #66269: mesa @22.1.7 does not build on PPC Tiger, Mac OS X 10.4.11, because of inappropriate format specifiers ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: mesa | ------------------------+----------------------- Comment (by kencu): closed by https://github.com/macports/macports- ports/commit/478db3b45321e52f34a2bfe3b9a7a406f8cb486c -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:38:41 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:38:41 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> References: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> Message-ID: <061.e1c8b3ba827358e6229d1e33a7f87102@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: libepoxy | ------------------------+----------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: fixed by: https://github.com/macports/macports- ports/commit/439761774952ff3cc28fb3ce336bc94f1de71bea -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:39:29 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:39:29 -0000 Subject: [MacPorts] #66269: mesa @22.1.7 does not build on PPC Tiger, Mac OS X 10.4.11, because of inappropriate format specifiers In-Reply-To: <046.f35ebbc129a163e9256268d8f01c84a0@macports.org> References: <046.f35ebbc129a163e9256268d8f01c84a0@macports.org> Message-ID: <061.16a472bd731c8fb4f3ab9489dd43ca05@macports.org> #66269: mesa @22.1.7 does not build on PPC Tiger, Mac OS X 10.4.11, because of inappropriate format specifiers ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: mesa | ------------------------+----------------------- Changes (by kencu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:42:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:42:34 -0000 Subject: [MacPorts] #66377: libtermkey @0.22_1: Portfile has a typo In-Reply-To: <046.3059f4b5afd69ce7b24c451179ee8782@macports.org> References: <046.3059f4b5afd69ce7b24c451179ee8782@macports.org> Message-ID: <061.c6ca1d5a905edd814214a16da565f78a@macports.org> #66377: libtermkey @0.22_1: Portfile has a typo -------------------------+-------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: libtermkey | -------------------------+-------------------- Changes (by Ken <21211439+kencu@?>): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"87ce0dabbd1da8f1043b64b5bbae41d6c296faef/macports-ports" 87ce0dabbd1da8f1043b64b5bbae41d6c296faef/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="87ce0dabbd1da8f1043b64b5bbae41d6c296faef" libtermkey: fix minor typo closes: https://trac.macports.org/ticket/66377 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 2 23:48:48 2022 From: noreply at macports.org (MacPorts) Date: Fri, 02 Dec 2022 23:48:48 -0000 Subject: [MacPorts] #66283: compilers portgroup uses -rpath on Tiger In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.a552811d0e23c968a521929a51af678b@macports.org> #66283: compilers portgroup uses -rpath on Tiger ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176 | ------------------------+----------------------- Comment (by kencu): How is that getting added, I wonder. The PG tests for gcc10 or greater, or devel: {{{ if { ${gcc_v} >= 10 || ${gcc_v} == "devel" } { configure.ldflags-delete -Wl,-rpath,${prefix}/lib/libgcc configure.ldflags-append -Wl,-rpath,${prefix}/lib/libgcc } }}} and you're using gcc7, so it should not be added to your build. Anyway, soon enough there will be a gcc10 on Tiger, so the test might as well be fixed to not use rpaths on Tiger, assuming MacPorts is going to keep supporting Tiger much longer. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 00:01:15 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 00:01:15 -0000 Subject: [MacPorts] #65208: py39-gobject3 fails to configure on Rosetta: ERROR: Include dir /opt/local/share/gobject-introspection-1.0/tests does not exist In-Reply-To: <049.5eba2e7ee1c03097d659a253033187d9@macports.org> References: <049.5eba2e7ee1c03097d659a253033187d9@macports.org> Message-ID: <064.dec778c823db8d157ee18a471052b23f@macports.org> #65208: py39-gobject3 fails to configure on Rosetta: ERROR: Include dir /opt/local/share/gobject-introspection-1.0/tests does not exist -------------------------------------+------------------------------------- Reporter: barracuda156 | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: powerpc, snowleopard, Port: py-gobject3, gobject- | rosetta introspection | -------------------------------------+------------------------------------- Comment (by barracuda156): The problem still persists, both when using `meson` 0.63.3 and the latest 0.64.1. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 00:07:50 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 00:07:50 -0000 Subject: [MacPorts] #64521: irssi fails to build for ppc on 10.6.8 (Rosetta) In-Reply-To: <049.d2f969d118ed23a382f8aac9e5ff15d7@macports.org> References: <049.d2f969d118ed23a382f8aac9e5ff15d7@macports.org> Message-ID: <064.d83813c9622a4bfcd3d12770bc84fc86@macports.org> #64521: irssi fails to build for ppc on 10.6.8 (Rosetta) ---------------------------+----------------------------------------- Reporter: barracuda156 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: powerpc snowleopard rosetta Port: irssi | ---------------------------+----------------------------------------- Comment (by barracuda156): I guess the problem is that the port build system fails to pass Macports archflags at linking stage: {{{ /usr/bin/cc -bundle -undefined dynamic_lookup -L/opt/local/lib -Wl,-headerpad_max_install_names -fstack-protector Channel.o Client.o Ctcp.o Dcc.o Irc.o Modes.o Netsplit.o Notifylist.o Query.o Server.o -o blib/arch/auto/Irssi/Irc/Irc.bundle \ \ ld: warning: in Channel.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Client.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Ctcp.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Dcc.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Irc.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Modes.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Netsplit.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Notifylist.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Query.o, file was built for ppc7400 which is not the architecture being linked (x86_64) ld: warning: in Server.o, file was built for ppc7400 which is not the architecture being linked (x86_64) chmod 755 blib/arch/auto/Irssi/Irc/Irc.bundle }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 00:09:40 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 00:09:40 -0000 Subject: [MacPorts] #64521: irssi fails to build for ppc on 10.6.8 (Rosetta) In-Reply-To: <049.d2f969d118ed23a382f8aac9e5ff15d7@macports.org> References: <049.d2f969d118ed23a382f8aac9e5ff15d7@macports.org> Message-ID: <064.fb997c9415b2dad70de18146391556da@macports.org> #64521: irssi fails to build for ppc on 10.6.8 (Rosetta) ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, snowleopard, rosetta Port: irssi | ---------------------------+------------------------------------------- Changes (by barracuda156): * keywords: powerpc snowleopard rosetta => powerpc, snowleopard, rosetta * owner: (none) => l2dy * version: 2.7.1 => 2.8.0 * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 00:24:27 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 00:24:27 -0000 Subject: [MacPorts] #64521: irssi fails to build for ppc on 10.6.8 (Rosetta) In-Reply-To: <049.d2f969d118ed23a382f8aac9e5ff15d7@macports.org> References: <049.d2f969d118ed23a382f8aac9e5ff15d7@macports.org> Message-ID: <064.4b9990a62bd22acf59f0a6c861b695f8@macports.org> #64521: irssi fails to build for ppc on 10.6.8 (Rosetta) ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: powerpc, snowleopard, rosetta Port: irssi | ---------------------------+------------------------------------------- Comment (by kencu): and should not see /usr/bin/cc being used ever? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 01:56:25 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 01:56:25 -0000 Subject: [MacPorts] #66371: Duplicate gopass-summon-provider Ports In-Reply-To: <042.2a6b2b5cf96540b7ed7f47ae24f1b886@macports.org> References: <042.2a6b2b5cf96540b7ed7f47ae24f1b886@macports.org> Message-ID: <057.e0e8579dfeaba97117a9095db1b64372@macports.org> #66371: Duplicate gopass-summon-provider Ports ---------------------------------+----------------------------------------- Reporter: blair | Owner: Nikolay Korotkiy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: gopass-summon- | provider | ---------------------------------+----------------------------------------- Changes (by Nikolay Korotkiy ): * owner: (none) => Nikolay Korotkiy * status: new => closed * resolution: => fixed Comment: In [changeset:"54cd84a00c3c40a66cb6faf781da4666365c2a5a/macports-ports" 54cd84a00c3c40a66cb6faf781da4666365c2a5a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="54cd84a00c3c40a66cb6faf781da4666365c2a5a" gopass-summon-provider: update to 1.14.11 Closes: https://trac.macports.org/ticket/66371 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 01:58:20 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 01:58:20 -0000 Subject: [MacPorts] #65870: icu @71.1 sets incorrect Python version In-Reply-To: <046.66d6047a3fbbb47af0a25c6097d34a87@macports.org> References: <046.66d6047a3fbbb47af0a25c6097d34a87@macports.org> Message-ID: <061.8553224d55d779e25f93fe08cfa5c200@macports.org> #65870: icu @71.1 sets incorrect Python version ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger ppc Port: icu | ------------------------+----------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: this looks as fixed as it will ever be, for the time being at least -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 02:16:59 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 02:16:59 -0000 Subject: [MacPorts] #65854: glib2 @2.70.5_0: build fails on 10.5 PPC: pragma GCC diagnostic not allowed inside functions In-Reply-To: <046.801314855d1fb80af4d2c8494665aa62@macports.org> References: <046.801314855d1fb80af4d2c8494665aa62@macports.org> Message-ID: <061.1d9e70f379e54852e2e82bb9ef3b74ea@macports.org> #65854: glib2 @2.70.5_0: build fails on 10.5 PPC: pragma GCC diagnostic not allowed inside functions ------------------------+------------------------- Reporter: ballapete | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: leopard ppc Port: glib2 | ------------------------+------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"bf232c7a084bee232ee1e6988402b6c9688fc200/macports-ports" bf232c7a084bee232ee1e6988402b6c9688fc200/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bf232c7a084bee232ee1e6988402b6c9688fc200" glib2: fix build with older gccs they don't accept pragmas inside functions just test against compiler matches gcc for now closes: https://trac.macports.org/ticket/65854 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 02:19:04 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 02:19:04 -0000 Subject: [MacPorts] #58626: nss @3.44 does not build on Mac OS X 10.4.11, PPC Tiger, 'SHA_MASK8' and 'SHA_MASK16' are both undeclared In-Reply-To: <046.2d0b81d9800092fafd1cd4a526c36953@macports.org> References: <046.2d0b81d9800092fafd1cd4a526c36953@macports.org> Message-ID: <061.9c9d31176c27c6ecbe43591349a14d93@macports.org> #58626: nss @3.44 does not build on Mac OS X 10.4.11, PPC Tiger, 'SHA_MASK8' and 'SHA_MASK16' are both undeclared ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: tiger Port: nss | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: nss builds on Tiger PPC now -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 02:21:51 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 02:21:51 -0000 Subject: [MacPorts] #63453: libffi @3.4.2_0 update caused some kind of mixup during rev-upgrade in Leopard PPC that results in a clear path not being followed NYD In-Reply-To: <046.a8bba76e51a6783ee4d281f77eea362a@macports.org> References: <046.a8bba76e51a6783ee4d281f77eea362a@macports.org> Message-ID: <061.c71b878b1b52c59d33d240f9205586cb@macports.org> #63453: libffi @3.4.2_0 update caused some kind of mixup during rev-upgrade in Leopard PPC that results in a clear path not being followed NYD -------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: leopard Port: libffi | -------------------------+-------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => worksforme Comment: we won't be making any more progress here. Please reopen with new information if this is still an issue for youl -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 04:40:51 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 04:40:51 -0000 Subject: [MacPorts] #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined In-Reply-To: <049.1d82130b540711fe530066891970425e@macports.org> References: <049.1d82130b540711fe530066891970425e@macports.org> Message-ID: <064.14a8150cd1ac31d96eea2cda4a1ac4a3@macports.org> #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined ---------------------------+---------------------- Reporter: barracuda156 | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: SoapyRTLSDR | ---------------------------+---------------------- Changes (by ryandesign): * cc: michaelld, gedgy63@? (added) Comment: Even though you're building with g++ I think you're still linking with Apple's ld. I think `--no-undefined` is an option that would be understood by the GNU linker but not by Apple's linker. [https://stackoverflow.com/questions/26971333/what-is-clangs-equivalent- to-no-undefined-gcc-flag According to a quick search], Apple's ld would need `-Wl,-undefined,error` instead. I see from the log that you're on Snow Leopard but building for ppc. I assume this is why it's building with g++. I don't see anything gcc- related in the port so I assume on standard configurations it would build with clang++ and not encounter this problem. I'm not sure what's causing `--no-undefined` to be used in the build. I don't see any occurrences of that string in the SoapyRTLSDR source code. Perhaps it comes from SoapyRTLSDR's dependency SoapySDR whose SoapySDRUtil.cmake file does contain these lines (or from some other file in the build chain that contains similar lines): {{{ if(CMAKE_COMPILER_IS_GNUCXX) #force a compile-time error when symbols are missing #otherwise modules will cause a runtime error on load target_link_libraries(${MODULE_TARGET} PRIVATE "-Wl,--no- undefined") endif() }}} These lines appear to assume that, if the compiler is GNU, then the linker must also be GNU, which is evidently not the case on your system at least and perhaps on all Mac systems. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 05:58:37 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 05:58:37 -0000 Subject: [MacPorts] #66096: libevent @2.12.12_1: Fails when libressl @3.6.0 installed, due to BIO_get_init In-Reply-To: <048.d33c032d557b6cfd8afb1c57fbcb27e6@macports.org> References: <048.d33c032d557b6cfd8afb1c57fbcb27e6@macports.org> Message-ID: <063.7d37ca4a58d0cb2176894cfc93e31ea3@macports.org> #66096: libevent @2.12.12_1: Fails when libressl @3.6.0 installed, due to BIO_get_init ---------------------------------+----------------------- Reporter: daphnediane | Owner: jerryyhom Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: haspatch Port: libevent, libressl | ---------------------------------+----------------------- Changes (by jerryyhom): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"44b21041dfac212bafeebd2b06db4f9779e76bf4/macports-ports" 44b21041dfac212bafeebd2b06db4f9779e76bf4/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="44b21041dfac212bafeebd2b06db4f9779e76bf4" libevent: Add upstream patch for libressl (#16681) * libevent: Add upstream patch for libressl close: https://trac.macports.org/ticket/66096 * Include full upstream patch (comment) for context. Co-authored-by: Eric A. Borisch }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 06:26:07 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 06:26:07 -0000 Subject: [MacPorts] #66387: py310-subprocess-tee @0.4.0_0: fails to build Message-ID: <049.598f340b0db10e6446d036f4580f27f6@macports.org> #66387: py310-subprocess-tee @0.4.0_0: fails to build -----------------------------+---------------------------------- Reporter: hexadecagram | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: monterey x86_64 | Port: py310-subprocess-tee -----------------------------+---------------------------------- Build step trips over the fact that there is no setup.py. The tarball does not contain setup.py and the setup.cfg seems quite incomplete, especially compared to the same file in the 0.3.5 tarball. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 06:26:48 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 06:26:48 -0000 Subject: [MacPorts] #66387: py310-subprocess-tee @0.4.0_0: fails to build In-Reply-To: <049.598f340b0db10e6446d036f4580f27f6@macports.org> References: <049.598f340b0db10e6446d036f4580f27f6@macports.org> Message-ID: <064.dd4531e1f9d8a9e3e904f8b741d7cb5c@macports.org> #66387: py310-subprocess-tee @0.4.0_0: fails to build -----------------------------------+----------------------------- Reporter: hexadecagram | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: monterey x86_64 Port: py310-subprocess-tee | -----------------------------------+----------------------------- Changes (by hexadecagram): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 10:35:34 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 10:35:34 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.2b1c9f8931472595cfe2262563cc2e50@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by ryandesign): I don't know R so forgive me if my questions have obvious answers. What's in /Users/kaufmannm/Library/R? Is it normal for things to exist there after a MacPorts R install and for them to be used when building things with R? If not?if those files came from some other place?maybe they are interfering with what you are trying to do. You could try renaming that directory to something else. Can you figure out why `-latomic` is being used? Is it for example coming from something within /Users/kaufmannm/Library/R or from something within the files installed by the MacPorts R port? If you can find where it is, can you try removing it? I suspect the existence of some code, somewhere, that says something like "if the processor is arm then add `-latomic`" which may be correct on operating systems that are not macOS but as far as I have been able to tell is not correct on macOS. I've encountered this in another port before (i.e. [cd9e090aab86cc29f29c66a8d7e2e2c34939e965 /macports-ports]). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 10:39:22 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 10:39:22 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.6cb26b283dd83b2366be1cc5eb61c551@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by ryandesign): You mentioned that the problem occurs when trying to build the "later" R package. I see that the "later" R package's configure script contains code designed to detect whether `-latomic` is needed. Maybe it is faulty on macOS. Here is where that code was introduced: https://github.com/r-lib/later/pull/114 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 11:54:44 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 11:54:44 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.d5d51ad93d2b37165a296c232b2fab20@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): Ryan is right, -latomic should not be needed. He found the script bit that tests for it, I modified it very slightly, and every time I run this script on Intel Ventura, it says "-latomic linker flag not needed." Can I ask what you see? {{{ #!/bin/sh echo "Running configure script" # Find compiler CC=clang++-mp-14 # Detect whether -latomic is needed during linking. This is needed on some # platforms, notably ARM (Raspberry Pi). echo "#include uint64_t v; int main() { return (int)__atomic_load_n(&v, __ATOMIC_ACQUIRE); }" | ${CC} -x c - if [ $? -eq 0 ]; then echo "-latomic linker flag not needed." else echo "-latomic linker flag needed." EXTRA_PKG_LIBS=-latomic fi # Success exit 0 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 12:27:06 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 12:27:06 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.9c79dab7b1d6d575a39cc235a67f5d2d@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by MarcKaufmann): Thanks. To Ryan's first point, the /Users/kaufmannm/Library/R part is where R installs packages, since it can't write to /opt/..., which belongs to root. I removed that folder, made the /opt/... path writable to test it, and the later package still doesn't install, with the same error. (Logs look identical to before without the mention of the "-I/Users/..." part). To Ken's point, I ran the script and get: {{{ Running configure script ld: library not found for -lc++ clang: error: linker command failed with exit code 1 (use -v to see invocation) -latomic linker flag needed. }}} I checked, and I have clang++-mp-14 on my machine, so that's not the problem. But clearly the script thinks I need the atomic library. What should I check next? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 12:49:30 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 12:49:30 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.b7221776b7fb96a3dfde7f315e91d4d0@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): this is the issue that is leading to the non-zero output that is leading the script to think you need -latomic: {{{ ld: library not found for -lc++ }}} Where the heck did your -lc++ go? I think I might have a clue... make a little file like this: {{{ % cat test.cpp #include uint64_t v; int main() { return (int)__atomic_load_n(&v, __ATOMIC_ACQUIRE); } }}} and then try to compile it with some verbosity flags added, and see what happens... I will guess you have no SDK, but let's see. Here's what I get: {{{ % clang++-mp-14 -v -Wl,-v test.cpp clang version 14.0.6 Target: x86_64-apple-darwin22.1.0 Thread model: posix InstalledDir: /opt/local/libexec/llvm-14/bin "/opt/local/libexec/llvm-14/bin/clang" -cc1 -triple x86_64-apple- macosx13.0.0 -Wundef-prefix=TARGET_OS_ -Werror=undef-prefix -Wdeprecated- objc-isa-usage -Werror=deprecated-objc-isa-usage -emit-obj -mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend -disable- llvm-verifier -discard-value-names -main-file-name test.cpp -mrelocation- model pic -pic-level 2 -mframe-pointer=all -ffp-contract=on -fno-rounding- math -funwind-tables=2 -target-sdk-version=13.0 -fcompatibility-qualified- id-block-type-checking -fvisibility-inlines-hidden-static-local-var -target-cpu penryn -tune-cpu generic -mllvm -treat-scalable-fixed-error- as-warning -debugger-tuning=lldb -target-linker-version 820.1 -v -fcoverage-compilation-dir=/Users/cunningh -resource-dir /opt/local/libexec/llvm-14/lib/clang/14.0.6 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -I/usr/local/include -stdlib=libc++ -internal-isystem /opt/local/libexec/llvm-14/bin/../include/c++/v1 -internal-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local/include -internal-isystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/include -internal-externc-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -fdeprecated-macro -fdebug-compilation-dir=/Users/cunningh -ferror-limit 19 -stack-protector 1 -fblocks -fencode-extended-block-signature -fregister-global-dtors-with-atexit -fgnuc-version=4.2.1 -fcxx-exceptions -fexceptions -fmax-type-align=16 -fcolor-diagnostics -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o /var/folders/b4/rjyd2skj48b3hc6t2xmpdyfh0000gn/T/test-e3047f.o -x c++ test.cpp clang -cc1 version 14.0.6 based upon LLVM 14.0.6 default target x86_64 -apple-darwin22.1.0 ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local/include" ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/Library/Frameworks" #include "..." search starts here: #include <...> search starts here: /opt/local/libexec/llvm-14/bin/../include/c++/v1 /opt/local/libexec/llvm-14/lib/clang/14.0.6/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks (framework directory) End of search list. "/opt/local/libexec/llvm-14/bin/ld" -demangle -lto_library /opt/local/libexec/llvm-14/lib/libLTO.dylib -no_deduplicate -dynamic -arch x86_64 -platform_version macos 13.0.0 13.0 -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -o a.out -L/usr/local/lib -v /var/folders/b4/rjyd2skj48b3hc6t2xmpdyfh0000gn/T/test-e3047f.o -lc++ -lSystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/lib/darwin/libclang_rt.osx.a @(#)PROGRAM:ld PROJECT:ld64-820.1 BUILD 18:42:34 Sep 11 2022 configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em Library search paths: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib Framework search paths: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 12:54:05 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 12:54:05 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.2a32c02837a739c3b901da18c65f776e@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): If you see you have no section like this in your build line: {{{ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk }}} then that is the issue that needs fixing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 12:59:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 12:59:56 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.afb5c1669214e7d1e9776f8170756bb9@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by MarcKaufmann): Yes, you are right, I am missing whatever it is this is looking for: {{{ % clang++-mp-14 -v -Wl, -v test.cpp clang version 14.0.6 Target: arm64-apple-darwin22.1.0 Thread model: posix InstalledDir: /opt/local/libexec/llvm-14/bin "/opt/local/libexec/llvm-14/bin/clang" -cc1 -triple arm64-apple- macosx13.0.0 -Wundef-prefix=TARGET_OS_ -Werror=undef-prefix -Wdeprecated- objc-isa-usage -Werror=deprecated-objc-isa-usage -emit-obj -mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend -disable- llvm-verifier -discard-value-names -main-file-name test.cpp -mrelocation- model pic -pic-level 2 -mframe-pointer=non-leaf -ffp-contract=on -fno- rounding-math -funwind-tables=2 -fcompatibility-qualified-id-block-type- checking -fvisibility-inlines-hidden-static-local-var -target-cpu apple-m1 -target-feature +v8.5a -target-feature +fp-armv8 -target-feature +neon -target-feature +crc -target-feature +crypto -target-feature +dotprod -target-feature +fp16fml -target-feature +ras -target-feature +lse -target-feature +rdm -target-feature +rcpc -target-feature +zcm -target- feature +zcz -target-feature +fullfp16 -target-feature +sha2 -target- feature +aes -target-abi darwinpcs -fallow-half-arguments-and-returns -mllvm -treat-scalable-fixed-error-as-warning -debugger-tuning=lldb -target-linker-version 820.1 -v -v -fcoverage-compilation-dir=/tmp -resource-dir /opt/local/libexec/llvm-14/lib/clang/14.0.6 -stdlib=libc++ -internal-isystem /opt/local/libexec/llvm-14/bin/../include/c++/v1 -internal-isystem /usr/local/include -internal-isystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/include -internal-externc- isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir=/tmp -ferror-limit 19 -stack-protector 1 -fblocks -fencode-extended-block- signature -fregister-global-dtors-with-atexit -fgnuc-version=4.2.1 -fcxx- exceptions -fexceptions -fmax-type-align=16 -fcolor-diagnostics -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o /var/folders/8_/0lh40nm57qq3069hrzss3s1m0000gn/T/test-5459d1.o -x c++ test.cpp clang -cc1 version 14.0.6 based upon LLVM 14.0.6 default target arm64 -apple-darwin22.1.0 ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/usr/include" #include "..." search starts here: #include <...> search starts here: /opt/local/libexec/llvm-14/bin/../include/c++/v1 /opt/local/libexec/llvm-14/lib/clang/14.0.6/include /System/Library/Frameworks (framework directory) /Library/Frameworks (framework directory) End of search list. "/opt/local/libexec/llvm-14/bin/ld" -demangle -lto_library /opt/local/libexec/llvm-14/lib/libLTO.dylib -no_deduplicate -dynamic -arch arm64 -platform_version macos 13.0.0 13.0.0 -o a.out /var/folders/8_/0lh40nm57qq3069hrzss3s1m0000gn/T/test-5459d1.o -lc++ -lSystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/lib/darwin/libclang_rt.osx.a ld: library not found for -lc++ clang: error: linker command failed with exit code 1 (use -v to see invocation) }}} I have Xcode CLI tools installed, at least according to this (in case that's what you meant with SDK): {{{ % xcode-select --version xcode-select version 2396. }}} So what is it that I am missing according to this, and how would I install it? R didn't complain about this, but some other things I wanted to install (shellcheck) said I needed a full Xcode install, which I didn't succeed at installing somehow, so I didn't install shellcheck. Is that what I'd need? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:03:25 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:03:25 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.99f802385f9808fd2ae0cb1f3c291e4a@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by MarcKaufmann): OK, thanks a lot Ken. Just saw your message after posting. How do I install it (since I do not see that line in my output)? I did read that I needed the Xcode CLI tools, but not the full SDK. So if I understand correctly, for R to work I should need the full SDK? I think the R-app port did warn me about this, but R did not. (I didn't install R-app for that reason yet.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:09:33 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:09:33 -0000 Subject: [MacPorts] #66352: clang-15: unable to locate default SDK In-Reply-To: <043.dd7d4114c232db35c8b48d405978fe84@macports.org> References: <043.dd7d4114c232db35c8b48d405978fe84@macports.org> Message-ID: <058.88660ec8b1d221420e22923f79fb20b4@macports.org> #66352: clang-15: unable to locate default SDK -------------------------+----------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura, x86_64 Port: clang-15 | -------------------------+----------------------------- Comment (by kencu): Replying to [comment:15 judaew]: > Thank you for taking the time for me. After rebuilding this port with Xcode installed, the issue disappeared. Currently, Clang finds SDKs both with and without Xcode. I am not sure that building with Xcode installed was the fix. Perhaps just rebuilding was the fix. > > P.S. If anyone gets this issue, then the best workaround without Xcode is the SDKROOT variable. It should help Clang find a path to the SDK. This is a short-term fix that will not work out well in the long run I believe. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:14:01 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:14:01 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.387f0d6186eaa1ab0d5195642684a1b0@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): well, here is where we saw something similar #66352 but I would like you to help me out here, as you are seeing the issue and I can't see it. Please do only this, to rebuild yourself a new llvm/clang-14. It will take a little while, sorry: {{{ sudo port -f uninstall clang-14 llvm-14 sudo port -v -s -N install clang-14 }}} and then try your test compile again -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:15:51 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:15:51 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.60e3c5978d3b6cbbc197ecef6d99d72d@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): If you do have Xcode installed, you need to open it at least once (double- click it) to get everything working. This is kinda unfortunate, but that is the reality of it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:17:04 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:17:04 -0000 Subject: [MacPorts] #66380: clang-14: unable to locate default SDK (was: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic) In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.8ecca6f3a85fee1aeb7ffdc46ff74a9f@macports.org> #66380: clang-14: unable to locate default SDK ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: clang-14 | ---------------------------+-------------------- Changes (by kencu): * cc: kjellpk, i0ntempest (removed) * port: R => clang-14 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:22:01 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:22:01 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic (was: clang-14: unable to locate default SDK) In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.428e70c99aa6f5b308ff232d97416d52@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Changes (by MarcKaufmann): * port: clang-14 => R Comment: There seems to be an issue with my Xcode installation I believe: {{{ % /usr/bin/xcodebuild --version xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance }}} Is my Xcode CLI tools masking the SDK? And what should I do first, open Xcode SDK (which I did, but I never created anything in the window, i.e. I immediately closed the window). Or should I do the rebuilding of the tools and see what I get? When you say "do the test compile" you probably mean the little file that Ken wrote that checks if atomic is needed or not? Happy to wait if it fixes the issue or helps you figure out what's going on. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:23:11 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:23:11 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.bea7028271e1805d33f9d2c1c5760b4c@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): The other possibility, I suppose, is that /usr/bin/xcrun sees Xcode is installed, and so tries to use it, but because Xcode has never been opened it is not fully functional and that results in this error. Try just opening Xcode once, and then see if everything works. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:27:49 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:27:49 -0000 Subject: [MacPorts] #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.2d614f33128a5611463edf5fc01b8da8@macports.org> #66380: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R | ---------------------------+-------------------- Comment (by kencu): Oh, you said you did already open Xcode once. OK. I get this: {{{ % xcode-select -p /Applications/Xcode.app/Contents/Developer }}} If yours is not that, set it to that, (xcode-select -s /Applications/Xcode.app/Contents/Developer) and then try your test compile again. Maybe that is the issue... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:29:36 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:29:36 -0000 Subject: [MacPorts] #66380: clang-14: unable to locate default SDK (was: R @4.2.2_1: error when installing package "later: ld: library not found for -latomic) In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.cce5d84d34a6b14fc357ec0d1a819fa4@macports.org> #66380: clang-14: unable to locate default SDK ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: clang-14 | ---------------------------+-------------------- Changes (by kencu): * port: R => clang-14 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 13:42:20 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 13:42:20 -0000 Subject: [MacPorts] #66380: clang-14: unable to locate default SDK In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.3d001a80767d89a94204c5db9eb2a14c@macports.org> #66380: clang-14: unable to locate default SDK ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: clang-14 | ---------------------------+-------------------- Comment (by MarcKaufmann): I had to switch the xcode-select (-s) and now it has the right path (it seems): {{{ % xcode-select -p /Applications/Xcode.app/Contents/Developer }}} The script still fails: {{{ % cat test.cpp #include uint64_t v; int main() { return (int)__atomic_load_n(&v, __ATOMIC_ACQUIRE); } % clang++-mp-14 -v -Wl, -v test.cpp clang version 14.0.6 Target: arm64-apple-darwin22.1.0 Thread model: posix InstalledDir: /opt/local/libexec/llvm-14/bin "/opt/local/libexec/llvm-14/bin/clang" -cc1 -triple arm64-apple- macosx13.0.0 -Wundef-prefix=TARGET_OS_ -Werror=undef-prefix -Wdeprecated- objc-isa-usage -Werror=deprecated-objc-isa-usage -emit-obj -mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend -disable- llvm-verifier -discard-value-names -main-file-name test.cpp -mrelocation- model pic -pic-level 2 -mframe-pointer=non-leaf -ffp-contract=on -fno- rounding-math -funwind-tables=2 -fcompatibility-qualified-id-block-type- checking -fvisibility-inlines-hidden-static-local-var -target-cpu apple-m1 -target-feature +v8.5a -target-feature +fp-armv8 -target-feature +neon -target-feature +crc -target-feature +crypto -target-feature +dotprod -target-feature +fp16fml -target-feature +ras -target-feature +lse -target-feature +rdm -target-feature +rcpc -target-feature +zcm -target- feature +zcz -target-feature +fullfp16 -target-feature +sha2 -target- feature +aes -target-abi darwinpcs -fallow-half-arguments-and-returns -mllvm -treat-scalable-fixed-error-as-warning -debugger-tuning=lldb -target-linker-version 820.1 -v -v -fcoverage-compilation-dir=/tmp -resource-dir /opt/local/libexec/llvm-14/lib/clang/14.0.6 -stdlib=libc++ -internal-isystem /opt/local/libexec/llvm-14/bin/../include/c++/v1 -internal-isystem /usr/local/include -internal-isystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/include -internal-externc- isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir=/tmp -ferror-limit 19 -stack-protector 1 -fblocks -fencode-extended-block- signature -fregister-global-dtors-with-atexit -fgnuc-version=4.2.1 -fcxx- exceptions -fexceptions -fmax-type-align=16 -fcolor-diagnostics -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o /var/folders/8_/0lh40nm57qq3069hrzss3s1m0000gn/T/test-87379a.o -x c++ test.cpp clang -cc1 version 14.0.6 based upon LLVM 14.0.6 default target arm64 -apple-darwin22.1.0 ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/usr/include" #include "..." search starts here: #include <...> search starts here: /opt/local/libexec/llvm-14/bin/../include/c++/v1 /opt/local/libexec/llvm-14/lib/clang/14.0.6/include /System/Library/Frameworks (framework directory) /Library/Frameworks (framework directory) End of search list. "/opt/local/libexec/llvm-14/bin/ld" -demangle -lto_library /opt/local/libexec/llvm-14/lib/libLTO.dylib -no_deduplicate -dynamic -arch arm64 -platform_version macos 13.0.0 13.0.0 -o a.out /var/folders/8_/0lh40nm57qq3069hrzss3s1m0000gn/T/test-87379a.o -lc++ -lSystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/lib/darwin/libclang_rt.osx.a ld: library not found for -lc++ clang: error: linker command failed with exit code 1 (use -v to see invocation) }}} Next I'll be running the recompiles for clang-14. Gonna be a while: {{{ sudo port -f uninstall clang-14 llvm-14 sudo port -v -s -N install clang-14 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:04:54 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 15:04:54 -0000 Subject: [MacPorts] #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined In-Reply-To: <049.1d82130b540711fe530066891970425e@macports.org> References: <049.1d82130b540711fe530066891970425e@macports.org> Message-ID: <064.8fdf42e497ba0e1e7aa2a852712f039d@macports.org> #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined ---------------------------+---------------------- Reporter: barracuda156 | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: SoapyRTLSDR | ---------------------------+---------------------- Comment (by barracuda156): Replying to [comment:1 ryandesign]: Thank you for responding and helping to find the cause! I have checked the source code prior to opening the ticket and did not find anything there. I guess this should be fixed with `SoapySDR` then, since this is not a Rosetta issue and apparently not even a PPC issue (but of course on PPC we only have GCC for now). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:10:25 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 15:10:25 -0000 Subject: [MacPorts] #66380: clang-14: unable to locate default SDK In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.02750091874ac0acfe5409937d54c24d@macports.org> #66380: clang-14: unable to locate default SDK ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: clang-14 | ---------------------------+-------------------- Comment (by MarcKaufmann): OK, the compilation has finished (I also synced port) and it is now working. The script passes: {{{ % clang++-mp-14 -v -Wl, -v test.cpp clang version 14.0.6 Target: arm64-apple-darwin22.1.0 Thread model: posix InstalledDir: /opt/local/libexec/llvm-14/bin "/opt/local/libexec/llvm-14/bin/clang" -cc1 -triple arm64-apple- macosx13.0.0 -Wundef-prefix=TARGET_OS_ -Werror=undef-prefix -Wdeprecated- objc-isa-usage -Werror=deprecated-objc-isa-usage -emit-obj -mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend -disable- llvm-verifier -discard-value-names -main-file-name test.cpp -mrelocation- model pic -pic-level 2 -mframe-pointer=non-leaf -ffp-contract=on -fno- rounding-math -funwind-tables=2 -target-sdk-version=13.0 -fcompatibility- qualified-id-block-type-checking -fvisibility-inlines-hidden-static-local- var -target-cpu apple-m1 -target-feature +v8.5a -target-feature +fp-armv8 -target-feature +neon -target-feature +crc -target-feature +crypto -target-feature +dotprod -target-feature +fp16fml -target-feature +ras -target-feature +lse -target-feature +rdm -target-feature +rcpc -target- feature +zcm -target-feature +zcz -target-feature +fullfp16 -target- feature +sha2 -target-feature +aes -target-abi darwinpcs -fallow-half- arguments-and-returns -mllvm -treat-scalable-fixed-error-as-warning -debugger-tuning=lldb -target-linker-version 820.1 -v -v -fcoverage- compilation-dir=/tmp -resource-dir /opt/local/libexec/llvm-14/lib/clang/14.0.6 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -I/usr/local/include -stdlib=libc++ -internal-isystem /opt/local/libexec/llvm-14/bin/../include/c++/v1 -internal-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local/include -internal-isystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/include -internal-externc-isystem /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -fdeprecated-macro -fdebug-compilation-dir=/tmp -ferror-limit 19 -stack- protector 1 -fblocks -fencode-extended-block-signature -fregister-global- dtors-with-atexit -fgnuc-version=4.2.1 -fcxx-exceptions -fexceptions -fmax-type-align=16 -fcolor-diagnostics -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o /var/folders/8_/0lh40nm57qq3069hrzss3s1m0000gn/T/test-c90de3.o -x c++ test.cpp clang -cc1 version 14.0.6 based upon LLVM 14.0.6 default target arm64 -apple-darwin22.1.0 ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/local/include" ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/Library/Frameworks" #include "..." search starts here: #include <...> search starts here: /opt/local/libexec/llvm-14/bin/../include/c++/v1 /opt/local/libexec/llvm-14/lib/clang/14.0.6/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks (framework directory) End of search list. "/opt/local/libexec/llvm-14/bin/ld" -demangle -lto_library /opt/local/libexec/llvm-14/lib/libLTO.dylib -no_deduplicate -dynamic -arch arm64 -platform_version macos 13.0.0 13.0 -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -o a.out -L/usr/local/lib /var/folders/8_/0lh40nm57qq3069hrzss3s1m0000gn/T /test-c90de3.o -lc++ -lSystem /opt/local/libexec/llvm-14/lib/clang/14.0.6/lib/darwin/libclang_rt.osx.a }}} and the package installation works as well. I guess that something had gone with my original installation of clang-14. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 15:46:37 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 15:46:37 -0000 Subject: [MacPorts] #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason Message-ID: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason --------------------------------------------+-------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: mountainlion | Port: yt-dlp --------------------------------------------+-------------------- Example output: {{{ [debug] Command-line config: ['--verbose', '--proxy', 'socks5://184.170.248.5:4145', 'https://youtu.be/dQw4w9WgXcQ'] [debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8 [debug] yt-dlp version 2022.11.11 [8b64402] (pip) [debug] Python 3.10.8 (CPython x86_64 64bit) - macOS-10.8.5-x86_64-i386-64bit (OpenSSL 3.0.7 1 Nov 2022) [debug] exe versions: ffmpeg 4.4.2 (fdk,setts), ffprobe 4.4.2, rtmpdump 2.4 [debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4 [debug] Proxy map: {'http': 'socks5://184.170.248.5:4145', 'https': 'socks5://184.170.248.5:4145'} [debug] Loaded 1723 extractors [debug] [youtube] Extracting URL: https://youtu.be/dQw4w9WgXcQ [youtube] dQw4w9WgXcQ: Downloading webpage WARNING: [youtube] Unable to download webpage: [youtube] dQw4w9WgXcQ: Downloading android player API JSON WARNING: [youtube] . Retrying (1/3)... [youtube] dQw4w9WgXcQ: Downloading android player API JSON WARNING: [youtube] . Retrying (2/3)... [youtube] dQw4w9WgXcQ: Downloading android player API JSON WARNING: [youtube] . Retrying (3/3)... [youtube] dQw4w9WgXcQ: Downloading android player API JSON [youtube] dQw4w9WgXcQ: Downloading iframe API JS WARNING: [youtube] Unable to download webpage: [youtube] dQw4w9WgXcQ: Downloading web player API JSON WARNING: [youtube] . Retrying (1/3)... [youtube] dQw4w9WgXcQ: Downloading web player API JSON WARNING: [youtube] . Retrying (2/3)... [youtube] dQw4w9WgXcQ: Downloading web player API JSON WARNING: [youtube] . Retrying (3/3)... [youtube] dQw4w9WgXcQ: Downloading web player API JSON WARNING: [youtube] Unable to download API page: (caused by URLError(Socks5Error(4, 'Host unreachable'))) ERROR: [youtube] dQw4w9WgXcQ: Unable to download API page: (caused by URLError(Socks5Error(4, 'Host unreachable'))) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 674, in extract ie_result = self._real_extract(url) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 3758, in _real_extract webpage, master_ytcfg, player_responses, player_url = self._download_player_responses(url, smuggled_data, video_id, webpage_url) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 3726, in _download_player_responses player_responses, player_url = self._extract_player_responses( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 3464, in _extract_player_responses raise last_error File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 3435, in _extract_player_responses pr = initial_pr if client == 'web' and initial_pr else self._extract_player_response( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 3355, in _extract_player_response return self._extract_response( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 860, in _extract_response for retry in self.RetryManager(): File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/utils.py", line 5921, in __iter__ self.error_callback(self.error, self.attempt, self.retries) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 3882, in _error_or_warning RetryManager.report_retry( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/utils.py", line 5929, in report_retry raise e File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 862, in _extract_response response = self._call_api( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/youtube.py", line 538, in _call_api return self._download_json( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 1034, in download_content res = getattr(self, download_handle.__name__)(url_or_request, video_id, **kwargs) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 998, in download_handle res = self._download_webpage_handle( File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 868, in _download_webpage_handle urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal, data=data, headers=headers, query=query, expected_status=expected_status) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 825, in _request_webpage raise ExtractorError(errmsg, cause=err) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 1348, in do_open h.request(req.get_method(), req.selector, req.data, headers, File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1282, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1328, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1277, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 1037, in _send_output self.send(msg) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/http/client.py", line 975, in send self.connect() File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/utils.py", line 1494, in connect self.sock.connect((self.host, self.port)) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/socks.py", line 264, in connect self._make_proxy(socket.socket.connect, address) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/socks.py", line 260, in _make_proxy setup_funcs[self._proxy.type](address) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/socks.py", line 235, in _setup_socks5 raise Socks5Error(status) yt_dlp.socks.Socks5Error: [Errno 4] Host unreachable During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/extractor/common.py", line 807, in _request_webpage return self._downloader.urlopen(self._create_request(url_or_request, data, headers, query)) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/YoutubeDL.py", line 3692, in urlopen return self._opener.open(req, timeout=self._socket_timeout) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/Users/user/Library/Python/3.10/lib/python/site- packages/yt_dlp/utils.py", line 1527, in https_open return self.do_open( File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/urllib/request.py", line 1351, in do_open raise URLError(err) urllib.error.URLError: }}} On other sites it basically displays the following error: {{{ Unable to download webpage: (caused by URLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:997)'))) }}} This happens regardless of whether an HTTP or SOCKS proxy is used. Google showed [https://github.com/yt-dlp/yt-dlp/issues/3102 a similar problem], but does certifi use sometimes system certificates or am I misunderstanding something? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 16:31:32 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 16:31:32 -0000 Subject: [MacPorts] #66380: clang-14: unable to locate default SDK In-Reply-To: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> References: <049.ca54f9dc8bca23ff9915a94fcc8d8488@macports.org> Message-ID: <064.a49f1e002fcb8da0318a27d9bdd15060@macports.org> #66380: clang-14: unable to locate default SDK ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: clang-14 | ---------------------------+-------------------- Comment (by kencu): but what, I wonder? tough nut to crack, but you?re second person w this issue now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 18:31:54 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 18:31:54 -0000 Subject: [MacPorts] #66384: py27-openssl: Please downgrade to 21.0.0 In-Reply-To: <047.76e3cd8af4225a1f3bbf773f8632d336@macports.org> References: <047.76e3cd8af4225a1f3bbf773f8632d336@macports.org> Message-ID: <062.0eb9232bdc3c4048908031649887afeb@macports.org> #66384: py27-openssl: Please downgrade to 21.0.0 -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-openssl | -------------------------+--------------------------------- Changes (by reneeotten): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"6580d062562b2dde9043adafb3489d220132c988/macports-ports" 6580d062562b2dde9043adafb3489d220132c988/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6580d062562b2dde9043adafb3489d220132c988" py-openssl: downgrade py27 subport to 21.0.0 Closes: https://trac.macports.org/ticket/66384 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 18:33:13 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 18:33:13 -0000 Subject: [MacPorts] #66387: py310-subprocess-tee @0.4.0_0: fails to build In-Reply-To: <049.598f340b0db10e6446d036f4580f27f6@macports.org> References: <049.598f340b0db10e6446d036f4580f27f6@macports.org> Message-ID: <064.13dee349a4e126117311f2e7f5c2e7a1@macports.org> #66387: py310-subprocess-tee @0.4.0_0: fails to build --------------------------------+---------------------- Reporter: hexadecagram | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-subprocess-tee | --------------------------------+---------------------- Changes (by reneeotten): * cc: judaew (removed) * status: new => assigned * keywords: monterey x86_64 => * port: py310-subprocess-tee => py-subprocess-tee * owner: (none) => judaew Comment: this probably should just use `python.pep517 yes` in the Portfile as the directory appears to contain a `pyproject.toml` file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 18:34:30 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 18:34:30 -0000 Subject: [MacPorts] #66370: py-psycopg2: default to postgresql15 In-Reply-To: <047.bb6d263a72a5a8eec6d20459d12d7066@macports.org> References: <047.bb6d263a72a5a8eec6d20459d12d7066@macports.org> Message-ID: <062.eb11763c08f25b838449bd2e1f14cb57@macports.org> #66370: py-psycopg2: default to postgresql15 --------------------------+---------------------- Reporter: mohd-akram | Owner: nerdling Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-psycopg2 | --------------------------+---------------------- Changes (by reneeotten): * cc: nerdling (removed) * status: new => assigned * version: => 2.8.0 * owner: (none) => nerdling -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 19:26:01 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 19:26:01 -0000 Subject: [MacPorts] #65742: Gnuradio gui stuck In-Reply-To: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> References: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> Message-ID: <063.7c629083f0ae8eafcf708fcb0ed88a60@macports.org> #65742: Gnuradio gui stuck --------------------------+----------------------- Reporter: adamgao1996 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: qtgui Port: gnuradio | --------------------------+----------------------- Comment (by J-in-MN): @ ra1nb0w can you please provide some hints as to what it means to "install gnuradio 3.10 from ?https://github.com/ra1nb0w/macports- ports/tree/gnuradio-3.10"? Is there some config file setting or command line options I have to use in my macports install? Or do I have to delete my entire macports install and rebuild it from source using the https://github.com/ra1nb0w/macports- ports/releases/tag/v2.8.0-archive? Or do I replace my /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports directory with a git clone of https://github.com/ra1nb0w/macports- ports/tree/gnuradio-3.10 and then build gnuradio from source with "sudo port -sv install gnuradio"? BTW, thank you for your efforts to keep the SDRangel port up to date. I am using that until we can get gnuradio 3.10.4 working on macOS 13 on Apple Silicon. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 19:56:34 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 19:56:34 -0000 Subject: [MacPorts] #66389: gr-osmosdr @20210117-cffef690_3 Build error Message-ID: <043.72c8743647feb5c421507c3c000a5611@macports.org> #66389: gr-osmosdr @20210117-cffef690_3 Build error --------------------+------------------------ Reporter: dwyerk | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gr-osmosdr --------------------+------------------------ gr-osmosdr fails to build with SWIG errors. I'm running: `sudo port install gr-osmosdr` Which results in: {{{ ---> Building gr-osmosdr Error: Failed to build gr-osmosdr: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_science_gr-osmosdr/gr- osmosdr/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gr-osmosdr failed }}} Build environment: {{{ :debug:sysinfo macOS 13.0.1 (darwin/22.1.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode 14.1, CLT 14.1.0.0.1.1666437224 }}} First of the errors from the logs: {{{ gr- osmosdr/work/build/swig/CMakeFiles/osmosdr_swig.dir/osmosdr_swigPYTHON_wrap.cxx:5077:152: error: unknown type name 'SWIGPY_SLICEOBJECT' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 3 19:57:19 2022 From: noreply at macports.org (MacPorts) Date: Sat, 03 Dec 2022 19:57:19 -0000 Subject: [MacPorts] #66389: gr-osmosdr @20210117-cffef690_3 Build error In-Reply-To: <043.72c8743647feb5c421507c3c000a5611@macports.org> References: <043.72c8743647feb5c421507c3c000a5611@macports.org> Message-ID: <058.9021f412f7fc433c79650af26534a43f@macports.org> #66389: gr-osmosdr @20210117-cffef690_3 Build error -------------------------+-------------------- Reporter: dwyerk | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gr-osmosdr | -------------------------+-------------------- Changes (by dwyerk): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 00:08:29 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 00:08:29 -0000 Subject: [MacPorts] #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason In-Reply-To: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> References: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> Message-ID: <082.17069ee14cc4b9d0337a77204423964c@macports.org> #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason ---------------------------------------------+-------------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: mountainlion Port: yt-dlp | ---------------------------------------------+-------------------------- Changes (by jmroot): * owner: (none) => ryandesign * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 00:09:07 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 00:09:07 -0000 Subject: [MacPorts] #66389: gr-osmosdr @20210117-cffef690_3 Build error In-Reply-To: <043.72c8743647feb5c421507c3c000a5611@macports.org> References: <043.72c8743647feb5c421507c3c000a5611@macports.org> Message-ID: <058.3566d8463dd7b99f3956ea22a8f2c7f9@macports.org> #66389: gr-osmosdr @20210117-cffef690_3 Build error -------------------------+----------------------- Reporter: dwyerk | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gr-osmosdr | -------------------------+----------------------- Changes (by jmroot): * owner: (none) => michaelld * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 00:31:49 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 00:31:49 -0000 Subject: [MacPorts] #66389: gr-osmosdr @20210117-cffef690_3 Build error In-Reply-To: <043.72c8743647feb5c421507c3c000a5611@macports.org> References: <043.72c8743647feb5c421507c3c000a5611@macports.org> Message-ID: <058.c7daa0dbf5cb20618460a5f6aa045eec@macports.org> #66389: gr-osmosdr @20210117-cffef690_3 Build error -------------------------+----------------------- Reporter: dwyerk | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gr-osmosdr | -------------------------+----------------------- Comment (by dwyerk): Digging around in the osmosdr code I found this really suspicious bit of code: {{{ // Workaround for a SWIG 2.0.4 bug with templates. Probably needs to be looked in to. %{ #if PY_VERSION_HEX >= 0x03020000 # define SWIGPY_SLICE_ARG(obj) ((PyObject*) (obj)) #else # define SWIGPY_SLICE_ARG(obj) ((PySliceObject*) (obj)) #endif %} }}} This patch at least lets it build. I copied the newer syntax that swig uses into this section. Presumably this is because macports is on to SWIG-4.1.0? {{{ diff --git a/swig/osmosdr_swig.i b/swig/osmosdr_swig.i index 550008b..cd44507 100644 --- a/swig/osmosdr_swig.i +++ b/swig/osmosdr_swig.i @@ -18,13 +18,16 @@ // Workaround for a SWIG 2.0.4 bug with templates. Probably needs to be looked in to. %{ +#include + #if PY_VERSION_HEX >= 0x03020000 -# define SWIGPY_SLICE_ARG(obj) ((PyObject*) (obj)) +# define SWIGPY_SLICEOBJECT PyObject #else -# define SWIGPY_SLICE_ARG(obj) ((PySliceObject*) (obj)) +# define SWIGPY_SLICEOBJECT PySliceObject #endif %} + %template(string_vector_t) std::vector; //%template(size_vector_t) std::vector; }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 00:40:59 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 00:40:59 -0000 Subject: [MacPorts] #66389: gr-osmosdr @20210117-cffef690_3 Build error In-Reply-To: <043.72c8743647feb5c421507c3c000a5611@macports.org> References: <043.72c8743647feb5c421507c3c000a5611@macports.org> Message-ID: <058.87de7261335b4c1e886d8f53ae9d7094@macports.org> #66389: gr-osmosdr @20210117-cffef690_3 Build error -------------------------+----------------------- Reporter: dwyerk | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gr-osmosdr | -------------------------+----------------------- Comment (by dwyerk): Also not entirely clear but SWIG-4.1.0 deprecated the `-py3` argument, which osmosdr passes, so we might have to also add {{{ %feature("python:annotations", "c"); }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 10:37:21 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 10:37:21 -0000 Subject: [MacPorts] #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason In-Reply-To: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> References: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> Message-ID: <082.59e876bc5441fce03891c10ec6f536f5@macports.org> #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason ---------------------------------------------+-------------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: mountainlion Port: yt-dlp | ---------------------------------------------+-------------------------- Changes (by ryandesign): * cc: stromnov (added) Comment: > does certifi use sometimes system certificates or am I misunderstanding something? I don't know. I don't have experience with proxies nor with certifi. Cc'ing Andrew who maintains py-certifi. Have you already performed the [wiki:ProblemHotlist#letsencrypt Let's Encrypt fix] on your system? (I don't know if it's relevant for this but it's good to do for other reasons.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 11:28:06 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 11:28:06 -0000 Subject: [MacPorts] #66089: Lua: either update to 5.4 or add a separate lua54 port (or both?) In-Reply-To: <048.1c7d94ddc07f2778a0b98fc672ddaa1c@macports.org> References: <048.1c7d94ddc07f2778a0b98fc672ddaa1c@macports.org> Message-ID: <063.f213080f6eb6677d48dca333fbbb642c@macports.org> #66089: Lua: either update to 5.4 or add a separate lua54 port (or both?) --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lua | --------------------------+-------------------- Comment (by harens): This is also required to update the lite-xl port, which requires lua 5.4. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 11:49:18 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 11:49:18 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" Message-ID: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" -----------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: qore -----------------------+----------------------- This ticket could well be due to a configuration error on my part, but the port is failing on both El Capitan and Ventura. However, the buildbots show that is was built in the last couple of days. I'll attach the CMake Error log. The configure script appears to be trying various locations to find `slist.h` or `slist`, but all are failing. Eventually it gives up. {{{ xcode-select -p /Applications/Xcode.app/Contents/Developer }}} I also have the Command Line Tools installed. Searching the file system for `slist.h` or `slist` shows many instances in various include folders. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 11:50:57 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 11:50:57 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.22808ec7f775fba2e1321d171898bc98@macports.org> #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: qore | ------------------------+----------------------- Changes (by snowflake): * Attachment "CMakeError.log" added. CMakeError.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:32:45 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 15:32:45 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing Message-ID: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: highsierra | Port: ext2fuse ------------------------+---------------------- {{{ if /usr/bin/clang -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/osxfuse/fuse -I/usr/include/fuse -I/usr/local/include/fuse -I../lib -I../lib/et -I../lib/ext2fs -D_FILE_OFFSET_BITS=64 -pipe -Os -I/opt/local/include/fuse -std=gnu89 -D__FreeBSD__=10 -I/opt/local/include/osxfuse/fuse -DENABLE_SWAPFS -arch x86_64 -MT ext2fuse-rename.o -MD -MP -MF ".deps/ext2fuse-rename.Tpo" -c -o ext2fuse-rename.o `test -f 'rename.c' || echo './'`rename.c; \ then mv -f ".deps/ext2fuse-rename.Tpo" ".deps/ext2fuse-rename.Po"; else rm -f ".deps/ext2fuse-rename.Tpo"; exit 1; fi perms.c:2:10: In file included from readdir.c:1: ./readdir.h:6:10fatal error:: fatal error'fuse_lowlevel.h' file not found : 'fuse_lowlevel.h' file not found In file included from symlink.c:1: ./symlink.h:6:10: fatal error: 'fuse_lowlevel.h' file not found #include ^~~~~~~~~~~~~~~~~ #include ^~~~~~~~~~~~~~~~~ #include ^~~~~~~~~~~~~~~~~ fuse-ext2fs.c:9:10: fatal error: 'fuse_lowlevel.h' file not found #include ^~~~~~~~~~~~~~~~~ 1 error generated. 1 error generated. 1 error generated. make[2]: *** [ext2fuse-perms.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: *** [ext2fuse-readdir.o] Error 1 make[2]: *** [ext2fuse-symlink.o] Error 1 1 error generated. make[2]: *** [ext2fuse-fuse-ext2fs.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_fuse_ext2fuse/ext2fuse/work /ext2fuse-src-0.8.1/src' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:33:46 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 15:33:46 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> References: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> Message-ID: <061.4387ec87ba458b3aca98437e9fcf40c0@macports.org> #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: highsierra Port: ext2fuse | ------------------------+------------------------ Changes (by ballapete): * Attachment "main.log" added. Main.log from High Sierra 10.13.6 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:37:53 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 15:37:53 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing Message-ID: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: hoghsierra | Port: macfuse ------------------------+--------------------- {{{ if /usr/bin/clang -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/osxfuse/fuse -I/usr/include/fuse -I/usr/local/include/fuse -I../lib -I../lib/et -I../lib/ext2fs -D_FILE_OFFSET_BITS=64 -pipe -Os -I/opt/local/include/fuse -std=gnu89 -D__FreeBSD__=10 -I/opt/local/include/osxfuse/fuse -DENABLE_SWAPFS -arch x86_64 -MT ext2fuse-perms.o -MD -MP -MF ".deps/ext2fuse-perms.Tpo" -c -o ext2fuse-perms.o `test -f 'perms.c' || echo './'`perms.c; \ then mv -f ".deps/ext2fuse-perms.Tpo" ".deps/ext2fuse-perms.Po"; else rm -f ".deps/ext2fuse-perms.Tpo"; exit 1; fi if /usr/bin/clang -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/osxfuse/fuse -I/usr/include/fuse -I/usr/local/include/fuse -I../lib -I../lib/et -I../lib/ext2fs -D_FILE_OFFSET_BITS=64 -pipe -Os -I/opt/local/include/fuse -std=gnu89 -D__FreeBSD__=10 -I/opt/local/include/osxfuse/fuse -DENABLE_SWAPFS -arch x86_64 -MT ext2fuse-rename.o -MD -MP -MF ".deps/ext2fuse-rename.Tpo" -c -o ext2fuse-rename.o `test -f 'rename.c' || echo './'`rename.c; \ then mv -f ".deps/ext2fuse-rename.Tpo" ".deps/ext2fuse-rename.Po"; else rm -f ".deps/ext2fuse-rename.Tpo"; exit 1; fi In file included from perms.creaddir.c:2:10: :fatal error: 'fuse_lowlevel.h' file not found1 : ./readdir.h:6:10: fatal error: 'fuse_lowlevel.h' file not found #include ^~~~~~~~~~~~~~~~~ #include ^~~~~~~~~~~~~~~~~ In file included from symlink.c:1: ./symlink.h:6:10: fatal error: 'fuse_lowlevel.h' file not found #include ^~~~~~~~~~~~~~~~~ fuse-ext2fs.c:9:10: fatal error: 'fuse_lowlevel.h' file not found #include ^~~~~~~~~~~~~~~~~ 1 error generated. 1 error generated. 1 error generated. 1 error generated. make[2]: *** [ext2fuse-perms.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: *** [ext2fuse-fuse-ext2fs.o] Error 1 make[2]: *** [ext2fuse-readdir.o] Error 1 make[2]: *** [ext2fuse-symlink.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_fuse_ext2fuse/ext2fuse/work /ext2fuse-src-0.8.1/src' make[1]: *** [all-recursive] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:38:22 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 15:38:22 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.223916319e03a9dca2a6c7f1384be9af@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: hoghsierra Port: macfuse | ------------------------+------------------------ Changes (by ballapete): * Attachment "main.log" added. Main.log from High Sierra 10.13.6 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:54:36 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 15:54:36 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> References: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> Message-ID: <061.5a57305f061b1c9c0b33307d42694bd7@macports.org> #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: highsierra Port: ext2fuse | ------------------------+------------------------ Comment (by ballapete): It builds when `macfuse` was installed before. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 15:54:48 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 15:54:48 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.f5329537502c8ed7786107c9573beea1@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: hoghsierra Port: macfuse | ------------------------+------------------------ Comment (by ballapete): It builds when `macfuse` was installed before. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:19:51 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 16:19:51 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> References: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> Message-ID: <061.37fb23a28ae8735ca36618a3823d5ce8@macports.org> #66391: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: highsierra Port: ext2fuse | ------------------------+------------------------ Comment (by ballapete): `osxfuse` is another option to solve this dependency. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:19:57 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 16:19:57 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.5801c3ba549a92513fad34d271354afe@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: hoghsierra Port: macfuse | ------------------------+------------------------ Comment (by ballapete): `osxfuse` is another option to solve this dependency. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 16:29:02 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 16:29:02 -0000 Subject: [MacPorts] #66393: Please use the official URI for gtk-mac-bundler Message-ID: <043.972ef958b755007a289050336cc8fa5e@macports.org> #66393: Please use the official URI for gtk-mac-bundler --------------------+----------------------------- Reporter: jralls | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gtk-mac-bundler --------------------+----------------------------- Instead of my personal repo. That URI is https://gitlab.gnome.org/GNOME /gtk-mac-bundler. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 17:41:26 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 17:41:26 -0000 Subject: [MacPorts] #66393: Please use the official URI for gtk-mac-bundler In-Reply-To: <043.972ef958b755007a289050336cc8fa5e@macports.org> References: <043.972ef958b755007a289050336cc8fa5e@macports.org> Message-ID: <058.50d280e0399910c3253aa55d2354d54c@macports.org> #66393: Please use the official URI for gtk-mac-bundler ------------------------------+---------------------- Reporter: jralls | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtk-mac-bundler | ------------------------------+---------------------- Changes (by raimue): * status: new => assigned * owner: (none) => mascguy -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 17:43:16 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 17:43:16 -0000 Subject: [MacPorts] #66134: MacVim @9.0.snapshot173_1: add python310 variant In-Reply-To: <042.885f975d741c1c76722d1c3524cea6d5@macports.org> References: <042.885f975d741c1c76722d1c3524cea6d5@macports.org> Message-ID: <057.154af9110ad1073106a63d07ffa743d8@macports.org> #66134: MacVim @9.0.snapshot173_1: add python310 variant --------------------------+-------------------- Reporter: rufty | Owner: raimue Type: enhancement | Status: closed Priority: Low | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: MacVim | --------------------------+-------------------- Changes (by raimue): * status: assigned => closed * resolution: => fixed Comment: A +python310 variant has been added with [changeset:96086ea2088db5c80bb3cde9ea4d0dd043b27219/macports-ports]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 17:45:13 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 17:45:13 -0000 Subject: [MacPorts] #65922: upgrade neovim to version 0.8 In-Reply-To: <044.e2171094b8cf8417ff30a94816e93c92@macports.org> References: <044.e2171094b8cf8417ff30a94816e93c92@macports.org> Message-ID: <059.c60b5be553c806326534de2892c0cd39@macports.org> #65922: upgrade neovim to version 0.8 ----------------------+-------------------- Reporter: dobbbri | Owner: raimue Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: neovim | ----------------------+-------------------- Changes (by raimue): * status: assigned => closed * resolution: => fixed Comment: The update to 0.8 was provided with [changeset:c1aa53a78b4ba7f0e9728c55ad77dad776d90f2c/macports-ports]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 19:39:33 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 19:39:33 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.d282dbfb2ad1a90c14702988f6438593@macports.org> #66365: Failed to build libgcc-devel: command execution failed ------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: gcc-devel | ------------------------+--------------------------- Comment (by VinzenzBildstein): I found the same issue: I tried cleaning the port and installing it using "port install libgcc- devel build.jobs=1": {{{ ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221126_0+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221126_0+stdlib_flag.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221126_0+stdlib_flag.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/libgcc-devel ---> Fetching distfiles for libgcc-devel ---> Attempting to fetch gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e.tar.gz from https://distfiles.macports.org/gcc-devel ---> Verifying checksums for libgcc-devel ---> Extracting libgcc-devel ---> Configuring libgcc-devel ---> Building libgcc-devel Error: Failed to build libgcc-devel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port libgcc-devel failed 28:~ root# less /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log 28:~ root# /opt/local/bin/port clean libgcc-devel ---> Cleaning libgcc-devel 28:~ root# ls /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log ls: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log: No such file or directory 28:~ root# /opt/local/bin/port install libgcc-devel build.jobs=1 ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221126_0+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221126_0+stdlib_flag.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221126_0+stdlib_flag.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/libgcc-devel ---> Fetching distfiles for libgcc-devel ---> Verifying checksums for libgcc-devel ---> Extracting libgcc-devel ---> Configuring libgcc-devel ---> Building libgcc-devel Error: Failed to build libgcc-devel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port libgcc-devel failed }}} The error from main.log is {{{ :info:build make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/libcpp' :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/./prev- gcc/xg++ -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/./prev- gcc/ -B/opt/local/arm64-apple-darwin22/bin/ -nostdinc++ -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- arm64-apple-darwin22/libstdc++-v3/src/.libs -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- arm64-apple-darwin22/libstdc++-v3/libsupc++/.libs -isystem /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- arm64-apple-darwin22/libstdc++-v3/include/arm64-apple-darwin22 -isystem /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- arm64-apple-darwin22/libstdc++-v3/include -isystem /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libstdc++-v3/libsupc++ -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- arm64-apple-darwin22/libstdc++-v3/src/.libs -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- arm64-apple-darwin22/libstdc++-v3/libsupc++/.libs -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/../include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/include -I/opt/local/include -g -O2 -fno-checking -gtoggle -W -Wall -Wno-narrowing -Wwrite-strings -Wmissing-format-attribute -pedantic -Wno-long-long -Werror -fno-exceptions -fno-rtti -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/../include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/include -I/opt/local/include -fPIC -c -o charset.o -MT charset.o -MMD -MP -MF .deps/charset.Tpo /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/charset.cc :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/charset.cc: In function 'const uchar* convert_escape(cpp_reader*, const uchar*, const uchar*, _cpp_strbuf*, cset_converter, cpp_string_location_reader*, cpp_substring_ranges*)': :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/charset.cc:2207:18: error: 'int sprintf(char*, const char*, ...)' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Werror=deprecated-declarations] :info:build 2207 | sprintf(buf, "%03o", (int) c); :info:build | ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~ :info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/system.h:38, :info:build from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/gcc-darwin- arm64-31e39275410a7a83f18e344a332bf5812f759a5e/libcpp/charset.cc:21: :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/prev- gcc/include-fixed/stdio.h:204:10: note: declared here :info:build 204 | int sprintf(char * __restrict, const char * __restrict, ...) __printflike(2, 3); :info:build | ^~~~~~~ :info:build cc1plus: all warnings being treated as errors :info:build make[3]: *** [charset.o] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/libcpp' :info:build make[2]: *** [all-stage2-libcpp] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build' :info:build make[1]: *** [stage2-bubble] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build' :info:build make: *** [bootstrap-lean] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build" && /usr/bin/make -j1 -w bootstrap-lean :info:build Exit code: 2 :error:build Failed to build libgcc-devel: command execution failed :debug:build Error code: CHILDSTATUS 77900 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 19:41:56 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 19:41:56 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.df365e63ae46e7482d51fee37fc44766@macports.org> #66365: Failed to build libgcc-devel: command execution failed ------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: gcc-devel | ------------------------+--------------------------- Comment (by VinzenzBildstein): Also, since this ticket is attributed to the port "gcc-devel" it does not show up when trying to search for issues with the port "libgcc-devel". I don't know if it's possible to change this easily. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 19:42:55 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 19:42:55 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.e217af2db34e4b8d2bc84664ea26b9ac@macports.org> #66365: Failed to build libgcc-devel: command execution failed ---------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Changes (by slackero): * port: gcc-devel => libgcc-devel -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 20:32:06 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 20:32:06 -0000 Subject: [MacPorts] #66394: Error when installing gcc11 on Ventura 13.0.1 Message-ID: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> #66394: Error when installing gcc11 on Ventura 13.0.1 ---------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gcc11 ---------------------+-------------------- ---> Fetching archive for p5.34-locale-gettext Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 -locale-gettext ---> Verifying checksums for p5.34-locale-gettext Error: Checksum (rmd160) mismatch for gettext-1.07.tar.gz Error: Checksum (sha256) mismatch for gettext-1.07.tar.gz Error: Failed to checksum p5.34-locale-gettext: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5 -locale-gettext/p5.34-locale-gettext/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gcc11 failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 20:37:59 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 20:37:59 -0000 Subject: [MacPorts] #66395: Error installing gnu plot on Ventura 13.0.1 Message-ID: <044.49dde1fb33b132184f22c2a99e261580@macports.org> #66395: Error installing gnu plot on Ventura 13.0.1 ---------------------+--------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gnuplot ---------------------+--------------------- ---> Fetching archive for p5.34-gssapi Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-gssapi ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-gssapi ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34-gssapi ---> Verifying checksums for p5.34-gssapi Error: Checksum (sha1) mismatch for GSSAPI-0.28.tar.gz Error: Checksum (rmd160) mismatch for GSSAPI-0.28.tar.gz Error: Failed to checksum p5.34-gssapi: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-gssapi/p5.34-gssapi/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gnuplot failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 20:39:36 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 20:39:36 -0000 Subject: [MacPorts] #66395: Error installing gnu plot on Ventura 13.0.1 In-Reply-To: <044.49dde1fb33b132184f22c2a99e261580@macports.org> References: <044.49dde1fb33b132184f22c2a99e261580@macports.org> Message-ID: <059.f4a06b1e8e32d19236fcdec8c2a9256e@macports.org> #66395: Error installing gnu plot on Ventura 13.0.1 ----------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | ----------------------+-------------------- Comment (by imos-99): Trying to install gnuplot on Intel Mac, encountered errors: Error: Checksum (sha1) mismatch for GSSAPI-0.28.tar.gz Error: Checksum (rmd160) mismatch for GSSAPI-0.28.tar.gz -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 20:49:43 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 20:49:43 -0000 Subject: [MacPorts] #66394: Error when installing gcc11 on Ventura 13.0.1 In-Reply-To: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> References: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> Message-ID: <059.05a4f368866156ba8f84945ec6f0b222@macports.org> #66394: Error when installing gcc11 on Ventura 13.0.1 ------------------------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: request | Status: new Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5.34-locale-gettext, gcc11 | ------------------------------------------+-------------------- Changes (by imos-99): * priority: Normal => High * type: defect => request * port: gcc11 => p5.34-locale-gettext, gcc11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 20:59:52 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 20:59:52 -0000 Subject: [MacPorts] #66396: Error: Checksum (rmd160/sha256) mismatch for gettext-1.07.tar.gz in Ventura 13.0.1 Message-ID: <044.8f7c1a9566311610d3da21ec9f257673@macports.org> #66396: Error: Checksum (rmd160/sha256) mismatch for gettext-1.07.tar.gz in Ventura 13.0.1 ---------------------+---------------------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: | Port: p5.34-locale-gettext ---------------------+---------------------------------- ---> Computing dependencies for p5.34-locale-gettext ---> Fetching archive for p5.34-locale-gettext Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 -locale-gettext ---> Verifying checksums for p5.34-locale-gettext Error: Checksum (rmd160) mismatch for gettext-1.07.tar.gz Error: Checksum (sha256) mismatch for gettext-1.07.tar.gz Error: Failed to checksum p5.34-locale-gettext: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5 -locale-gettext/p5.34-locale-gettext/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port p5.34-locale-gettext failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:00:34 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:00:34 -0000 Subject: [MacPorts] #66396: Error: Checksum (rmd160/sha256) mismatch for gettext-1.07.tar.gz in Ventura 13.0.1 In-Reply-To: <044.8f7c1a9566311610d3da21ec9f257673@macports.org> References: <044.8f7c1a9566311610d3da21ec9f257673@macports.org> Message-ID: <059.d5c41d4846b68b65a3d91485d8e77b75@macports.org> #66396: Error: Checksum (rmd160/sha256) mismatch for gettext-1.07.tar.gz in Ventura 13.0.1 -----------------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5.34-locale-gettext | -----------------------------------+-------------------- Comment (by imos-99): I was trying to remedy this issue by following the Macports FAQ, but was unable to do so. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:17:49 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:17:49 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 is missing a dependency on a fuse port (was: ext2fuse @0.8.1_3 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing) In-Reply-To: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> References: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> Message-ID: <061.dce656ab0bf9687a63dfd62400208937@macports.org> #66391: ext2fuse @0.8.1_3 is missing a dependency on a fuse port ------------------------+---------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ext2fuse | ------------------------+---------------------- Changes (by jmroot): * status: new => assigned * keywords: highsierra => * owner: (none) => ra1nb0w Comment: The dependency appears to have been removed in [d45dad7484d80bcd546d596fee4061310dd2b7b3/macports-ports]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:21:31 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:21:31 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.a179a61bfb00cd15e5fc21024baa3436@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+---------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: macfuse | ------------------------+---------------------- Changes (by jmroot): * owner: (none) => ra1nb0w * cc: mohd-akram (added) * status: new => assigned * keywords: hoghsierra => Comment: The error quoted in the description is from ext2fuse, not macfuse. The attached log doesn't appear to contain any error. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:29:38 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:29:38 -0000 Subject: [MacPorts] #66394: p5.34-locale-gettext checksum mismatch (was: Error when installing gcc11 on Ventura 13.0.1) In-Reply-To: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> References: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> Message-ID: <059.dca30d92b623bf4ebe516ff606f16962@macports.org> #66394: p5.34-locale-gettext checksum mismatch --------------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5-locale-gettext | --------------------------------+-------------------- Changes (by jmroot): * priority: High => Normal * port: p5.34-locale-gettext, gcc11 => p5-locale-gettext * type: request => defect Old description: > ---> Fetching archive for p5.34-locale-gettext > Warning: Your DNS servers incorrectly claim to know the address of > nonexistent hosts. This may cause checksum mismatches for some ports. See > this page for more information: > > ---> Attempting to fetch p5.34-locale- > gettext-1.70.0_1.darwin_22.x86_64.tbz2 from > https://packages.macports.org/p5.34-locale-gettext > ---> Attempting to fetch p5.34-locale- > gettext-1.70.0_1.darwin_22.x86_64.tbz2 from > http://mirror.fcix.net/macports/packages/p5.34-locale-gettext > ---> Attempting to fetch p5.34-locale- > gettext-1.70.0_1.darwin_22.x86_64.tbz2 from > https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 > -locale-gettext > ---> Verifying checksums for p5.34-locale-gettext > Error: Checksum (rmd160) mismatch for gettext-1.07.tar.gz > Error: Checksum (sha256) mismatch for gettext-1.07.tar.gz > Error: Failed to checksum p5.34-locale-gettext: Unable to verify file > checksums > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5 > -locale-gettext/p5.34-locale-gettext/main.log for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port gcc11 failed New description: {{{ ---> Fetching archive for p5.34-locale-gettext Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 -locale-gettext ---> Verifying checksums for p5.34-locale-gettext Error: Checksum (rmd160) mismatch for gettext-1.07.tar.gz Error: Checksum (sha256) mismatch for gettext-1.07.tar.gz Error: Failed to checksum p5.34-locale-gettext: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5 -locale-gettext/p5.34-locale-gettext/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gcc11 failed }}} -- Comment: Probably a dead mirror combined with your broken DNS (as per the warning). To do anything about it, we need to know which mirror the download came from, which is not shown in the output you quoted. wiki:FAQ#checksums -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:32:18 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:32:18 -0000 Subject: [MacPorts] #66395: p5.34-gssapi checksum mismatch (was: Error installing gnu plot on Ventura 13.0.1) In-Reply-To: <044.49dde1fb33b132184f22c2a99e261580@macports.org> References: <044.49dde1fb33b132184f22c2a99e261580@macports.org> Message-ID: <059.ccb9f748abcdfbc56487683fd14cd71e@macports.org> #66395: p5.34-gssapi checksum mismatch ------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5-gssapi | ------------------------+-------------------- Changes (by jmroot): * port: gnuplot => p5-gssapi Old description: > ---> Fetching archive for p5.34-gssapi > Warning: Your DNS servers incorrectly claim to know the address of > nonexistent hosts. This may cause checksum mismatches for some ports. See > this page for more information: > > ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 > from https://packages.macports.org/p5.34-gssapi > ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 > from http://mirror.fcix.net/macports/packages/p5.34-gssapi > ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 > from > https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34-gssapi > ---> Verifying checksums for p5.34-gssapi > Error: Checksum (sha1) mismatch for GSSAPI-0.28.tar.gz > Error: Checksum (rmd160) mismatch for GSSAPI-0.28.tar.gz > Error: Failed to checksum p5.34-gssapi: Unable to verify file checksums > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-gssapi/p5.34-gssapi/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port gnuplot failed New description: {{{ ---> Fetching archive for p5.34-gssapi Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-gssapi ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-gssapi ---> Attempting to fetch p5.34-gssapi-0.280.0_3.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34-gssapi ---> Verifying checksums for p5.34-gssapi Error: Checksum (sha1) mismatch for GSSAPI-0.28.tar.gz Error: Checksum (rmd160) mismatch for GSSAPI-0.28.tar.gz Error: Failed to checksum p5.34-gssapi: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-gssapi/p5.34-gssapi/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gnuplot failed }}} -- Comment: Same underlying problem as #66394, just with a different port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:32:38 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:32:38 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.c56a93016a9923bfe6eb44f0135e8d32@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+---------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: macfuse | ------------------------+---------------------- Comment (by ballapete): Sorry, I see it now too. I asked port to build more than package. I am going to clean my Mac and try again! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:34:21 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:34:21 -0000 Subject: [MacPorts] #66396: p5.34-locale-gettext checksum mismatch (was: Error: Checksum (rmd160/sha256) mismatch for gettext-1.07.tar.gz in Ventura 13.0.1) In-Reply-To: <044.8f7c1a9566311610d3da21ec9f257673@macports.org> References: <044.8f7c1a9566311610d3da21ec9f257673@macports.org> Message-ID: <059.087b21a10924334311f564eff4f3e4a2@macports.org> #66396: p5.34-locale-gettext checksum mismatch --------------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: p5-locale-gettext | --------------------------------+-------------------- Changes (by jmroot): * status: new => closed * priority: High => Normal * resolution: => duplicate * port: p5.34-locale-gettext => p5-locale-gettext Old description: > ---> Computing dependencies for p5.34-locale-gettext > ---> Fetching archive for p5.34-locale-gettext > Warning: Your DNS servers incorrectly claim to know the address of > nonexistent hosts. This may cause checksum mismatches for some ports. See > this page for more information: > > ---> Attempting to fetch p5.34-locale- > gettext-1.70.0_1.darwin_22.x86_64.tbz2 from > https://packages.macports.org/p5.34-locale-gettext > ---> Attempting to fetch p5.34-locale- > gettext-1.70.0_1.darwin_22.x86_64.tbz2 from > http://mirror.fcix.net/macports/packages/p5.34-locale-gettext > ---> Attempting to fetch p5.34-locale- > gettext-1.70.0_1.darwin_22.x86_64.tbz2 from > https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 > -locale-gettext > ---> Verifying checksums for p5.34-locale-gettext > Error: Checksum (rmd160) mismatch for gettext-1.07.tar.gz > Error: Checksum (sha256) mismatch for gettext-1.07.tar.gz > Error: Failed to checksum p5.34-locale-gettext: Unable to verify file > checksums > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5 > -locale-gettext/p5.34-locale-gettext/main.log for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port p5.34-locale-gettext failed New description: {{{ ---> Computing dependencies for p5.34-locale-gettext ---> Fetching archive for p5.34-locale-gettext Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-locale-gettext ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 -locale-gettext ---> Verifying checksums for p5.34-locale-gettext Error: Checksum (rmd160) mismatch for gettext-1.07.tar.gz Error: Checksum (sha256) mismatch for gettext-1.07.tar.gz Error: Failed to checksum p5.34-locale-gettext: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5 -locale-gettext/p5.34-locale-gettext/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port p5.34-locale-gettext failed }}} -- Comment: #66394 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:39:45 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:39:45 -0000 Subject: [MacPorts] #66394: p5.34-locale-gettext checksum mismatch In-Reply-To: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> References: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> Message-ID: <059.4832e64e826d2276c9020d6a4d08a0bc@macports.org> #66394: p5.34-locale-gettext checksum mismatch --------------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5-locale-gettext | --------------------------------+-------------------- Comment (by imos-99): Where could I find the info about the mirror? In the log file? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:46:47 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:46:47 -0000 Subject: [MacPorts] #66394: p5.34-locale-gettext checksum mismatch In-Reply-To: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> References: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> Message-ID: <059.7ba3d5ada36e8ffa5c57f0427c53439e@macports.org> #66394: p5.34-locale-gettext checksum mismatch --------------------------------+-------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: p5-locale-gettext | --------------------------------+-------------------- Comment (by imos-99): Here is the list of mirrors and errors from the main.log file: :msg:archivefetch ---> Fetching archive for p5.34-locale-gettext :warn:archivefetch Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information: :debug:archivefetch Executing org.macports.archivefetch (p5.34-locale- gettext) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 506/501 :info:archivefetch ---> p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/p5.34-locale-gettext :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/p5.34-locale-gettext :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch p5.34-locale- gettext-1.70.0_1.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/p5.34 -locale-gettext :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:fetch fetch phase started at Sun Dec 4 13:36:00 PST 2022 :notice:fetch ---> Fetching distfiles for p5.34-locale-gettext :debug:fetch elevating privileges for fetch: euid changed to 0, egid changed to 0. :debug:fetch dropping privileges: euid changed to 506, egid changed to 501. :debug:fetch Executing org.macports.fetch (p5.34-locale-gettext) :info:fetch ---> gettext-1.07.tar.gz does not exist in /opt/local/var/macports/distfiles/perl5 :notice:fetch ---> Attempting to fetch gettext-1.07.tar.gz from http://download.xs4all.nl/CPAN/modules/by-module/Locale :debug:fetch Privilege de-escalation not attempted as not running as root. :debug:checksum checksum phase started at Sun Dec 4 13:36:01 PST 2022 :notice:checksum ---> Verifying checksums for p5.34-locale-gettext :debug:checksum Executing org.macports.checksum (p5.34-locale-gettext) :info:checksum ---> Checksumming gettext-1.07.tar.gz :debug:checksum Calculated (rmd160) is 9c1185a5c5e9fc54612808977ee8f548b2258d31 :error:checksum Checksum (rmd160) mismatch for gettext-1.07.tar.gz :info:checksum Portfile checksum: gettext-1.07.tar.gz rmd160 0f5efafdfa6ede6b766cbb5dac12c980b3566068 :info:checksum Distfile checksum: gettext-1.07.tar.gz rmd160 9c1185a5c5e9fc54612808977ee8f548b2258d31 :debug:checksum Calculated (sha256) is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 :error:checksum Checksum (sha256) mismatch for gettext-1.07.tar.gz :info:checksum Portfile checksum: gettext-1.07.tar.gz sha256 909d47954697e7c04218f972915b787bd1244d75e3bd01620bc167d5bbc49c15 :info:checksum Distfile checksum: gettext-1.07.tar.gz sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 :info:checksum The correct checksum line may be: :info:checksum checksums rmd160 9c1185a5c5e9fc54612808977ee8f548b2258d31 \ :info:checksum sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 \ :info:checksum size 0 :error:checksum Failed to checksum p5.34-locale-gettext: Unable to verify file checksums -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 21:53:33 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 21:53:33 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.dba3aa012b16e3b1c325d70c975e5baa@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing ------------------------+---------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: macfuse | ------------------------+---------------------- Comment (by ballapete): `macfuse` builds without problem ? and it's so fast, that it's almost invisible. This is my failure! BTW, `ext4fuse` has a working dependency to `macfuse` or `osxfuse`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:05:27 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 22:05:27 -0000 Subject: [MacPorts] #66229: glib-2.70.5:Uses GCC 4.2 instead of present GCC 7, leading to build failure. In-Reply-To: <045.1568b16871ff0dbb9e662742fc9951fa@macports.org> References: <045.1568b16871ff0dbb9e662742fc9951fa@macports.org> Message-ID: <060.32c255133166b433aacb079f91cfd9c3@macports.org> #66229: glib-2.70.5:Uses GCC 4.2 instead of present GCC 7, leading to build failure. -----------------------+-------------------- Reporter: AutumnHW | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.0 Resolution: fixed | Keywords: Port: glib2 | -----------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: https://github.com/macports/macports- ports/commit/bf232c7a084bee232ee1e6988402b6c9688fc200 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:27:31 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 22:27:31 -0000 Subject: [MacPorts] #66394: p5.34-locale-gettext checksum mismatch In-Reply-To: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> References: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> Message-ID: <059.96195da79bba8d12df6c2867cf14420a@macports.org> #66394: p5.34-locale-gettext checksum mismatch --------------------------------+-------------------- Reporter: imos-99 | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-locale-gettext | --------------------------------+-------------------- Changes (by jmroot): * status: new => closed * owner: (none) => jmroot * resolution: => fixed Comment: In [changeset:"f2239f7fce387cf09097c3717f494c7fa14e0c83/macports-ports" f2239f7fce387cf09097c3717f494c7fa14e0c83/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f2239f7fce387cf09097c3717f494c7fa14e0c83" Remove dead mirror download.xs4all.nl Fixes: https://trac.macports.org/ticket/66394 Fixes: https://trac.macports.org/ticket/66395 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:27:31 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 22:27:31 -0000 Subject: [MacPorts] #66395: p5.34-gssapi checksum mismatch In-Reply-To: <044.49dde1fb33b132184f22c2a99e261580@macports.org> References: <044.49dde1fb33b132184f22c2a99e261580@macports.org> Message-ID: <059.ffed14da52a8f71b21161139ed334b80@macports.org> #66395: p5.34-gssapi checksum mismatch ------------------------+-------------------- Reporter: imos-99 | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-gssapi | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * owner: (none) => jmroot * resolution: => fixed Comment: In [changeset:"f2239f7fce387cf09097c3717f494c7fa14e0c83/macports-ports" f2239f7fce387cf09097c3717f494c7fa14e0c83/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f2239f7fce387cf09097c3717f494c7fa14e0c83" Remove dead mirror download.xs4all.nl Fixes: https://trac.macports.org/ticket/66394 Fixes: https://trac.macports.org/ticket/66395 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:30:34 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 22:30:34 -0000 Subject: [MacPorts] #66394: p5.34-locale-gettext checksum mismatch In-Reply-To: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> References: <044.0090dcf9cca216b6acaa99db746e9d82@macports.org> Message-ID: <059.aaf0af2f39a27c7980f9fd99af337720@macports.org> #66394: p5.34-locale-gettext checksum mismatch --------------------------------+-------------------- Reporter: imos-99 | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: p5-locale-gettext | --------------------------------+-------------------- Comment (by jmroot): Once that change reaches the rsync server, you should be good to go after a `sudo port selfupdate` and a `sudo port clean --dist p5.34-locale- gettext`. I would still advise switching to a better DNS server if possible. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 22:48:18 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 22:48:18 -0000 Subject: [MacPorts] #65877: gpgme @1.17.1 does not build on PPC Tiger, Mac OS X 10.4.11, because "ath.h:80:36: error: unknown type name 'fd_set'; did you mean 'nfds_t'?'" In-Reply-To: <046.08a185a40ede2e920b6da2d42f318938@macports.org> References: <046.08a185a40ede2e920b6da2d42f318938@macports.org> Message-ID: <061.fa548613025ff1910ddec72e3a63f1a9@macports.org> #65877: gpgme @1.17.1 does not build on PPC Tiger, Mac OS X 10.4.11, because "ath.h:80:36: error: unknown type name 'fd_set'; did you mean 'nfds_t'?'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger ppc Port: gpgme | ------------------------+----------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"008a3a69aa93ac53a081b80a4a325eb55b9ca8c6/macports-ports" 008a3a69aa93ac53a081b80a4a325eb55b9ca8c6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="008a3a69aa93ac53a081b80a4a325eb55b9ca8c6" gpgme: fix build on Tiger the header is not being pulled in on Tiger as it is on newer systems. cf port:libassuan closes: https://trac.macports.org/ticket/65877 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 23:16:32 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 23:16:32 -0000 Subject: [MacPorts] #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing In-Reply-To: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> References: <046.4caee0893bb98be02a777b5d5645c8ca@macports.org> Message-ID: <061.812286b17d35fd2e5cfa0ad86c1771ee@macports.org> #66392: macfuse @4.4.1 does not build on macOS High Sierra, Version 10.13.6, because fuse_lowlevel.h is missing -------------------------+--------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: Port: macfuse | -------------------------+--------------------- Changes (by kencu): * status: assigned => closed * resolution: => worksforme Comment: thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 23:19:16 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 23:19:16 -0000 Subject: [MacPorts] #65877: gpgme @1.17.1 does not build on PPC Tiger, Mac OS X 10.4.11, because "ath.h:80:36: error: unknown type name 'fd_set'; did you mean 'nfds_t'?'" In-Reply-To: <046.08a185a40ede2e920b6da2d42f318938@macports.org> References: <046.08a185a40ede2e920b6da2d42f318938@macports.org> Message-ID: <061.cc4f2a3ba12513c529c57f9d9d3fa236@macports.org> #65877: gpgme @1.17.1 does not build on PPC Tiger, Mac OS X 10.4.11, because "ath.h:80:36: error: unknown type name 'fd_set'; did you mean 'nfds_t'?'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger ppc Port: gpgme | ------------------------+----------------------- Comment (by kencu): noted that POLL should be disabled on older system. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 4 23:23:12 2022 From: noreply at macports.org (MacPorts) Date: Sun, 04 Dec 2022 23:23:12 -0000 Subject: [MacPorts] #66397: gpgme @1.18: consider forcing POLL to be disabled on older systems Message-ID: <042.d40b9d2cc8a8e228a2832ea6f7255d89@macports.org> #66397: gpgme @1.18: consider forcing POLL to be disabled on older systems --------------------+-------------------- Reporter: kencu | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gpgme --------------------+-------------------- https://trac.macports.org/ticket/65877#comment:1 "Note that 10.8 and older have a buggy poll implementation which will potentially be a problem for this port. It may be best to disable use of poll on those OS versions and let it fall back to using select." -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:12:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 04:12:19 -0000 Subject: [MacPorts] #66111: libedit @20221009-3.1 uses an old configure argument In-Reply-To: <046.2fe2b8af6915c724270129981f6cdba8@macports.org> References: <046.2fe2b8af6915c724270129981f6cdba8@macports.org> Message-ID: <061.cb9deba91037c88c701e74279aeeddae@macports.org> #66111: libedit @20221009-3.1 uses an old configure argument --------------------------+--------------------------------- Reporter: ballapete | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: monterey, leopard Port: libedit | --------------------------+--------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => worksforme Comment: looks like nothing to do here. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:53:15 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 04:53:15 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.51fb811db2d9c954c270bafa4a94f66b@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: somewhere fixed, as it builds now: https://ports.macports.org/port/xorg-libxcb/details/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 04:55:52 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 04:55:52 -0000 Subject: [MacPorts] #54411: elftoolchain @0.7.1 won't build on Snow Leopard, Mac OS X 10.6.8, (cxx_stdlib = libc++) because of "Undefined symbols for architecture x86_64" In-Reply-To: <046.4d2dcc7e0239025b438ddb9872395c51@macports.org> References: <046.4d2dcc7e0239025b438ddb9872395c51@macports.org> Message-ID: <061.84f27413e2335adfb973d3b0289b628a@macports.org> #54411: elftoolchain @0.7.1 won't build on Snow Leopard, Mac OS X 10.6.8, (cxx_stdlib = libc++) because of "Undefined symbols for architecture x86_64" ---------------------------+----------------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.4.1 Resolution: fixed | Keywords: snowleopard legacy-os Port: elftoolchain | ---------------------------+----------------------------------- Changes (by Ken <21211439+kencu@?>): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"95ff57af1e75a91181f0fa6bb3af67d7e351b8ee/macports-ports" 95ff57af1e75a91181f0fa6bb3af67d7e351b8ee/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="95ff57af1e75a91181f0fa6bb3af67d7e351b8ee" elftoolchain: fix missing strnlen closes: https://trac.macports.org/ticket/54411 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:09:15 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:09:15 -0000 Subject: [MacPorts] #64152: Clang-11 uses on macOS Monterey, Version 12.0.1, C header files Xcode 13, i.e. macOS' Clang 13 In-Reply-To: <046.f4c0a3aa01ced111a0755ccb6b8ead15@macports.org> References: <046.f4c0a3aa01ced111a0755ccb6b8ead15@macports.org> Message-ID: <061.8d75cdfae7f6a91165c285ca03662abe@macports.org> #64152: Clang-11 uses on macOS Monterey, Version 12.0.1, C header files Xcode 13, i.e. macOS' Clang 13 -------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: worksforme | Keywords: monterey Port: clang-11 | -------------------------+---------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: nothing to fix here -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:12:20 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:12:20 -0000 Subject: [MacPorts] #64021: clamav @0.104.1_1 does not build on PPC Mac OS X 10.4.11, Tiger, because: 'O_SYMLINK' undeclared In-Reply-To: <046.e787740a7049ff0ef7763ef98c06a372@macports.org> References: <046.e787740a7049ff0ef7763ef98c06a372@macports.org> Message-ID: <061.59b63d2b057d4c0f9dcc701a4f64f075@macports.org> #64021: clamav @0.104.1_1 does not build on PPC Mac OS X 10.4.11, Tiger, because: 'O_SYMLINK' undeclared -----------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: wontfix | Keywords: tiger Port: legacy-support | -----------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => wontfix Comment: a new port, clamav-legacy, is needed because the current clamav port requires rust to build. The new port is being tracked here: #64613 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:15:27 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:15:27 -0000 Subject: [MacPorts] #65305: libdeflate @1.11 does not build on PPC Mac OS X 10.4.11, Tiger, because: Makefile:130: *** only one `else' per conditional. Stop. In-Reply-To: <046.d0b1891f0bc4e3a5ad95d301f4112c7b@macports.org> References: <046.d0b1891f0bc4e3a5ad95d301f4112c7b@macports.org> Message-ID: <061.22efe69ec9efa593573bcfb9f50f7b4b@macports.org> #65305: libdeflate @1.11 does not build on PPC Mac OS X 10.4.11, Tiger, because: Makefile:130: *** only one `else' per conditional. Stop. -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger Port: libdeflate | -------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:16:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:16:19 -0000 Subject: [MacPorts] #65305: libdeflate @1.11 does not build on PPC Mac OS X 10.4.11, Tiger, because: Makefile:130: *** only one `else' per conditional. Stop. In-Reply-To: <046.d0b1891f0bc4e3a5ad95d301f4112c7b@macports.org> References: <046.d0b1891f0bc4e3a5ad95d301f4112c7b@macports.org> Message-ID: <061.0fd79f45b34f082a3572cab5a2a946eb@macports.org> #65305: libdeflate @1.11 does not build on PPC Mac OS X 10.4.11, Tiger, because: Makefile:130: *** only one `else' per conditional. Stop. -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger Port: libdeflate | -------------------------+-------------------- Comment (by kencu): someone might open a new ticket about gmake being always used by libdeflate, but this issue, the build failure on Tiger, is closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:18:53 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:18:53 -0000 Subject: [MacPorts] #38338: Pdftk @1.44 +gcc45 crashes by default In-Reply-To: <046.1e245010cd556f2f8dd8a6f91f3a34e9@macports.org> References: <046.1e245010cd556f2f8dd8a6f91f3a34e9@macports.org> Message-ID: <061.39cd43e65ecf64ab6adb6d4b54938d8a@macports.org> #38338: Pdftk @1.44 +gcc45 crashes by default ------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: pdftk | ------------------------+------------------------ Changes (by kencu): * status: new => closed * resolution: => fixed Comment: I have used pdftk on virtually all systems without crashes. If you see a crash with a current pdftk build, pls open a new ticket with current information. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:20:26 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:20:26 -0000 Subject: [MacPorts] #39791: libstdcxx 4.8.1 fails to build on PPC Tiger because of undefined symbols In-Reply-To: <046.8add8ba6f452e728c8d83a09ac3139e4@macports.org> References: <046.8add8ba6f452e728c8d83a09ac3139e4@macports.org> Message-ID: <061.9420712267b41fedb5787c06a643a719@macports.org> #39791: libstdcxx 4.8.1 fails to build on PPC Tiger because of undefined symbols ------------------------+------------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.99 Resolution: wontfix | Keywords: powerpc powerpc64 tiger Port: libstdcxx | ------------------------+------------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => wontfix Comment: this port no longer exists -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:23:23 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:23:23 -0000 Subject: [MacPorts] #41752: binutils-2.24 fails to build on PPC Tiger because of "multiple definitions of symbol _filename_cmp" In-Reply-To: <046.97ac8792ca3083e41c1d7d2fdaa4de98@macports.org> References: <046.97ac8792ca3083e41c1d7d2fdaa4de98@macports.org> Message-ID: <061.f9cc5ed231f9680b7ab8b6c01f692d79@macports.org> #41752: binutils-2.24 fails to build on PPC Tiger because of "multiple definitions of symbol _filename_cmp" ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.99 Resolution: fixed | Keywords: Port: binutils | ------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: sounds like you sorted this out a decade ago. If this still is an issue for you, please open up a new ticket with a new log with current information. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:25:04 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:25:04 -0000 Subject: [MacPorts] #59115: libssh2 @1.9.0 fails to build on PPC Mac OS X 10.5.8 because '#pragma GCC diagnostic not allowed inside functions' In-Reply-To: <046.8da065f24b26e62fcd87afc2a2f1dea8@macports.org> References: <046.8da065f24b26e62fcd87afc2a2f1dea8@macports.org> Message-ID: <061.a2a1254ac652c9af2ae2395fd4f20e8b@macports.org> #59115: libssh2 @1.9.0 fails to build on PPC Mac OS X 10.5.8 because '#pragma GCC diagnostic not allowed inside functions' ------------------------+--------------------- Reporter: ballapete | Owner: Gminfly Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: leopard Port: libssh2 | ------------------------+--------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: https://github.com/macports/macports- ports/commit/00257b8e56ac982a52514abf0e609a83509657b9 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:26:54 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:26:54 -0000 Subject: [MacPorts] #59939: pstoedit @3.75 does not build (documentation) on High Sierra because latex2man.sty is missing In-Reply-To: <046.2e5c3271f31aac480617b368c86d4e87@macports.org> References: <046.2e5c3271f31aac480617b368c86d4e87@macports.org> Message-ID: <061.824879345a8aba6ead1c77a376b444f6@macports.org> #59939: pstoedit @3.75 does not build (documentation) on High Sierra because latex2man.sty is missing ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: Port: pstoedit | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: builds on high sierra now: https://ports.macports.org/port/pstoedit/details/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:28:59 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:28:59 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2361958=3A_Build_of_python38_=40?= =?utf-8?q?3=2E8=2E7_fails_on_intel_Big_Sur=2C_macOS_11=2E1=2C_so?= =?utf-8?q?mehow=E2=80=A6?= In-Reply-To: <046.61cf28a6380ab9d1978342d637eed123@macports.org> References: <046.61cf28a6380ab9d1978342d637eed123@macports.org> Message-ID: <061.c83ec600b9e66785a30bb5f4984dee14@macports.org> #61958: Build of python38 @3.8.7 fails on intel Big Sur, macOS 11.1, somehow? -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: worksforme | Keywords: bigsur Port: python38 | -------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 05:32:20 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 05:32:20 -0000 Subject: [MacPorts] #18931: /opt/local/share/info/dir contains defective content In-Reply-To: <046.191f170f53abe882db48a1e542f88abf@macports.org> References: <046.191f170f53abe882db48a1e542f88abf@macports.org> Message-ID: <061.6168d8d045663c72a49e8a4e5f371d96@macports.org> #18931: /opt/local/share/info/dir contains defective content ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Resolution: fixed | Keywords: Port: | ------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: after 14 years, I don't see anything to fix here -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 06:03:57 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 06:03:57 -0000 Subject: [MacPorts] #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 Message-ID: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 ---------------------+---------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: | Port: libgcc11 ---------------------+---------------------- Intel 64 bit processor Mac Pro, Ventura 13.0.1, Xcode 14.5 Encountered error (copied from main.log): Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -B./ _muldi3_s.o _negdi2_s.o _lshrdi3_s.o _ashldi3_s.o _ashrdi3_s.o _cmpdi2_s.o _ucmpdi2_s.o _clear_cache_s.o _trampoline_s.o __main_s.o _absvsi2_s.o _absvdi2_s.o _addvsi3_s.o _addvdi3_s.o _subvsi3_s.o _subvdi3_s.o _mulvsi3_s.o _mulvdi3_s.o _negvsi2_s.o _negvdi2_s.o _ctors_s.o _ffssi2_s.o _ffsdi2_s.o _clz_s.o _clzsi2_s.o _clzdi2_s.o _ctzsi2_s.o _ctzdi2_s.o _popcount_tab_s.o _popcountsi2_s.o _popcountdi2_s.o _paritysi2_s.o _paritydi2_s.o _powisf2_s.o _powidf2_s.o _powixf2_s.o _powitf2_s.o _mulhc3_s.o _mulsc3_s.o _muldc3_s.o _mulxc3_s.o _multc3_s.o _divhc3_s.o _divsc3_s.o _divdc3_s.o _divxc3_s.o _divtc3_s.o _bswapsi2_s.o _bswapdi2_s.o _clrsbsi2_s.o _clrsbdi2_s.o _fixunssfsi_s.o _fixunsdfsi_s.o _fixunsxfsi_s.o _fixsfdi_s.o _fixdfdi_s.o _fixxfdi_s.o _fixunssfdi_s.o _fixunsdfdi_s.o _fixunsxfdi_s.o _floatdisf_s.o _floatdidf_s.o _floatdixf_s.o _floatundisf_s.o _floatundidf_s.o _floatundixf_s.o _fixsfti_s.o _fixdfti_s.o _fixxfti_s.o _fixtfti_s.o _fixunssfti_s.o _fixunsdfti_s.o _fixunsxfti_s.o _fixunstfti_s.o _floattisf_s.o _floattidf_s.o _floattixf_s.o _floattitf_s.o _floatuntisf_s.o _floatuntidf_s.o _floatuntixf_s.o _floatuntitf_s.o _divdi3_s.o _moddi3_s.o _divmoddi4_s.o _udivdi3_s.o _umoddi3_s.o _udivmoddi4_s.o _udiv_w_sdiv_s.o darwin-64_s.o heap-trampoline_s.o cpuinfo_s.o sfp-exceptions_s.o addtf3_s.o divtf3_s.o eqtf2_s.o getf2_s.o letf2_s.o multf3_s.o negtf2_s.o subtf3_s.o unordtf2_s.o fixtfsi_s.o fixunstfsi_s.o floatsitf_s.o floatunsitf_s.o fixtfdi_s.o fixunstfdi_s.o floatditf_s.o floatunditf_s.o fixtfti_s.o fixunstfti_s.o floattitf_s.o floatuntitf_s.o extendsftf2_s.o extenddftf2_s.o extendxftf2_s.o trunctfsf2_s.o trunctfdf2_s.o trunctfxf2_s.o enable-execute-stack_s.o emutls_s.o libgcc.a -lSystem :info:build MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- multi-lib | sed -e 's/;.*$//'` ; \ :info:build for mlib in $MLIBS ; do \ :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ :info:build done :info:build xgcc: warning: could not understand version '13.0' :info:build lipo -output libgcc_s.1.1.dylib \ :info:build -create libgcc_s.1.1.dylib_T* :info:build rm libgcc_s.1.1.dylib_T* :info:build MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- multi-lib | sed -e 's/;.*$//'` ; \ :info:build for mlib in $MLIBS ; do \ :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ :info:build arch=`lipo -info libgcc_s.1.1.dylib_T_${mlib} | sed -e 's/.*:\ //'` ; \ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking -arch ${arch} -nodefaultlibs -dynamiclib -nodefaultrpaths \ :info:build -o libgcc_s.1.dylib_T_${mlib} \ :info:build -Wl,-reexport_library,libgcc_s.1.1.dylib_T_${mlib} \ :info:build -lSystem \ :info:build -Wl,-reexported_symbols_list,/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/gcc-11.3.0/libgcc/config /darwin-unwind.ver \ :info:build -install_name @rpath/libgcc_s.1.dylib \ :info:build -compatibility_version 1 -current_version 1.1 ; \ :info:build done :info:build xgcc: warning: could not understand version '13.0' :info:build xgcc: warning: could not understand version '13.0' :info:build ld: targeted OS version does not support -reexported_symbols_list :info:build collect2: error: ld returned 1 exit status :info:build make[3]: *** [libgcc_s.1.dylib] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64 -apple-darwin22/libgcc' :info:build make[2]: *** [all-stage1-target-libgcc] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build make[1]: *** [stage1-bubble] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build make: *** [bootstrap-lean] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build" && /usr/bin/make -j8 -w bootstrap-lean :info:build Exit code: 2 :error:build Failed to build libgcc11: command execution failed :debug:build Error code: CHILDSTATUS 62135 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/main.log for details. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 08:58:28 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 08:58:28 -0000 Subject: [MacPorts] #66399: php82-zip is missing Message-ID: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> #66399: php82-zip is missing --------------------+-------------------- Reporter: temp | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------+-------------------- Since php82 will be released on thursday, I'm wondering why php82-zip is still missing, isn't it a core extension? Just updated to php82 RC7, and still no zip extension. Is this known? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 09:36:11 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 09:36:11 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.46c8b877607c122c081d8b60e383d0b9@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Changes (by jmroot): * cc: kencu (added) Comment: But does it build with +docs? That's not a default variant. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 09:44:23 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 09:44:23 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2361958=3A_Build_of_python38_=40?= =?utf-8?q?3=2E8=2E7_fails_on_intel_Big_Sur=2C_macOS_11=2E1=2C_so?= =?utf-8?q?mehow=E2=80=A6?= In-Reply-To: <046.61cf28a6380ab9d1978342d637eed123@macports.org> References: <046.61cf28a6380ab9d1978342d637eed123@macports.org> Message-ID: <061.0d5545b3f3260b06280171565b803afd@macports.org> #61958: Build of python38 @3.8.7 fails on intel Big Sur, macOS 11.1, somehow? -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: worksforme | Keywords: bigsur Port: python38 | -------------------------+-------------------- Comment (by jmroot): The ticket doesn't mention it anywhere but this must have been with +optimizations, and would have been fixed by [4866e21854ac067f6e55ffad6c65094f3a2484ab/macports-ports], FTR. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 09:47:12 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 09:47:12 -0000 Subject: [MacPorts] #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 In-Reply-To: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> References: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> Message-ID: <059.6b0ceb78ca83922a3ae69c9d55cc9d05@macports.org> #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 -----------------------+--------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc11 | -----------------------+--------------------- Changes (by jmroot): * keywords: => ventura * priority: High => Normal Old description: > Intel 64 bit processor Mac Pro, Ventura 13.0.1, Xcode 14.5 > > Encountered error (copied from main.log): > Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -B./ _muldi3_s.o > _negdi2_s.o _lshrdi3_s.o _ashldi3_s.o _ashrdi3_s.o _cmpdi2_s.o > _ucmpdi2_s.o _clear_cache_s.o _trampoline_s.o __main_s.o _absvsi2_s.o > _absvdi2_s.o _addvsi3_s.o _addvdi3_s.o _subvsi3_s.o _subvdi3_s.o > _mulvsi3_s.o _mulvdi3_s.o _negvsi2_s.o _negvdi2_s.o _ctors_s.o > _ffssi2_s.o _ffsdi2_s.o _clz_s.o _clzsi2_s.o _clzdi2_s.o _ctzsi2_s.o > _ctzdi2_s.o _popcount_tab_s.o _popcountsi2_s.o _popcountdi2_s.o > _paritysi2_s.o _paritydi2_s.o _powisf2_s.o _powidf2_s.o _powixf2_s.o > _powitf2_s.o _mulhc3_s.o _mulsc3_s.o _muldc3_s.o _mulxc3_s.o _multc3_s.o > _divhc3_s.o _divsc3_s.o _divdc3_s.o _divxc3_s.o _divtc3_s.o _bswapsi2_s.o > _bswapdi2_s.o _clrsbsi2_s.o _clrsbdi2_s.o _fixunssfsi_s.o _fixunsdfsi_s.o > _fixunsxfsi_s.o _fixsfdi_s.o _fixdfdi_s.o _fixxfdi_s.o _fixunssfdi_s.o > _fixunsdfdi_s.o _fixunsxfdi_s.o _floatdisf_s.o _floatdidf_s.o > _floatdixf_s.o _floatundisf_s.o _floatundidf_s.o _floatundixf_s.o > _fixsfti_s.o _fixdfti_s.o _fixxfti_s.o _fixtfti_s.o _fixunssfti_s.o > _fixunsdfti_s.o _fixunsxfti_s.o _fixunstfti_s.o _floattisf_s.o > _floattidf_s.o _floattixf_s.o _floattitf_s.o _floatuntisf_s.o > _floatuntidf_s.o _floatuntixf_s.o _floatuntitf_s.o _divdi3_s.o > _moddi3_s.o _divmoddi4_s.o _udivdi3_s.o _umoddi3_s.o _udivmoddi4_s.o > _udiv_w_sdiv_s.o darwin-64_s.o heap-trampoline_s.o cpuinfo_s.o sfp- > exceptions_s.o addtf3_s.o divtf3_s.o eqtf2_s.o getf2_s.o letf2_s.o > multf3_s.o negtf2_s.o subtf3_s.o unordtf2_s.o fixtfsi_s.o fixunstfsi_s.o > floatsitf_s.o floatunsitf_s.o fixtfdi_s.o fixunstfdi_s.o floatditf_s.o > floatunditf_s.o fixtfti_s.o fixunstfti_s.o floattitf_s.o floatuntitf_s.o > extendsftf2_s.o extenddftf2_s.o extendxftf2_s.o trunctfsf2_s.o > trunctfdf2_s.o trunctfxf2_s.o enable-execute-stack_s.o emutls_s.o > libgcc.a -lSystem > :info:build > MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc > -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ > -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- > darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem > /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- > multi-lib | sed -e 's/;.*$//'` ; \ > :info:build for mlib in $MLIBS ; do \ > :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ > :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ > :info:build done > :info:build xgcc: warning: could not understand version '13.0' > :info:build lipo -output libgcc_s.1.1.dylib \ > :info:build -create libgcc_s.1.1.dylib_T* > :info:build rm libgcc_s.1.1.dylib_T* > :info:build > MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc > -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ > -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- > darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem > /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- > multi-lib | sed -e 's/;.*$//'` ; \ > :info:build for mlib in $MLIBS ; do \ > :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ > :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ > :info:build arch=`lipo -info libgcc_s.1.1.dylib_T_${mlib} | sed -e > 's/.*:\ //'` ; \ > :info:build > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc > -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ > -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- > darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem > /opt/local/x86_64-apple-darwin22/sys-include -fno-checking -arch > ${arch} -nodefaultlibs -dynamiclib -nodefaultrpaths \ > :info:build -o libgcc_s.1.dylib_T_${mlib} \ > :info:build -Wl,-reexport_library,libgcc_s.1.1.dylib_T_${mlib} \ > :info:build -lSystem \ > :info:build > -Wl,-reexported_symbols_list,/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/gcc-11.3.0/libgcc/config > /darwin-unwind.ver \ > :info:build -install_name @rpath/libgcc_s.1.dylib \ > :info:build -compatibility_version 1 -current_version 1.1 ; \ > :info:build done > :info:build xgcc: warning: could not understand version '13.0' > :info:build xgcc: warning: could not understand version '13.0' > :info:build ld: targeted OS version does not support > -reexported_symbols_list > :info:build collect2: error: ld returned 1 exit status > :info:build make[3]: *** [libgcc_s.1.dylib] Error 1 > :info:build make[3]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64 > -apple-darwin22/libgcc' > :info:build make[2]: *** [all-stage1-target-libgcc] Error 2 > :info:build make[2]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' > :info:build make[1]: *** [stage1-bubble] Error 2 > :info:build make[1]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' > :info:build make: *** [bootstrap-lean] Error 2 > :info:build make: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' > :info:build Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build" > && /usr/bin/make -j8 -w bootstrap-lean > :info:build Exit code: 2 > :error:build Failed to build libgcc11: command execution failed > :debug:build Error code: CHILDSTATUS 62135 2 > :debug:build Backtrace: command execution failed > :debug:build while executing > :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" > :debug:build invoked from within > :debug:build "command_exec -callback > portprogress::target_progress_callback build" > :debug:build (procedure "portbuild::build_main" line 8) > :debug:build invoked from within > :debug:build "$procedure $targetname" > :error:build See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/main.log > for details. New description: Intel 64 bit processor Mac Pro, Ventura 13.0.1, Xcode 14.5 Encountered error (copied from main.log): {{{ Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -B./ _muldi3_s.o _negdi2_s.o _lshrdi3_s.o _ashldi3_s.o _ashrdi3_s.o _cmpdi2_s.o _ucmpdi2_s.o _clear_cache_s.o _trampoline_s.o __main_s.o _absvsi2_s.o _absvdi2_s.o _addvsi3_s.o _addvdi3_s.o _subvsi3_s.o _subvdi3_s.o _mulvsi3_s.o _mulvdi3_s.o _negvsi2_s.o _negvdi2_s.o _ctors_s.o _ffssi2_s.o _ffsdi2_s.o _clz_s.o _clzsi2_s.o _clzdi2_s.o _ctzsi2_s.o _ctzdi2_s.o _popcount_tab_s.o _popcountsi2_s.o _popcountdi2_s.o _paritysi2_s.o _paritydi2_s.o _powisf2_s.o _powidf2_s.o _powixf2_s.o _powitf2_s.o _mulhc3_s.o _mulsc3_s.o _muldc3_s.o _mulxc3_s.o _multc3_s.o _divhc3_s.o _divsc3_s.o _divdc3_s.o _divxc3_s.o _divtc3_s.o _bswapsi2_s.o _bswapdi2_s.o _clrsbsi2_s.o _clrsbdi2_s.o _fixunssfsi_s.o _fixunsdfsi_s.o _fixunsxfsi_s.o _fixsfdi_s.o _fixdfdi_s.o _fixxfdi_s.o _fixunssfdi_s.o _fixunsdfdi_s.o _fixunsxfdi_s.o _floatdisf_s.o _floatdidf_s.o _floatdixf_s.o _floatundisf_s.o _floatundidf_s.o _floatundixf_s.o _fixsfti_s.o _fixdfti_s.o _fixxfti_s.o _fixtfti_s.o _fixunssfti_s.o _fixunsdfti_s.o _fixunsxfti_s.o _fixunstfti_s.o _floattisf_s.o _floattidf_s.o _floattixf_s.o _floattitf_s.o _floatuntisf_s.o _floatuntidf_s.o _floatuntixf_s.o _floatuntitf_s.o _divdi3_s.o _moddi3_s.o _divmoddi4_s.o _udivdi3_s.o _umoddi3_s.o _udivmoddi4_s.o _udiv_w_sdiv_s.o darwin-64_s.o heap-trampoline_s.o cpuinfo_s.o sfp-exceptions_s.o addtf3_s.o divtf3_s.o eqtf2_s.o getf2_s.o letf2_s.o multf3_s.o negtf2_s.o subtf3_s.o unordtf2_s.o fixtfsi_s.o fixunstfsi_s.o floatsitf_s.o floatunsitf_s.o fixtfdi_s.o fixunstfdi_s.o floatditf_s.o floatunditf_s.o fixtfti_s.o fixunstfti_s.o floattitf_s.o floatuntitf_s.o extendsftf2_s.o extenddftf2_s.o extendxftf2_s.o trunctfsf2_s.o trunctfdf2_s.o trunctfxf2_s.o enable-execute-stack_s.o emutls_s.o libgcc.a -lSystem :info:build MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- multi-lib | sed -e 's/;.*$//'` ; \ :info:build for mlib in $MLIBS ; do \ :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ :info:build done :info:build xgcc: warning: could not understand version '13.0' :info:build lipo -output libgcc_s.1.1.dylib \ :info:build -create libgcc_s.1.1.dylib_T* :info:build rm libgcc_s.1.1.dylib_T* :info:build MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- multi-lib | sed -e 's/;.*$//'` ; \ :info:build for mlib in $MLIBS ; do \ :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ :info:build arch=`lipo -info libgcc_s.1.1.dylib_T_${mlib} | sed -e 's/.*:\ //'` ; \ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking -arch ${arch} -nodefaultlibs -dynamiclib -nodefaultrpaths \ :info:build -o libgcc_s.1.dylib_T_${mlib} \ :info:build -Wl,-reexport_library,libgcc_s.1.1.dylib_T_${mlib} \ :info:build -lSystem \ :info:build -Wl,-reexported_symbols_list,/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/gcc-11.3.0/libgcc/config /darwin-unwind.ver \ :info:build -install_name @rpath/libgcc_s.1.dylib \ :info:build -compatibility_version 1 -current_version 1.1 ; \ :info:build done :info:build xgcc: warning: could not understand version '13.0' :info:build xgcc: warning: could not understand version '13.0' :info:build ld: targeted OS version does not support -reexported_symbols_list :info:build collect2: error: ld returned 1 exit status :info:build make[3]: *** [libgcc_s.1.dylib] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64 -apple-darwin22/libgcc' :info:build make[2]: *** [all-stage1-target-libgcc] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build make[1]: *** [stage1-bubble] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build make: *** [bootstrap-lean] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/work/build" && /usr/bin/make -j8 -w bootstrap-lean :info:build Exit code: 2 :error:build Failed to build libgcc11: command execution failed :debug:build Error code: CHILDSTATUS 62135 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/main.log for details. }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 09:49:15 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 09:49:15 -0000 Subject: [MacPorts] #66399: php82-zip is missing In-Reply-To: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> References: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> Message-ID: <056.32245240f3359caaa42a43da29510763@macports.org> #66399: php82-zip is missing ----------------------+------------------------ Reporter: temp | Owner: ryandesign Type: request | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: php-zip | ----------------------+------------------------ Changes (by jmroot): * owner: (none) => ryandesign * status: new => assigned * type: defect => request * port: => php-zip -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:02:06 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:02:06 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.7b14259faa1a8bfcca74bb6737d71f21@macports.org> #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: qore | ------------------------+----------------------- Changes (by snowflake): * Attachment "debug-2022-12-05.log" added. log generated with port -ds -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:05:07 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:05:07 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.94d133d0b0c0babf74612dc14786377a@macports.org> #66390: qore @1.12.3 - configure phase cannot find c++ header "slist" ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: qore | ------------------------+----------------------- Comment (by snowflake): I've made some progress. The El Capitan version now updates the binary from the Macports buildbots. I've confirmed it is building from the same Portfile. I have no idea where the real error lies. My knowledge of Cmake is non- existent, and I haven't not gone anywhere near C++ for many years. Even then, my understanding was minimal. Comparing the buildbot log with my log, I can see very little difference. There is undoubtedly some conflict somewhere. I'll attach a log generated with port -ds It's quite possible that the system clang is missing an include file. Maybe if I was to uninstall all my ports and then build qore it would work. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:07:21 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:07:21 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.f3ac2a867e620266bbfc888fe2bf4190@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): I did not wait again an hour, but even with `Python 3.10` and `doxygen @1.9.3_3` it's stuck here, for ten minutes: {{{ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_x11_xorg-libxcb/xorg- libxcb/work/libxcb-1.15/src/xvmc.h:817: warning: The following parameters of xcb_xvmc_list_subpicture_types_unchecked(xcb_connection_t *c, xcb_xv_port_t port_id, xcb_xvmc_surface_t surface_id) are not documented: parameter 'port_id' parameter 'surface_id' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_x11_xorg-libxcb/xorg- libxcb/work/libxcb-1.15/src/xvmc.h:471: warning: The following parameter of xcb_xvmc_list_surface_types(xcb_connection_t *c, xcb_xv_port_t port_id) is not documented: parameter 'port_id' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_x11_xorg-libxcb/xorg- libxcb/work/libxcb-1.15/src/xvmc.h:483: warning: The following parameter of xcb_xvmc_list_surface_types_unchecked(xcb_connection_t *c, xcb_xv_port_t port_id) is not documented: parameter 'port_id' }}} Building the docs starts here: {{{ Making all in doc make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_x11_xorg-libxcb/xorg- libxcb/work/libxcb-1.15/doc' doxygen xcb.doxygen warning: Tag 'USE_WINDOWS_ENCODING' at line 64 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'DETAILS_AT_TOP' at line 156 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'SHOW_DIRECTORIES' at line 390 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'COLS_IN_ALPHA_INDEX' at line 620 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'HTML_ALIGN_MEMBERS' at line 675 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'XML_SCHEMA' at line 907 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'XML_DTD' at line 913 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'PERL_PATH' at line 1074 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'CLASS_DIAGRAMS' at line 1087 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'MAX_DOT_GRAPH_WIDTH' at line 1197 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag 'MAX_DOT_GRAPH_HEIGHT' at line 1205 of file 'xcb.doxygen' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: argument 'a4wide' for option PAPER_TYPE is not a valid enum value Using the default: a4! }}} But, when I sent an interrupt to `port` a form popped up telling me that `dot` had crashed, `/opt/local/bin/dot` (from `graphviz-devel @7.0.3`). Could be it's worth to upgrade to version `1.9.5 (release date 26 August 2022)`? Or test with `graphviz @7.0.1`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:27:33 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:27:33 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure fails if doxygen is active (was: qore @1.12.3 - configure phase cannot find c++ header "slist") In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.93e32b08fe0958358634cc2dfff85d1e@macports.org> #66390: qore @1.12.3 - configure fails if doxygen is active ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: qore | ------------------------+----------------------- Comment (by snowflake): I tried deactivating `doxygen` and the configure phase now works. Build also succeeds. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:35:06 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:35:06 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure fails if doxygen is active In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.6cc7a054e52c80ec1b7f9e03f890fc6d@macports.org> #66390: qore @1.12.3 - configure fails if doxygen is active ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: qore | ------------------------+----------------------- Comment (by davidnich): thanks for reporting this - I'll try to reproduce, but I only have Venture (13.0.1) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:43:21 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:43:21 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.08e6063c82b9747d6fd10af8bbe2dc86@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): I am building once more watching in another window of GNU Emacs what is happening in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_x11_xorg-libxcb/xorg- libxcb/work/libxcb-1.15/doc/manual. It seems that 1888 DOT files ? la `inherit_graph_<#>.dot` are converted into PNG, MAP and MD5 formats. After conversion the DOT file is deleted. The process started at 12:13 h and seems to have some endurance ? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:56:48 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:56:48 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure fails if doxygen is active In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.31f3c180335d730d7359de756b7a9f3f@macports.org> #66390: qore @1.12.3 - configure fails if doxygen is active ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: qore | ------------------------+----------------------- Comment (by davidnich): the problem was that the tar.bz2 source archive was missing some new Doxygen templates causing builds with doxygen detected to fail. It should be fixed now. Thanks for raising this issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 11:57:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 11:57:19 -0000 Subject: [MacPorts] #66390: qore @1.12.3 - configure fails if doxygen is active In-Reply-To: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> References: <046.19e5184cbb19b358ab7cc0bb0ccf5c08@macports.org> Message-ID: <061.24f99acb5d5b7d0718e645e874365640@macports.org> #66390: qore @1.12.3 - configure fails if doxygen is active ------------------------+----------------------- Reporter: snowflake | Owner: davidnich Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: fixed | Keywords: Port: qore | ------------------------+----------------------- Changes (by davidnich): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 12:45:09 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 12:45:09 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.ae95bd60d64ac86ff32691280dcd4bd4@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): The conversion process of these 1,889 files (they start with a zero number) finished at 13:27 h, followed by some more DOT files. These took another almost ten minutes. Without the docs the port builds in less than a minute. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 13:22:45 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 13:22:45 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.ab192550caf16777fa2c334522ce86d0@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): On a more powerful intel MacBook Pro build with documentation takes less than ten minutes? Could there be a warning in `Portfile` that on some systems (one of them is High Sierra with Sandy Bridge ??BTW, there is a utility I only seldom use that can output the CPU's name, which one is that?) building the docs could take very long? After all: invalid report. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:50:29 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 14:50:29 -0000 Subject: [MacPorts] #66370: py-psycopg2: default to postgresql15 In-Reply-To: <047.bb6d263a72a5a8eec6d20459d12d7066@macports.org> References: <047.bb6d263a72a5a8eec6d20459d12d7066@macports.org> Message-ID: <062.2f4ef06ba643283528477e66a70e1dde@macports.org> #66370: py-psycopg2: default to postgresql15 --------------------------+---------------------- Reporter: mohd-akram | Owner: nerdling Type: enhancement | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-psycopg2 | --------------------------+---------------------- Changes (by nerdling): * status: assigned => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 14:51:39 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 14:51:39 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.162164eb2f6ee4fb4bffa4bf592dc2de@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): On a `PowerBook G4 with Mac OS X 10.5.8, Leopard`, building `xorg-libxcb +docs` took just 75 min. I presume now that `graphviz-devel` is the culprit? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 15:10:11 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 15:10:11 -0000 Subject: [MacPorts] #66370: py-psycopg2: default to postgresql15 In-Reply-To: <047.bb6d263a72a5a8eec6d20459d12d7066@macports.org> References: <047.bb6d263a72a5a8eec6d20459d12d7066@macports.org> Message-ID: <062.e90977b2d1a049e595b303e37947a894@macports.org> #66370: py-psycopg2: default to postgresql15 --------------------------+---------------------- Reporter: mohd-akram | Owner: nerdling Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-psycopg2 | --------------------------+---------------------- Changes (by nerdling): * status: accepted => closed * resolution: => fixed Comment: Replaced postgresql 9.6 with 15 in 95d847a5e3b342f9523d1121bbafe828a85e5dcc. Also kept the old variant for the dead python 27 version of the port. Such out-of-date software really shouldn't be used if security is considered at all. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 15:35:52 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 15:35:52 -0000 Subject: [MacPorts] #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.bc6d7b370272f844638bbea8ef9ea9b7@macports.org> #58540: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): On `intel Monterey` building `xorg-libxcb +docs` with `graphviz-devel` took almost ten minutes as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:08:32 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 16:08:32 -0000 Subject: [MacPorts] #66400: nut @2.7.4_0 Failed to build nut: command execution failed Message-ID: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> #66400: nut @2.7.4_0 Failed to build nut: command execution failed ------------------------------------+----------------------------- Reporter: shardul10 | Owner: (none) Type: defect | Status: new Priority: High | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Keywords: nut _str_rtrim libtool | Port: nut ------------------------------------+----------------------------- :info:build Undefined symbols for architecture arm64: :info:build "_str_rtrim", referenced from: :info:build _nutscan_scan_usb in libnutscan_la-scan_usb.o :info:build ld: symbol(s) not found for architecture arm64 :debug:main Starting logging for nut @2.7.4_0 :debug:sysinfo macOS 13.0.1 (darwin/22.1.0) arch arm :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:08:56 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 16:08:56 -0000 Subject: [MacPorts] #66400: nut @2.7.4_0 Failed to build nut: command execution failed In-Reply-To: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> References: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> Message-ID: <061.dbc14f652f1d2b9758f68321bc0eeddc@macports.org> #66400: nut @2.7.4_0 Failed to build nut: command execution failed ------------------------+------------------------------------ Reporter: shardul10 | Owner: (none) Type: defect | Status: new Priority: High | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Resolution: | Keywords: nut _str_rtrim libtool Port: nut | ------------------------+------------------------------------ Changes (by shardul10): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:12:01 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 16:12:01 -0000 Subject: [MacPorts] #66401: install fails with 404 error Message-ID: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> #66401: install fails with 404 error --------------------------+---------------------------------- Reporter: angryjohnnie | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py310-subprocess-tee --------------------------+---------------------------------- subprocess-tee-0.4.0.tar.gz does not exist in the macports repo or mirrors. the latest version is 0.3.5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:15:34 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 16:15:34 -0000 Subject: [MacPorts] #66400: nut @2.7.4_0 Failed to build nut: command execution failed In-Reply-To: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> References: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> Message-ID: <061.2f49c25ee36b1111fc2a05d164543d06@macports.org> #66400: nut @2.7.4_0 Failed to build nut: command execution failed ------------------------+------------------------------------ Reporter: shardul10 | Owner: (none) Type: defect | Status: new Priority: High | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Resolution: | Keywords: nut _str_rtrim libtool Port: nut | ------------------------+------------------------------------ Comment (by shardul10): Followed the instructions install nut. I am using Apple Mac mini M1 with Ventura 13.0.1 (22A400) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:47:00 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 16:47:00 -0000 Subject: [MacPorts] #58540: xorg-libxcb +docs @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end (was: xorg-libxcb @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end) In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.b32bbf53458d060066970614da04b4ff@macports.org> #58540: xorg-libxcb +docs @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 16:54:57 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 16:54:57 -0000 Subject: [MacPorts] #58540: xorg-libxcb +docs @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.fb972c19f0ca329183e32c6ce1b45a23@macports.org> #58540: xorg-libxcb +docs @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by kencu): If it?s a specific, non-default variant that fails, please remember to put that information in the title as it is relevant to both searching and to ticket cleanup projects. I fixed almost all your Tiger tickets in a few minutes, but sorting out what is still relevant in the rest of your many tickets is taking a long time. Can you find a few minutes to close of the ancient, irrelevant ones? Then I can find and fix the rest of the fixable ones. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 17:09:02 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 17:09:02 -0000 Subject: [MacPorts] #58540: xorg-libxcb +docs @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end In-Reply-To: <046.007a588c6e238a90463e733d5dab8e50@macports.org> References: <046.007a588c6e238a90463e733d5dab8e50@macports.org> Message-ID: <061.a7091a91341a9d72111dc0d020e820cb@macports.org> #58540: xorg-libxcb +docs @1.13.1 does not build on High Sierra (macOS 10.13.6) because building documentation never finds an end --------------------------+------------------------ Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: highsierra Port: xorg-libxcb | --------------------------+------------------------ Comment (by ballapete): Alright! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 17:13:16 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 17:13:16 -0000 Subject: [MacPorts] #46701: kerberos5 does not build on PPC Tiger, Mac OS X 10.4.11, because void value cannot be ignored as it ought to be In-Reply-To: <046.c78d4f9fadec29184efbd0f15e352fdf@macports.org> References: <046.c78d4f9fadec29184efbd0f15e352fdf@macports.org> Message-ID: <061.709e547edc14993c53ea42a99d229cea@macports.org> #46701: kerberos5 does not build on PPC Tiger, Mac OS X 10.4.11, because void value cannot be ignored as it ought to be ------------------------+--------------------------- Reporter: ballapete | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: tiger powerpc Port: kerberos5 | ------------------------+--------------------------- Comment (by ballapete): `Kerberos5` is now `@1.20.1`, installed, and working. So this ticket can be closed IMO. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 17:53:20 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 17:53:20 -0000 Subject: [MacPorts] #54519: py27-cryptography @2.0: error: -Werror=sign-conversion: No option -Wsign-conversion In-Reply-To: <046.c015f63578961c0a1f68d6236bc3ccff@macports.org> References: <046.c015f63578961c0a1f68d6236bc3ccff@macports.org> Message-ID: <061.17917612b44e384c6245ae6ad3f46b68@macports.org> #54519: py27-cryptography @2.0: error: -Werror=sign-conversion: No option -Wsign- conversion ------------------------------+--------------------------------------- Reporter: ballapete | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.4.1 Resolution: | Keywords: tiger leopard snowleopard Port: py-cryptography | ------------------------------+--------------------------------------- Comment (by ballapete): Right now `Tiger` does not need that package, `Python 2.7` is gone, and we're now at version `3.3.2`. Nevertheless, the modern `port` builds with just a few complaints about values set or used in `CPython`. It can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 18:23:18 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 18:23:18 -0000 Subject: [MacPorts] #66069: doxygen @1.9.5 upgrade failure on 10.13.6: error: call to unavailable function 'get': introduced in macOS 10.14 In-Reply-To: <042.58f76604bc10e14c3d0b8dc4c27fed7b@macports.org> References: <042.58f76604bc10e14c3d0b8dc4c27fed7b@macports.org> Message-ID: <057.3a3fdb5bf477f50211c62d66ce9c2796@macports.org> #66069: doxygen @1.9.5 upgrade failure on 10.13.6: error: call to unavailable function 'get': introduced in macOS 10.14 ----------------------+-------------------- Reporter: rufty | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: doxygen | ----------------------+-------------------- Comment (by ballapete): To me it seems that this failure depends on exactly one patch file: `patch-CMakeLists.txt.diff`. Leaving that away `Doxygen 1.9.5`, builds, survives its test at 100%, and also succeeds to build the `xorg-libxcb +docs`. All on `macOS High Sierra, Version 10.13.6`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 18:35:40 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 18:35:40 -0000 Subject: [MacPorts] #46701: kerberos5 does not build on PPC Tiger, Mac OS X 10.4.11, because void value cannot be ignored as it ought to be In-Reply-To: <046.c78d4f9fadec29184efbd0f15e352fdf@macports.org> References: <046.c78d4f9fadec29184efbd0f15e352fdf@macports.org> Message-ID: <061.6f22b7af825c9e07496c4af4d653b148@macports.org> #46701: kerberos5 does not build on PPC Tiger, Mac OS X 10.4.11, because void value cannot be ignored as it ought to be ------------------------+--------------------------- Reporter: ballapete | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: tiger powerpc Port: kerberos5 | ------------------------+--------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 18:36:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 18:36:19 -0000 Subject: [MacPorts] #54519: py27-cryptography @2.0: error: -Werror=sign-conversion: No option -Wsign-conversion In-Reply-To: <046.c015f63578961c0a1f68d6236bc3ccff@macports.org> References: <046.c015f63578961c0a1f68d6236bc3ccff@macports.org> Message-ID: <061.8cab009991a800dca7e33cf4627d1eee@macports.org> #54519: py27-cryptography @2.0: error: -Werror=sign-conversion: No option -Wsign- conversion ------------------------------+--------------------------------------- Reporter: ballapete | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.4.1 Resolution: fixed | Keywords: tiger leopard snowleopard Port: py-cryptography | ------------------------------+--------------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 19:00:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 19:00:13 -0000 Subject: [MacPorts] #66322: swig-clisp, swig-chicken @4.1.0_1: Error: No files have been installed in the destroot directory! In-Reply-To: <048.e43c57a30041154a818e00859b434869@macports.org> References: <048.e43c57a30041154a818e00859b434869@macports.org> Message-ID: <063.0f962d07e6f98e19d5fee84eb9580dcc@macports.org> #66322: swig-clisp, swig-chicken @4.1.0_1: Error: No files have been installed in the destroot directory! --------------------------+----------------------- Reporter: cooljeanius | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: swig | --------------------------+----------------------- Comment (by cooljeanius): Reconfirmed after the update to 4.1.1_0. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 19:54:23 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 19:54:23 -0000 Subject: [MacPorts] #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports Message-ID: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports -----------------------+------------------------- Reporter: snowflake | Owner: nerdling Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: py-psycopg2 -----------------------+------------------------- There is a checksum failure in all sub-ports. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 19:58:43 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 19:58:43 -0000 Subject: [MacPorts] #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports In-Reply-To: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> References: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> Message-ID: <061.88910f25fdfc30594d689526a1dd1198@macports.org> #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports --------------------------+---------------------- Reporter: snowflake | Owner: nerdling Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: py-psycopg2 | --------------------------+---------------------- Changes (by nerdling): * status: assigned => accepted -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:03:37 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 20:03:37 -0000 Subject: [MacPorts] #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports In-Reply-To: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> References: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> Message-ID: <061.40a0a586f336bd9b93615b67809b4d6e@macports.org> #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports --------------------------+---------------------- Reporter: snowflake | Owner: nerdling Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: fixed | Keywords: Port: py-psycopg2 | --------------------------+---------------------- Changes (by nerdling): * status: accepted => closed * resolution: => fixed Comment: Fixed in c4c090577d55a6e1b9698dd4c610a2863c9b4928. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:27:12 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 20:27:12 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.e78061d362a28eabdf47105416d746a3@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+--------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: R | ---------------------------------+--------------------- Changes (by ryrrah): * Attachment "main.2.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:29:01 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 20:29:01 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.bfa3212aaf5ca39b9019ce7bc6d695d7@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+---------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------------------+---------------------- Changes (by ryrrah): * status: closed => reopened * resolution: fixed => Comment: The fix has not worked for me. This still fails to build. I've attached the main.log file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:41:36 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 20:41:36 -0000 Subject: [MacPorts] #66322: swig-clisp, swig-chicken @4.1.0_1: Error: No files have been installed in the destroot directory! In-Reply-To: <048.e43c57a30041154a818e00859b434869@macports.org> References: <048.e43c57a30041154a818e00859b434869@macports.org> Message-ID: <063.8d52744bc77415b9eb95b592f50e578b@macports.org> #66322: swig-clisp, swig-chicken @4.1.0_1: Error: No files have been installed in the destroot directory! --------------------------+----------------------- Reporter: cooljeanius | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: swig | --------------------------+----------------------- Comment (by michaelld): Yup I see this too ... trying to figure out what's going on -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:41:48 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 20:41:48 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.03a83211dc57e3180f63c3f4752abd21@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+--------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: R | ---------------------------------+--------------------- Changes (by i0ntempest): * status: reopened => closed * resolution: => fixed Comment: The errors you?re having is different and unrelated to this ticket (a bunch of implicit declaration and undeclared identifier). Try reinstalling your CLT. If still not resolved please open a new ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 20:47:10 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 20:47:10 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.877ca2142b24d3fc450735fb753943fa@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+--------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: R | ---------------------------------+--------------------- Comment (by kencu): The error also was against a different port, {{{libiodbc}}}, FYI. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:02:25 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:02:25 -0000 Subject: [MacPorts] #57755: libmacho @921 does not build on PPC Mac OS X 10.4.11, Tiger, because /opt/local/bin/i686-apple-darwin8-gcc-apple-4.2.4': execvp: No such file or directory In-Reply-To: <046.2b653121dded86ade4e3259135baa8e2@macports.org> References: <046.2b653121dded86ade4e3259135baa8e2@macports.org> Message-ID: <061.aec822aba90b709a542b1ee169cf3e3a@macports.org> #57755: libmacho @921 does not build on PPC Mac OS X 10.4.11, Tiger, because /opt/local/bin/i686-apple-darwin8-gcc-apple-4.2.4': execvp: No such file or directory ------------------------+---------------------- Reporter: ballapete | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: | Keywords: tiger Port: libmacho | ------------------------+---------------------- Comment (by ballapete): When I remember correctly then `libmacho` was needed by `libunwind`. The latter seems to have finished service, is not needed anymore. The recent `Portfile` seems to be a mess, because `libmacho` cannot be built `apple- gcc42 @5666.3_16+gpl3` because of such reasons with: {{{ /usr/bin/gcc-4.0 -Os -g -Wall -D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_ -D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_ -I. -I./../include -I. -isysroot /Developer/SDKs/MacOSX10.4u.sdk -Os -arch i386 -arch ppc -c -o ./slot_name.o slot_name.c make: xcrun: Command not found static -o ./libmacho.a arch.o getsecbyname.o getsegbyname.o get_end.o swap.o hppa_swap.o i386_swap.o m68k_swap.o sparc_swap.o ppc_swap.o i860_swap.o m88k_swap.o slot_name.o make: static: Command not found make: [libmacho.a] Error 127 (ignored) make: xcrun: Command not found /usr/bin/gcc-4.0 -Os -g -Wall -D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_ -D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_ -I. -I./../include -I. -isysroot /Developer/SDKs/MacOSX10.4u.sdk -Os -arch i386 -arch ppc -dynamiclib \ -o ./libmacho.dylib arch.o getsecbyname.o getsegbyname.o get_end.o swap.o hppa_swap.o i386_swap.o m68k_swap.o sparc_swap.o ppc_swap.o i860_swap.o m88k_swap.o slot_name.o \ -install_name /opt/local/lib/libmacho.1.dylib \ -compatibility_version 1 \ -current_version 949.0.1 \ ./libmacho.dylib make: *** [libmacho.dylib] Segmentation fault (core dumped) make: *** Deleting file `libmacho.dylib' make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_libmacho/libmacho/work/cctools-949.0.1/libmacho' }}} Using `apple-gcc42 @5666.3_15` to build results in the same failure. So let's forget and close this ticket? (Or should I try with apple-gcc42 @5666.3_16?) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:13:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:13:19 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.1d19c6946a7c73f51e1bd33e52062b56@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: TeXShop | --------------------------+-------------------- Comment (by Schamschula): I emailed upstream and got instructions. Unfortunately, it only works when applied manually. I'm working on making it work programmatically. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:30:21 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:30:21 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.bb5522a605eb3afc9a66f8125bbc053b@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: TeXShop | --------------------------+-------------------- Comment (by Schamschula): I've figured it out. I need to remove all references to Sparkle from {{{TeXShop.xcodeproj/project.pbxproj}}}. However, I'll wait for the next version (5.08) to be released. The patch may be unstable from release to release. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:31:39 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:31:39 -0000 Subject: [MacPorts] #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' In-Reply-To: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> References: <055.aa706bff1f33dcbd75adeb9742da65af@macports.org> Message-ID: <070.1e481f335b9727066de544827c71badb@macports.org> #66095: R @ 4.2.1_1: failed to build ''ATSFontFindFromName' is unavailable' ---------------------------------+--------------------- Reporter: karoliskoncevicius | Owner: kjellpk Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: R | ---------------------------------+--------------------- Comment (by kencu): I just installed "R" on Ventura Intel without any trouble. Finished a few minutes ago: {{{ % port -v installed R The following ports are currently installed: R @4.2.2_2+builtin_lapack+cairo+gcc12+openmp+recommended+x11 (active) requested_variants='' platform='darwin 22' archs='x86_64' date='2022-12-05T13:15:02-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:40:00 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:40:00 -0000 Subject: [MacPorts] #59122: py-numpy @1.17.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of "'for' loop initial declaration used outside C99 mode" In-Reply-To: <046.121a36ddf176a94d3ddc32b9f0c13277@macports.org> References: <046.121a36ddf176a94d3ddc32b9f0c13277@macports.org> Message-ID: <061.ddce51dd101fb623aff5e1c7540bf0a5@macports.org> #59122: py-numpy @1.17.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of "'for' loop initial declaration used outside C99 mode" ------------------------+----------------------- Reporter: ballapete | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.0 Resolution: | Keywords: tiger Port: py-numpy | ------------------------+----------------------- Comment (by ballapete): This package is not needed anymore by some other `port` (once needed by `boost`?). When I start to build it I still see {{{ /usr/bin/gnutar: numpy-1.23.5/.coveragerc: implausibly old time stamp 1970-01-01 01:00:00 }}} plus a few hundred similar lines. When will this vanish? I have `lbzip2` installed, doesn't this work without such silly complaints? `CC='/opt/local/bin/gcc-mp-7'` is now recorded in the build process' environment, so it should build. Before I see this report: {{{ Running from numpy source directory. /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py310-numpy/work/numpy-1.23.5/setup.py:86: DeprecationWarning: `numpy.distutils` is deprecated since NumPy 1.23.0, as a result of the deprecation of `distutils` itself. It will be removed for Python >= 3.12. For older Python versions it will remain present. It is recommended to use `setuptools < 60.0` for those Python versions. For more details, see: https://numpy.org/devdocs/reference/distutils_status_migration.html }}} `py-numpy` and `py310-numpy` built, because the `Portfile` was upgraded. So this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:42:03 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:42:03 -0000 Subject: [MacPorts] #59571: py37-numpy @1.17.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of many errors In-Reply-To: <046.177352f4aac536f1d23c08558bc210e5@macports.org> References: <046.177352f4aac536f1d23c08558bc210e5@macports.org> Message-ID: <061.6f09f27bd5b69f8148333544d6173fcd@macports.org> #59571: py37-numpy @1.17.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of many errors ------------------------+----------------------- Reporter: ballapete | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: tiger Port: py-numpy | ------------------------+----------------------- Comment (by ballapete): Meanwhile a more up-to-date version builds without problem. So this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:45:15 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:45:15 -0000 Subject: [MacPorts] #60162: bash @5.0.16 builds on PPC Mac OS X 10.4.11, Tiger, with an error In-Reply-To: <046.31846b147544635e3715d6e4c367283c@macports.org> References: <046.31846b147544635e3715d6e4c367283c@macports.org> Message-ID: <061.7a4235244d19a8fb477e14529c5428cc@macports.org> #60162: bash @5.0.16 builds on PPC Mac OS X 10.4.11, Tiger, with an error ------------------------+------------------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: tiger powerpc legacy-os Port: bash | ------------------------+------------------------------------- Comment (by ballapete): `bash @5.2.9` could be built and installed, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:49:31 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:49:31 -0000 Subject: [MacPorts] #61094: intltool @0.51.0_5 still depends on Perl 5.28 In-Reply-To: <046.f4d4a04808798c33cdcc1458bf93cf84@macports.org> References: <046.f4d4a04808798c33cdcc1458bf93cf84@macports.org> Message-ID: <061.11e655e0d2598698fbd98f631fd6dfeb@macports.org> #61094: intltool @0.51.0_5 still depends on Perl 5.28 --------------------------+---------------------- Reporter: ballapete | Owner: dbevans Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: intltool | --------------------------+---------------------- Comment (by ballapete): `intltool @0.51.0` is still installed but uses now `p5.34-getopt-long, p5.34-pathtools, p5.34-scalar-list-utils, p5.34-xml-parser`. So this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:49:58 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:49:58 -0000 Subject: [MacPorts] #60162: bash @5.0.16 builds on PPC Mac OS X 10.4.11, Tiger, with an error In-Reply-To: <046.31846b147544635e3715d6e4c367283c@macports.org> References: <046.31846b147544635e3715d6e4c367283c@macports.org> Message-ID: <061.99ce7a3efe4c322ed84c80739a76a0dd@macports.org> #60162: bash @5.0.16 builds on PPC Mac OS X 10.4.11, Tiger, with an error ------------------------+------------------------------------- Reporter: ballapete | Owner: raimue Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: tiger powerpc legacy-os Port: bash | ------------------------+------------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:50:22 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:50:22 -0000 Subject: [MacPorts] #59571: py37-numpy @1.17.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of many errors In-Reply-To: <046.177352f4aac536f1d23c08558bc210e5@macports.org> References: <046.177352f4aac536f1d23c08558bc210e5@macports.org> Message-ID: <061.9f957820c9757d46088a00f4bd255524@macports.org> #59571: py37-numpy @1.17.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of many errors ------------------------+----------------------- Reporter: ballapete | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: tiger Port: py-numpy | ------------------------+----------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:50:53 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:50:53 -0000 Subject: [MacPorts] #59122: py-numpy @1.17.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of "'for' loop initial declaration used outside C99 mode" In-Reply-To: <046.121a36ddf176a94d3ddc32b9f0c13277@macports.org> References: <046.121a36ddf176a94d3ddc32b9f0c13277@macports.org> Message-ID: <061.eb0a68731cfbba4ebb25b60bd07aac98@macports.org> #59122: py-numpy @1.17.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of "'for' loop initial declaration used outside C99 mode" ------------------------+----------------------- Reporter: ballapete | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.0 Resolution: fixed | Keywords: tiger Port: py-numpy | ------------------------+----------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:51:10 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:51:10 -0000 Subject: [MacPorts] #61094: intltool @0.51.0_5 still depends on Perl 5.28 In-Reply-To: <046.f4d4a04808798c33cdcc1458bf93cf84@macports.org> References: <046.f4d4a04808798c33cdcc1458bf93cf84@macports.org> Message-ID: <061.f3c69482ce87b9aa41a0383b4ff652f5@macports.org> #61094: intltool @0.51.0_5 still depends on Perl 5.28 --------------------------+--------------------- Reporter: ballapete | Owner: dbevans Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: intltool | --------------------------+--------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:51:14 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:51:14 -0000 Subject: [MacPorts] #61276: meson @0.55.3: /usr/bin/gnutar: meson-0.55.3/COPYING: implausibly old time stamp 1970-01-01 01:00:00 In-Reply-To: <046.0a86d98c16e6b9b16b81c2068cd51dda@macports.org> References: <046.0a86d98c16e6b9b16b81c2068cd51dda@macports.org> Message-ID: <061.eef4515d6472a38a8cd266faf3bd8a9d@macports.org> #61276: meson @0.55.3: /usr/bin/gnutar: meson-0.55.3/COPYING: implausibly old time stamp 1970-01-01 01:00:00 ------------------------+--------------------------------------------- Reporter: ballapete | Owner: git@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger leopard powerpc legacy-os Port: meson | ------------------------+--------------------------------------------- Comment (by ballapete): This fault is more numerous than ever, because the Python folks are updating their packages as if tomorrow will be another day. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:59:44 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:59:44 -0000 Subject: [MacPorts] #61276: meson @0.55.3: /usr/bin/gnutar: meson-0.55.3/COPYING: implausibly old time stamp 1970-01-01 01:00:00 In-Reply-To: <046.0a86d98c16e6b9b16b81c2068cd51dda@macports.org> References: <046.0a86d98c16e6b9b16b81c2068cd51dda@macports.org> Message-ID: <061.0b85b6675e98ae8ed644ee39018c90b9@macports.org> #61276: meson @0.55.3: /usr/bin/gnutar: meson-0.55.3/COPYING: implausibly old time stamp 1970-01-01 01:00:00 ------------------------+--------------------------------------------- Reporter: ballapete | Owner: git@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger leopard powerpc legacy-os Port: meson | ------------------------+--------------------------------------------- Comment (by kencu): Does https://github.com/python/cpython/pull/29693 being committed mean that at some point this problem will just disappear, when newer pythons are being used more commonly? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 21:59:51 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 21:59:51 -0000 Subject: [MacPorts] #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version In-Reply-To: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> References: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> Message-ID: <061.9d0dabc22b9d3be25efce23afa385f10@macports.org> #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version -----------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.6.3 Resolution: | Keywords: haspatch Port: graphviz-devel | -----------------------------+-------------------------------- Comment (by ballapete): Right now `graphviz-devel @7.0.3_0+gdk_pixbuf+pangocairo+poppler+rsvg+x11` is installed. It still has this fault: {{{ pete 234 /\ l -t /opt/local/share/man/man1 | more total 20264 lrwxr-xr-x 1 root admin 8 5 Dez 21:30 dot2gxl.1 -> gv2gxl.1 pete 237 /\ man dot2gxl man: No such file or directory Failed to open the message catalog man on the path NLSPATH= No manual entry for dot2gxl }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:02:45 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:02:45 -0000 Subject: [MacPorts] #61526: libzzip @0.13.71 can be built with Python 3 In-Reply-To: <046.0e60b006e46ea05b4721f6b15155fc65@macports.org> References: <046.0e60b006e46ea05b4721f6b15155fc65@macports.org> Message-ID: <061.c55e025ae6d92b677c66cf796ad0bc84@macports.org> #61526: libzzip @0.13.71 can be built with Python 3 --------------------------+---------------------- Reporter: ballapete | Owner: mojca Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: bigsur Port: libzzip | --------------------------+---------------------- Comment (by ballapete): Right now ` libzzip @0.13.72_0` is installed and it makes uses of `Python 3`: {{{ pete 239 /\ port deps libzzip Full Name: libzzip @0.13.72_0 Build Dependencies: cmake, pkgconfig, python310, apple-gcc42 Library Dependencies: zlib Test Dependencies: unzip, zip }}} So this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:06:11 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:06:11 -0000 Subject: [MacPorts] #63328: kerberos5 @1.19.2 needs corrected configure options In-Reply-To: <046.6ee674f0245ed130b17ea27713a5a001@macports.org> References: <046.6ee674f0245ed130b17ea27713a5a001@macports.org> Message-ID: <061.80c278121d0e2825075da398f225152e@macports.org> #63328: kerberos5 @1.19.2 needs corrected configure options --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: kerberos5 | --------------------------+------------------------ Comment (by ballapete): Recent `kerberos5 @1.20.1` has stopped using this old `configure option`, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:07:09 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:07:09 -0000 Subject: [MacPorts] #61526: libzzip @0.13.71 can be built with Python 3 In-Reply-To: <046.0e60b006e46ea05b4721f6b15155fc65@macports.org> References: <046.0e60b006e46ea05b4721f6b15155fc65@macports.org> Message-ID: <061.01293b87a420729e3087a216b813c14d@macports.org> #61526: libzzip @0.13.71 can be built with Python 3 --------------------------+-------------------- Reporter: ballapete | Owner: mojca Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: bigsur Port: libzzip | --------------------------+-------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:19:25 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:19:25 -0000 Subject: [MacPorts] #63747: pango @1.48.9_1 seems to need the Python package typogrify, at least on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.7dbaa88521b5affaee481d8f86044982@macports.org> References: <046.7dbaa88521b5affaee481d8f86044982@macports.org> Message-ID: <061.54d7f8cfb5af657b43af96eac637937c@macports.org> #63747: pango @1.48.9_1 seems to need the Python package typogrify, at least on PPC Tiger, Mac OS X 10.4.11 --------------------------+--------------------------- Reporter: ballapete | Owner: mascguy Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger pending Port: pango | --------------------------+--------------------------- Comment (by ballapete): The `dependencies` of `gi-docgen @2022.2` have changed. They are now: {{{ pete 273 /\ port deps gi-docgen pango Full Name: gi-docgen @2022.2_0 Build Dependencies: py310-setuptools, apple-gcc42 Library Dependencies: py310-jinja2, py310-markdown, py310-markupsafe, py310-pygments, py310-toml, py310-typogrify, python310 }}} Building `pango @1.50.7` I see now: {{{ gi-docgen| Project name: gi-docgen gi-docgen| Project version: 2022.2 gi-docgen| Program python3 (jinja2, markdown, markupsafe, pygments, toml, typogrify) found: YES (/opt/local/bin/python3) modules: jinja2, markdown, markupsafe, pygments, toml, typogrify gi-docgen| Program gi-docgen.py found: YES (/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_x11_pango/pango/work/pango-1.50.7/subprojects /gi-docgen/gi-docgen.py) gi-docgen| Configuring gi-docgen.pc using configuration gi-docgen| Build targets in project: 0 gi-docgen| Subproject gi-docgen finished. Dependency gi-docgen from subproject subprojects/gi-docgen found: YES 2022.2 Configuring config.h using configuration Configuring pango-features.h using configuration Program glib-mkenums found: YES (/opt/local/bin/glib-mkenums) Program g-ir-scanner found: YES (/opt/local/bin/g-ir-scanner) Run-time dependency harfbuzz-gobject found: YES 5.3.1 Found pkg-config: /opt/local/bin/pkg-config (0.29.2) Build-time dependency gobject-introspection-1.0 found: YES 1.72.0 Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached) Program g-ir-scanner found: YES (/opt/local/bin/g-ir-scanner) Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached) Program g-ir-compiler found: YES (/opt/local/bin/g-ir-compiler) Program help2man found: YES (/opt/local/bin/help2man) Program build-aux/meson/dist-docs.py found: YES (/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_x11_pango/pango/work/pango-1.50.7 /build-aux/meson/dist-docs.py) Build targets in project: 75 }}} So it's finer than before and the ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:21:20 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:21:20 -0000 Subject: [MacPorts] #63747: pango @1.48.9_1 seems to need the Python package typogrify, at least on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.7dbaa88521b5affaee481d8f86044982@macports.org> References: <046.7dbaa88521b5affaee481d8f86044982@macports.org> Message-ID: <061.83181db8650fa4e8efc93e2641b03e2d@macports.org> #63747: pango @1.48.9_1 seems to need the Python package typogrify, at least on PPC Tiger, Mac OS X 10.4.11 --------------------------+--------------------------- Reporter: ballapete | Owner: mascguy Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger pending Port: pango | --------------------------+--------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:21:56 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:21:56 -0000 Subject: [MacPorts] #63328: kerberos5 @1.19.2 needs corrected configure options In-Reply-To: <046.6ee674f0245ed130b17ea27713a5a001@macports.org> References: <046.6ee674f0245ed130b17ea27713a5a001@macports.org> Message-ID: <061.4accf05c1dc81ae6af8803245db3971b@macports.org> #63328: kerberos5 @1.19.2 needs corrected configure options --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger Port: kerberos5 | --------------------------+------------------------ Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:32:21 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:32:21 -0000 Subject: [MacPorts] #63120: boost176 needs a compiler that supports C++11 In-Reply-To: <046.683b2a00b4d743368f6ae01a9a1b1d21@macports.org> References: <046.683b2a00b4d743368f6ae01a9a1b1d21@macports.org> Message-ID: <061.0615fbab3e41a8a291dc6fcd5ba04bd1@macports.org> #63120: boost176 needs a compiler that supports C++11 ------------------------+------------------------------------ Reporter: ballapete | Owner: Chris Jones Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger Port: boost176 | ------------------------+------------------------------------ Comment (by ballapete): `boost176 @1.76.0_6` is now the standard and it builds easily (within one day). So this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:34:52 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:34:52 -0000 Subject: [MacPorts] #63505: clamav @0.104.0 does not build on PPC Tiger, Mac OS X 10.4.11, because clamav-0.104.0/shared/linux/cert_util_linux.c is missing In-Reply-To: <046.d1a183a0c65d9036c3b39ba1a56c53f7@macports.org> References: <046.d1a183a0c65d9036c3b39ba1a56c53f7@macports.org> Message-ID: <061.c265ed117332dcdb1e829b2c803043ac@macports.org> #63505: clamav @0.104.0 does not build on PPC Tiger, Mac OS X 10.4.11, because clamav-0.104.0/shared/linux/cert_util_linux.c is missing ------------------------+-------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger Port: clamav | ------------------------+-------------------- Comment (by ballapete): `clamav @0.104.4_0` is installed as probably last version (ClamAV 1.0 needs Rust), so this ticket can be closed IMO. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:36:22 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:36:22 -0000 Subject: [MacPorts] #63547: gnupg2 @2.3.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of redefinition of typedef 'KEYBOX_HANDLE' In-Reply-To: <046.3d99c262c1d615fefdcc7d6d676b1756@macports.org> References: <046.3d99c262c1d615fefdcc7d6d676b1756@macports.org> Message-ID: <061.ac32534b2df07ed814aece93ccf18d4a@macports.org> #63547: gnupg2 @2.3.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of redefinition of typedef 'KEYBOX_HANDLE' ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: gnupg2 | ------------------------+-------------------- Comment (by ballapete): `gnupg2 @2.2.40` is now installed, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:42:53 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:42:53 -0000 Subject: [MacPorts] #64023: tcl @8.6.12 does not understand the configure option --enable-corefoundation In-Reply-To: <046.2d550bb475a1f9649a021e448d8883d4@macports.org> References: <046.2d550bb475a1f9649a021e448d8883d4@macports.org> Message-ID: <061.9832f0b9611bfd130eb44a21c3f271f0@macports.org> #64023: tcl @8.6.12 does not understand the configure option --enable- corefoundation ------------------------+--------------------------------- Reporter: ballapete | Owner: MarcusCalhoun-Lopez Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: tcl | ------------------------+--------------------------------- Comment (by ballapete): Since it seems to be more of a Tcl than a MacPorts problem this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:42:56 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:42:56 -0000 Subject: [MacPorts] #63505: clamav @0.104.0 does not build on PPC Tiger, Mac OS X 10.4.11, because clamav-0.104.0/shared/linux/cert_util_linux.c is missing In-Reply-To: <046.d1a183a0c65d9036c3b39ba1a56c53f7@macports.org> References: <046.d1a183a0c65d9036c3b39ba1a56c53f7@macports.org> Message-ID: <061.2e10347e771cdb0114bbeb87fda9057f@macports.org> #63505: clamav @0.104.0 does not build on PPC Tiger, Mac OS X 10.4.11, because clamav-0.104.0/shared/linux/cert_util_linux.c is missing ------------------------+-------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger Port: clamav | ------------------------+-------------------- Comment (by kencu): closed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 22:59:07 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 22:59:07 -0000 Subject: [MacPorts] #58591: check @0.10.0 does not build on PPC Tiger, MacOSX 10.4.11, because of native void function unsetenv() In-Reply-To: <046.83f56b537d664f680d1742a4848fef89@macports.org> References: <046.83f56b537d664f680d1742a4848fef89@macports.org> Message-ID: <061.b0503f537ebe5c94f3511f4a7368a264@macports.org> #58591: check @0.10.0 does not build on PPC Tiger, MacOSX 10.4.11, because of native void function unsetenv() ------------------------+-------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: tiger Port: check | ------------------------+-------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"bc6c3bd1ec9e323062630a3fc90623fca59648a3/macports-ports" bc6c3bd1ec9e323062630a3fc90623fca59648a3/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bc6c3bd1ec9e323062630a3fc90623fca59648a3" check: fix build on Tiger closes: https://trac.macports.org/ticket/58591 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:02:18 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:02:18 -0000 Subject: [MacPorts] #62842: webkit2-gtk @2.28.2_2 +debug+minibrowser+quartz: error: use of undeclared identifier 'remoteProcessID' In-Reply-To: <048.d57a709e15594138625630d4fab16728@macports.org> References: <048.d57a709e15594138625630d4fab16728@macports.org> Message-ID: <063.da7e26d36666b4f63544fe04f2b7ef69@macports.org> #62842: webkit2-gtk @2.28.2_2 +debug+minibrowser+quartz: error: use of undeclared identifier 'remoteProcessID' --------------------------+---------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: haspatch Port: webkit2-gtk | --------------------------+---------------------- Comment (by cooljeanius): Pull request opened: https://github.com/macports/macports-ports/pull/16898 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:11:01 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:11:01 -0000 Subject: [MacPorts] #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown In-Reply-To: <046.f821cfbd8c953cf655691b8779962d59@macports.org> References: <046.f821cfbd8c953cf655691b8779962d59@macports.org> Message-ID: <061.2fca2a22802321775649435a565abc3c@macports.org> #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: leopard Port: pango | --------------------------+------------------------ Comment (by ballapete): The problem with `markdown` seems to be fixed in `pango @1.50.7`, see #63747. The `meson nm` problem is treated in closed ticket #66346, but not solved. I have to apply the patch to my `new meson build` and then to rebuild `pango`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:19:05 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:19:05 -0000 Subject: [MacPorts] #65897: gimp 2.10.32 quartz does not display characters on 10.7 In-Reply-To: <045.4fec85375bb7d41301fb47345382a0c9@macports.org> References: <045.4fec85375bb7d41301fb47345382a0c9@macports.org> Message-ID: <060.c506a302a50748c7b4f1b46c68cae23c@macports.org> #65897: gimp 2.10.32 quartz does not display characters on 10.7 -----------------------+---------------------- Reporter: rmottola | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: lion gtk Port: gimp2 | -----------------------+---------------------- Comment (by rmottola): I'm unsurem @lukaso : I don't really get displayed anything, not squares. Also, i suppose that maybe in that case, it was a quite new macOS system, in my case, I did not change fonts. So perhaps the default changed? strange. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:30:16 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:30:16 -0000 Subject: [MacPorts] #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown In-Reply-To: <046.f821cfbd8c953cf655691b8779962d59@macports.org> References: <046.f821cfbd8c953cf655691b8779962d59@macports.org> Message-ID: <061.50dff144809385f4b152389e2c82e9cb@macports.org> #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: leopard Port: pango | --------------------------+------------------------ Comment (by ballapete): The problem with `"lt_cv_path_NM"` is gone ? was it really a problem with `pango` or rather with `gi-docgen`? This dependency is at first not found although installed: {{{ Dependency sysprof-capture-4 skipped: feature sysprof disabled Run-time dependency gi-docgen found: NO (tried pkgconfig, framework and cmake) Looking for a fallback subproject for the dependency gi-docgen }}} and then rebuilt? {{{ Executing subproject gi-docgen gi-docgen| Project name: gi-docgen gi-docgen| Project version: 2022.2 gi-docgen| Program python3 (jinja2, markdown, markupsafe, pygments, toml, typogrify) found: YES (/opt/local/bin/python3) modules: jinja2, markdown, markupsafe, pygments, toml, typogrify gi-docgen| Program gi-docgen.py found: YES (/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_x11_pango/pango/work/pango-1.50.7/subprojects /gi-docgen/gi-docgen.py) gi-docgen| Configuring gi-docgen.pc using configuration gi-docgen| Build targets in project: 0 gi-docgen| Subproject gi-docgen finished. Dependency gi-docgen from subproject subprojects/gi-docgen found: YES 2022.2 Configuring config.h using configuration }}} Anyway, all dependencies are met. And my `patched version of meson` does not produce the `nm complaints`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:32:31 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:32:31 -0000 Subject: [MacPorts] #66400: nut @2.7.4_0 Failed to build: Undefined symbol "_str_rtrim" (was: nut @2.7.4_0 Failed to build nut: command execution failed) In-Reply-To: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> References: <046.0aeafafabb9e33a727dde442886b0e63@macports.org> Message-ID: <061.31fdf246df95034fffd9e1ce5eabb990@macports.org> #66400: nut @2.7.4_0 Failed to build: Undefined symbol "_str_rtrim" ------------------------+-------------------- Reporter: shardul10 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: nut | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * priority: High => Normal * milestone: MacPorts Future => * keywords: nut _str_rtrim libtool => * resolution: => duplicate Old description: > :info:build Undefined symbols for architecture arm64: > :info:build "_str_rtrim", referenced from: > :info:build _nutscan_scan_usb in libnutscan_la-scan_usb.o > :info:build ld: symbol(s) not found for architecture arm64 > > :debug:main Starting logging for nut @2.7.4_0 > :debug:sysinfo macOS 13.0.1 (darwin/22.1.0) arch arm > :debug:sysinfo MacPorts 2.8.0 > :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 > :debug:sysinfo SDK 13 New description: {{{ :info:build Undefined symbols for architecture arm64: :info:build "_str_rtrim", referenced from: :info:build _nutscan_scan_usb in libnutscan_la-scan_usb.o :info:build ld: symbol(s) not found for architecture arm64 :debug:main Starting logging for nut @2.7.4_0 :debug:sysinfo macOS 13.0.1 (darwin/22.1.0) arch arm :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 }}} -- Comment: #61598 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:36:42 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:36:42 -0000 Subject: [MacPorts] #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown In-Reply-To: <046.f821cfbd8c953cf655691b8779962d59@macports.org> References: <046.f821cfbd8c953cf655691b8779962d59@macports.org> Message-ID: <061.a48455c827587d98ecc2606ce06b502b@macports.org> #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: leopard Port: pango | --------------------------+------------------------ Comment (by ballapete): The reports when handling `PangoOT, PangoFT2, and PangoXft` have vanished ? all in recent version `pango @1.50.7`. IMO this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:41:46 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:41:46 -0000 Subject: [MacPorts] #66401: py310-subprocess-tee @0.4.0: install fails with 404 error (was: install fails with 404 error) In-Reply-To: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> References: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> Message-ID: <064.35055b670827b537caea21f9ba5b85ab@macports.org> #66401: py310-subprocess-tee @0.4.0: install fails with 404 error --------------------------------+---------------------- Reporter: angryjohnnie | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-subprocess-tee | --------------------------------+---------------------- Changes (by jmroot): * owner: (none) => judaew * status: new => assigned * port: py310-subprocess-tee => py-subprocess-tee Comment: Works fine here: {{{ % sudo port -v checksum py310-subprocess-tee Password: ---> Fetching distfiles for py310-subprocess-tee ---> subprocess-tee-0.4.0.tar.gz does not exist in /opt/local/var/macports/distfiles/py-subprocess-tee ---> Attempting to fetch subprocess-tee-0.4.0.tar.gz from https://distfiles.macports.org/py-subprocess-tee % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 12815 100 12815 0 0 10270 0 0:00:01 0:00:01 --:--:-- 10293 ---> Verifying checksums for py310-subprocess-tee ---> Checksumming subprocess-tee-0.4.0.tar.gz }}} Please attach your log. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:47:51 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:47:51 -0000 Subject: [MacPorts] #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports In-Reply-To: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> References: <046.e418f1a0aa361a10d4b4cc7f28b67158@macports.org> Message-ID: <061.1d84eadb6bbe82ccc10e9dedb013dc14@macports.org> #66402: py-psycopg2 @2.9.5 - checksum failure in sub-ports --------------------------+---------------------- Reporter: snowflake | Owner: nerdling Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: fixed | Keywords: Port: py-psycopg2 | --------------------------+---------------------- Comment (by jmroot): Fixed commit link. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:49:52 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:49:52 -0000 Subject: [MacPorts] #65891: py39-libxml2 @2.10.2 does not build on PPC Tiger, Mac OS X 10.4.11, because gcc-apple-4.2 expected in libxml2-py.c something different In-Reply-To: <046.2e5de30273570a8c2fdc5d09d4824c40@macports.org> References: <046.2e5de30273570a8c2fdc5d09d4824c40@macports.org> Message-ID: <061.0ac71973f9e5ea40f46f18c96f32f8b2@macports.org> #65891: py39-libxml2 @2.10.2 does not build on PPC Tiger, Mac OS X 10.4.11, because gcc-apple-4.2 expected in libxml2-py.c something different -------------------------+--------------------------------- Reporter: ballapete | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger ppc Port: py-libxml2 | -------------------------+--------------------------------- Comment (by ballapete): `py310-libxml2 @2.10.2` builds with only a few `warnings`. It can be closed (for `Tiger`). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:52:57 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:52:57 -0000 Subject: [MacPorts] #41199: gconf @2.32.4_3 does not build because of missing symbol _PyUnicodeUCS2_AsUTF8String in/opt/local/lib/gobject-introspection/giscanner/_giscanner.so In-Reply-To: <046.fddb0d29a5b0356be5a57671f1d78816@macports.org> References: <046.fddb0d29a5b0356be5a57671f1d78816@macports.org> Message-ID: <061.49f32793f107721e61f7ad7a1b6993ad@macports.org> #41199: gconf @2.32.4_3 does not build because of missing symbol _PyUnicodeUCS2_AsUTF8String in/opt/local/lib/gobject- introspection/giscanner/_giscanner.so ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: gconf | ------------------------+-------------------------------- Comment (by ballapete): This problem is related to `Python 2` and its kind of handling characters beyond US-ASCII, I think. It can be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:57:03 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:57:03 -0000 Subject: [MacPorts] #61561: blackbox @0.76 does not build on PPC Tiger, Mac OS X 10.4.11, In-Reply-To: <046.e8a0533cfda7e5cb834c8f65f7b8394f@macports.org> References: <046.e8a0533cfda7e5cb834c8f65f7b8394f@macports.org> Message-ID: <061.b4010fcf1fc31a0bbdcc4e24ddd4799d@macports.org> #61561: blackbox @0.76 does not build on PPC Tiger, Mac OS X 10.4.11, ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: tiger ppc Port: blackbox | ------------------------+----------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"8855e386d49f2752c5a2e5709821c26ebd6012fe/macports-ports" 8855e386d49f2752c5a2e5709821c26ebd6012fe/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8855e386d49f2752c5a2e5709821c26ebd6012fe" blackbox: fix missing header on old systems closes: https://trac.macports.org/ticket/61561 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 5 23:59:03 2022 From: noreply at macports.org (MacPorts) Date: Mon, 05 Dec 2022 23:59:03 -0000 Subject: [MacPorts] #57506: libgcc6 @6.5.0 does not build on PPC Mac OS X 10.4.11, Tiger, with G4 (7447A) because of "Bootstrap comparison failure!" In-Reply-To: <046.25c6b2f3cf86267e5130a87058b17dea@macports.org> References: <046.25c6b2f3cf86267e5130a87058b17dea@macports.org> Message-ID: <061.81d7268bf9622022746f294c1a8ce694@macports.org> #57506: libgcc6 @6.5.0 does not build on PPC Mac OS X 10.4.11, Tiger, with G4 (7447A) because of "Bootstrap comparison failure!" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: | Keywords: tiger Port: libgcc6 | ------------------------+-------------------- Comment (by ballapete): The time of this compiler is over. It is possible that missing disk space caused the failure. It can certainly be closed, except there are objections. Then I'll rebuild? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:01:45 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:01:45 -0000 Subject: [MacPorts] #57547: gcc5 @5.5.0_4 does not build on PPC MacOS X 10.4.11, Tiger with HFSX because of "Bootstrap comparison failure!" In-Reply-To: <046.937938c3d618f60a1caa1a98f9d596ff@macports.org> References: <046.937938c3d618f60a1caa1a98f9d596ff@macports.org> Message-ID: <061.f7fb54d0d483cb2981880eccbfaac15b@macports.org> #57547: gcc5 @5.5.0_4 does not build on PPC MacOS X 10.4.11, Tiger with HFSX because of "Bootstrap comparison failure!" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: | Keywords: tiger Port: gcc5 | ------------------------+-------------------- Comment (by ballapete): Here too it's possible that missing disk space caused the failure. If no- one objects: it can be closed. This compiler's time is (almost) used up (I think `pdftk` needs it, or some version GCC 4.x?). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:10:00 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:10:00 -0000 Subject: [MacPorts] #57755: libmacho @921 does not build on PPC Mac OS X 10.4.11, Tiger, because /opt/local/bin/i686-apple-darwin8-gcc-apple-4.2.4': execvp: No such file or directory In-Reply-To: <046.2b653121dded86ade4e3259135baa8e2@macports.org> References: <046.2b653121dded86ade4e3259135baa8e2@macports.org> Message-ID: <061.c08a79c7486bc4f4e9398553360495ab@macports.org> #57755: libmacho @921 does not build on PPC Mac OS X 10.4.11, Tiger, because /opt/local/bin/i686-apple-darwin8-gcc-apple-4.2.4': execvp: No such file or directory ------------------------+---------------------- Reporter: ballapete | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: tiger Port: libmacho | ------------------------+---------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"942bba32d2313fcd417df395ae11591d42a332e6/macports-ports" 942bba32d2313fcd417df395ae11591d42a332e6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="942bba32d2313fcd417df395ae11591d42a332e6" libmacho: fix build on Tiger closes: https://trac.macports.org/ticket/57755 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:23:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:23:08 -0000 Subject: [MacPorts] #64980: python38 @3.8.13 does not build on PPC Tiger, Mac OS X 10.4.11, because: No such file or directory: '/opt/local/include/copyfile.h' In-Reply-To: <046.342bb1b0983e629bf5644d10713b3de2@macports.org> References: <046.342bb1b0983e629bf5644d10713b3de2@macports.org> Message-ID: <061.1b6e43771f6973b9ca6b91f3ba7550f8@macports.org> #64980: python38 @3.8.13 does not build on PPC Tiger, Mac OS X 10.4.11, because: No such file or directory: '/opt/local/include/copyfile.h' ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger Port: python38 | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: python38 installs on Tiger PPC now without intervention: {{{ $ port -v installed python38 The following ports are currently installed: python38 @3.8.15_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-12-05T16:19:18-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:43:02 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:43:02 -0000 Subject: [MacPorts] #61598: nut @2.7.4: Undefined symbols In-Reply-To: <043.219a43199e2f8d5a3cf37ee72d715146@macports.org> References: <043.219a43199e2f8d5a3cf37ee72d715146@macports.org> Message-ID: <058.3e89dda9e328e861d2f56a3142d2d752@macports.org> #61598: nut @2.7.4: Undefined symbols ---------------------+-------------------- Reporter: AP1010 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: bigsur Port: nut | ---------------------+-------------------- Comment (by jmroot): In [changeset:"fd0b4c82f50698b21054caf383a72ac7693e9591/macports-ports" fd0b4c82f50698b21054caf383a72ac7693e9591/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fd0b4c82f50698b21054caf383a72ac7693e9591" nut: patch libtool bug, use add_users See: https://trac.macports.org/ticket/61598 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:48:53 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:48:53 -0000 Subject: [MacPorts] #65407: librsvg @2.40.20_5: build fails on darwin 9, previous revision didn't In-Reply-To: <044.eafaeef6a9f5b5cf709e3549ea595d06@macports.org> References: <044.eafaeef6a9f5b5cf709e3549ea595d06@macports.org> Message-ID: <059.a77811ce17754665b137d8b5c4088900@macports.org> #65407: librsvg @2.40.20_5: build fails on darwin 9, previous revision didn't ----------------------+---------------------- Reporter: kakuhen | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: pending Port: librsvg | ----------------------+---------------------- Comment (by kencu): https://gitlab.gnome.org/GNOME/librsvg/-/commit/104fb592b0c32f9e9e3e9246210682dfa0ce4a60 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:50:20 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:50:20 -0000 Subject: [MacPorts] #61598: nut @2.7.4: Undefined symbols In-Reply-To: <043.219a43199e2f8d5a3cf37ee72d715146@macports.org> References: <043.219a43199e2f8d5a3cf37ee72d715146@macports.org> Message-ID: <058.3d6e60e1268035112c43803d904bdc75@macports.org> #61598: nut @2.7.4: Undefined symbols ---------------------+-------------------- Reporter: AP1010 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: bigsur Port: nut | ---------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 00:53:04 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 00:53:04 -0000 Subject: [MacPorts] #65407: librsvg @2.40.20_5: build fails on darwin 9, previous revision didn't In-Reply-To: <044.eafaeef6a9f5b5cf709e3549ea595d06@macports.org> References: <044.eafaeef6a9f5b5cf709e3549ea595d06@macports.org> Message-ID: <059.83d8a9e4bb070f37712fce126560164e@macports.org> #65407: librsvg @2.40.20_5: build fails on darwin 9, previous revision didn't ----------------------+--------------------- Reporter: kakuhen | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: pending Port: librsvg | ----------------------+--------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"d50c5142902af4c3fcad0868446a185b33f2b40a/macports-ports" d50c5142902af4c3fcad0868446a185b33f2b40a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d50c5142902af4c3fcad0868446a185b33f2b40a" librsvg: fix build on older systems fallback librsvg had a missing vapi dep closes: https://trac.macports.org/ticket/65407 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:31:42 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:31:42 -0000 Subject: [MacPorts] #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) In-Reply-To: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> References: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> Message-ID: <064.d020f0c4b10910b5a1183bdcf18fb167@macports.org> #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) ---------------------------+---------------------------------- Reporter: barracuda156 | Owner: kencu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard, snowleopard Port: gdk-pixbuf2 | ---------------------------+---------------------------------- Comment (by kencu): OK, I bumped into this finally on a Leopard Intel system and may have sorted it out. gdk-pixbuf2 builds on that system with gcc-4.2, but still throws the malloc error that you see when using the new libstdc++ in gcc7.5+. This is a bit of a weird situation, because as far as I can see (looking quickly), there is no c++ code anywhere in gdk-pixbuf2. But somewhere, one of the libraries it links to must invoke some, because crash it does. So we need to do the legacysupport binwrapping trick on the gdk-pixbuf2 binaries. But legacysupport never anticipated this case, so it tries to block you, thinking you're out of your mind perhaps, by making sure you're only binwrapping if the stdlib=macports-libstdc++. So to allow the binwrapping to work, we have to tell MacPorts that is what we are doing, and then it can work, the bins are wrapped, and all works well. Adding this to the gdk-pixbuf2 portfile fixes the bins, in the end: {{{ PortGroup legacysupport 1.1 legacysupport.newest_darwin_requires_legacy 10 legacysupport.redirect_bins gdk-pixbuf-csource gdk-pixbuf-pixdata gdk- pixbuf-query-loaders gdk-pixbuf-thumbnailer compiler.cxx_standard 2011 }}} And then this works again without crashing: {{{ $ sudo gdk-pixbuf-query-loaders --update-cache }}} Now, everyone is going to find it completely stupid to set {{{compiler.cxx_standard 2011}}} on a port that only uses "C", so we probably have to come up with some new plan on how to enable that. Or just copy-paste the post-destroot into the portfile and tweak it so it works. But here I defer to the maintainer, as no point wasting time on something that won't get committed. And now, a whole new chapter in the {{{malloc: *** error for object 0x1017e2458: Non-aligned pointer being freed}}} saga opens. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:41:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:41:09 -0000 Subject: [MacPorts] #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) In-Reply-To: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> References: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> Message-ID: <064.4c7c9c6cdf030c6f799ce804d0930f66@macports.org> #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) ---------------------------+---------------------------------- Reporter: barracuda156 | Owner: kencu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard, snowleopard Port: gdk-pixbuf2 | ---------------------------+---------------------------------- Comment (by kencu): for those who wish to try this more easily: https://github.com/macports/macports-ports/pull/16901 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:41:46 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:41:46 -0000 Subject: [MacPorts] #65407: librsvg @2.40.20_5: build fails on darwin 9, previous revision didn't In-Reply-To: <044.eafaeef6a9f5b5cf709e3549ea595d06@macports.org> References: <044.eafaeef6a9f5b5cf709e3549ea595d06@macports.org> Message-ID: <059.ecd639f48b56ab0778de0eb1a50b4071@macports.org> #65407: librsvg @2.40.20_5: build fails on darwin 9, previous revision didn't ----------------------+--------------------- Reporter: kakuhen | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: pending Port: librsvg | ----------------------+--------------------- Comment (by kencu): the gdk-pixbuf2 malloc errors are handled here: https://github.com/macports/macports-ports/pull/16901 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:49:32 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:49:32 -0000 Subject: [MacPorts] #57547: gcc5 @5.5.0_4 does not build on PPC MacOS X 10.4.11, Tiger with HFSX because of "Bootstrap comparison failure!" In-Reply-To: <046.937938c3d618f60a1caa1a98f9d596ff@macports.org> References: <046.937938c3d618f60a1caa1a98f9d596ff@macports.org> Message-ID: <061.27e57a5bae3084abc9892ef326b001a4@macports.org> #57547: gcc5 @5.5.0_4 does not build on PPC MacOS X 10.4.11, Tiger with HFSX because of "Bootstrap comparison failure!" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: tiger Port: gcc5 | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:49:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:49:55 -0000 Subject: [MacPorts] #57506: libgcc6 @6.5.0 does not build on PPC Mac OS X 10.4.11, Tiger, with G4 (7447A) because of "Bootstrap comparison failure!" In-Reply-To: <046.25c6b2f3cf86267e5130a87058b17dea@macports.org> References: <046.25c6b2f3cf86267e5130a87058b17dea@macports.org> Message-ID: <061.d18505dffefbb02387edffabf430436f@macports.org> #57506: libgcc6 @6.5.0 does not build on PPC Mac OS X 10.4.11, Tiger, with G4 (7447A) because of "Bootstrap comparison failure!" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: tiger Port: libgcc6 | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:50:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:50:23 -0000 Subject: [MacPorts] #41199: gconf @2.32.4_3 does not build because of missing symbol _PyUnicodeUCS2_AsUTF8String in/opt/local/lib/gobject-introspection/giscanner/_giscanner.so In-Reply-To: <046.fddb0d29a5b0356be5a57671f1d78816@macports.org> References: <046.fddb0d29a5b0356be5a57671f1d78816@macports.org> Message-ID: <061.215d0109dbe27ca3da396905722b57e8@macports.org> #41199: gconf @2.32.4_3 does not build because of missing symbol _PyUnicodeUCS2_AsUTF8String in/opt/local/lib/gobject- introspection/giscanner/_giscanner.so ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: fixed | Keywords: Port: gconf | ------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:50:32 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:50:32 -0000 Subject: [MacPorts] #41199: gconf @2.32.4_3 does not build because of missing symbol _PyUnicodeUCS2_AsUTF8String in/opt/local/lib/gobject-introspection/giscanner/_giscanner.so In-Reply-To: <046.fddb0d29a5b0356be5a57671f1d78816@macports.org> References: <046.fddb0d29a5b0356be5a57671f1d78816@macports.org> Message-ID: <061.02518a632153f082ebff1bb660f9de41@macports.org> #41199: gconf @2.32.4_3 does not build because of missing symbol _PyUnicodeUCS2_AsUTF8String in/opt/local/lib/gobject- introspection/giscanner/_giscanner.so ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: fixed | Keywords: Port: gconf | ------------------------+-------------------------------- Comment (by kencu): as requested -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:50:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:50:49 -0000 Subject: [MacPorts] #65891: py39-libxml2 @2.10.2 does not build on PPC Tiger, Mac OS X 10.4.11, because gcc-apple-4.2 expected in libxml2-py.c something different In-Reply-To: <046.2e5de30273570a8c2fdc5d09d4824c40@macports.org> References: <046.2e5de30273570a8c2fdc5d09d4824c40@macports.org> Message-ID: <061.855ee626bb8dac928efb85aff6f71c56@macports.org> #65891: py39-libxml2 @2.10.2 does not build on PPC Tiger, Mac OS X 10.4.11, because gcc-apple-4.2 expected in libxml2-py.c something different -------------------------+--------------------------------- Reporter: ballapete | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger ppc Port: py-libxml2 | -------------------------+--------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:51:36 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:51:36 -0000 Subject: [MacPorts] #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown In-Reply-To: <046.f821cfbd8c953cf655691b8779962d59@macports.org> References: <046.f821cfbd8c953cf655691b8779962d59@macports.org> Message-ID: <061.a7ec26bb4dbee3cbe9754fa0ac1929ca@macports.org> #64370: pango @1.50.3_0+quartz+x11: Exception: python3 is missing modules: markdown --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: leopard Port: pango | --------------------------+------------------------ Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:53:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:53:18 -0000 Subject: [MacPorts] #64023: tcl @8.6.12 does not understand the configure option --enable-corefoundation In-Reply-To: <046.2d550bb475a1f9649a021e448d8883d4@macports.org> References: <046.2d550bb475a1f9649a021e448d8883d4@macports.org> Message-ID: <061.a5435d923dc9e80b4e476975bd658271@macports.org> #64023: tcl @8.6.12 does not understand the configure option --enable- corefoundation ------------------------+--------------------------------- Reporter: ballapete | Owner: MarcusCalhoun-Lopez Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: tcl | ------------------------+--------------------------------- Comment (by kencu): closing as requested -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:53:37 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:53:37 -0000 Subject: [MacPorts] #63547: gnupg2 @2.3.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of redefinition of typedef 'KEYBOX_HANDLE' In-Reply-To: <046.3d99c262c1d615fefdcc7d6d676b1756@macports.org> References: <046.3d99c262c1d615fefdcc7d6d676b1756@macports.org> Message-ID: <061.5319aeff2db3d7b748672899f081c34d@macports.org> #63547: gnupg2 @2.3.2 does not build on PPC Tiger, Mac OS X 10.4.11, because of redefinition of typedef 'KEYBOX_HANDLE' ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger Port: gnupg2 | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: as requested -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 01:57:06 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 01:57:06 -0000 Subject: [MacPorts] #64023: tcl @8.6.12 does not understand the configure option --enable-corefoundation In-Reply-To: <046.2d550bb475a1f9649a021e448d8883d4@macports.org> References: <046.2d550bb475a1f9649a021e448d8883d4@macports.org> Message-ID: <061.515bcdd48ea9102cc86a7771b220dcc6@macports.org> #64023: tcl @8.6.12 does not understand the configure option --enable- corefoundation ------------------------+--------------------------------- Reporter: ballapete | Owner: MarcusCalhoun-Lopez Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: tiger Port: tcl | ------------------------+--------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:30:27 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 02:30:27 -0000 Subject: [MacPorts] #61092: latexdiff @1.3.1.1 still uses Perl 5.28 In-Reply-To: <046.51d08a6df67e24259fa6785f77263b4b@macports.org> References: <046.51d08a6df67e24259fa6785f77263b4b@macports.org> Message-ID: <061.0fe5e4e71bb72b6a6b07765fda2fad18@macports.org> #61092: latexdiff @1.3.1.1 still uses Perl 5.28 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: latexdiff | --------------------------+-------------------- Comment (by kencu): uses perl 5.34 now -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 02:30:34 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 02:30:34 -0000 Subject: [MacPorts] #61092: latexdiff @1.3.1.1 still uses Perl 5.28 In-Reply-To: <046.51d08a6df67e24259fa6785f77263b4b@macports.org> References: <046.51d08a6df67e24259fa6785f77263b4b@macports.org> Message-ID: <061.c7272affc023fdae8f635ccaa351b3df@macports.org> #61092: latexdiff @1.3.1.1 still uses Perl 5.28 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: latexdiff | --------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:00:25 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 05:00:25 -0000 Subject: [MacPorts] #66387: py310-subprocess-tee @0.4.0_0: fails to build In-Reply-To: <049.598f340b0db10e6446d036f4580f27f6@macports.org> References: <049.598f340b0db10e6446d036f4580f27f6@macports.org> Message-ID: <064.d4affddb4bb0db31b36c39e37d60abab@macports.org> #66387: py310-subprocess-tee @0.4.0_0: fails to build --------------------------------+-------------------- Reporter: hexadecagram | Owner: judaew Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-subprocess-tee | --------------------------------+-------------------- Changes (by Vadym-Valdis Yudaiev ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"4431e1daa68df015c621a0d4f9f0c2e0205bb49f/macports-ports" 4431e1daa68df015c621a0d4f9f0c2e0205bb49f/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4431e1daa68df015c621a0d4f9f0c2e0205bb49f" py-subprocess-tee: Fix build Fixed: https://trac.macports.org/ticket/66387 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:06:28 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 05:06:28 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails Message-ID: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails ----------------------------+--------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: ccache | Port: libbson ----------------------------+--------------------- While upgrading libbson on MAC OSX 13.0.1 The following error gets generated in main.log :info:build ccache: error: Failed to create directory /opt/local/var/macports/build/.ccache/tmp: Operation not permitted main.log is attached for reference -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:07:27 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 05:07:27 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.58f2a15b3baf6c28d7acf5bdb27444cc@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ccache Port: libbson | -----------------------------+-------------------- Changes (by sudheerhebbale): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 05:09:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 05:09:18 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.50102ab53d7a9403b64f07df4f76f14d@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ccache Port: libbson | -----------------------------+-------------------- Description changed by sudheerhebbale: Old description: > While upgrading libbson on MAC OSX 13.0.1 > > The following error gets generated in main.log > > :info:build ccache: error: Failed to create directory > /opt/local/var/macports/build/.ccache/tmp: Operation not permitted > > main.log is attached for reference New description: While upgrading libbson on MAC OSX 13.0.1 The following error gets generated in main.log :info:build ccache: error: Failed to create directory /opt/local/var/macports/build/.ccache/tmp: Operation not permitted main.log is attached for reference Tried with configureccache set to no as well, resulting in the same error -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:15:12 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 06:15:12 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.a47f18d95f3664de3d29699859eddc59@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Changes (by jmroot): * status: new => assigned * keywords: ccache => * owner: (none) => ryandesign Comment: The cmake portgroup does some very strange things with the configure.ccache option that are probably causing this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:35:58 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 06:35:58 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.73673e9185aaa09895efafecf07ccdeb@macports.org> #66365: Failed to build libgcc-devel: command execution failed ---------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Changes (by slackero): * Attachment "ibgcc-devel at 12-20221202_0.log.zip" added. Log ibgcc-devel at 12-20221202_0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 06:38:03 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 06:38:03 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.8cbe8279b407ec824971acc849a293eb@macports.org> #66365: Failed to build libgcc-devel: command execution failed ---------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Comment (by slackero): The build of the updated version libgcc-devel @12-20221202_0+stdlib_flag also fails. The log file is attached. {{{ :debug:main Starting logging for libgcc-devel @12-20221202_0+stdlib_flag :debug:sysinfo macOS 13.0.1 (darwin/22.1.0) arch arm :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode 14.1, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0 ... :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc- devel/work/build" && /usr/bin/make -j10 -w bootstrap-lean :info:build Exit code: 2 :error:build Failed to build libgcc-devel: command execution failed :debug:build Error code: CHILDSTATUS 67670 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 07:35:47 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 07:35:47 -0000 Subject: [MacPorts] #61598: nut @2.7.4: Undefined symbols In-Reply-To: <043.219a43199e2f8d5a3cf37ee72d715146@macports.org> References: <043.219a43199e2f8d5a3cf37ee72d715146@macports.org> Message-ID: <058.f9374137ba1a11b98e66e1be077724c0@macports.org> #61598: nut @2.7.4: Undefined symbols ---------------------+-------------------- Reporter: AP1010 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: bigsur Port: nut | ---------------------+-------------------- Comment (by shardul10): Replying to [comment:9 jmroot]: Can you please elaborate? How to patch the libtool bug? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:30:10 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:30:10 -0000 Subject: [MacPorts] #66397: gpgme @1.18: consider forcing POLL to be disabled on older systems In-Reply-To: <042.d40b9d2cc8a8e228a2832ea6f7255d89@macports.org> References: <042.d40b9d2cc8a8e228a2832ea6f7255d89@macports.org> Message-ID: <057.6a27754e68c67e00208c1571980ca558@macports.org> #66397: gpgme @1.18: consider forcing POLL to be disabled on older systems ---------------------+-------------------- Reporter: kencu | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gpgme | ---------------------+-------------------- Description changed by ryandesign: Old description: > https://trac.macports.org/ticket/65877#comment:1 > > "Note that 10.8 and older have a buggy poll implementation which will > potentially be a problem for this port. It may be best to disable use of > poll on those OS versions and let it fall back to using select." New description: comment:ticket:65877:1 "Note that 10.8 and older have a buggy poll implementation which will potentially be a problem for this port. It may be best to disable use of poll on those OS versions and let it fall back to using select." -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:31:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:31:41 -0000 Subject: [MacPorts] #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 In-Reply-To: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> References: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> Message-ID: <059.8ebbbc951896ccd78ef0bc7571adf3a3@macports.org> #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 -----------------------+--------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc11 | -----------------------+--------------------- Comment (by ryandesign): Replying to [ticket:66398 imos-99]: > {{{ > :info:build xgcc: warning: could not understand version '13.0' > }}} gcc11 might be too old to work on macOS 13. Did you try a newer version of gcc, like gcc12 or gcc-devel? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:36:05 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:36:05 -0000 Subject: [MacPorts] #66404: 2.8.0 bsdmake-24_1.darwin_22.x86_64.tbz2 not available in repos Message-ID: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> #66404: 2.8.0 bsdmake-24_1.darwin_22.x86_64.tbz2 not available in repos --------------------------+-------------------- Reporter: feinbein1968 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: --------------------------+-------------------- Hi there, I get an error when installing bsdmake via port, it seems to me the right version is not yet in the repositories. Thanks Christian {{{ /opt/local/bin/port install bsdmake ---> Fetching archive for bsdmake ---> Attempting to fetch bsdmake-24_1.darwin_22.x86_64.tbz2 from https://fra.de.packages.macports.org/bsdmake ---> Attempting to fetch bsdmake-24_1.darwin_22.x86_64.tbz2 from https://nue.de.packages.macports.org/bsdmake ---> Attempting to fetch bsdmake-24_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/bsdmake ---> Verifying checksums for bsdmake Error: Checksum (rmd160) mismatch for bsdmake-24.tar.gz Error: Checksum (sha256) mismatch for bsdmake-24.tar.gz Error: Failed to checksum bsdmake: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_bsdmake/bsdmake/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port bsdmake failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:37:28 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:37:28 -0000 Subject: [MacPorts] #66399: php82-zip is missing In-Reply-To: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> References: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> Message-ID: <056.bd3e1829d58e2b54c86370601577cdac@macports.org> #66399: php82-zip is missing ----------------------+------------------------ Reporter: temp | Owner: ryandesign Type: request | Status: accepted Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: php-zip | ----------------------+------------------------ Changes (by ryandesign): * status: assigned => accepted Comment: zip is a third-party php module (https://pecl.php.net/package/zip). I typically wait until a new php version's first final release before adding the subports to third-party modules. zip claims to be compatible with php 8.2 so it shouldn't be a problem for me to add php82-zip after updating php82 to 8.2.0 when that comes out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:43:24 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:43:24 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.bd694d4d259b314ced2e6b6008b4dd2c@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Old description: > While upgrading libbson on MAC OSX 13.0.1 > > The following error gets generated in main.log > > :info:build ccache: error: Failed to create directory > /opt/local/var/macports/build/.ccache/tmp: Operation not permitted > > main.log is attached for reference > > Tried with configureccache set to no as well, resulting in the same error New description: While upgrading libbson on MAC OSX 13.0.1 The following error gets generated in main.log {{{ :info:build ccache: error: Failed to create directory /opt/local/var/macports/build/.ccache/tmp: Operation not permitted }}} main.log is attached for reference Tried with configureccache set to no as well, resulting in the same error -- Comment (by ryandesign): Hmm, I always build with `configureccache yes` on my main machine and I don't recall seeing this problem with libbson, and our buildbot machines build with `configureccache no` and I don't think I've seen it there either. However, I haven't tried Ventura yet; maybe something has changed. Are the permissions and ownership of /opt/local/var/macports/build and /opt/local/var/macports/build/.ccache and /opt/local/var/macports/build/.ccache/tmp correct? On my system I have: {{{ $ ls -ld /opt/local/var/macports/build{,/.ccache{,/tmp}} drwxr-xr-x 61 root wheel 1952 Dec 4 09:05 /opt/local/var/macports/build drwxr-xr-x 20 macports wheel 640 Dec 4 08:44 /opt/local/var/macports/build/.ccache drwxr-xr-x 4 macports wheel 128 Dec 4 08:49 /opt/local/var/macports/build/.ccache/tmp }}} Based on the error message I presume /opt/local/var/macports/build/.ccache/tmp does not yet exist on your system. Has this worked for you before? Does it work with other ports? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:48:33 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:48:33 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.d7b244412e47700a65f55e5cf737cfa3@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by sudheerhebbale): Permissions in /opt/local/var/macports/build are correct, all files are owned by root:wheel As such I have run the port command with sudo. Below is the list of files in /opt/local/var/macports ` drwxr-xr-x 25 root wheel 800 Dec 6 10:28 build drwxr-xr-x 316 root wheel 10112 Dec 6 10:21 distfiles drwxr-xr-x 3 root wheel 96 Jan 1 2021 home drwxr-xr-x 3 macports wheel 96 Dec 6 10:30 incoming drwxr-xr-x 30 root wheel 960 Dec 6 10:21 logs -rw-r--r-- 1 root wheel 1477 Dec 6 10:30 pingtimes drwxr-xr-x 9 root wheel 288 Nov 15 10:11 registry drwxrwxrwt 3 root wheel 96 Nov 15 10:11 sip-workaround drwxr-xr-x 462 root wheel 14784 Nov 22 09:59 software drwxr-xr-x 3 root wheel 96 Sep 25 2017 sources ` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 10:52:59 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 10:52:59 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.e42edea7b2b6cefb006bb349590f9af9@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by ryandesign): Ok, I do see a similar problem... {{{ ccache: error: Failed to create temporary file for /opt/local/var/macports/build/.ccache/tmp/inode- cache-64.v1.tmp.5fCn6l.tmp: Operation not permitted }}} ...if I build with `configureccache=no` but with the ccache port still installed. I see in the log... {{{ :info:configure -- Compiling with CCache enabled. Disable by setting MONGO_USE_CCACHE to OFF }}} ...so this build system has special code for finding ccache, which I should disable. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:02:16 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:02:16 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.45739e5d79afd58130cb494e0a7d186d@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by ryandesign): In [changeset:"dc49b02703c39d8e5ca9bd6414e7b38ccfc6d67d/macports-ports" dc49b02703c39d8e5ca9bd6414e7b38ccfc6d67d/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="dc49b02703c39d8e5ca9bd6414e7b38ccfc6d67d" mongo-c-driver: Set MONGO_USE_CCACHE=OFF MacPorts will still use ccache if so configured in macports.conf. See: https://trac.macports.org/ticket/66403 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:14:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:14:55 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.cd665cc8c4266e0cf6b97e2cf295658b@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by sudheerhebbale): Still experiencing the same problem after setting configureccache no I guess it will take some time for the changes to reflect in all distributions Will try after some time and update -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:15:51 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:15:51 -0000 Subject: [MacPorts] #66405: nebula: use 'bin' Make target to build the right arch Message-ID: <048.2a086383ce1d76aa8237b88c40bb8788@macports.org> #66405: nebula: use 'bin' Make target to build the right arch -------------------------+------------------------- Reporter: herbygillot | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: nebula -------------------------+------------------------- The `nebula` port currently uses the `bin-darwin` build target, which builds the amd64 version of `nebula`. The port needs to invoke the `bin` target instead of `bin-darwin`. The `bin` target will build for the appropriate architecture, whether amd64 or arm64. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:19:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:19:18 -0000 Subject: [MacPorts] #66405: nebula: use 'bin' Make target to build the right arch In-Reply-To: <048.2a086383ce1d76aa8237b88c40bb8788@macports.org> References: <048.2a086383ce1d76aa8237b88c40bb8788@macports.org> Message-ID: <063.03f4658b7d902983891d025e2c0d5445@macports.org> #66405: nebula: use 'bin' Make target to build the right arch --------------------------+------------------------- Reporter: herbygillot | Owner: herbygillot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: nebula | --------------------------+------------------------- Changes (by herbygillot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"eecd0b7a4e9fc9d2bca23ce5673b57a47a6f088c/macports-ports" eecd0b7a4e9fc9d2bca23ce5673b57a47a6f088c/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="eecd0b7a4e9fc9d2bca23ce5673b57a47a6f088c" nebula: use the bin make target so that the build targets the right arch Fixes: https://trac.macports.org/ticket/66405 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:27:51 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:27:51 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch (was: 2.8.0 bsdmake-24_1.darwin_22.x86_64.tbz2 not available in repos) In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.cf6d957b8a3bbe1dd8635c621e7cfd76@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => raimue * port: => bsdmake Comment: The output you've shown starts with the distfile already downloaded. Which mirror was it downloaded from? wiki:FAQ#checksums -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:55:02 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:55:02 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.2b4a1728c7c5be93c977c469680d49e1@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by jmroot): Looks like opensource.apple.com is redirecting to github, which gives a different tarball with identical contents to the one we previously mirrored except for the directory name. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 11:56:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 11:56:18 -0000 Subject: [MacPorts] #64021: clamav @0.104.1_1 does not build on PPC Mac OS X 10.4.11, Tiger, because: 'O_SYMLINK' undeclared In-Reply-To: <046.e787740a7049ff0ef7763ef98c06a372@macports.org> References: <046.e787740a7049ff0ef7763ef98c06a372@macports.org> Message-ID: <061.7f36f8fb0296972bb9445bc548747696@macports.org> #64021: clamav @0.104.1_1 does not build on PPC Mac OS X 10.4.11, Tiger, because: 'O_SYMLINK' undeclared -----------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: wontfix | Keywords: tiger Port: legacy-support | -----------------------------+-------------------- Comment (by ballapete): `clamav @0.104.4` is meanwhile installed, probably the last version that will build on `Tiger` or on `Leopards`. Since this ticket has a follow-up, it could be closed? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:00:11 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:00:11 -0000 Subject: [MacPorts] #64105: libtextstyle @0.21 does not build on PPC Mac OS X 10.4.11, Tiger, because: libproc.h: No such file or directory In-Reply-To: <046.c41c7df5f5584109ff2518358a8de87e@macports.org> References: <046.c41c7df5f5584109ff2518358a8de87e@macports.org> Message-ID: <061.8b95759df75dec204e7dbf628eae3d32@macports.org> #64105: libtextstyle @0.21 does not build on PPC Mac OS X 10.4.11, Tiger, because: libproc.h: No such file or directory ---------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: duplicate | Keywords: tiger Port: libtextstyle | ---------------------------+-------------------- Comment (by ballapete): Since it finally built, the problem seems to be solved and the ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:08:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:08:49 -0000 Subject: [MacPorts] #59021: kerberos5 @1.17_1 uses unused configure option --with-pkinit-crypto-impl and fails to find Python 3 on PPC Mac OS X 10.4.11, Tiger In-Reply-To: <046.0700a91264a33bd7d39c125d705f3a6a@macports.org> References: <046.0700a91264a33bd7d39c125d705f3a6a@macports.org> Message-ID: <061.0fb63babe0d4d806a02e0d72a5917860@macports.org> #59021: kerberos5 @1.17_1 uses unused configure option --with-pkinit-crypto-impl and fails to find Python 3 on PPC Mac OS X 10.4.11, Tiger ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: | Keywords: tiger Port: kerberos5 | ------------------------+-------------------- Comment (by ballapete): The change has come (out?) and `kerberos5 @1.20.1` builds and installs now. So this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:11:17 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:11:17 -0000 Subject: [MacPorts] #59876: ImageMagick @6.9.10-80 does not build on PPC Tiger, Mac OS X 10.4.11, because 'MagickAddressType' undeclared In-Reply-To: <046.182b9802e5e8bf25c649588064e854b8@macports.org> References: <046.182b9802e5e8bf25c649588064e854b8@macports.org> Message-ID: <061.80e8819819a9b1f33e6a026cb11a2e1f@macports.org> #59876: ImageMagick @6.9.10-80 does not build on PPC Tiger, Mac OS X 10.4.11, because 'MagickAddressType' undeclared --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: tiger Port: ImageMagick | --------------------------+------------------------ Comment (by ballapete): Obviously the problem was solved and now `ImageMagick @6.9.11-60` builds and installs. The ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:13:22 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:13:22 -0000 Subject: [MacPorts] #60120: gtk3 @3.24.14 does not build on PPC Tiger, Mac OS X 10.4.11, because "Something went wrong bootstrapping makefile fragments" In-Reply-To: <046.4a93df408ac32918245a3b86dddaffdd@macports.org> References: <046.4a93df408ac32918245a3b86dddaffdd@macports.org> Message-ID: <061.14dcbd1a3a503d20f36976647c593489@macports.org> #60120: gtk3 @3.24.14 does not build on PPC Tiger, Mac OS X 10.4.11, because "Something went wrong bootstrapping makefile fragments" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: tiger Port: gtk3 | ------------------------+-------------------- Comment (by ballapete): Now `gtk3 @3.24.34` is installed, the problem obviously solved. The ticket can be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:14:00 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:14:00 -0000 Subject: [MacPorts] #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) Message-ID: <048.4862f7c021d74aba503c089a8538c3db@macports.org> #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) -------------------------+-------------------- Reporter: c-kloukinas | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: emacs | Port: slime -------------------------+-------------------- File lib/hyperspec.el at line 1318 is: {{{ (define-obsolete-variable-alias 'common-lisp-glossary-fun 'common-lisp-hyperspec-glossary-function) }}} When the installer tries to byte-compile this file it breaks, because this function expects a 3rd argument as well (WHEN). Slime on github passes this value for WHEN "2015-12-29" - see: https://github.com/slime/slime/blob/master/lib/hyperspec.el {{{ (define-obsolete-variable-alias 'common-lisp-glossary-fun 'common-lisp-hyperspec-glossary-function "2015-12-29") }}} After adding that extra arg, make compile inside /opt/local/var/macports/build/_opt_local_var_macports_sources_github .com_macports_macports-ports_lang_slime/slime/work/slime-2.20 worked for me. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:19:02 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:19:02 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.f70ad0490c825568ac5d36a47a333a9c@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): Doing it as mortal me I get: {{{ pete 260 /\ /opt/local/libexec/mpstats submit Submitting data to https://ports.macports.org/statistics/submit/ ... Error: SSL connect error while executing "curl post "submission\[data\]=$json" $stats_url" Exit 1 pete 261 /\ port -v installed | ggrep curl curl @7.86.0_0+ares+http2+sftp_scp+ssl (active) requested_variants='+ares+http2+sftp_scp+ssl' platform='darwin 8' archs='ppc' date='2022-11-14T13:13:38+0100' curl-ca-bundle @7.86.0_0 (active) requested_variants='' platform='darwin 8' archs='noarch' date='2022-11-13T17:47:20+0100' pete 262 /\ which curl /opt/local/bin/curl }}} and as root I get: {{{ root 290 /\ /opt/local/libexec/mpstats submit Submitting data to https://ports.macports.org/statistics/submit/ ... Error: SSL connect error while executing "curl post "submission\[data\]=$json" $stats_url" root 291 /\ which curl /opt/local/bin/curl }}} Is it impossible to fix this "port"? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:23:24 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:23:24 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.e9aa7e6e30f51a954381471c24dd5524@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by feinbein1968): I dont understand your question, sorry I am new to macports. I got to this point when trying to install xymon-client on a OSX-Ventura. The steps so far where: {{{ wget https://github.com/macports/macports- base/releases/download/v2.8.0/MacPorts-2.8.0-13-Ventura.pkg installer -pkg ~/Downloads/MacPorts-2.5.4-10.14-Mojave.pkg -target / /opt/local/bin/port -v selfupdate /opt/local/bin/port install xymon-client }}} The error I get when trying with xymon-client is the same, when I do: {{{ /opt/local/bin/port install bsdmake }}} In the log it says {{{ :info:archivefetch ---> bsdmake-24_1.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch bsdmake- 24_1.darwin_22.x86_64.tbz2 from https://fra.de.packages.macports.org/bsdmake :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch bsdmake- 24_1.darwin_22.x86_64.tbz2 from https://nue.de.packages.macports.org/bsdmake :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch bsdmake- 24_1.darwin_22.x86_64.tbz2 from https://packages.macports.org/bsdmake }}} And this is correct, there is no file named 'bsdmake- 24_1.darwin_**22**.x86_64.tbz2' at any of those 3 URLs above. The 'newest' version of the same file (by size) is bsdmake- 24_1.darwin_**21**.x86_64.tbz2 I will also attach the full log. Thanks for helping anyway. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:23:44 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:23:44 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.e5b8632a6dcec64f311e74e5ac3c82de@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Changes (by feinbein1968): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:24:11 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:24:11 -0000 Subject: [MacPorts] #66407: Okular installation not working in Ventura13.0.1(arm64) Message-ID: <048.b290a364acf84d138d576190e2eeb91b@macports.org> #66407: Okular installation not working in Ventura13.0.1(arm64) -------------------------+-------------------- Reporter: Naageswaran | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -------------------------+-------------------- When tried to follow the procedure given in https://ports.macports.org/port/okular/ to install Okular, the following error message appeared. Error: Cannot install okular for the arch 'arm64' because its dependency qt4-mac only supports the archs 'ppc ppc64 i386 x86_64'. Could you update the port Okular for 'arm64'? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:29:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:29:43 -0000 Subject: [MacPorts] #60120: gtk3 @3.24.14 does not build on PPC Tiger, Mac OS X 10.4.11, because "Something went wrong bootstrapping makefile fragments" In-Reply-To: <046.4a93df408ac32918245a3b86dddaffdd@macports.org> References: <046.4a93df408ac32918245a3b86dddaffdd@macports.org> Message-ID: <061.6eb8644787c95eb957d9cee8a1a8ea85@macports.org> #60120: gtk3 @3.24.14 does not build on PPC Tiger, Mac OS X 10.4.11, because "Something went wrong bootstrapping makefile fragments" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: tiger Port: gtk3 | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:31:36 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:31:36 -0000 Subject: [MacPorts] #59876: ImageMagick @6.9.10-80 does not build on PPC Tiger, Mac OS X 10.4.11, because 'MagickAddressType' undeclared In-Reply-To: <046.182b9802e5e8bf25c649588064e854b8@macports.org> References: <046.182b9802e5e8bf25c649588064e854b8@macports.org> Message-ID: <061.a56941af613cea14543521e4f4442207@macports.org> #59876: ImageMagick @6.9.10-80 does not build on PPC Tiger, Mac OS X 10.4.11, because 'MagickAddressType' undeclared --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: tiger Port: ImageMagick | --------------------------+------------------------ Changes (by kencu): * status: accepted => closed * resolution: => fixed Comment: thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:32:40 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:32:40 -0000 Subject: [MacPorts] #59021: kerberos5 @1.17_1 uses unused configure option --with-pkinit-crypto-impl and fails to find Python 3 on PPC Mac OS X 10.4.11, Tiger In-Reply-To: <046.0700a91264a33bd7d39c125d705f3a6a@macports.org> References: <046.0700a91264a33bd7d39c125d705f3a6a@macports.org> Message-ID: <061.b899acba6a34ba012ba85461a36d7508@macports.org> #59021: kerberos5 @1.17_1 uses unused configure option --with-pkinit-crypto-impl and fails to find Python 3 on PPC Mac OS X 10.4.11, Tiger ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: tiger Port: kerberos5 | ------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:37:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:37:23 -0000 Subject: [MacPorts] #65453: gnupg2 @2.2.35 has no configure option --disable-openldap In-Reply-To: <046.5db4b9423aa1c22a6c67e389b12584ab@macports.org> References: <046.5db4b9423aa1c22a6c67e389b12584ab@macports.org> Message-ID: <061.56fa0083f6873c4f1d5c29e5b68ef8ed@macports.org> #65453: gnupg2 @2.2.35 has no configure option --disable-openldap ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger Port: gnupg2 | ------------------------+-------------------- Comment (by ballapete): Building `gnupg2 @2.2.40` on `Monterey` the same complaint appears. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:39:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:39:08 -0000 Subject: [MacPorts] #66408: Minetest fails to build on Mac OS 10.12 Message-ID: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> #66408: Minetest fails to build on Mac OS 10.12 -----------------------------+---------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: minetest gmp | Port: minetest -----------------------------+---------------------- Building fails for Minetest on Mac OS 10.12. The reason is undefined symbols. Here are a few of them: ___gmpz_add ___gmpz_clear ___gmpz_export ___gmpz_import These functions appear to be for libgmp. I searched the log and did find this text: :info:configure -- Using GMP provided by system. :info:configure -- Found GMP: /opt/local/lib/libgmp.dylib -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:39:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:39:31 -0000 Subject: [MacPorts] #66408: Minetest fails to build on Mac OS 10.12 In-Reply-To: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> References: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> Message-ID: <067.60a868ccb3e6521846d2440dcacea159@macports.org> #66408: Minetest fails to build on Mac OS 10.12 ------------------------------+-------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: minetest gmp Port: minetest | ------------------------------+-------------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:40:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:40:09 -0000 Subject: [MacPorts] #65581: eet @1.7.10 cannot be built on intel Monterey and PPC Tiger In-Reply-To: <046.fb4e18a3e4732ad73621dccdd22eb975@macports.org> References: <046.fb4e18a3e4732ad73621dccdd22eb975@macports.org> Message-ID: <061.3e039742a45af6b2d69dc9155ad53c78@macports.org> #65581: eet @1.7.10 cannot be built on intel Monterey and PPC Tiger ------------------------+----------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, monterey Port: eet | ------------------------+----------------------------- Comment (by ballapete): The use of `Enlightenment` was tried as a work-around, but it's obvious that this software is too old for today, so the ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:44:29 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:44:29 -0000 Subject: [MacPorts] #66283: compilers portgroup uses -rpath on Tiger In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.eb825a5dace46bd71a44b87fcece3dca@macports.org> #66283: compilers portgroup uses -rpath on Tiger ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176 | ------------------------+----------------------- Comment (by ballapete): The bug is clearly in `boost176 Portfile`, since the `other ports build`, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 12:49:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 12:49:41 -0000 Subject: [MacPorts] #66408: Minetest fails to build on Mac OS 10.12 In-Reply-To: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> References: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> Message-ID: <067.a1cdd1ed657d4ad2ed29adab2c623dda@macports.org> #66408: Minetest fails to build on Mac OS 10.12 ------------------------------+-------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: minetest gmp Port: minetest | ------------------------------+-------------------------- Comment (by programmingkidx): I ran 'sudo port -f activate gmp' and this fixed the problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 13:03:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 13:03:08 -0000 Subject: [MacPorts] #65799: mupdf @1.20.3: builds fail across-the-board: expected '; ' after top level declarator In-Reply-To: <044.bb74fa920282dbd660ee00909988bdc4@macports.org> References: <044.bb74fa920282dbd660ee00909988bdc4@macports.org> Message-ID: <059.c7f574a2dda84859dd0f8b618e83037c@macports.org> #65799: mupdf @1.20.3: builds fail across-the-board: expected ';' after top level declarator ----------------------+----------------------- Reporter: mascguy | Owner: essandess Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: mupdf | ----------------------+----------------------- Comment (by gctwnl): Is there anything being done about this? Might we for instance as a workaround exclude this font in the config? And not only this font but also others, as mine now fails (clang crash) on `NotoSansOldPersian- Regular.otf` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 13:13:38 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 13:13:38 -0000 Subject: [MacPorts] #66408: Minetest: links to gmp opportunistically (was: Minetest fails to build on Mac OS 10.12) In-Reply-To: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> References: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> Message-ID: <067.f1744ed27513ddeb1289c51e3e31c831@macports.org> #66408: Minetest: links to gmp opportunistically ------------------------------+-------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: minetest gmp Port: minetest | ------------------------------+-------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 13:20:51 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 13:20:51 -0000 Subject: [MacPorts] #63507: xorg-server-legacy @1.20.10_2 does not build on PPC Tiger, Mac OS X 20.4.11, because bundle_trampoline.c:32:19: error: spawn.h: No such file or directory In-Reply-To: <046.e87b25cbabb65c48b304002b81c7222d@macports.org> References: <046.e87b25cbabb65c48b304002b81c7222d@macports.org> Message-ID: <061.6de538dd35a99c28cbf59ebb71173fcf@macports.org> #63507: xorg-server-legacy @1.20.10_2 does not build on PPC Tiger, Mac OS X 20.4.11, because bundle_trampoline.c:32:19: error: spawn.h: No such file or directory ---------------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: xorg-server-legacy | ---------------------------------+-------------------- Comment (by ballapete): The recent version of `Portfile` uses the `configure arguments --disable- dri2 --disable-dri3` which seem to be obsolete now, since I recall `mesa @22.1.7` now supports this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 13:25:29 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 13:25:29 -0000 Subject: [MacPorts] #65799: mupdf @1.20.3: builds fail across-the-board: expected '; ' after top level declarator In-Reply-To: <044.bb74fa920282dbd660ee00909988bdc4@macports.org> References: <044.bb74fa920282dbd660ee00909988bdc4@macports.org> Message-ID: <059.deda5050ce32a88fef547d0504ea1500@macports.org> #65799: mupdf @1.20.3: builds fail across-the-board: expected ';' after top level declarator ----------------------+----------------------- Reporter: mascguy | Owner: essandess Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: mupdf | ----------------------+----------------------- Comment (by gctwnl): From StackExchange: One possible solution to this issue is to tell the mupdf configure script not to compile the NotoSansOldPersian-Regular.otf font. You can do this by passing the `--without-font-truetype` option to the ./configure script when building mupdf. This will prevent mupdf from trying to compile the font, which should allow the compilation process to complete successfully. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 13:46:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 13:46:08 -0000 Subject: [MacPorts] #63507: xorg-server-legacy @1.20.10_2 does not build on PPC Tiger, Mac OS X 20.4.11, because bundle_trampoline.c:32:19: error: spawn.h: No such file or directory In-Reply-To: <046.e87b25cbabb65c48b304002b81c7222d@macports.org> References: <046.e87b25cbabb65c48b304002b81c7222d@macports.org> Message-ID: <061.7736b5628ea85dce987ca92ba1682bd8@macports.org> #63507: xorg-server-legacy @1.20.10_2 does not build on PPC Tiger, Mac OS X 20.4.11, because bundle_trampoline.c:32:19: error: spawn.h: No such file or directory ---------------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: xorg-server-legacy | ---------------------------------+-------------------- Comment (by ballapete): I tried to build once with `unchanged Portfile` but with `GCC 7` instead of `default GCC 4.2` ? and ran into a different failure: {{{ libtool: compile: /opt/local/bin/gcc-mp-7 -DHAVE_CONFIG_H -I. -I../../include -DBUILD_DATE=\"20221206\" -DXSERVER_VERSION=\"1.20.10\" -DUSE_NEW_CLUT -DXFree86Server -I../../miext/rootless -I../../pseudoramiX -DX11LIBDIR=\"/opt/local/lib\" -isystem/opt/local/include/LegacySupport -I/opt/local/include -I/opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/x11 /xorg-server-legacy/files/include -DHAVE_DIX_CONFIG_H -Wall -Wpointer- arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing- prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing- noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror =missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -fno-strict-aliasing -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I../../include -I../../include -I../../Xext -I../../damageext -I../../xfixes -I../../Xi -I../../mi -I../../miext/sync -I../../miext/shadow -I../../miext/damage -I../../render -I../../randr -I../../fb -I../../dbe -I../../present -pipe -Os -arch ppc -D_THREAD_SAFE -pthread -DROOTLESS_WORKAROUND -DROOTLESS_SAFEALPHA -DNO_ALLOCA -c X11Application.m -fno-common -DPIC -o .libs/X11Application.o In file included from X11Controller.h:41:0, from X11Application.h:36, from X11Application.m:39: xpr/x-list.h:51:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' X_EXTERN void X_PFX(list_free_1) (x_list * node); ^~~~ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:52:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_prepend) (x_list * lst, void *data); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:54:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_append) (x_list * lst, void *data); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:55:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_remove) (x_list * lst, void *data); ^ xpr/x-list.h:56:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' X_EXTERN void X_PFX(list_free) (x_list * lst); ^~~~ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:57:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_pop) (x_list * lst, void **data_ret); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:59:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_copy) (x_list * lst); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:60:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_reverse) (x_list * lst); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:61:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_find) (x_list * lst, void *data); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:62:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_nth) (x_list * lst, int n); ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:63:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_filter) (x_list * src, ^ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:66:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_map) (x_list * src, ^ xpr/x-list.h:70:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'unsigned' X_EXTERN unsigned int X_PFX(list_length) (x_list * lst); ^~~~~~~~ xpr/x-list.h:71:10: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void' X_EXTERN void X_PFX(list_foreach) (x_list * lst, void (*fun) ^~~~ xpr/x-list.h:48:18: error: unknown type name '__private_extern__' #define X_EXTERN __private_extern__ ^ xpr/x-list.h:48:18: note: in definition of macro 'X_EXTERN' #define X_EXTERN __private_extern__ ^~~~~~~~~~~~~~~~~~ xpr/x-list.h:75:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token X_EXTERN x_list *X_PFX(list_sort) (x_list * lst, ^ X11Application.m:103:12: warning: redundant redeclaration of 'darwinFakeButtons' [-Wredundant-decls] extern int darwinFakeButtons; ^~~~~~~~~~~~~~~~~ In file included from X11Application.m:41:0: darwin.h:68:12: note: previous declaration of 'darwinFakeButtons' was here extern int darwinFakeButtons; ^~~~~~~~~~~~~~~~~ X11Application.m: In function '-[X11Application sendEvent:]': X11Application.m:321:5: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] OSX_BOOL for_appkit, for_x; ^~~~~~~~ X11Application.m:351:21: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] NSWindow *mainWindow = [self mainWindow]; ^~~~~~~~ X11Application.m:497:17: warning: 'X11Application' may not respond to '-set_front_process:' [self set_front_process:nil]; ^ X11Application.m:497:17: warning: (Messages without a matching method signature X11Application.m:497:17: warning: will be assumed to return 'id' and accept X11Application.m:497:17: warning: '...' as arguments.) X11Application.m: In function 'X11ApplicationCanEnterRandR': X11Application.m:1156:5: warning: non-ASCII character in CFString literal [--all-warnings] msg = NSLocalizedString( ^~~ make[3]: *** [X11Application.lo] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:04:28 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:04:28 -0000 Subject: [MacPorts] #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason In-Reply-To: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> References: <067.cdfc822060fba7852e8c9e7dae352831@macports.org> Message-ID: <082.3fe2a1fe7826e65a770a0ee6b3d344e2@macports.org> #66388: yt-dlp @2022.11.11: proxy mode is broken for some reason ---------------------------------------------+-------------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: mountainlion Port: yt-dlp | ---------------------------------------------+-------------------------- Comment (by aeiouaeiouaeiouaeiouaeiouaeiou): Replying to [comment:2 ryandesign]: > Have you already performed the [wiki:ProblemHotlist#letsencrypt Let's Encrypt fix] on your system? I did it right after reinstalling the system, otherwise apps like Mail and Contacts would not work. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:22:34 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:22:34 -0000 Subject: [MacPorts] #66409: asciidoctor @2.0.18: temporarily switch back to ruby30 Message-ID: <067.7cd4e7d9b995566a8fafd90caab3d316@macports.org> #66409: asciidoctor @2.0.18: temporarily switch back to ruby30 --------------------------------------------+------------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: lion mountainlion | Port: asciidoctor --------------------------------------------+------------------------- https://github.com/macports/macports- ports/commit/93b793acfebdc3fb04d6d2f2511d11192b16b7e6 https://trac.macports.org/ticket/66054 I cannot update ccache because it depends on it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:24:16 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:24:16 -0000 Subject: [MacPorts] #66409: asciidoctor @2.0.18: temporarily switch back to ruby30 In-Reply-To: <067.7cd4e7d9b995566a8fafd90caab3d316@macports.org> References: <067.7cd4e7d9b995566a8fafd90caab3d316@macports.org> Message-ID: <082.5e6087dce39a7e5102f5fbfcd8b9b226@macports.org> #66409: asciidoctor @2.0.18: temporarily switch back to ruby30 ---------------------------------------------+----------------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: mountainlion Port: asciidoctor | mavericks ---------------------------------------------+----------------------------- Changes (by aeiouaeiouaeiouaeiouaeiouaeiou): * keywords: lion mountainlion => mountainlion mavericks * version: => 2.8.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:24:33 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:24:33 -0000 Subject: [MacPorts] #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> References: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> Message-ID: <061.8a7371b176e578ff7526da8a088e00b6@macports.org> #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: libtool | ------------------------+-------------------- Comment (by ballapete): `libtool @2.4.7_0` still has problems: {{{ Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_libtool/libtool/work/libtool-2.4.7" && ./configure --prefix=/opt/local --disable-silent-rules --program- prefix=g DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_libtool/libtool/work/libtool-2.4.7" && ./configure --prefix=/opt/local --disable-silent-rules --program- prefix=g expr: brackets ([ ]) not balanced ## ------------------------- ## ## Configuring libtool 2.4.7 ## ## ------------------------- ## }}} The bug is in `libtool-2.4.7/build-aux/git-version-gen`: {{{ 74 me=$0 75 76 year=`expr "$scriptversion" : '\([^-]*\)'` 77 version="git-version-gen $scriptversion }}} as this output shows: {{{ ++ /bin/sh -x build-aux/git-version-gen .tarball-version + scriptversion=2022-01-27.18 + me=build-aux/git-version-gen ++ expr 2022-01-27.18 : '\([^-]*\)' expr: brackets ([ ]) not balanced + year= + version=git-version-gen 2022-01-27.18 }}} This expression works for me in old bashes, version 3.x, and returns the value of year, i.e. 2022. The variable is exactly once used here: `Copyright (C) ${year} Free Software Foundation, Inc.`. Version of `/bin/sh` is: {{{ GNU bash, version 2.05b.0(1)-release (powerpc-apple-darwin8.0) }}} `echo $scriptversion | cut -d - -f 1` can deliver the searched for value. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:25:12 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:25:12 -0000 Subject: [MacPorts] #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> References: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> Message-ID: <061.56f414258e4550208132783c7c3fd4d3@macports.org> #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: libtool | ------------------------+-------------------- Comment (by ballapete): Anyway, this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:41:51 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:41:51 -0000 Subject: [MacPorts] #64478: openjdk17-openj9: crashing on El Captain In-Reply-To: <067.c61269c12d633634bfdeff93037c1d72@macports.org> References: <067.c61269c12d633634bfdeff93037c1d72@macports.org> Message-ID: <082.5b1056e77b088689fc01517a8419e859@macports.org> #64478: openjdk17-openj9: crashing on El Captain ---------------------------------------------+----------------------- Reporter: aeiouaeiouaeiouaeiouaeiouaeiou | Owner: breun Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: elcapitan Port: openjdk17-openj9 | ---------------------------------------------+----------------------- Comment (by aeiouaeiouaeiouaeiouaeiouaeiou): The ticket can probably be closed because their builds have started officially targeting only macOS 10.14+. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:50:44 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:50:44 -0000 Subject: [MacPorts] #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> References: <046.20f0c3330ea0588585ededf32bb0e040@macports.org> Message-ID: <061.3e97f5f9d4ad47ee4117300a9814be06@macports.org> #66381: libepoxy @1.5.10 stopped building on PPC Tiger, Mac OS X 10.4.11 ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: libepoxy | ------------------------+----------------------- Comment (by ballapete): It built again now, so the ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 14:58:28 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 14:58:28 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.0a3bea8c91c484ed9fa1ac6eddb6ec86@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): It built in my corrected setup, so the ticket can be closed. (Or is there a need to contact me for `GCC 1x` testing?) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:01:38 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 15:01:38 -0000 Subject: [MacPorts] #65584: asymptote 2.70_3 fails to build under macOS Monterey 12.5 on M1 In-Reply-To: <044.aa9d23246a6dec58b2f82239290c9326@macports.org> References: <044.aa9d23246a6dec58b2f82239290c9326@macports.org> Message-ID: <059.1039868e938378bf614274d2d81839d8@macports.org> #65584: asymptote 2.70_3 fails to build under macOS Monterey 12.5 on M1 ------------------------+----------------------------- Reporter: murrayE | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: monterey, arm64 Port: asymptote | ------------------------+----------------------------- Comment (by LenoreHorner): I'm seeing the same abort traps on Ventura on an M1 MacBook Pro. How are people getting around this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:08:40 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 15:08:40 -0000 Subject: [MacPorts] #65892: gtk3: windows displayed as all black, for x11 install In-Reply-To: <044.d0934e485f29d1e7ac8878bc9aa1f1a9@macports.org> References: <044.d0934e485f29d1e7ac8878bc9aa1f1a9@macports.org> Message-ID: <059.747fd29dbdb4b433e021793afb6d2b7e@macports.org> #65892: gtk3: windows displayed as all black, for x11 install -------------------------+-------------------------- Reporter: asic512 | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: monterey x11 Port: gtk3 gnome | -------------------------+-------------------------- Comment (by LenoreHorner): Discussion at https://github.com/XQuartz/XQuartz/issues/31 suggests XQuartz 2.8.3_rc1 plus setting defaults write org.xquartz.X11 enable_render_extension 0 might fix the problem (or might make things cripplingly slow). I can (barely) read Gnucash through this, but it's quite painful and I'd love to see a fix. What can I do to help? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:14:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 15:14:41 -0000 Subject: [MacPorts] #65892: gtk3: windows displayed as all black, for x11 install In-Reply-To: <044.d0934e485f29d1e7ac8878bc9aa1f1a9@macports.org> References: <044.d0934e485f29d1e7ac8878bc9aa1f1a9@macports.org> Message-ID: <059.4cbc6a27a06403cbed99c174a7af6d57@macports.org> #65892: gtk3: windows displayed as all black, for x11 install -------------------------+-------------------------- Reporter: asic512 | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: monterey x11 Port: gtk3 gnome | -------------------------+-------------------------- Comment (by LenoreHorner): The defaults write does not fix things for me on M1 on Ventura using xorg- server that I just checked for updates today. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:51:05 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 15:51:05 -0000 Subject: [MacPorts] #66401: py310-subprocess-tee @0.4.0: install fails with 404 error In-Reply-To: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> References: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> Message-ID: <064.c88843d1385d727f2933f1c1f99bbe78@macports.org> #66401: py310-subprocess-tee @0.4.0: install fails with 404 error --------------------------------+---------------------- Reporter: angryjohnnie | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-subprocess-tee | --------------------------------+---------------------- Changes (by angryjohnnie): * Attachment "logfile.txt" added. log file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 15:55:10 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 15:55:10 -0000 Subject: [MacPorts] #66401: py310-subprocess-tee @0.4.0: install fails with 404 error In-Reply-To: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> References: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> Message-ID: <064.28da9410dc42a7caa8b1384148227e7f@macports.org> #66401: py310-subprocess-tee @0.4.0: install fails with 404 error --------------------------------+---------------------- Reporter: angryjohnnie | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-subprocess-tee | --------------------------------+---------------------- Comment (by angryjohnnie): it appears that there's just no darwin22 file in the repos. this ticket can be closed. my apologies -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 16:12:06 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 16:12:06 -0000 Subject: [MacPorts] #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version In-Reply-To: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> References: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> Message-ID: <061.ea4e0f44d81917526cf802a1b40fbae0@macports.org> #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version -----------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.6.3 Resolution: | Keywords: haspatch Port: graphviz-devel | -----------------------------+-------------------------------- Comment (by ryandesign): In [changeset:"5d143a161e71de772631a547636fc172b8fbe7d5/macports-ports" 5d143a161e71de772631a547636fc172b8fbe7d5/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5d143a161e71de772631a547636fc172b8fbe7d5" graphviz-devel: Update to 7.0.4 Work around MacPorts base bug with symlinks to symlinks to manpages. See: https://trac.macports.org/ticket/61288 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 16:18:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 16:18:08 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.4baa20094adc4cc70e8152a30f195b0d@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by ryandesign): It typically takes about an hour for a change to propagate from git to rsync, so by now you should be able to `sudo port selfupdate` to receive the fix. Let me know if it helps. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 16:20:03 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 16:20:03 -0000 Subject: [MacPorts] #65582: util-linux @2.38_1 does not build on PPC Tiger, Mac OS X 10.4.11, because of "Undefined symbols: "_timersub", referenced from: _print_stats in hardlink-hardlink.o" In-Reply-To: <046.e241c4a6c70c6bb03ab73dbabffadcca@macports.org> References: <046.e241c4a6c70c6bb03ab73dbabffadcca@macports.org> Message-ID: <061.15c93f6cd0e22b72eb643245626f89d9@macports.org> #65582: util-linux @2.38_1 does not build on PPC Tiger, Mac OS X 10.4.11, because of "Undefined symbols: "_timersub", referenced from: _print_stats in hardlink-hardlink.o" -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger Port: util-linux | -------------------------+-------------------- Comment (by ballapete): The problem persist ? since `Portfile` not updated? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 16:37:48 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 16:37:48 -0000 Subject: [MacPorts] #60936: unbound @1.11.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of error: 'IPV6_TCLASS' undeclared In-Reply-To: <046.c306046194eb7f63f13ad0276448fa50@macports.org> References: <046.c306046194eb7f63f13ad0276448fa50@macports.org> Message-ID: <061.e60e32fc1463f0922e70d60b25c56e19@macports.org> #60936: unbound @1.11.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of error: 'IPV6_TCLASS' undeclared ------------------------+-------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: fixed | Keywords: tiger Port: unbound | ------------------------+-------------------- Comment (by ballapete): With `unbound @1.17.0_0` the file `services/listen_dnsport.c` is being patched so that it compiles. In the end the `port builds` and so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 17:02:37 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 17:02:37 -0000 Subject: [MacPorts] #66410: ps2eps fails with checksum error Message-ID: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> #66410: ps2eps fails with checksum error --------------------+--------------------------- Reporter: hmeine | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ps2eps at 1.70_0 --------------------+--------------------------- I don't know why this has been happening for me but apparently not everyone else: `sudo port install texlive` failed due to a distfile checksum error with ps2eps @1.70_0. I found the file with the correct properties (from 2010) at https://archive.linux.duke.edu/ctan/support/ and manually copied it to /opt/local/var/macports/distfiles/ps2eps/ps2eps.zip, but all automatic downloads picked up a smaller file that failed the checksum tests. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 17:26:45 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 17:26:45 -0000 Subject: [MacPorts] #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link In-Reply-To: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> References: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> Message-ID: <061.1915a72708b71d31ddae79fbd008e92a@macports.org> #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link ------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: leopard Port: qpdf | ------------------------+--------------------- Comment (by ballapete): Recent `version @11.2.0` does not build: {{{ [ 22%] Building CXX object libqpdf/CMakeFiles/libqpdf_object.dir/QUtil.cc.o cd /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/build/libqpdf && /opt/local/bin/g++-mp-7 -DPOINTERHOLDER_TRANSITION=4 -DQPDF_DISABLE_QTC=1 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/qpdf-11.2.0/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/qpdf-11.2.0/libqpdf -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/build/libqpdf -isystem /opt/local/include -pipe -Os -DNDEBUG -I/opt/local/include -D_GLIBCXX_USE_CXX11_ABI=0 -O3 -DNDEBUG -arch ppc -mmacosx-version- min=10.4 -fvisibility=hidden -Wall -Wconversion -Wsign-conversion -Wshadow=local -Wold-style-cast -std=c++1z -MD -MT libqpdf/CMakeFiles/libqpdf_object.dir/QUtil.cc.o -MF CMakeFiles/libqpdf_object.dir/QUtil.cc.o.d -o CMakeFiles/libqpdf_object.dir/QUtil.cc.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/qpdf-11.2.0/libqpdf/QUtil.cc /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/qpdf-11.2.0/libqpdf/QUtil.cc: In function 'QUtil::QPDFTime QUtil::get_current_qpdf_time()': /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/qpdf-11.2.0/libqpdf/QUtil.cc:951:43: error: invalid operands of types 'char*(int, int)' and 'int' to binary 'operator/' int tzoff = static_cast(timezone / 60); ~~~~~~~~~^~~~ make[2]: *** [libqpdf/CMakeFiles/libqpdf_object.dir/QUtil.cc.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_qpdf/qpdf/work/build' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 17:29:26 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 17:29:26 -0000 Subject: [MacPorts] #65581: eet @1.7.10 cannot be built on intel Monterey and PPC Tiger ==> obsolete? (was: eet @1.7.10 cannot be built on intel Monterey and PPC Tiger) In-Reply-To: <046.fb4e18a3e4732ad73621dccdd22eb975@macports.org> References: <046.fb4e18a3e4732ad73621dccdd22eb975@macports.org> Message-ID: <061.b2da8770b6cae65662600550162b98b1@macports.org> #65581: eet @1.7.10 cannot be built on intel Monterey and PPC Tiger ==> obsolete? ------------------------+----------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, monterey Port: eet | ------------------------+----------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 18:03:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 18:03:23 -0000 Subject: [MacPorts] #66283: compilers portgroup uses -rpath on Tiger In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.4dcc590df3ae8336c0cff7d40db903e5@macports.org> #66283: compilers portgroup uses -rpath on Tiger ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176 | ------------------------+----------------------- Comment (by kencu): I can't build boost171 on Tiger unless I tweak the compilers PG as well. The compilers PortGroup is adding the rpath flag on Tiger, and that needs to be fixed. The code to return the gcc version seems to be broken -- on Tiger, it returns UNKNOWN. I guess to TCL, "UNKNOWN" is >= 10, so the rpath is added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 18:04:06 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 18:04:06 -0000 Subject: [MacPorts] #66283: compilers portgroup is not adequately testing for gcc_v, and adds -rpath on Tiger (was: compilers portgroup uses -rpath on Tiger) In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.5cd9d54933587bf869fa4b18c1cba538@macports.org> #66283: compilers portgroup is not adequately testing for gcc_v, and adds -rpath on Tiger ---------------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176, boost171 | ---------------------------------+----------------------- Changes (by kencu): * port: boost176 => boost176, boost171 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 19:17:25 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 19:17:25 -0000 Subject: [MacPorts] #66283: compilers portgroup is not correctly testing for gcc_v (was: compilers portgroup is not adequately testing for gcc_v, and adds -rpath on Tiger) In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.5d22d0ac1a7331fe4f08fbeee4142da1@macports.org> #66283: compilers portgroup is not correctly testing for gcc_v ---------------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176, boost171 | ---------------------------------+----------------------- Changes (by kencu): * cc: cjones051073 (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 19:17:35 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 19:17:35 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.c073476382d769ca4249588d9e490d76@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by ballapete): It built here too with `gmake-apple @3.81_0`. The ticket can be closed. After finishing checking my `Tiger` tickets: Should I start decimate my open `Leopard` tickets? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 19:17:50 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 19:17:50 -0000 Subject: [MacPorts] #66283: compilers portgroup is not correctly testing for gcc_v In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.54fcfec171e2eb792b0e8c071d490ea7@macports.org> #66283: compilers portgroup is not correctly testing for gcc_v ---------------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176, boost171 | ---------------------------------+----------------------- Comment (by kencu): Chris, The compilers PG seems to be doing something off at least with the boost ports. We noted it is always adding the RPATH on Tiger, which started this, but the issue is not with Tiger, but with the way it is finding the current gcc_version to see if RPATH should be added. On Mojave, testing with boost171, I added this to the compilers PG: {{{ proc compilers::add_gcc_rpath_support {} { global prefix set gcc_v [compilers::get_current_gcc_version] if { ${gcc_v} >= 10 || ${gcc_v} == "devel" } { puts "adding RPATH, because gcc_v is:" puts ${gcc_v} configure.ldflags-delete -Wl,-rpath,${prefix}/lib/libgcc configure.ldflags-append -Wl,-rpath,${prefix}/lib/libgcc } } }}} and I see this, doing a "port info" with boost171: {{{ $ port info adding RPATH, because gcc_v is: UNKNOWN adding RPATH, because gcc_v is: UNKNOWN boost171 @1.71.0_6 (devel) }}} I see the same on Tiger, where gcc is gcc7. The error shows up on Tiger because rpath is not supported there, but Tiger is not the cause of the issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 19:36:39 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 19:36:39 -0000 Subject: [MacPorts] #65509: util-linux @2.38_1 has a configure script that reports empty space In-Reply-To: <046.17e9e0b87355cc87360d7c678dcb3c1f@macports.org> References: <046.17e9e0b87355cc87360d7c678dcb3c1f@macports.org> Message-ID: <061.d175b6ba9b7c89a6a57fecf2a50b26c7@macports.org> #65509: util-linux @2.38_1 has a configure script that reports empty space -------------------------+---------------------------- Reporter: ballapete | Owner: kurthindenburg Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: leopard Port: util-linux | -------------------------+---------------------------- Comment (by ballapete): The same is also visible on `Monterey`, so I'll report that on the package's home page. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 20:48:42 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 20:48:42 -0000 Subject: [MacPorts] #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" In-Reply-To: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> References: <046.6e872c9738b68509fb5915be6cc4d51b@macports.org> Message-ID: <061.8cf63bfea84e967186c82018aaa0650d@macports.org> #66270: nss @3.85 does not build on PPC Tiger, Mac OS X 10.4.11, because "No rule to make target '../certhigh/Darwin8.11.0_gcc-apple-4.2_OPT.OBJ/certhtml.o'" ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: nss | ------------------------+----------------------- Comment (by kencu): I would very much appreciate if you could screen your Leopard tickets and close/recommend closing the ones that have been fixed. Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 20:52:24 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 20:52:24 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2362906=3A_ming_=400=2E4=2E8_can?= =?utf-8?q?not_be_built_on_PPC_Leopard_because_static_declaration?= =?utf-8?q?_of_=E2=80=98swf4debug=E2=80=99_follows_non-static_dec?= =?utf-8?q?laration?= In-Reply-To: <046.6724be8302d6aa31b7b794c490bea405@macports.org> References: <046.6724be8302d6aa31b7b794c490bea405@macports.org> Message-ID: <061.ca22aea4380a4249f54d288af0aebead@macports.org> #62906: ming @0.4.8 cannot be built on PPC Leopard because static declaration of ?swf4debug? follows non-static declaration ------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: leopard Port: ming | ------------------------+------------------------ Comment (by ballapete): Recently two patches are applied to `ming @0.4.8_0` and it does not build on PPC Tiger, Mac OS X 10.4.11: {{{ mv -f .deps/swf5compiler.tab.Tpo .deps/swf5compiler.tab.Plo /bin/sh ../../libtool --tag=CC --mode=compile /opt/local/bin/gcc- apple-4.2 -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I./.. -I/opt/local/include -pipe -Os -arch ppc -Wall -DSWF_BIG_ENDIAN -MT lex.swf4.lo -MD -MP -MF .deps/lex.swf4.Tpo -c -o lex.swf4.lo lex.swf4.c libtool: compile: /opt/local/bin/gcc-apple-4.2 -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I./.. -I/opt/local/include -pipe -Os -arch ppc -Wall -DSWF_BIG_ENDIAN -MT lex.swf4.lo -MD -MP -MF .deps/lex.swf4.Tpo -c lex.swf4.c -fno-common -DPIC -o .libs/lex.swf4.o ./swf4compiler.flex:12: error: static declaration of 'swf4debug' follows non-static declaration swf4compiler.tab.h:45: error: previous declaration of 'swf4debug' was here make[4]: *** [lex.swf4.lo] Error 1 make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_multimedia_ming/ming/work /libming-ming-0_4_8/src/actioncompiler' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 20:58:38 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 20:58:38 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.6d46dfbced6b2d54fadaecef2cf276fd@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: octave | ------------------------+--------------------------------- Comment (by kencu): I ran into this today too. Crashed my Ventura system overnight. Installing {{{octave -docs}}} works fine, though: {{{ % port -v installed octave The following ports are currently installed: octave @7.3.0_0+app+gfortran+graphicsmagick+openblas+qt5+sound+sundials (active) requested_variants='-docs' platform='darwin 22' archs='x86_64' date='2022-12-06T11:05:47-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 20:58:47 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 20:58:47 -0000 Subject: [MacPorts] #66225: Building libzzip takes an eternity on PPC Mac OS X 10.5.8, Leopard In-Reply-To: <046.0072c4ff3aa0245e6ee70e93169b89fe@macports.org> References: <046.0072c4ff3aa0245e6ee70e93169b89fe@macports.org> Message-ID: <061.ca453603d57d7394ecea9d816063c366@macports.org> #66225: Building libzzip takes an eternity on PPC Mac OS X 10.5.8, Leopard ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: libzzip | ------------------------+------------------------- Comment (by ballapete): The tests still take some eternities? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 21:27:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 21:27:18 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.e4f9a6e203e0ba244452e61901b09a6b@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: octave | ------------------------+--------------------------------- Comment (by kencu): as per the other ticket, the issue is discussed and worked on here . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 21:56:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 21:56:31 -0000 Subject: [MacPorts] #66188: libsdl2: re-enable universal building i386/x86_64 In-Reply-To: <042.582af0a95cfb4576ef8fc43811e85270@macports.org> References: <042.582af0a95cfb4576ef8fc43811e85270@macports.org> Message-ID: <057.5ca4b13f652fea8049cd2c7d6f5ede4f@macports.org> #66188: libsdl2: re-enable universal building i386/x86_64 ----------------------+-------------------- Reporter: kencu | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libsdl2 | ----------------------+-------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:12:24 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 22:12:24 -0000 Subject: [MacPorts] #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version In-Reply-To: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> References: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> Message-ID: <061.1afb8faa4f744967e85b33a2cec4114d@macports.org> #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version -----------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.6.3 Resolution: | Keywords: haspatch Port: graphviz-devel | -----------------------------+-------------------------------- Comment (by ballapete): On PPC Tiger, Mac OS X 10.4.11, the update has a flaw in `configure`: {{{ checking for off64_t... no checking for struct stat64... no checking for ... no checking for fcntl.h... yes checking for search.h... yes }}} In `configure` we can find: {{{ 20011 ac_fn_c_check_type "$LINENO" "struct stat64" "ac_cv_type_struct_stat64" "$ac_includes_default" 20012 if test "x$ac_cv_type_struct_stat64" = xyes 20013 then : 20014 20015 printf "%s\n" "#define HAVE_STRUCT_STAT64 1" >>confdefs.h 20016 20017 20018 fi 20019 ac_fn_c_check_type "$LINENO" "" "ac_cv_type_" "$ac_includes_default" 20020 if test "x$ac_cv_type_" = xyes 20021 then : 20022 20023 printf "%s\n" "#define HAVE_ 1" >>confdefs.h 20024 20025 20026 fi }}} and in its `config.log` therefore: {{{ configure:20019: checking for configure:20019: /opt/local/bin/gcc-mp-7 -c -pipe -Os -arch ppc -Wall -Wextra -Wmissing-include-dirs -Wswitch-default -Wfloat-equal -Wundef -Wshadow -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wconversion -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wtrampolines -Wlogical-op -fno-common -Wall -isystem/opt/local/include/LegacySupport -I/opt/local/include -I/opt/local/include conftest.c >&5 conftest.c: In function 'main': conftest.c:62:13: error: expected expression before ')' token if (sizeof ()) ^ configure:20019: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "graphviz" | #define PACKAGE_TARNAME "graphviz" | #define PACKAGE_VERSION "7.0.4" | #define PACKAGE_STRING "graphviz 7.0.4" | #define PACKAGE_BUGREPORT "https://gitlab.com/graphviz/graphviz/-/issues" | #define PACKAGE_URL "" | #define GVPLUGIN_CONFIG_FILE "config6" | #define GVPLUGIN_VERSION 6 | #define DARWIN 1 | #define DARWIN_DYLIB "" | #define DEFAULT_FONTPATH "~/Library/Fonts:/Library/Fonts:/Network/Library/Fonts:/System/Library/Fonts" | #define PATHSEPARATOR ":" | #define DEFAULT_DPI 96 | #define BROWSER "open" | #define YYTEXT_POINTER 1 | #define HAVE_STDIO_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_UNISTD_H 1 | #define STDC_HEADERS 1 | #define HAVE_DLFCN_H 1 | #define LT_OBJDIR ".libs/" | #define HAVE_CXX11 1 | /* end confdefs.h. */ | #include | #ifdef HAVE_STDIO_H | # include | #endif | #ifdef HAVE_STDLIB_H | # include | #endif | #ifdef HAVE_STRING_H | # include | #endif | #ifdef HAVE_INTTYPES_H | # include | #endif | #ifdef HAVE_STDINT_H | # include | #endif | #ifdef HAVE_STRINGS_H | # include | #endif | #ifdef HAVE_SYS_TYPES_H | # include | #endif | #ifdef HAVE_SYS_STAT_H | # include | #endif | #ifdef HAVE_UNISTD_H | # include | #endif | int | main (void) | { | if (sizeof ()) | return 0; | ; | return 0; | } configure:20019: result: no }}} Some keyword to check for seems to be missing? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:14:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 22:14:31 -0000 Subject: [MacPorts] #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version In-Reply-To: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> References: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> Message-ID: <061.9a45a448d3e60f950351dd298405f1b4@macports.org> #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version -----------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.6.3 Resolution: | Keywords: haspatch Port: graphviz-devel | -----------------------------+-------------------------------- Comment (by ryandesign): Replying to [comment:20 ballapete]: > On PPC Tiger, Mac OS X 10.4.11, the update has a flaw in `configure`: That doesn't seem to have anything to do with this ticket; please file a new one or ideally discuss it with the developers of graphviz since I don't think we're doing anything unusual in the portfile to cause that problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:49:37 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 22:49:37 -0000 Subject: [MacPorts] #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version In-Reply-To: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> References: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> Message-ID: <061.a6a8b729405d0c53e6e5b7d6c034351b@macports.org> #61288: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version -----------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.6.3 Resolution: | Keywords: haspatch Port: graphviz-devel | -----------------------------+-------------------------------- Comment (by ballapete): The man pages are now correct, on Tiger and, more promimently, on Monterey. SO this ticket can be closed as well! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 22:51:51 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 22:51:51 -0000 Subject: [MacPorts] #61288: graphviz, graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version (was: graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version) In-Reply-To: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> References: <046.1e81b9a53dd6bc97e4a96f435538a1e8@macports.org> Message-ID: <061.195d87c5f6cf0b3c4e76fa828696ed8f@macports.org> #61288: graphviz, graphviz-devel: manpage symlink to symlink doesn't get recreated to compressed version ---------------------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: assigned Priority: Normal | Milestone: Component: base | Version: 2.6.3 Resolution: | Keywords: haspatch Port: graphviz, graphviz-devel | ---------------------------------------+-------------------------------- Changes (by ryandesign): * port: graphviz-devel => graphviz, graphviz-devel Comment: The problem remains to be fixed in the graphviz port, and as I said in comment:13 the ticket should remain open until the base bug is fixed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 6 23:38:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 06 Dec 2022 23:38:55 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.51eb026814d1a08d2372e002480f80e3@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: octave | ------------------------+--------------------------------- Comment (by SpikeLightfoot): I'd like to know how to implement that solution, but I need some hand- holding. Replying to [comment:9 kencu]: > as per the other ticket, the issue is discussed and worked on here . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 00:07:09 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 00:07:09 -0000 Subject: [MacPorts] #65867: boost176 @1.76.0_5 does not build on PPC Tiger, Mac OS X 10.4.11, because ld: -rpath can only be used when targeting Mac OS X 10.5 or later In-Reply-To: <046.993ba3da565b4e0881db1933fbdd701d@macports.org> References: <046.993ba3da565b4e0881db1933fbdd701d@macports.org> Message-ID: <061.bcd3abb19b7933563aa0b9ca725cfc02@macports.org> #65867: boost176 @1.76.0_5 does not build on PPC Tiger, Mac OS X 10.4.11, because ld: -rpath can only be used when targeting Mac OS X 10.5 or later ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger ppc Port: boost176 | ------------------------+----------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"013f72b85e6a840d47321d76be6d995ae76800af/macports-ports" 013f72b85e6a840d47321d76be6d995ae76800af/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="013f72b85e6a840d47321d76be6d995ae76800af" compilersPG: don't add rpath on Tiger closes: https://trac.macports.org/ticket/65867 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 00:13:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 00:13:47 -0000 Subject: [MacPorts] #66283: compilers portgroup is not correctly testing for gcc_v In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.98739ce6a627a67e679e071747221aff@macports.org> #66283: compilers portgroup is not correctly testing for gcc_v ---------------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: boost176, boost171 | ---------------------------------+----------------------- Comment (by kencu): This commit [013f72b85e6a840d47321d76be6d995ae76800af/macports-ports] takes the step of not adding rpath if the system is Tiger. That covers off the immediate Tiger rpath issue, and heads off the time in the future as well when gcc10+ is available on Tiger. But the issue with the gcc_v returning as UNKNOWN remains, and still should be fixed separately. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 00:33:09 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 00:33:09 -0000 Subject: [MacPorts] #66411: pdfjam @2.08: New homepage; update version Message-ID: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> #66411: pdfjam @2.08: New homepage; update version --------------------------+----------------------- Reporter: Dave-Allured | Owner: jjstickel Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: pdfjam --------------------------+----------------------- Pdfjam has moved from https://warwick.ac.uk to github. New version is available, currently 3.03. New repo and home page: https://github.com/rrthomas/pdfjam Please update portfile: version, homepage, master_sites, etc. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 00:40:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 00:40:50 -0000 Subject: [MacPorts] #66411: pdfjam @2.08: New homepage; update version In-Reply-To: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> References: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> Message-ID: <064.7dbaefae2a3eef0f220806fc19831971@macports.org> #66411: pdfjam @2.08: New homepage; update version ---------------------------+----------------------- Reporter: Dave-Allured | Owner: jjstickel Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: pdfjam | ---------------------------+----------------------- Comment (by Dave-Allured): Pdfjam may conflict with Texlive. Documentation on both sides says "pdfjam is included in texlive". I do not know how this is handled within the current texlive port. Research needed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:12:27 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 01:12:27 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.835e47f9a0b1bc415d4e176b1c4e96b4@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Changes (by sudheerhebbale): * Attachment "main.2.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:17:05 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 01:17:05 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.9e83bd4f7005155e786c4f4affbd18b2@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by sudheerhebbale): The same issue seems to be there. I ran this as root user as well (instead of running port with sudo), resulting in the same status -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:25:21 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 01:25:21 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.b132c097b75b86fc45949eeef883356d@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by sudheerhebbale): This time created the directory /opt/local/var/macports/build/.ccache/tmp with 777 permission and ran the sudo port command Resulting in inability to create directories within, such as `` :info:build ccache: error: Failed to create temporary file for /opt/local/var/macports/build/.ccache/tmp/inode-cache-64.v1.tmp.H0w9vh. tmp: Operation not permitted :info:build ccache: error: Failed to create temporary file for /opt/local/var/macports/build/.ccache/tmp/inode-cache-64.v1.tmp.fmLNwf. tmp: Operation not permitted `` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:37:12 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 01:37:12 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2365933=3A_git_=402=2E38=2E0_doe?= =?utf-8?q?s_not_build_with_gcc-4=2E2=2C_because_wrong_number_of_?= =?utf-8?q?arguments_specified_for_=E2=80=98deprecated=E2=80=99_a?= =?utf-8?q?ttribute?= In-Reply-To: <046.7b18750bb24135d07fcc094cfe3101c5@macports.org> References: <046.7b18750bb24135d07fcc094cfe3101c5@macports.org> Message-ID: <061.0b86632f094542e90ef97b7bfa2b3b1b@macports.org> #65933: git @2.38.0 does not build with gcc-4.2, because wrong number of arguments specified for ?deprecated? attribute ------------------------+------------------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: leopard tiger haspatch Port: git | ------------------------+------------------------------------ Comment (by kencu): official upstream fix: https://github.com/git/git/commit/7c07f36ad20ff206f6ed1a5609b295ec471b6cca -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:44:42 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 01:44:42 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2365933=3A_git_=402=2E38=2E0_doe?= =?utf-8?q?s_not_build_with_gcc-4=2E2=2C_because_wrong_number_of_?= =?utf-8?q?arguments_specified_for_=E2=80=98deprecated=E2=80=99_a?= =?utf-8?q?ttribute?= In-Reply-To: <046.7b18750bb24135d07fcc094cfe3101c5@macports.org> References: <046.7b18750bb24135d07fcc094cfe3101c5@macports.org> Message-ID: <061.c951d07b1a70f1c2b0364d9059324471@macports.org> #65933: git @2.38.0 does not build with gcc-4.2, because wrong number of arguments specified for ?deprecated? attribute ------------------------+------------------------------------ Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: leopard tiger haspatch Port: git | ------------------------+------------------------------------ Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"f9197a41f8dc7189897710c0c7fd1521cd299357/macports-ports" f9197a41f8dc7189897710c0c7fd1521cd299357/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f9197a41f8dc7189897710c0c7fd1521cd299357" git: fix build with older gcc versions uses upstream patch closes: https://trac.macports.org/ticket/65933 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 01:49:21 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 01:49:21 -0000 Subject: [MacPorts] #63507: xorg-server-legacy @1.20.10_2 does not build on PPC Tiger, Mac OS X 20.4.11, because bundle_trampoline.c:32:19: error: spawn.h: No such file or directory In-Reply-To: <046.e87b25cbabb65c48b304002b81c7222d@macports.org> References: <046.e87b25cbabb65c48b304002b81c7222d@macports.org> Message-ID: <061.77e33b8d32ec6c30ebb5c4e30960ae92@macports.org> #63507: xorg-server-legacy @1.20.10_2 does not build on PPC Tiger, Mac OS X 20.4.11, because bundle_trampoline.c:32:19: error: spawn.h: No such file or directory ---------------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: duplicate | Keywords: tiger Port: xorg-server-legacy | ---------------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => duplicate Comment: #62654 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:29:56 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 02:29:56 -0000 Subject: [MacPorts] #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) In-Reply-To: <048.4862f7c021d74aba503c089a8538c3db@macports.org> References: <048.4862f7c021d74aba503c089a8538c3db@macports.org> Message-ID: <063.461327b8bb5f22fe926a62ba58e04357@macports.org> #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) --------------------------+---------------------- Reporter: c-kloukinas | Owner: easye Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: slime | --------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => easye * keywords: emacs => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:35:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 02:35:35 -0000 Subject: [MacPorts] #58653: Some portfiles fail to parse under linux In-Reply-To: <042.1d2c9221ec502f66185a21b0e7cec824@macports.org> References: <042.1d2c9221ec502f66185a21b0e7cec824@macports.org> Message-ID: <057.7c59036dcf19fd4d60a68a12953df531@macports.org> #58653: Some portfiles fail to parse under linux -------------------------------------------------+------------------------- Reporter: mojca | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: botan chicken fpc gnuradio macos- | vpn-server mlt octave psi py-eric-ide qt4-mac | texworks wireshark22 | -------------------------------------------------+------------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: Everything parses now as far as I'm aware. Please open a new ticket for anything that doesn't. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:39:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 02:39:37 -0000 Subject: [MacPorts] #66407: Okular installation not working in Ventura13.0.1(arm64) In-Reply-To: <048.b290a364acf84d138d576190e2eeb91b@macports.org> References: <048.b290a364acf84d138d576190e2eeb91b@macports.org> Message-ID: <063.938c3611e377bb07dfe6be957868b108@macports.org> #66407: Okular installation not working in Ventura13.0.1(arm64) -----------------------------+------------------------- Reporter: Naageswaran | Owner: NicosPavlov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: okular qt4-mac | -----------------------------+------------------------- Changes (by jmroot): * owner: (none) => NicosPavlov * status: new => assigned * port: => okular qt4-mac Comment: I think an arm64 build of Okular would require updating to a newer version that would require KDE 5, which is not yet in MacPorts (or getting Qt 4 to work on arm64, which also doesn't seem easy.) Maybe the okular port should set `supported_archs` to match qt4-mac in the meantime? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:47:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 02:47:37 -0000 Subject: [MacPorts] #66410: ps2eps @1.70_0 stealth update (was: ps2eps fails with checksum error) In-Reply-To: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> References: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> Message-ID: <058.f120f073b3b33739aab43cf8b9e832ea@macports.org> #66410: ps2eps @1.70_0 stealth update ---------------------+-------------------- Reporter: hmeine | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ps2eps | ---------------------+-------------------- Changes (by jmroot): * port: ps2eps at 1.70_0 => ps2eps Comment: MacPorts will use different mirrors depending on how close they are to you. The file mirrored on distfiles.macports.org has checksums matching the Portfile's, but http://mirrors.ctan.org/support/ has a different file now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:53:15 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 02:53:15 -0000 Subject: [MacPorts] #66411: pdfjam @2.08: New homepage; update version In-Reply-To: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> References: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> Message-ID: <064.3e1e7c05c210afb5ff512af8ad5252f6@macports.org> #66411: pdfjam @2.08: New homepage; update version ---------------------------+----------------------- Reporter: Dave-Allured | Owner: jjstickel Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: pdfjam | ---------------------------+----------------------- Changes (by jmroot): * cc: drkp (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 02:59:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 02:59:51 -0000 Subject: [MacPorts] #65799: mupdf @1.20.3: builds fail across-the-board: expected '; ' after top level declarator In-Reply-To: <044.bb74fa920282dbd660ee00909988bdc4@macports.org> References: <044.bb74fa920282dbd660ee00909988bdc4@macports.org> Message-ID: <059.f401a1e2d7204e97077346f708a65d8f@macports.org> #65799: mupdf @1.20.3: builds fail across-the-board: expected ';' after top level declarator ----------------------+----------------------- Reporter: mascguy | Owner: essandess Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: mupdf | ----------------------+----------------------- Comment (by jmroot): Sounds like a reasonable workaround for the short term. Has anyone opened an issue with LLVM? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 06:43:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 06:43:37 -0000 Subject: [MacPorts] #65582: util-linux @2.38_1 does not build on PPC Tiger, Mac OS X 10.4.11, because of "Undefined symbols: "_timersub", referenced from: _print_stats in hardlink-hardlink.o" In-Reply-To: <046.e241c4a6c70c6bb03ab73dbabffadcca@macports.org> References: <046.e241c4a6c70c6bb03ab73dbabffadcca@macports.org> Message-ID: <061.73841a807ea83ccd406cc1bf5c5f510d@macports.org> #65582: util-linux @2.38_1 does not build on PPC Tiger, Mac OS X 10.4.11, because of "Undefined symbols: "_timersub", referenced from: _print_stats in hardlink-hardlink.o" -------------------------+-------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger Port: util-linux | -------------------------+-------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"57c7693a5b1b5821de65439fdd0e0cdeafd17340/macports-ports" 57c7693a5b1b5821de65439fdd0e0cdeafd17340/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="57c7693a5b1b5821de65439fdd0e0cdeafd17340" util-linux: fix build on Tiger strict POSIX disables certain functions on Tiger closes: https://trac.macports.org/ticket/65582 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 06:43:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 06:43:37 -0000 Subject: [MacPorts] #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) In-Reply-To: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> References: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> Message-ID: <064.9335708e6694c3377616edf5690ee05c@macports.org> #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) ---------------------------+---------------------------------- Reporter: barracuda156 | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: leopard, snowleopard Port: gdk-pixbuf2 | ---------------------------+---------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"15b554df23131d2b73c8d1eeaa5d5c4eac630400/macports-ports" 15b554df23131d2b73c8d1eeaa5d5c4eac630400/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="15b554df23131d2b73c8d1eeaa5d5c4eac630400" gdk-pixbuf2: binwrap bins when needed prevents malloc errors with newer versions of libstdc++ closes: https://trac.macports.org/ticket/66159 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 09:29:21 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 09:29:21 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.e1b44deddf4b9fcb715c9c01b08589a5@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by ryandesign): According to your log, you're not yet using the fixed version of the portfile. (`-DMONGO_USE_CCACHE=OFF` doesn't appear in the log.) Did you run `sudo port selfupdate`? If so, is it actually syncing your ports? If you run `sudo port -d selfupdate` is there some error message? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 09:48:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 09:48:37 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.b36ddeb9d70675b2540dccef8e5cfd43@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libbson | -----------------------------+------------------------ Comment (by sudheerhebbale): Post sudo port selfupdate, build and deploy of libbson went through Thanks Now while compiling broken dependencies some of the other ports are failing (e.g. xalanc) :-) Will follow that up with separate tickets -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 10:10:20 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 10:10:20 -0000 Subject: [MacPorts] #66403: Upgrading libbson on MAC OSX 13.0.1 fails In-Reply-To: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> References: <051.bc01faa2cc6336529e514e45d5de0a8d@macports.org> Message-ID: <066.32774c8ce6e0f82e7d5adf7234ff9ac7@macports.org> #66403: Upgrading libbson on MAC OSX 13.0.1 fails -----------------------------+------------------------ Reporter: sudheerhebbale | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libbson | -----------------------------+------------------------ Changes (by ryandesign): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 10:18:10 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 10:18:10 -0000 Subject: [MacPorts] #66407: Okular installation not working in Ventura13.0.1(arm64) In-Reply-To: <048.b290a364acf84d138d576190e2eeb91b@macports.org> References: <048.b290a364acf84d138d576190e2eeb91b@macports.org> Message-ID: <063.9267eb1cee4bb03ff3b11088a186b2f9@macports.org> #66407: Okular installation not working in Ventura13.0.1(arm64) -----------------------------+------------------------- Reporter: Naageswaran | Owner: NicosPavlov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: okular qt4-mac | -----------------------------+------------------------- Comment (by ryandesign): Replying to [comment:1 jmroot]: > Maybe the okular port should set `supported_archs` to match qt4-mac in the meantime? I would think that all ports that depend on qt4 should do that, and that perhaps the qt4 portgroup would be the place to do it. I think I've mentioned that elsewhere before. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 10:25:55 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 10:25:55 -0000 Subject: [MacPorts] #66294: binaryen fails to build on macOS Ventura with Xcode-14.1 In-Reply-To: <043.2925498b2cecc541bc1096dbbae11492@macports.org> References: <043.2925498b2cecc541bc1096dbbae11492@macports.org> Message-ID: <058.a923a9b3154a1fba199ab34cf5c06287@macports.org> #66294: binaryen fails to build on macOS Ventura with Xcode-14.1 -----------------------+--------------------------------- Reporter: bit-fu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: binaryen | -----------------------+--------------------------------- Comment (by ryandesign): Yes, ports should not use `-Werror` precisely for this kind of reason. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:12:07 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:12:07 -0000 Subject: [MacPorts] #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutils Message-ID: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi- docgen is missing a Python packagen, docutils -------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: gdk-pixbuf2 -------------------------+------------------------- {{{ Found CMake: /opt/local/bin/cmake (3.24.3) Run-time dependency gi-docgen found: NO (tried pkgconfig, framework and cmake) Looking for a fallback subproject for the dependency gi-docgen Executing subproject gi-docgen gi-docgen| Project name: gi-docgen gi-docgen| Project version: 2022.3 gi-docgen| subprojects/gi-docgen/meson.build:10:0: Exception: ['/usr/bin/python']> is not a valid python or it is missing distutils Subproject subprojects/gi-docgen is buildable: NO (disabling) Dependency gi-docgen from subproject gi-docgen found: NO (subproject failed to configure) Configuring gdk-pixbuf.toml using configuration Configuring gdk-pixdata.toml using configuration Program gi-docgen found: YES (/opt/local/bin/gi-docgen) }}} {{{ The following ports are currently installed: docutils_select @0.1_1 (active) requested_variants='' platform='darwin 9' archs='noarch' date='2022-12-07T12:44:56+0100' gi-docgen @2022.2_0 (active) requested_variants='' platform='darwin 9' archs='noarch' date='2022-12-02T18:25:18+0100' py310-docutils @0.19_0 (active) requested_variants='' platform='darwin 9' archs='noarch' date='2022-12-07T12:50:38+0100' python310 @3.10.8_0 requested_variants='' platform='darwin 9' archs='ppc' date='2022-12-02T17:53:12+0100' python310 @3.10.9_0 (active) requested_variants='' platform='darwin 9' archs='ppc' date='2022-12-07T12:23:29+0100' }}} I killed the build process because it is uncertain whether something usable would result from it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:12:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:12:41 -0000 Subject: [MacPorts] #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutils In-Reply-To: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> References: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> Message-ID: <061.cf987063cac023b0485498bb94530d14@macports.org> #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi- docgen is missing a Python packagen, docutils --------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: gdk-pixbuf2 | --------------------------+------------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Leopard -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:15:42 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:15:42 -0000 Subject: [MacPorts] #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutils In-Reply-To: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> References: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> Message-ID: <061.7b52180e7db104670fd4fb9db20d9ac8@macports.org> #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi- docgen is missing a Python packagen, docutils --------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: gdk-pixbuf2 | --------------------------+------------------------- Changes (by ballapete): * Attachment "meson-log.txt" added. Meson-log.txt from PPC Leopard -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:23:00 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:23:00 -0000 Subject: [MacPorts] #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutils In-Reply-To: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> References: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> Message-ID: <061.4ccf87cc40ef11ce743a748bc7cd25e0@macports.org> #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi- docgen is missing a Python packagen, docutils --------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: gdk-pixbuf2 | --------------------------+------------------------- Comment (by kencu): I. think you could just let it finish, as in the end: {{{ Program gi-docgen found: YES (/opt/local/bin/gi-docgen) }}} and the apps work?. being a bit harsh, perhaps, about warnings? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:24:28 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:24:28 -0000 Subject: [MacPorts] #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutil, but later finds it (was: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutils) In-Reply-To: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> References: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> Message-ID: <061.15eebf941fb293e9b358195288283653@macports.org> #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi- docgen is missing a Python packagen, docutil, but later finds it --------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: gdk-pixbuf2 | --------------------------+------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:40:04 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:40:04 -0000 Subject: [MacPorts] #37103: ImageMagick 6.8.0 does not correctly display SVG files on PPC (here Leopard 10.5.8) In-Reply-To: <046.3f974d98d0073e31314847fb41d9a6e0@macports.org> References: <046.3f974d98d0073e31314847fb41d9a6e0@macports.org> Message-ID: <061.adf840b57ef397ded02e200e02d0c146@macports.org> #37103: ImageMagick 6.8.0 does not correctly display SVG files on PPC (here Leopard 10.5.8) --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: off-colour Port: ImageMagick | --------------------------+------------------------ Comment (by ballapete): `display from ImageMagick @6.9.11-60` displays `PNG and SVG` files quite similar to Preview.app, so this ticket can be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:41:13 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:41:13 -0000 Subject: [MacPorts] #37103: ImageMagick 6.8.0 does not correctly display SVG files on PPC (here Leopard 10.5.8) In-Reply-To: <046.3f974d98d0073e31314847fb41d9a6e0@macports.org> References: <046.3f974d98d0073e31314847fb41d9a6e0@macports.org> Message-ID: <061.0f0f390425c92a6c652329932ffcd200@macports.org> #37103: ImageMagick 6.8.0 does not correctly display SVG files on PPC (here Leopard 10.5.8) --------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: off-colour Port: ImageMagick | --------------------------+------------------------ Changes (by kencu): * status: new => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 12:44:15 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 12:44:15 -0000 Subject: [MacPorts] #37385: Qpdf @3.0.2 does not build on PPC Leopard Mac OS X 10.5.8 because of test failure for Pl_ASCII85Decoder In-Reply-To: <046.ddb3b933f31e74c045b40a542cb336b0@macports.org> References: <046.ddb3b933f31e74c045b40a542cb336b0@macports.org> Message-ID: <061.6769089a61648f451d2702849de72ccf@macports.org> #37385: Qpdf @3.0.2 does not build on PPC Leopard Mac OS X 10.5.8 because of test failure for Pl_ASCII85Decoder ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: leopard powerpc Port: qpdf | ------------------------+-------------------------------- Comment (by ballapete): In version `@5.1.0` this problem was solved obviously, the versions `@10.3.1, @10.3.2, and @10.4.0` built correctly as well, so this ticket can be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 13:04:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 13:04:49 -0000 Subject: [MacPorts] #41355: Zenity @2.32.1_4 needs a fix after upgrade to libnotify @0.7.6_0 In-Reply-To: <046.6bfd104270623d8496d7b13dbb9a8e37@macports.org> References: <046.6bfd104270623d8496d7b13dbb9a8e37@macports.org> Message-ID: <061.14efbd719133f896adaa107797b5d4f8@macports.org> #41355: Zenity @2.32.1_4 needs a fix after upgrade to libnotify @0.7.6_0 ------------------------+--------------------- Reporter: ballapete | Owner: dbevans Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: zenity | ------------------------+--------------------- Comment (by ballapete): Recently `zenity @3.32.0_1` cannot be built on `PPC Leopard` because `selected compiler can't build for i386`. The ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 13:07:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 13:07:50 -0000 Subject: [MacPorts] #47476: scons does not properly add header guards to generated config header In-Reply-To: <046.bb13fff5ccf036ba23983a413eaddd2a@macports.org> References: <046.bb13fff5ccf036ba23983a413eaddd2a@macports.org> Message-ID: <061.97df9453b69a161dc62469b0f84467cd@macports.org> #47476: scons does not properly add header guards to generated config header ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: scons | ------------------------+-------------------------------- Comment (by ballapete): This port does not seem needed anymore, so IMO this ticket can be closed. In future `GCC 1x` will be used, so I heard (or rather read)? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 13:16:03 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 13:16:03 -0000 Subject: [MacPorts] #51815: librsvg @2.40.16 does not build on PPC Mac OS X 10.5.8, Leopard, because of "./libtool: eval: line 1085: syntax error near unexpected token `|' " In-Reply-To: <046.d0e502d33655e2547cfbfa62456fc2ef@macports.org> References: <046.d0e502d33655e2547cfbfa62456fc2ef@macports.org> Message-ID: <061.1d6c98cf16f5c024f93cfc02a8faa495@macports.org> #51815: librsvg @2.40.16 does not build on PPC Mac OS X 10.5.8, Leopard, because of "./libtool: eval: line 1085: syntax error near unexpected token `|' " ------------------------+---------------------- Reporter: ballapete | Owner: larryv Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libtool | ------------------------+---------------------- Comment (by ballapete): `librsvg @2.40.20_5+viewer` is installed. Before `librsvg @2.40.20_3+viewer and librsvg @2.40.20_4+viewer` were installed, built with `ibtool @2.4.6`, so the issue was solved and this ticket can be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:14:00 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:14:00 -0000 Subject: [MacPorts] #52116: Binutils @2.26 fail to build on PPC Leopard, Mac OS X 10.5.8, because ../include/libiberty.h contains unexpected material In-Reply-To: <046.6a8bf3bfc47145608ee7f2d929162076@macports.org> References: <046.6a8bf3bfc47145608ee7f2d929162076@macports.org> Message-ID: <061.47853cc9065de1c571ab5aa0feba6d03@macports.org> #52116: Binutils @2.26 fail to build on PPC Leopard, Mac OS X 10.5.8, because ../include/libiberty.h contains unexpected material ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: binutils | ------------------------+-------------------------------- Comment (by ballapete): Recent `binutils @2.39_1` do not build here on PPC Leopard, Mac OS X 10.5.8: {{{ libtool: compile: /usr/bin/gcc-4.2 -std=gnu99 -DHAVE_CONFIG_H -I. -D_GNU_SOURCE -I. -I./../include -I./../bfd -I../bfd -DNOBFD=0 -I/opt/local/include -std=gnu99 -Wall -W -Wall -Wwrite-strings -Wmissing- format-attribute -Wstrict-prototypes -Wmissing-prototypes -Wold-style- definition -pedantic -Wno-long-long -I./../zlib -pipe -Os -arch ppc -MT libctf_la-ctf-open-bfd.lo -MD -MP -MF .deps/libctf_la-ctf-open-bfd.Tpo -c ctf-open-bfd.c -fno-common -DPIC -o .libs/libctf_la-ctf-open-bfd.o libtool: compile: /usr/bin/gcc-4.2 -std=gnu99 -DHAVE_CONFIG_H -I. -D_GNU_SOURCE -I. -I./../include -I./../bfd -I../bfd -DNOBFD=0 -I/opt/local/include -std=gnu99 -Wall -W -Wall -Wwrite-strings -Wmissing- format-attribute -Wstrict-prototypes -Wmissing-prototypes -Wold-style- definition -pedantic -Wno-long-long -I./../zlib -pipe -Os -arch ppc -MT libctf_la-ctf-open-bfd.lo -MD -MP -MF .deps/libctf_la-ctf-open-bfd.Tpo -c ctf-open-bfd.c -o libctf_la-ctf-open-bfd.o >/dev/null 2>&1 mv -f .deps/libctf_la-ctf-open-bfd.Tpo .deps/libctf_la-ctf-open-bfd.Plo /bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc-4.2 -std=gnu99 -std=gnu99 -Wall -W -Wall -Wwrite-strings -Wmissing-format-attribute -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -pedantic -Wno-long-long -I./../zlib -pipe -Os -arch ppc -version-info 0:0:0 -export-symbols-regex ctf_.* -L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc -o libctf.la -rpath /opt/local/lib libctf_la-ctf-archive.lo libctf_la-ctf-dump.lo libctf_la- ctf-create.lo libctf_la-ctf-decl.lo libctf_la-ctf-error.lo libctf_la-ctf- hash.lo libctf_la-ctf-labels.lo libctf_la-ctf-dedup.lo libctf_la-ctf- link.lo libctf_la-ctf-lookup.lo libctf_la-ctf-open.lo libctf_la-ctf- serialize.lo libctf_la-ctf-sha1.lo libctf_la-ctf-string.lo libctf_la-ctf- subr.lo libctf_la-ctf-types.lo libctf_la-ctf-util.lo libctf_la-ctf-open- bfd.lo -L/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_binutils/binutils/work/binutils-2.39/libctf/../libiberty/pic -liberty -lintl ../bfd/libbfd.la -L/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_binutils/binutils/work/binutils-2.39/libctf/../libiberty/pic -liberty -lintl -L./../zlib -lz libtool: link: warning: `/opt/local/lib/libintl.la' seems to be moved libtool: link: /opt/local/bin/nm -B .libs/libctf_la-ctf-archive.o .libs /libctf_la-ctf-dump.o .libs/libctf_la-ctf-create.o .libs/libctf_la-ctf- decl.o .libs/libctf_la-ctf-error.o .libs/libctf_la-ctf-hash.o .libs /libctf_la-ctf-labels.o .libs/libctf_la-ctf-dedup.o .libs/libctf_la-ctf- link.o .libs/libctf_la-ctf-lookup.o .libs/libctf_la-ctf-open.o .libs /libctf_la-ctf-serialize.o .libs/libctf_la-ctf-sha1.o .libs/libctf_la-ctf- string.o .libs/libctf_la-ctf-subr.o .libs/libctf_la-ctf-types.o .libs /libctf_la-ctf-util.o .libs/libctf_la-ctf-open-bfd.o | | /opt/local/bin/gsed 's/.* //' | sort | uniq > .libs/libctf.exp ./libtool: eval: line 1115: syntax error near unexpected token `|' ./libtool: eval: line 1115: `/opt/local/bin/nm -B .libs/libctf_la-ctf- archive.o .libs/libctf_la-ctf-dump.o .libs/libctf_la-ctf-create.o .libs /libctf_la-ctf-decl.o .libs/libctf_la-ctf-error.o .libs/libctf_la-ctf- hash.o .libs/libctf_la-ctf-labels.o .libs/libctf_la-ctf-dedup.o .libs /libctf_la-ctf-link.o .libs/libctf_la-ctf-lookup.o .libs/libctf_la-ctf- open.o .libs/libctf_la-ctf-serialize.o .libs/libctf_la-ctf-sha1.o .libs /libctf_la-ctf-string.o .libs/libctf_la-ctf-subr.o .libs/libctf_la-ctf- types.o .libs/libctf_la-ctf-util.o .libs/libctf_la-ctf-open-bfd.o | | /opt/local/bin/gsed 's/.* //' | sort | uniq > .libs/libctf.exp' make[3]: *** [libctf.la] Error 1 make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_binutils/binutils/work/binutils-2.39/libctf' make[2]: *** [all] Error 2 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_binutils/binutils/work/binutils-2.39/libctf' make[1]: *** [all-libctf] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_binutils/binutils/work/binutils-2.39' }}} SInce I do not need them the ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:15:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:15:51 -0000 Subject: [MacPorts] #52116: Binutils @2.26 fail to build on PPC Leopard, Mac OS X 10.5.8, because ../include/libiberty.h contains unexpected material In-Reply-To: <046.6a8bf3bfc47145608ee7f2d929162076@macports.org> References: <046.6a8bf3bfc47145608ee7f2d929162076@macports.org> Message-ID: <061.d2c1941e11eb4d9357f8f815c308bbdf@macports.org> #52116: Binutils @2.26 fail to build on PPC Leopard, Mac OS X 10.5.8, because ../include/libiberty.h contains unexpected material ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: binutils | ------------------------+-------------------------------- Changes (by ballapete): * Attachment "main.2.log" added. Newer main.log from building binutils @2.39_1 on PPC Leopard, Mac OS X 10.5.8 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:17:27 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:17:27 -0000 Subject: [MacPorts] #52117: Qpdf @6.0.0 does not build on PPC Leopard, Mac OS X 10.5.8 because of Undefined symbol "Pl_MD5::persistAcrossFinish(bool)" that ld could not find In-Reply-To: <046.7954189b1f72027aa401cde42a7139f1@macports.org> References: <046.7954189b1f72027aa401cde42a7139f1@macports.org> Message-ID: <061.c81a673f90b7aebbf222e67924ad6316@macports.org> #52117: Qpdf @6.0.0 does not build on PPC Leopard, Mac OS X 10.5.8 because of Undefined symbol "Pl_MD5::persistAcrossFinish(bool)" that ld could not find ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: leopard powerpc Port: qpdf | ------------------------+-------------------------------- Comment (by ballapete): This ticket can be closed since a newer version, `@10.4.0`, could be installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:21:01 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:21:01 -0000 Subject: [MacPorts] #66411: pdfjam @2.08: New homepage; update version In-Reply-To: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> References: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> Message-ID: <064.d2a73c5275c46bb0c397f3814ce782bb@macports.org> #66411: pdfjam @2.08: New homepage; update version ---------------------------+----------------------- Reporter: Dave-Allured | Owner: jjstickel Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: pdfjam | ---------------------------+----------------------- Comment (by Dave-Allured): Replying to [comment:1 Dave-Allured]: > Pdfjam may conflict with Texlive. Oh I see. There is no conflict. The texlive core does not install pdfjam. Pdfjam is simply a dependency of supplemental port **texlive-bin- extra**. So, safe to update this port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:21:38 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:21:38 -0000 Subject: [MacPorts] #54393: Port fails to execute an upgrade with the additional arguments given at invocation but uses it for upgrading the ports on which the given port depends In-Reply-To: <046.f8b5e4c227cabc1e249f39959215d514@macports.org> References: <046.f8b5e4c227cabc1e249f39959215d514@macports.org> Message-ID: <061.8772368ea7406fee1ed193fb8a4e210a@macports.org> #54393: Port fails to execute an upgrade with the additional arguments given at invocation but uses it for upgrading the ports on which the given port depends ------------------------+--------------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.4.1 Resolution: | Keywords: tiger leopard snowleopard Port: | ------------------------+--------------------------------------- Comment (by ballapete): Since I knew that the settings in `Portfile` were at least inadequate I assumed that I could override them. Insn't this the default behaviour for the case without `rev-`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:22:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:22:47 -0000 Subject: [MacPorts] #54640: py27-cryptography @2.0.3 does not build on PPC Leopard, Mac OS X 10.5.8, because "Symbol not found: _PyUnicodeUCS2_FromObject" In-Reply-To: <046.56fbaa0c83b5c81c00ee1e8690efef8d@macports.org> References: <046.56fbaa0c83b5c81c00ee1e8690efef8d@macports.org> Message-ID: <061.1ca80aa436ba8669a395031595eb4b87@macports.org> #54640: py27-cryptography @2.0.3 does not build on PPC Leopard, Mac OS X 10.5.8, because "Symbol not found: _PyUnicodeUCS2_FromObject" ------------------------------+---------------------- Reporter: ballapete | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.4.1 Resolution: | Keywords: leopard Port: py-cryptography | ------------------------------+---------------------- Comment (by ballapete): `Python 2.7` has gone, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:23:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:23:47 -0000 Subject: [MacPorts] #55525: py27-pynacl @1.2.1_1 does not build on PPC Leopard, Mac OS X 10.5.8, because Symbol not found: _PyUnicodeUCS2_FromObject In-Reply-To: <046.152a6b2cc811e139d070affa03affb0d@macports.org> References: <046.152a6b2cc811e139d070affa03affb0d@macports.org> Message-ID: <061.8c04666fe4b8b157cf290d69f6d3cfc8@macports.org> #55525: py27-pynacl @1.2.1_1 does not build on PPC Leopard, Mac OS X 10.5.8, because Symbol not found: _PyUnicodeUCS2_FromObject ------------------------+---------------------- Reporter: ballapete | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.4.2 Resolution: | Keywords: leopard Port: py-pynacl | ------------------------+---------------------- Comment (by ballapete): `Python 2.7` has gone, so this ticket can be closed as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:25:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:25:58 -0000 Subject: [MacPorts] #56513: gtk-doc @1.28_1 does not build on PPC Leopard, Mac OS X 10.5.8, because Python with UCS4 support is missing? In-Reply-To: <046.fca0780526dee046c3ec64cbca886343@macports.org> References: <046.fca0780526dee046c3ec64cbca886343@macports.org> Message-ID: <061.ccb798e4b8a96295679b5aecef5cd78e@macports.org> #56513: gtk-doc @1.28_1 does not build on PPC Leopard, Mac OS X 10.5.8, because Python with UCS4 support is missing? ------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.4.4 Resolution: | Keywords: leopard Port: gtk-doc | ------------------------+--------------------- Comment (by ballapete): Again, `Python 2.7` has gone and so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:29:46 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:29:46 -0000 Subject: [MacPorts] #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi-docgen is missing a Python packagen, docutil, but later finds it In-Reply-To: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> References: <046.650b4b0c712593abb0cebfcb84f47903@macports.org> Message-ID: <061.2926b4b7e4b17a57b53e3aa0cc40c501@macports.org> #66412: gdk-pixbuf2 @2.42.9_1 reports on PPC Leopard, Mac OS X 10.5.8, that gi- docgen is missing a Python packagen, docutil, but later finds it --------------------------+------------------------- Reporter: ballapete | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: gdk-pixbuf2 | --------------------------+------------------------- Changes (by ryandesign): * owner: (none) => mascguy * cc: mascguy@? (removed) * status: new => assigned * type: request => defect -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:31:26 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:31:26 -0000 Subject: [MacPorts] #59664: source-highlight @3.1.9 does not build on PPC Mac OS X 10.5.8, Leopard, because new source-highlight binary cannot produc HTML doc from Java source file In-Reply-To: <046.712c063fd89aed49938db4d254712b67@macports.org> References: <046.712c063fd89aed49938db4d254712b67@macports.org> Message-ID: <061.842166628507b10e489becf7bebc65e3@macports.org> #59664: source-highlight @3.1.9 does not build on PPC Mac OS X 10.5.8, Leopard, because new source-highlight binary cannot produc HTML doc from Java source file -------------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: leopard Port: source-highlight | -------------------------------+---------------------- Comment (by ballapete): Some versions could be built and installed later (`source-highlight @3.1.9_0, source-highlight @3.1.9_1`), and the versions of `boost` do not use it anymore, so the ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:32:02 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:32:02 -0000 Subject: [MacPorts] #66401: py310-subprocess-tee @0.4.0: install fails with 404 error In-Reply-To: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> References: <049.74dbc600e6d8d41e5c32681e2ff4ef45@macports.org> Message-ID: <064.f0f97cc1182793b4642aae70344ee186@macports.org> #66401: py310-subprocess-tee @0.4.0: install fails with 404 error --------------------------------+-------------------- Reporter: angryjohnnie | Owner: judaew Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: py-subprocess-tee | --------------------------------+-------------------- Changes (by ryandesign): * status: assigned => closed * resolution: => duplicate Comment: True, there are no darwin 22 archives for any port at this time. We (I) haven't started building them yet. This shouldn't be a problem because MacPorts will then build from source on your system. The problem shown in the log you attached was fixed in #66387. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:34:24 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:34:24 -0000 Subject: [MacPorts] #61115: Gnupg2 does not work on Mac OS X 10.5.x and older In-Reply-To: <046.93998ed904c9f765303245a68a77bd79@macports.org> References: <046.93998ed904c9f765303245a68a77bd79@macports.org> Message-ID: <061.831ddbefa959dc103fab2425a4e57833@macports.org> #61115: Gnupg2 does not work on Mac OS X 10.5.x and older --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: npth, gnupg | --------------------------+-------------------- Comment (by ballapete): I think this is still true. For me it's no problem because I have a patched and working installation of `npth`. Until it's possible upgrade? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:44:28 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:44:28 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.a540036dc5294abadca196104ca4ca2e@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): `PPC Leopard, Mac OS X 10.5.8` shows the same behaviour. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:47:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:47:48 -0000 Subject: [MacPorts] #62617: p5.30-libwww-perl has a "need to do a sane metamerge!" In-Reply-To: <046.b772c1b889e8cde1e1faab381165c23a@macports.org> References: <046.b772c1b889e8cde1e1faab381165c23a@macports.org> Message-ID: <061.d8380a034f3c42ab277a837aa4a9fe04@macports.org> #62617: p5.30-libwww-perl has a "need to do a sane metamerge!" -----------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: leopard Port: p5-libwww-perl | -----------------------------+--------------------- Comment (by ballapete): Right now `p5.34-libwww-perl @6.670.0` is installed, and since upgrading the package then worked, the ticket can be closed IMO. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 14:54:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 14:54:49 -0000 Subject: [MacPorts] #66411: pdfjam @2.08: New homepage; update version In-Reply-To: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> References: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> Message-ID: <064.8a9133e9cfc6741d8ef4f585cbfb4a1c@macports.org> #66411: pdfjam @2.08: New homepage; update version ---------------------------+----------------------- Reporter: Dave-Allured | Owner: jjstickel Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: pdfjam | ---------------------------+----------------------- Comment (by jjstickel): Seems straightforward. I have less time for macports these days, so a submitting a PR would move this along more quickly. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:06:34 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:06:34 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2362906=3A_ming_=400=2E4=2E8_can?= =?utf-8?q?not_be_built_on_PPC_Leopard_because_static_declaration?= =?utf-8?q?_of_=E2=80=98swf4debug=E2=80=99_follows_non-static_dec?= =?utf-8?q?laration?= In-Reply-To: <046.6724be8302d6aa31b7b794c490bea405@macports.org> References: <046.6724be8302d6aa31b7b794c490bea405@macports.org> Message-ID: <061.4f4b462a1100456b9e2519ea87c264e0@macports.org> #62906: ming @0.4.8 cannot be built on PPC Leopard because static declaration of ?swf4debug? follows non-static declaration ------------------------+------------------------ Reporter: ballapete | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: leopard Port: ming | ------------------------+------------------------ Comment (by ballapete): On `PPC Leopard, Mac OS X 10.5.8` I still get: {{{ /bin/sh ../../libtool --tag=CC --mode=compile /usr/bin/gcc-4.2 -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I./.. -I/opt/local/include -pipe -Os -arch ppc -Wall -DSWF_BIG_ENDIAN -MT lex.swf4.lo -MD -MP -MF .deps/lex.swf4.Tpo -c -o lex.swf4.lo lex.swf4.c libtool: compile: /usr/bin/gcc-4.2 -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I./.. -I/opt/local/include -pipe -Os -arch ppc -Wall -DSWF_BIG_ENDIAN -MT lex.swf4.lo -MD -MP -MF .deps/lex.swf4.Tpo -c lex.swf4.c -fno-common -DPIC -o .libs/lex.swf4.o ./swf4compiler.flex:12: error: static declaration of 'swf4debug' follows non-static declaration swf4compiler.tab.h:45: error: previous declaration of 'swf4debug' was here make[4]: *** [lex.swf4.lo] Error 1 make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_multimedia_ming/ming/work /libming-ming-0_4_8/src/actioncompiler' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:08:56 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:08:56 -0000 Subject: [MacPorts] #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link In-Reply-To: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> References: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> Message-ID: <061.23b9c5c3101c2705522a0805ccd6b8ba@macports.org> #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link ------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: leopard Port: qpdf | ------------------------+--------------------- Comment (by ballapete): Since a newer version, `@10.4.0`, is installed this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:30:29 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:30:29 -0000 Subject: [MacPorts] #66413: cppcheck @2.9.3 seems to have in Portfile one 'reinplace' too many Message-ID: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> #66413: cppcheck @2.9.3 seems to have in Portfile one 'reinplace' too many -------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: cppcheck -------------------------+---------------------- {{{ ---> Extracting cppcheck Warning: reinplace /CXXFLAGS/s/-O2/-Os -D_GLIBCXX_USE_CXX11_ABI=0/ didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_cppcheck/cppcheck/work/cppcheck-2.9.3/Makefile ---> Configuring cppcheck }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:48:29 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:48:29 -0000 Subject: [MacPorts] #60093: gtkglext @1.2.0_11 +quartz does not configure on macOS Catalina, Version 10.15.3, because 'configure: error: X development libraries not found' In-Reply-To: <046.1ed92cb7bcc273e733276caa6cf949eb@macports.org> References: <046.1ed92cb7bcc273e733276caa6cf949eb@macports.org> Message-ID: <061.722c8aa5326f3232ef26f178cc1bba5b@macports.org> #60093: gtkglext @1.2.0_11 +quartz does not configure on macOS Catalina, Version 10.15.3, because 'configure: error: X development libraries not found' ------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: catalina Port: gtkglext | ------------------------+---------------------- Comment (by ballapete): `macOS Catalina` is gone (for me), so presumingly this ticket can be closed? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:51:28 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:51:28 -0000 Subject: [MacPorts] #66411: pdfjam @2.08: New homepage; update version In-Reply-To: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> References: <049.3208b803bffa1a3d3277d13cb1413d1a@macports.org> Message-ID: <064.e72d514228b6c8e0838ba9212e99517f@macports.org> #66411: pdfjam @2.08: New homepage; update version ---------------------------+----------------------- Reporter: Dave-Allured | Owner: jjstickel Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: pdfjam | ---------------------------+----------------------- Comment (by Dave-Allured): I also do not have the time right now for update and testing. I just wanted to get a bookmark in for this new repo. Volunteer welcome. No hurry, the current version seems to be working well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:51:33 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:51:33 -0000 Subject: [MacPorts] #61472: "./restore_ports.tcl myports.txt" fails on Big Sur without giving a single hint (what the problem might be, where I could look up details, ...) In-Reply-To: <046.d055c153331fe55f033abdc0e68429de@macports.org> References: <046.d055c153331fe55f033abdc0e68429de@macports.org> Message-ID: <061.99d7149f12183e74b009849d743779c4@macports.org> #61472: "./restore_ports.tcl myports.txt" fails on Big Sur without giving a single hint (what the problem might be, where I could look up details, ...) ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: bigsur Port: | ------------------------+-------------------- Comment (by ballapete): `macOS Big Sur` has gone for me, the cause for this ticket seems to be rare, and so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:54:03 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:54:03 -0000 Subject: [MacPorts] #59664: source-highlight @3.1.9 does not build on PPC Mac OS X 10.5.8, Leopard, because new source-highlight binary cannot produc HTML doc from Java source file In-Reply-To: <046.712c063fd89aed49938db4d254712b67@macports.org> References: <046.712c063fd89aed49938db4d254712b67@macports.org> Message-ID: <061.0c9be29c10c52bf67652a8f065cedffc@macports.org> #59664: source-highlight @3.1.9 does not build on PPC Mac OS X 10.5.8, Leopard, because new source-highlight binary cannot produc HTML doc from Java source file -------------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: leopard Port: source-highlight | -------------------------------+--------------------- Changes (by kencu): * status: reopened => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:54:40 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:54:40 -0000 Subject: [MacPorts] #37385: Qpdf @3.0.2 does not build on PPC Leopard Mac OS X 10.5.8 because of test failure for Pl_ASCII85Decoder In-Reply-To: <046.ddb3b933f31e74c045b40a542cb336b0@macports.org> References: <046.ddb3b933f31e74c045b40a542cb336b0@macports.org> Message-ID: <061.3d1c9ed4f8868abfea7e0267a45e6144@macports.org> #37385: Qpdf @3.0.2 does not build on PPC Leopard Mac OS X 10.5.8 because of test failure for Pl_ASCII85Decoder ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: leopard powerpc Port: qpdf | ------------------------+-------------------------------- Changes (by kencu): * status: reopened => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:55:20 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:55:20 -0000 Subject: [MacPorts] #41355: Zenity @2.32.1_4 needs a fix after upgrade to libnotify @0.7.6_0 In-Reply-To: <046.6bfd104270623d8496d7b13dbb9a8e37@macports.org> References: <046.6bfd104270623d8496d7b13dbb9a8e37@macports.org> Message-ID: <061.fbfc84ab0d9c3eb18c79b2abaf61dad3@macports.org> #41355: Zenity @2.32.1_4 needs a fix after upgrade to libnotify @0.7.6_0 ------------------------+--------------------- Reporter: ballapete | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: fixed | Keywords: Port: zenity | ------------------------+--------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:55:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:55:50 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.f29c1b81963a384693bd62c67ad56dc3@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by cjones051073): Twhat point are you trying to make with those latest post ? We know what the issue is, and they add nothing on top of that. `mpstats` uses `port` which in turn does not use `curl`, the macports provide one or the system one, but instead is linked against the system `libcurl`. This, on these ancient OSes is going to be woefully out of date, hence the problems. As already mentioned above, a number of times, you need to rebuild your macPorts base installation to use a newer `libcurl` then the system one, which is what is used by default. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:56:10 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:56:10 -0000 Subject: [MacPorts] #51815: librsvg @2.40.16 does not build on PPC Mac OS X 10.5.8, Leopard, because of "./libtool: eval: line 1085: syntax error near unexpected token `|' " In-Reply-To: <046.d0e502d33655e2547cfbfa62456fc2ef@macports.org> References: <046.d0e502d33655e2547cfbfa62456fc2ef@macports.org> Message-ID: <061.11303869441989779e68bad2e6c960eb@macports.org> #51815: librsvg @2.40.16 does not build on PPC Mac OS X 10.5.8, Leopard, because of "./libtool: eval: line 1085: syntax error near unexpected token `|' " ------------------------+-------------------- Reporter: ballapete | Owner: larryv Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: libtool | ------------------------+-------------------- Changes (by kencu): * status: reopened => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:57:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:57:48 -0000 Subject: [MacPorts] #52117: Qpdf @6.0.0 does not build on PPC Leopard, Mac OS X 10.5.8 because of Undefined symbol "Pl_MD5::persistAcrossFinish(bool)" that ld could not find In-Reply-To: <046.7954189b1f72027aa401cde42a7139f1@macports.org> References: <046.7954189b1f72027aa401cde42a7139f1@macports.org> Message-ID: <061.4c784eb07d39a1c8802a27f93be5bb8b@macports.org> #52117: Qpdf @6.0.0 does not build on PPC Leopard, Mac OS X 10.5.8 because of Undefined symbol "Pl_MD5::persistAcrossFinish(bool)" that ld could not find ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: leopard powerpc Port: qpdf | ------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 15:59:04 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 15:59:04 -0000 Subject: [MacPorts] #62617: p5.30-libwww-perl has a "need to do a sane metamerge!" In-Reply-To: <046.b772c1b889e8cde1e1faab381165c23a@macports.org> References: <046.b772c1b889e8cde1e1faab381165c23a@macports.org> Message-ID: <061.0639de513bdcb4bbe6c55458010c5714@macports.org> #62617: p5.30-libwww-perl has a "need to do a sane metamerge!" -----------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: leopard Port: p5-libwww-perl | -----------------------------+--------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: thx -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:13:57 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:13:57 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.4e4bece9c498429ce7ba24fd456fa326@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): Replying to [comment:24 cjones051073]: > > As already mentioned above, a number of times, you need to rebuild your macPorts base installation to use a newer `libcurl` then the system one, which is what is used by default. How can that be done? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:29:19 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:29:19 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" Message-ID: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" --------------------------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: libffi snow leopard patch can't find | Port: libffi --------------------------------------------------+-------------------- When trying to install libffi on Mac OS 10.6.8 I see this error: ---> Applying patches to libffi Error: Failed to patch libffi: can't read "patch.cmd": Failed to locate 'patch' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:29:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:29:54 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.db48d41015b8a0a0f649f742e92e6d51@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" -------------------------+------------------------------------------------- Reporter: | Owner: (none) programmingkidx | Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: libffi snow leopard patch can't Port: libffi | find -------------------------+------------------------------------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:31:33 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:31:33 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.c31b0729c3bed18828aa7bb2cba70ab2@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by cjones051073): Ken posted instructions in the very first comment https://trac.macports.org/ticket/61333#comment:1 you need to rebuild macports base from source, configuring the build to use a custom up to date curl installation. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:43:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:43:51 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.467cae08d18e8bcefcd67b89fe1cab2d@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): I still cannot make any sense of this lengthy discussion. I already tried one or two things that I thought of I had understood, but they did not change anything. I think it's better to close this ticket and uninstall mpstats! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:51:18 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:51:18 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.18b8b6f81ed9be0065478f50310aad40@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by cjones051073): This ticket should not be closed as the issue is valid, and the information here has allowed a number of others to reinstall base which fixed things for them. In short you, need to follow the macports instructions to install base from source https://www.macports.org/install.php See the "Source installation" section follow the instructions there, at at the point you configure the build instead of running just `./configure` run `./configure --with- curlprefix=/X/Y/Z` replacing `/X/Y/Z` with the path to the external curl installation you wish to use. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 16:59:32 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 16:59:32 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.4b3dca5e54df378ea871c35edc00b4f8@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Comment (by ballapete): The problem is not solved yet, or it was solved only a preliminary release like 28.1.91 or such. It still exists can easily be triggered as shown in the attached screenshot. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:01:56 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 17:01:56 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.29c70728bb8e6b52a71da43564294da5@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port in GNU Emacs and ticket #53404.png" added. The final scan after successfully installing a port resets tty mode -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:07:56 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 17:07:56 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.43abcc6f8e659947d60feeb676740b26@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Comment (by ballapete): The picture is taken on `macOS High Sierra, Version 10.13.6` in recent `emacs @28.2_0+x11 (active) requested_variants='+x11' platform='darwin 17' archs='x86_64' date='2022-09-21T13:03:19+0200'`. Works similarly in `Monterey`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:36:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 17:36:41 -0000 Subject: [MacPorts] #47476: scons does not properly add header guards to generated config header In-Reply-To: <046.bb13fff5ccf036ba23983a413eaddd2a@macports.org> References: <046.bb13fff5ccf036ba23983a413eaddd2a@macports.org> Message-ID: <061.0a05dc2b23fbeb793ad909ced35590ac@macports.org> #47476: scons does not properly add header guards to generated config header ------------------------+-------------------------------- Reporter: ballapete | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: scons | ------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: closing as fixed. A new ticket with new information would be needed if this arises again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 17:38:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 17:38:35 -0000 Subject: [MacPorts] #54393: Port fails to execute an upgrade with the additional arguments given at invocation but uses it for upgrading the ports on which the given port depends In-Reply-To: <046.f8b5e4c227cabc1e249f39959215d514@macports.org> References: <046.f8b5e4c227cabc1e249f39959215d514@macports.org> Message-ID: <061.51d79766733f069a7bc6cb9860204083@macports.org> #54393: Port fails to execute an upgrade with the additional arguments given at invocation but uses it for upgrading the ports on which the given port depends -------------------------+--------------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.4.1 Resolution: worksforme | Keywords: tiger leopard snowleopard Port: | -------------------------+--------------------------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: closing as this is the expected behaviour for the port command -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 18:49:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 18:49:48 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory Message-ID: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory -----------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: cmake -----------------------+----------------------- `sudo port patch cmake` does not work. It attempts to patch an empty directory. This is odd, as it worked last week. It may be related to using the latest macports-base checkout. This happens on both El Capitan and Monterey. Checkouts: [ffdb7d9ee9e59e9d69a2f29ac08dfd5090f84759/macports-base] (version 2.8.99) [0cc71e8df56f9a4aa28ec508d45169cde759c00e/macports-ports] {{{ sudo port clean cmake sudo port extract cmake cd $(port work cmake) ls cmake-v3.24.3-c974557598645360fbabac71352b083117e3cc17 sudo port -d patch cmake ls cmake-3.24.3 cmake-v3.24.3-c974557598645360fbabac71352b083117e3cc17 The directory with the short name, which has now appeared, is empty. }}} Here's a partial listing of the log. It's applying the patch to the empty directory and failing: {{{ Executing: cd "/opt/local/var/macports/build/_Users_davidevans_macports_sources_github .com_macports_macports-ports_devel_cmake/cmake/work/cmake-3.24.3" && /usr/bin/patch -p0 < '/Users/davidevans/macports/sources/github.com/macports/macports- ports/devel/cmake/files/patch-Modules-noArchCheck.diff' DEBUG: system: cd "/opt/local/var/macports/build/_Users_davidevans_macports_sources_github .com_macports_macports-ports_devel_cmake/cmake/work/cmake-3.24.3" && /usr/bin/patch -p0 < '/Users/davidevans/macports/sources/github.com/macports/macports- ports/devel/cmake/files/patch-Modules-noArchCheck.diff' can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Modules/BasicConfigVersion-AnyNewerVersion.cmake.in.orig |+++ Modules/BasicConfigVersion-AnyNewerVersion.cmake.in -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 21 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Modules/BasicConfigVersion-ExactVersion.cmake.in.orig |+++ Modules/BasicConfigVersion-ExactVersion.cmake.in -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 39 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Modules/BasicConfigVersion-SameMajorVersion.cmake.in.orig |+++ Modules/BasicConfigVersion-SameMajorVersion.cmake.in -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 57 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Modules/BasicConfigVersion-SameMinorVersion.cmake.in.orig |+++ Modules/BasicConfigVersion-SameMinorVersion.cmake.in -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored Command failed: cd "/opt/local/var/macports/build/_Users_davidevans_macports_sources_github .com_macports_macports-ports_devel_cmake/cmake/work/cmake-3.24.3" && /usr/bin/patch -p0 < '/Users/davidevans/macports/sources/github.com/macports/macports- ports/devel/cmake/files/patch-Modules-noArchCheck.diff' Exit code: 1 Error: Failed to patch cmake: command execution failed DEBUG: Error code: CHILDSTATUS 62912 1 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 18:59:12 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 18:59:12 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.be4a3b8ed4889edd5dfb580cecaac597@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): `./configure` needed two arguments: `--with- curlprefix=/opt/local/lib/libcurl.dylib CURL_CONFIG=/opt/local/bin/curl- config`. First submission worked without complaint. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:09:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 19:09:35 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.dfb133c528fca3011127864c9818a550@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by cjones051073): --with-curlprefix expects a directory, not a complet path to a library?. Also, be aware that build base against a library provided by your primary macports prefix is unsafe, as if you remove that port you will render you macports installation unusable. Its much better to use an entirely distinct installation to avoid this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:19:15 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 19:19:15 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.aa893df962b22e26f6347a2b79a113c0@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+----------------------- Comment (by michaelld): Works for me on the following: * Port version `2.8.0-99-20221129-01-3d9856bc` / macOS version `11.7.2 20G1008` Intel / Xcode version `12.3 12C33` * Port version `2.8.0-99-20221116-01-887b2fb9` / macOS version `11.7.2 20G1011` ARM64 / Xcode version `13.2.1 13C100` * Port version `2.8.0-99-20221116-01-887b2fb9` / macOS version `13.1 22C5059b` / Xcode version `14.1 14B47b` I will update one of these to the latest BASE code & see what happens -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:26:14 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 19:26:14 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.d49aa90ea87bbc685fcc22f17597ce55@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+----------------------- Comment (by michaelld): Yup I see this issue too with the latest BASE HEAD .. across the board, not just a specific OS / Xcode version -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:26:57 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 19:26:57 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.2073715b18a936bad0865685e8eed795@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+----------------------- Comment (by michaelld): ah ... guessing it's a default patch level setting -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:36:19 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 19:36:19 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.c3da733851eb6fcb6d4bdafbe2d52ed0@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+----------------------- Comment (by michaelld): or not ... that's correct ...hmmm ... strange !!! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 19:39:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 19:39:37 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.b28676d80cb8a8cfadbd828c1819706a@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+----------------------- Comment (by michaelld): ah ... looks like the link from short WORKSRCDIR to long isn't working ... {{{ $ pwd /opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_devel_cmake/cmake/work $ ll cmake* cmake-3.24.3: cmake-v3.24.3-c974557598645360fbabac71352b083117e3cc17: total 440 -rw-rw-rw- 1 macports admin 1411 Nov 1 10:55 .clang-format -rw-rw-rw- 1 macports admin 1377 Nov 1 10:55 .clang-tidy drwxrwxrwx 7 macports admin 224 Nov 1 10:55 Auxiliary/ -rw-rw-rw- 1 macports admin 10073 Nov 1 10:55 CMakeCPack.cmake -rw-rw-rw- 1 macports admin 12255 Nov 1 10:55 CMakeCPackOptions.cmake.in -rw-rw-rw- 1 macports admin 153 Nov 1 10:55 CMakeGraphVizOptions.cmake -rw-rw-rw- 1 macports admin 34829 Nov 1 10:55 CMakeLists.txt -rw-rw-rw- 1 macports admin 4481 Nov 1 10:55 CMakeLogo.gif -rw-rw-rw- 1 macports admin 3118 Nov 1 10:55 CONTRIBUTING.rst -rw-rw-rw- 1 macports admin 566 Nov 1 10:55 CTestConfig.cmake -rw-rw-rw- 1 macports admin 6915 Nov 1 10:55 CTestCustom.cmake.in -rw-rw-rw- 1 macports admin 4802 Nov 1 10:55 CompileFlags.cmake -rw-rw-rw- 1 macports admin 5440 Nov 1 10:55 Copyright.txt -rw-rw-rw- 1 macports admin 374 Nov 1 10:55 DartConfig.cmake drwxrwxrwx 22 macports admin 704 Nov 1 10:55 Help/ drwxrwxrwx 5 macports admin 160 Nov 1 10:55 Licenses/ drwxrwxrwx 441 macports admin 14112 Nov 1 10:55 Modules/ drwxrwxrwx 5 macports admin 160 Nov 1 10:55 Packaging/ -rw-rw-rw- 1 macports admin 3951 Nov 1 10:55 README.rst drwxrwxrwx 765 macports admin 24480 Nov 1 10:55 Source/ drwxrwxrwx 13 macports admin 416 Nov 1 10:55 Templates/ drwxrwxrwx 307 macports admin 9824 Nov 1 10:55 Tests/ drwxrwxrwx 29 macports admin 928 Nov 1 10:55 Utilities/ -rwxrwxrwx 1 macports admin 64762 Nov 1 10:55 bootstrap* -rw-rw-rw- 1 macports admin 789 Nov 1 10:55 cmake_uninstall.cmake.in -rwxrwxrwx 1 macports admin 99 Nov 1 10:55 configure* -rw-rw-rw- 1 macports admin 28046 Nov 1 10:55 doxygen.config }}} WORKSRCDIR is set to the short version, which is empty ... here's a prior one that's working: {{{ $ pwd /opt/local/var/macports/build/_opt_sources_MacPorts_ports_github_macports_devel_cmake/cmake/work $ ll total 8 drwxrwxrwx 2 macports admin 64 Dec 7 14:11 .home/ -rw-rw-rw- 1 macports admin 219 Dec 7 14:11 .macports.cmake.state drwxrwxrwx 2 macports admin 64 Dec 7 14:11 .tmp/ lrwxrwxrwx 1 macports admin 54 Dec 7 14:11 cmake-3.24.3@ -> cmake-v3.24.3-c974557598645360fbabac71352b083117e3cc17 drwxrwxrwx 31 macports admin 992 Dec 7 14:11 cmake-v3.24.3-c974557598645360fbabac71352b083117e3cc17/ }}} So looks like the prior symlink was replaced by a directory ... oops! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 20:06:04 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 20:06:04 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.aa2c67a3fb8d8f9fe6db5b8897d57cff@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): Thank you! I'll rebuilt with corrected settings. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 20:11:14 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 20:11:14 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.59ea5e5b10964f6b3cf31ecb50d7dbed@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+----------------------- Reporter: snowflake | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+----------------------- Comment (by michaelld): oh wow ... the [https://github.com/macports/macports- base/commit/7921b2e05e9a4c9cda6efedee496affb305dcc07 commit being reverted (7921b2e05)] is from December 29, 2017 at 10:54:09 AM EST ... can't say I'm happy about that reversion given that it will break ports like cmake. The [https://github.com/macports/macports- base/commit/ffdb7d9ee9e59e9d69a2f29ac08dfd5090f84759 commit message for the reversion] says `This change silently broke an unknown number of ports due to different behaviour of symlinks vs directories. See e.g. slime, scm_breeze. The reversion may also break things, but at least they'll give an error rather than silently installing nothing but a broken link.` So ... the original commit broke stuff, and reverting it also breaks stuff ... which is worse? hmmm ... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 20:12:15 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 20:12:15 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.ac45902abdeb95db548a1f61080e949c@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Changes (by michaelld): * cc: jmroot (added) * owner: michaelld => jmroot -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 20:15:09 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 20:15:09 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.13dedd2d5ac4d1f5c81a730d9213a247@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by michaelld): Luckily this not part of the current MP release, so there's time to fix it before the next release :) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:31:15 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:31:15 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.cc5fac052c25da43b2c34ae1139db038@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Comment (by ballapete): The GNU Emacs support demands to use their programme without configuration, i.e. "vanilla", if I understand this term correctly. Therefore it is launched with `-Q`. The additional argument `-nw` tells GNU Emacs not to launch with its own windows or frames. For comparison I did also uninstall/install a `port leaf` in XTerm and in Terminal. Obviously GNU Emacs only with its own X11 windows or without windows in XTerm is susceptible for signals from port's scan. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:32:46 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:32:46 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.69a47c8a9af3cec53f11b02ed1d9e74e@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port upgrade in GNU Emacs -Q and ticket #53404.png" added. Port upgrade in X client GNU Emacs 28.2 -Q on High Sierra -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:33:56 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:33:56 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.9a44136bf18f42577ce1a5dd81d90dc2@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port install in GNU Emacs -Q -nw in XTerm and ticket #53404.png" added. Port install in GNU Emacs 28.2 -Q in XTerm on High Sierra -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:34:38 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:34:38 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.8b85db28ec072a782d700a706f25e1fe@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port install in GNU Emacs -Q -nw in Terminal and ticket #53404.png" added. Port install in GNU Emacs 28.2 -Q in Apple Terminal on High Sierra -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:35:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:35:48 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.7d47ea82edd47d9d803ef8ecca982b94@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port install in Terminal and ticket #53404.png" added. Port install directly in Apple Terminal on High Sierra -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:36:24 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:36:24 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.a24ee43c6e26e533dae0e7f4d8f048e6@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port install in XTerm and ticket #53404.png" added. Port install directly in XTerm on High Sierra -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 21:37:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 21:37:54 -0000 Subject: [MacPorts] #53404: `port upgrade outdated` changes colours in terminal emulation In-Reply-To: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> References: <046.b7ad34c9df058bd8a5869e9712a5ae73@macports.org> Message-ID: <061.40e564c8d475ccc016d2d0451569753f@macports.org> #53404: `port upgrade outdated` changes colours in terminal emulation ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Changes (by ballapete): * Attachment "Port install in Emacs.app -Q in Terminal and ticket #53404.png" added. Port install in Emacs.app -Q and ticket #53404 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 22:42:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 22:42:54 -0000 Subject: [MacPorts] #55528: py27-cython @0.27.3 built on Mac OS X 10.5.8, Leopard, stops py27-cryptography, py27-pynacl, nghttp2 from building In-Reply-To: <046.6fdd4a765bd1d6b5716e04cf2280ae8f@macports.org> References: <046.6fdd4a765bd1d6b5716e04cf2280ae8f@macports.org> Message-ID: <061.bb9f324be1835ab69e3834760730fb8e@macports.org> #55528: py27-cython @0.27.3 built on Mac OS X 10.5.8, Leopard, stops py27-cryptography, py27-pynacl, nghttp2 from building -------------------------------------------------+------------------------- Reporter: ballapete | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.4.2 Resolution: | Keywords: leopard Port: py-cython, python26, python27, | python32 | -------------------------------------------------+------------------------- Comment (by ballapete): `Python 2.7` has gone, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 23:16:00 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 23:16:00 -0000 Subject: [MacPorts] #66416: Please update py310-wxpython-4.0 Message-ID: <043.f1a2496a1501be4a9be51b401ce9ca9a@macports.org> #66416: Please update py310-wxpython-4.0 --------------------+-------------------------------- Reporter: adsche | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py310-wxpython-4.0 --------------------+-------------------------------- Hi, in August, version 4.2 of wxPython (Phoenix) was released: https://github.com/wxWidgets/Phoenix/releases Please consider updating the port as the new version contains some critical fixes. (e.g., in the current port version, the wxplot module is just broken - you can try running .../site-packages/wx/lib/plot/examples/demo.py to see). Thank you! PS: Would it make sense to update the port name as well? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 23:20:29 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 23:20:29 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.51e6b6c540ab8ff6d0264126b1ac8b84@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by adsche): I get this as well (macOS Ventura 13.0.1, xcode 14.1, ARM64 (M2), python 3.10.9+lto+optimizations, py310-numpy @1.23.5_0+gfortran+openblas) Numpy does indeed not contain the 'missing'(?) random.pxd file: {{{ port contents py310-numpy | grep pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/__init__.cython-30.pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/__init__.pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/random/__init__.pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/random/_bounded_integers.pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/random/_common.pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/random/bit_generator.pxd /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/numpy/random/c_distributions.pxd }}} Anything I can do to help debug this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 23:27:25 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 23:27:25 -0000 Subject: [MacPorts] #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found In-Reply-To: <049.521d65af872f54499686954a79c7cec2@macports.org> References: <049.521d65af872f54499686954a79c7cec2@macports.org> Message-ID: <064.df5eeeb8930b98c367e0327515a227b6@macports.org> #66252: py310-scipy @1.9.3: _biasedurn.pyx:13:4: 'numpy/random.pxd' not found ---------------------------+----------------------- Reporter: renzresearch | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-scipy | ---------------------------+----------------------- Comment (by adsche): Ok, wow, indeed, it picked up the wrong cython. `sudo port select cython cython310` fixed it for me (it was cython39 before which I did not install nor select manually). However, does the port maybe have to be fixed to use the correct one? Otherwise it would require manual intervention to have py39-scipy and py310-scipy installed at the same time, correct? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 7 23:54:26 2022 From: noreply at macports.org (MacPorts) Date: Wed, 07 Dec 2022 23:54:26 -0000 Subject: [MacPorts] #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 In-Reply-To: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> References: <046.26215b8742342ed53a25e79ff9750ae6@macports.org> Message-ID: <061.6b5d78a06e25897d887dec382fc3472b@macports.org> #61333: mpstats @0.1.8_6 cannot submit reports on PPC Tiger and Leopard, Mac OS X 10.4.11 resp. 10.5.8 ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.3 Resolution: | Keywords: tiger, leopard Port: mpstats | ------------------------+---------------------------- Comment (by ballapete): On `PPC Tiger, Mac OS X 10.4.11` success as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 00:06:22 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 00:06:22 -0000 Subject: [MacPorts] #66416: Please update py310-wxpython-4.0 In-Reply-To: <043.f1a2496a1501be4a9be51b401ce9ca9a@macports.org> References: <043.f1a2496a1501be4a9be51b401ce9ca9a@macports.org> Message-ID: <058.e7c95e82337e00cf163cf6a960217898@macports.org> #66416: Please update py310-wxpython-4.0 ------------------------------+-------------------- Reporter: adsche | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-wxpython-4.0 | ------------------------------+-------------------- Changes (by adsche): * port: py310-wxpython-4.0 => py-wxpython-4.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 02:41:04 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 02:41:04 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.481a117e8476dedb295193a4aee2ce4f@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by jmroot): For most ports, setting worksrcdir correctly is all that's needed to avoid problems. If there are ports where it's difficult to work out the value of worksrcdir a priori, I'd be open to having an option that can be set to enable the behaviour (though I think renaming rather than symlinking would still be safer in that case.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 02:43:31 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 02:43:31 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.169a9ad42ca67b54e75040f9fde596af@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Changes (by jmroot): * cc: jmroot (removed) * cc: michaelld (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 02:54:12 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 02:54:12 -0000 Subject: [MacPorts] #66413: cppcheck @2.9.3 CXXFLAGS reinplace didn't change anything (was: cppcheck @2.9.3 seems to have in Portfile one 'reinplace' too many) In-Reply-To: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> References: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> Message-ID: <061.22b1f77d86126a542409e1e40560bada@macports.org> #66413: cppcheck @2.9.3 CXXFLAGS reinplace didn't change anything ------------------------+---------------------------- Reporter: ballapete | Owner: kurthindenburg Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: cppcheck | ------------------------+---------------------------- Changes (by jmroot): * keywords: leopard ppc => * owner: (none) => kurthindenburg * status: new => assigned * cc: khindenburg@? (removed) Comment: I'd suspect the Makefile has changed since earlier versions so the search pattern no longer matches. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 02:59:35 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 02:59:35 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.148dad4e350e24bfbbe330f37a8ef408@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" -------------------------+------------------------------------------------- Reporter: | Owner: (none) programmingkidx | Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: libffi snow leopard patch can't Port: libffi | find -------------------------+------------------------------------------------- Comment (by jmroot): If you don't have `/usr/bin/patch`, then you have an incomplete OS installation. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 07:29:21 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 07:29:21 -0000 Subject: [MacPorts] #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) In-Reply-To: <048.4862f7c021d74aba503c089a8538c3db@macports.org> References: <048.4862f7c021d74aba503c089a8538c3db@macports.org> Message-ID: <063.efc5308b72c09a3dbbf65e3532adb7b8@macports.org> #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) --------------------------+---------------------- Reporter: c-kloukinas | Owner: easye Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: slime | --------------------------+---------------------- Comment (by easye): My preference for "fixing" this would be to update the pointer in the github source checkout to something more contemporary than slime-2.20. Would @c-kloukinas be able to use a newer version of SLIME, or is there some reason to stay with the old one? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 11:34:59 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 11:34:59 -0000 Subject: =?utf-8?q?=5BMacPorts=5D_=2366417=3A_python310_=403=2E10=2E9_see?= =?utf-8?q?ms_to_install_static_libraries=2C_but_they_are_faulty_?= =?utf-8?q?=E2=80=93_why_at_all=3F?= Message-ID: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> #66417: python310 @3.10.9 seems to install static libraries, but they are faulty ? why at all? -----------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger, monterey | Port: python310 -----------------------------+----------------------- `configure` has the option `--without-static-libpython`. Leaving it out results in: {{{ pete 228 /\ port contents python310 | ggrep libpython /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/libpython3.10.dylib /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.a /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.dylib pete 229 /\ ls -l `port contents python310 | ggrep libpython` lrwxr-xr-x 1 root wheel 9 8 Dez 09:29 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/libpython3.10.dylib -> ../Python lrwxr-xr-x 1 root wheel 15 8 Dez 09:29 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.a -> ../../../Python lrwxr-xr-x 1 root wheel 15 8 Dez 09:29 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.dylib -> ../../../Python pete 230 /\ ls -Lil `port contents python310 | ggrep libpython` 96769351 -rwxr-xr-x 1 root wheel 3577140 8 Dez 09:15 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/libpython3.10.dylib 96769351 -rwxr-xr-x 1 root wheel 3577140 8 Dez 09:15 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.a 96769351 -rwxr-xr-x 1 root wheel 3577140 8 Dez 09:15 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.dylib pete 231 /\ find /opt/local -type f -inum 96769351 -ls 96769351 6992 -rwxr-xr-x 1 root wheel 3577140 8 Dez 09:15: /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python pete 232 /\ file /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python: Mach-O dynamically linked shared library ppc }}} The SDKs do not contain many, /opt/local/lib has 266 of them. And in other places many, many more. Are they necessary? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 11:38:25 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 11:38:25 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366417=3A_python310_=403=2E10?= =?utf-8?q?=2E9_seems_to_install_static_libraries=2C_but_they_are?= =?utf-8?q?_faulty_=E2=80=93_why_at_all=3F?= In-Reply-To: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> References: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> Message-ID: <061.bbf16b4b57d8f1f1c95e9fea7c7116be@macports.org> #66417: python310 @3.10.9 seems to install static libraries, but they are faulty ? why at all? ------------------------+----------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger, monterey Port: python310 | ------------------------+----------------------------- Comment (by ballapete): The originally built static library is different: {{{ root 281 /\ gfind /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.9 \( -name "libpython*" -o -name "*.a" \) -ls 96783484 68 -rwxr-xr-x 1 macports admin 65727 Dez 6 19:31 /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.9/Tools/gdb/libpython.py 96792229 15264 -rw-r--r-- 1 macports admin 15626416 Dez 8 10:14 /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.9/libpython3.10.a root 282 /\ file /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.9/libpython3.10.a /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3.10.9/libpython3.10.a: current ar archive }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 11:45:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 11:45:27 -0000 Subject: [MacPorts] #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile Message-ID: <046.555f7ae3c563228c6413868d979d4b78@macports.org> #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile -----------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: cppcheck -----------------------+---------------------- {{{ Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_cppcheck/cppcheck/work/cppcheck-2.9.3" && /usr/bin/make -j1 -w all man CXX="/opt/local/bin/g++-mp-7 -arch ppc" DB2MAN=/opt/local/share/xsl/docbook-xsl-nons/manpages/docbook.xsl FILESDIR=/opt/local/share/cppcheck HAVE_RULES=yes MATCHCOMPILER=yes PREFIX=/opt/local PYTHON_INTERPRETER=/opt/local/bin/python3.10 DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_cppcheck/cppcheck/work/cppcheck-2.9.3" && /usr/bin/make -j1 -w all man CXX="/opt/local/bin/g++-mp-7 -arch ppc" DB2MAN=/opt/local/share/xsl/docbook-xsl-nons/manpages/docbook.xsl FILESDIR=/opt/local/share/cppcheck HAVE_RULES=yes MATCHCOMPILER=yes PREFIX=/opt/local PYTHON_INTERPRETER=/opt/local/bin/python3.10 make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_cppcheck/cppcheck/work/cppcheck-2.9.3' Makefile:106: Extraneous text after `else' directive Makefile:108: Extraneous text after `else' directive Makefile:108: *** only one `else' per conditional. Stop. make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_cppcheck/cppcheck/work/cppcheck-2.9.3' }}} Btter use `gmake`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 11:46:15 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 11:46:15 -0000 Subject: [MacPorts] #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile In-Reply-To: <046.555f7ae3c563228c6413868d979d4b78@macports.org> References: <046.555f7ae3c563228c6413868d979d4b78@macports.org> Message-ID: <061.7b094c27bf1ce520f139fbb91b4ca0e8@macports.org> #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: cppcheck | ------------------------+----------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Tiger, Mac OS X 10.4.11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 13:16:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 13:16:09 -0000 Subject: [MacPorts] #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile In-Reply-To: <046.555f7ae3c563228c6413868d979d4b78@macports.org> References: <046.555f7ae3c563228c6413868d979d4b78@macports.org> Message-ID: <061.60ca1a94d95fe9bb3b475d00e4aafb7d@macports.org> #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: cppcheck | ------------------------+----------------------- Comment (by ballapete): Yes, `gmake` is necessary on `Tiger`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 13:17:39 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 13:17:39 -0000 Subject: [MacPorts] #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> References: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> Message-ID: <061.20a1dd2b85f4768f45e7bb4996a62095@macports.org> #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: libtool | ------------------------+-------------------- Comment (by ballapete): Here is a patch that fixes `expr on Tiger/bash 2`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 13:20:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 13:20:27 -0000 Subject: [MacPorts] #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 In-Reply-To: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> References: <046.a59f0537f23ebac3a42489c2689cc0da@macports.org> Message-ID: <061.41531b6af0e181f088d7829183273e74@macports.org> #63736: libtool @2.4.6_13 complains about incorrectly used utility xattrs of PPC Tiger, Mac OS X 10.4.11 ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: libtool | ------------------------+-------------------- Changes (by ballapete): * Attachment "build-aux_git-version-gen_Tiger.patch" added. Patch to make expr in GNU bash, version 2.05b.0(1)-release of Tiger, Mac OS X 10.4.11, work here -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 14:02:41 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 14:02:41 -0000 Subject: [MacPorts] #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) Message-ID: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) -----------------------+------------------------ Reporter: snowflake | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: py-pypdf2 -----------------------+------------------------ Note: I am using the latest version of `port`version 2.8.99 [ffdb7d9ee9e59e9d69a2f29ac08dfd5090f84759/macports-base] This ticket is very similar to #66415 `cmake @3.24.3 - patch does not work - attempts to patch an empty directory` {{{ DEBUG: euid/egid changed to: 502/501 DEBUG: Executing proc-post-org.macports.extract-extract-0 DEBUG: Executing proc-post-org.macports.extract-extract-1 Error: Error: Error: github PortGroup: Error: ${worksrcpath} does not exist after extracting distfiles. This might indicate that the author or project is different than set in the Portfile due to a rename at GitHub. Please examine the extracted directory in /opt/local/var/macports/build/_Users_davidevans_macports_sources_github .com_macports_macports-ports_python_py-pypdf2/py310-pypdf2/work and try to correct the Portfile by either changing the author or project or adding the worksrcdir option with the correct directory name. Error: Error: Failed to extract py310-pypdf2: Unexpected github tarball extract. DEBUG: Error code: NONE -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 14:54:56 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 14:54:56 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.03fb249128f1fabd7da0615c543a3113@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by catap): Peter, I'd like to ask your help and test https://github.com/macports /macports-ports/pull/16922 on your hardware. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:00:54 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:00:54 -0000 Subject: [MacPorts] #66420: Building on Ventura fails Message-ID: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> #66420: Building on Ventura fails ---------------------+-------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ffmpeg ---------------------+-------------------- Building ffmpeg on Ventura (M1 chip) fails, due to problem with building soxr: ''$sudo port -N install ffmpeg +nonfree''\\ ''Computing dependencies for ffmpeg''\\ ''Dependencies to be installed: soxr speex speexdsp svt-av1 yasm x264 zig zvbi\\ ''Fetching archive for soxr''\\ ''Attempting to fetch soxr-0.1.3 .darwin 22.arm64.tbz2 from https: //packages.macports.org/soxr''\\ ''Attempting to fetch soxr-0.1.3_O. darwin 22.arm64.tbz2 from https://cph.dk.packages.macports.org/soxr''\\ ''Attempting to fetch soxr-0.1.3_0.darwin_22.arm64.tbz2 from https://fra.de.packages.macports.org/soxr''\\ ''Building soxr''\\ ''Error. Failed to build soxr: command execution failed''\\ There is a bug report on soxr for a similar error (I believe) stating that it will build with the universal flag. Hoping you can update the ffmpeg port to use this ? or perhaps it is more complicated than that ? I'm not at home here, just guessing ? Thanks in advance and thanks for all the past work done in having this port available! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:15:01 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:15:01 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails (was: Building on Ventura fails) In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.cdc60ab43e80a244492f2cb7d05f49bc@macports.org> #66420: soxr @0.1.3 Building on Ventura fails ----------------------+-------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: soxr | ----------------------+-------------------- Changes (by jmroot): * port: ffmpeg => soxr Comment: Please attach the log. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:18:33 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:18:33 -0000 Subject: [MacPorts] #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) In-Reply-To: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> References: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> Message-ID: <061.b3f28440b0b750c331c0c59472256343@macports.org> #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) ------------------------+------------------------ Reporter: snowflake | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: py-pypdf2 | ------------------------+------------------------ Comment (by jmroot): The message is correct; the project has moved from https://github.com/mstamy2/PyPDF2 to https://github.com/py-pdf/PyPDF2. I believe `github.tarball_from archive` helps to avoid this kind of problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:24:44 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:24:44 -0000 Subject: [MacPorts] #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) In-Reply-To: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> References: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> Message-ID: <061.b5f9b915ceac93a709a3c8d42ac27dc6@macports.org> #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) ------------------------+------------------------ Reporter: snowflake | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: py-pypdf2 | ------------------------+------------------------ Comment (by jmroot): Or, GitHub autogenerated tarball troubles could be avoided entirely by downloading from PyPI. https://pypi.org/project/PyPDF2/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:25:02 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:25:02 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.79aa4ea9226a83b8d0f29f48820f6b09@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): Replying to [comment:62 catap]: Building `icu-devel` and `test`ing it? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:32:20 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:32:20 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.a845cae97bc6e69cf5b9ee0d8dbf135f@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by catap): Yep. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 15:40:16 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 15:40:16 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.ddada92fe89d1b4aabbc69a41a84fd30@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): Up-to-date? `-rw-r--r-- 1 root x11 10277 21 Nov 06:39 /opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/devel /icu-devel/Portfile` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 16:32:20 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 16:32:20 -0000 Subject: [MacPorts] #66421: pinentry-mac 0.9.4.1 building failed on OSX Ventura 13.0.1 Message-ID: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> #66421: pinentry-mac 0.9.4.1 building failed on OSX Ventura 13.0.1 ----------------------------+-------------------------- Reporter: LudgerBreil209 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: pinentry-mac ----------------------------+-------------------------- building failed on OSX 13.0.1 with "command execution failed" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 16:35:16 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 16:35:16 -0000 Subject: [MacPorts] #66421: pinentry-mac 0.9.4.1 building failed on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.fa18873215b227dfa6f615d86215a4dc@macports.org> #66421: pinentry-mac 0.9.4.1 building failed on OSX Ventura 13.0.1 -----------------------------+-------------------- Reporter: LudgerBreil209 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+-------------------- Changes (by LudgerBreil209): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 16:41:19 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 16:41:19 -0000 Subject: [MacPorts] #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile In-Reply-To: <046.555f7ae3c563228c6413868d979d4b78@macports.org> References: <046.555f7ae3c563228c6413868d979d4b78@macports.org> Message-ID: <061.54e0508709ded6c4c628ddb5f6f819c9@macports.org> #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: cppcheck | ------------------------+----------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/16923 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 16:41:52 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 16:41:52 -0000 Subject: [MacPorts] #66413: cppcheck @2.9.3 CXXFLAGS reinplace didn't change anything In-Reply-To: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> References: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> Message-ID: <061.7034fb357a0806f7953cc68aa4033ca5@macports.org> #66413: cppcheck @2.9.3 CXXFLAGS reinplace didn't change anything ------------------------+---------------------------- Reporter: ballapete | Owner: kurthindenburg Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: cppcheck | ------------------------+---------------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/16923 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 17:06:36 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 17:06:36 -0000 Subject: [MacPorts] #61486: fluxbox @1.3.7_1 does not compile on macOS Big Sur, Version 11.0.1, because "src/FbTk/FbTime.cc:64:10: error: redefinition of '_mono'" In-Reply-To: <046.d49667ac0c5cf48d9e28f0c588bc82a7@macports.org> References: <046.d49667ac0c5cf48d9e28f0c588bc82a7@macports.org> Message-ID: <061.d112cf97d203fc6605bf6de2aeb4c26d@macports.org> #61486: fluxbox @1.3.7_1 does not compile on macOS Big Sur, Version 11.0.1, because "src/FbTk/FbTime.cc:64:10: error: redefinition of '_mono'" ------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: bigsur Port: fluxbox | ------------------------+-------------------- Comment (by ballapete): On macOS Monterey, Version 12.6, `fluxbox` builds. Since the time of `Big Sur` is gone for me, the ticket can be closed IMO. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 17:14:34 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 17:14:34 -0000 Subject: [MacPorts] #61843: /opt/local/var/macports/software/gdk-pixbuf2/gdk-pixbuf2-2.42.0_0+x11.darwin_15.x86_64.tbz2: BC.Gif.Exploit.Agent-1425366.Agent FOUND In-Reply-To: <043.ab7ce435da7c6b3107d58152c6ae3171@macports.org> References: <043.ab7ce435da7c6b3107d58152c6ae3171@macports.org> Message-ID: <058.79f5ec3250de1eb2a615e7a8ba2a6c1a@macports.org> #61843: /opt/local/var/macports/software/gdk-pixbuf2/gdk- pixbuf2-2.42.0_0+x11.darwin_15.x86_64.tbz2: BC.Gif.Exploit.Agent-1425366.Agent FOUND --------------------------+---------------------- Reporter: dbl001 | Owner: mascguy Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: Port: gdk-pixbuf2 | --------------------------+---------------------- Comment (by ballapete): Some weeks ago I tried to report the problem to the ClamAV people ? no answer yet. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 17:27:10 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 17:27:10 -0000 Subject: [MacPorts] #63829: mpstats submit failed cause DST Root CA X3 Expiration In-Reply-To: <050.88f49fcf55d888d52949b0c696d778aa@macports.org> References: <050.88f49fcf55d888d52949b0c696d778aa@macports.org> Message-ID: <065.8b263184017c7e865845a3629cf56822@macports.org> #63829: mpstats submit failed cause DST Root CA X3 Expiration ----------------------------+-------------------- Reporter: laggardkernel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mpstats | ----------------------------+-------------------- Comment (by ballapete): I did rebuild MacPorts 2.8.0 from source, configured with the additional arguments `--with-curlprefix=/opt/local/lib CURL_CONFIG=/opt/local/bin /curl-config` (without the latter `configure` does not seem to find the shell script) . And I also installed what was built. On `Tiger, Mac OS X 10.4.11, and Leopard, Mac OS X 10.5.8` it works now to `successfully submit` the list of installed `port`s. Discussed in #61333. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 17:33:22 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 17:33:22 -0000 Subject: [MacPorts] #66026: python2_select @0.0_4 offers python27-apple on macOS Monterey, Version 12.6 In-Reply-To: <046.78d60e91d3a14ff94beec2992066a6db@macports.org> References: <046.78d60e91d3a14ff94beec2992066a6db@macports.org> Message-ID: <061.8978d0cdaceca73b1188397b50b8eaf5@macports.org> #66026: python2_select @0.0_4 offers python27-apple on macOS Monterey, Version 12.6 -----------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: monterey Port: python2_select | -----------------------------+---------------------- Comment (by ballapete): After uninstalling `python2_select` I can see: {{{ python2 none none }}} Why? `Python 2` is dead since years. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 17:51:02 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 17:51:02 -0000 Subject: [MacPorts] #64815: py38-build @0.7.0 does not install on High Sierra, macOS 10.13.6, because: /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8: No module named install.__main__; 'install' is a package and cannot be directly executed In-Reply-To: <046.225e8821f3c0faeb6905099c58d61237@macports.org> References: <046.225e8821f3c0faeb6905099c58d61237@macports.org> Message-ID: <061.db3f022a1c8ece3627321d24ed9fa4fe@macports.org> #64815: py38-build @0.7.0 does not install on High Sierra, macOS 10.13.6, because: /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8: No module named install.__main__; 'install' is a package and cannot be directly executed -------------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: highsierra Port: py38-build | -------------------------+------------------------ Comment (by ballapete): Meanwhile `Python 3.10` is installed, so this ticket can be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 17:58:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 17:58:13 -0000 Subject: [MacPorts] #64503: chromaprint @1.5.1 does not build again on macOS High Sierra, Version 10.13.6 In-Reply-To: <046.65cf198a970d0e70fa750a11c22825d7@macports.org> References: <046.65cf198a970d0e70fa750a11c22825d7@macports.org> Message-ID: <061.53d622ee0f82034fbb6ade7936ebc7c6@macports.org> #64503: chromaprint @1.5.1 does not build again on macOS High Sierra, Version 10.13.6 --------------------------+---------------------------- Reporter: ballapete | Owner: kurthindenburg Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: highsierra Port: chromaprint | --------------------------+---------------------------- Comment (by ballapete): It just built! with `AppleClang 10.0.0.10001044`. (But I forgot what I wanted to do with it? Something with CDpedia?) The ticket can be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:01:53 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 18:01:53 -0000 Subject: [MacPorts] #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) In-Reply-To: <048.4862f7c021d74aba503c089a8538c3db@macports.org> References: <048.4862f7c021d74aba503c089a8538c3db@macports.org> Message-ID: <063.f2c6bca6f9bf203544c71f2062408ebb@macports.org> #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) --------------------------+---------------------- Reporter: c-kloukinas | Owner: easye Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: slime | --------------------------+---------------------- Comment (by c-kloukinas): Sure, a new version of slime would be the best way forward. Best, Chris -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:04:04 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 18:04:04 -0000 Subject: [MacPorts] #56423: emacs-devel @20170918 as X client cannot be used with recent fontconfig @2.13.0_0 and non-C locale In-Reply-To: <046.608cde03ca94f9ccbdd339f6c7ff1b37@macports.org> References: <046.608cde03ca94f9ccbdd339f6c7ff1b37@macports.org> Message-ID: <061.b0e3fe81227541b45783f6241a90d63e@macports.org> #56423: emacs-devel @20170918 as X client cannot be used with recent fontconfig @2.13.0_0 and non-C locale --------------------------+------------------------ Reporter: ballapete | Owner: drkp Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.4.3 Resolution: | Keywords: highsierra Port: emacs-devel | --------------------------+------------------------ Comment (by ballapete): I think this ticket can be closed now. I then was working on a bug in GNU Emacs and needed to access updated sources. MacPorts offered the ability to perform this very easily, without having to perform a handful of steps more or less manually/automatically. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:12:14 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 18:12:14 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366417=3A_python310_=403=2E10?= =?utf-8?q?=2E9_seems_to_install_static_libraries=2C_but_they_are?= =?utf-8?q?_faulty_=E2=80=93_why_at_all=3F?= In-Reply-To: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> References: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> Message-ID: <061.74b82a13f60de784dc6e004266533b7d@macports.org> #66417: python310 @3.10.9 seems to install static libraries, but they are faulty ? why at all? ------------------------+----------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger, monterey Port: python310 | ------------------------+----------------------------- Comment (by ballapete): The same on `macOS High Sierra, Version 10.13.6`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 18:12:53 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 18:12:53 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366417=3A_python310_=403=2E10?= =?utf-8?q?=2E9_seems_to_install_static_libraries=2C_but_they_are?= =?utf-8?q?_faulty_=E2=80=93_why_at_all=3F?= In-Reply-To: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> References: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> Message-ID: <061.852a591ab80e3948482e0f127ae2350a@macports.org> #66417: python310 @3.10.9 seems to install static libraries, but they are faulty ? why at all? ------------------------+----------------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger, highsierra, monterey Port: python310 | ------------------------+----------------------------------------- Changes (by ballapete): * keywords: tiger, monterey => tiger, highsierra, monterey -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 20:00:05 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 20:00:05 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366417=3A_python310_=403=2E10?= =?utf-8?q?=2E9_seems_to_install_static_libraries=2C_but_they_are?= =?utf-8?q?_faulty_=E2=80=93_why_at_all=3F?= In-Reply-To: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> References: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> Message-ID: <061.71f838fabe4bd5818067ef8ee7020833@macports.org> #66417: python310 @3.10.9 seems to install static libraries, but they are faulty ? why at all? ------------------------+----------------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger, highsierra, monterey Port: python310 | ------------------------+----------------------------------------- Comment (by ballapete): On intel Monterey it does not seem to make much of difference whether `Python 3.10` is `configured --without-static-libpython` or without this option, as default. This situation has {{{ 532365306 8 -rwxr-xr-x 1 root wheel 49400 7 Dez 03:06 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Resources/Python.app/Contents/MacOS/Python 532350588 0 lrwxr-xr-x 1 root wheel 9 7 Dez 03:06 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/libpython3.10.dylib -> ../Python 532353525 0 lrwxr-xr-x 1 root wheel 15 7 Dez 03:06 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.a -> ../../../Python 532353526 0 lrwxr-xr-x 1 root wheel 15 7 Dez 03:06 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.dylib -> ../../../Python 532350580 4104 -rwxr-xr-x 1 root wheel 4188688 7 Dez 03:05 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python 531241552 0 lrwxr-xr-x 1 root wheel 67 1 Dez 12:16 /opt/local/Library/Frameworks/Python.framework/Python -> /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python }}} and the other has 20,040 bytes less: {{{ 532349776 8 -rwxr-xr-x 1 root wheel 49400 8 Dez 20:40 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Resources/Python.app/Contents/MacOS/Python 532335049 0 lrwxr-xr-x 1 root wheel 9 8 Dez 20:40 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/libpython3.10.dylib -> ../Python 532337976 0 lrwxr-xr-x 1 root wheel 15 8 Dez 20:40 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.a -> ../../../Python 532337977 0 lrwxr-xr-x 1 root wheel 15 8 Dez 20:40 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/config-3.10-darwin/libpython3.10.dylib -> ../../../Python 532335041 4104 -rwxr-xr-x 1 root wheel 4168648 8 Dez 20:36 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python 531241552 0 lrwxr-xr-x 1 root wheel 67 1 Dez 12:16 /opt/local/Library/Frameworks/Python.framework/Python -> /opt/local/Library/Frameworks/Python.framework/Versions/3.10/Python }}} It's just strange (to me) what `Python 3.10` does. IMO the ticket can be closed as `invalid`. (`port test python310` is OK.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 20:02:32 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 20:02:32 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 Message-ID: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 ----------------------------+--------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gnuplot ----------------------------+--------------------- Trying to install gnuplot on an M2 macbook pro running Monterey 12.6.1. I've iterated a few times, and in the end, everything gets hung up on this: ---> Computing dependencies for llvm-3.7. Error: Cannot install llvm-3.7 for the arch 'x86_64' because Error: its dependency libedit cannot build for the required arch. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port llvm-3.7 failed Any advice on how to get llvm-3.7 installed as universal or for arm64 explicitly? As far as I can tell, everything else seems to be in place. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 20:28:18 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 20:28:18 -0000 Subject: [MacPorts] #65892: gtk3: windows displayed as all black, for x11 install In-Reply-To: <044.d0934e485f29d1e7ac8878bc9aa1f1a9@macports.org> References: <044.d0934e485f29d1e7ac8878bc9aa1f1a9@macports.org> Message-ID: <059.911abea48a1fd2f499aded68b98f760d@macports.org> #65892: gtk3: windows displayed as all black, for x11 install -------------------------+-------------------------- Reporter: asic512 | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: monterey x11 Port: gtk3 gnome | -------------------------+-------------------------- Comment (by asic512): I use GNU Emacs 28.2: no problem. I use Nautilus: black issue (even if I can see the list of files). I use Evince: black issue for the menus but the pdf is OK. So the problem seems to come from gtk. My Windows Manager is IceWM. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 20:40:39 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 20:40:39 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.16dc4287dd1be63cd6af237ff099067e@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Description changed by natelsonoptics: Old description: > Trying to install gnuplot on an M2 macbook pro running Monterey 12.6.1. > I've iterated a few times, and in the end, everything gets hung up on > this: > > ---> Computing dependencies for llvm-3.7. > Error: Cannot install llvm-3.7 for the arch 'x86_64' because > Error: its dependency libedit cannot build for the required arch. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port llvm-3.7 failed > > Any advice on how to get llvm-3.7 installed as universal or for arm64 > explicitly? As far as I can tell, everything else seems to be in place. New description: Trying to install gnuplot on an M2 macbook pro running Monterey 12.6.1. I've iterated a few times, and in the end, everything gets hung up on this: {{{---> Computing dependencies for llvm-3.7. Error: Cannot install llvm-3.7 for the arch 'x86_64' because Error: its dependency libedit cannot build for the required arch. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port llvm-3.7 failed}}} Any advice on how to get llvm-3.7 installed as universal or for arm64 explicitly? As far as I can tell, everything else seems to be in place. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 22:12:02 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 22:12:02 -0000 Subject: [MacPorts] #66208: hdf5 @1.12.2_0+cxx+gcc12+hl: Port hdf5 is still broken (cxx_stdlib mismatch) after rebuilding it more than 3 times. In-Reply-To: <046.92333f9107c01cb19bffe6bfcdd6b8af@macports.org> References: <046.92333f9107c01cb19bffe6bfcdd6b8af@macports.org> Message-ID: <061.a1fb4b82d79a060a24a6da43ea72291b@macports.org> #66208: hdf5 @1.12.2_0+cxx+gcc12+hl: Port hdf5 is still broken (cxx_stdlib mismatch) after rebuilding it more than 3 times. ------------------------+---------------------- Reporter: massonseb | Owner: eborisch Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: hdf5 | ------------------------+---------------------- Comment (by massonseb): Up to now, I was able to compile - hdf5 @1.12.2_1+cxx+hl+openmpi which used openmpi-default - netcdf @4.9.0_0+dap+netcdf4+openmpi which also used openmpi-default - netcdf-fortran @4.6.0_0+gcc12+openmpi which required openmpi-gcc12 instead of openmpi-default. I am wondering if mixing libraries compiled with openmpi-default and openmpi-gcc12 could create a problem as these 2 versions are not using the same C compiler... \\ I am also wondering why netcdf-fortran cannot be compiled with openmpi- default+gcc12 as it includes the same gfortran compiler than openmpi- gcc12. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 22:14:01 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 22:14:01 -0000 Subject: [MacPorts] #66208: hdf5 @1.12.2_0+cxx+gcc12+hl: Port hdf5 is still broken (cxx_stdlib mismatch) after rebuilding it more than 3 times. In-Reply-To: <046.92333f9107c01cb19bffe6bfcdd6b8af@macports.org> References: <046.92333f9107c01cb19bffe6bfcdd6b8af@macports.org> Message-ID: <061.70b431db3635693728a56ce04e3d959b@macports.org> #66208: hdf5 @1.12.2_0+cxx+gcc12+hl: Port hdf5 is still broken (cxx_stdlib mismatch) after rebuilding it more than 3 times. ------------------------+---------------------- Reporter: massonseb | Owner: eborisch Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: hdf5 | ------------------------+---------------------- Comment (by massonseb): Replying to [comment:9 cjones051073]: > Setting both ldflags and cxxflags should be handled via > > https://github.com/macports/macports- ports/blob/master/_resources/port1.0/group/compilers-1.0.tcl#L363 > > Please make sure your builds are using the above. yes I have the same line L363 in my file `/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compilers-1.0.tcl` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 23:22:47 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 23:22:47 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.795e840dc1f238cc97ced62e49b6b252@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: octave | ------------------------+--------------------------------- Comment (by gjolleyrogers): +1 also need some hand holding -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 8 23:34:10 2022 From: noreply at macports.org (MacPorts) Date: Thu, 08 Dec 2022 23:34:10 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.781c2914cfbd542534e1c5343356d8f1@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Comment (by kencu): llvm-3.7 will most likely never be installable for arm64. The trick here is to figure out why it is being called in, and stop that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 00:34:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 00:34:18 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 (was: pinentry-mac 0.9.4.1 building failed on OSX Ventura 13.0.1) In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.b75b2ff7af50b8fef21e6a873dd9a0c3@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => Ionic -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 00:35:41 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 00:35:41 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.a2f033755c416e1f7ecba0498802645a@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Comment (by jmroot): Trace mode is known to break things sometimes (which is one of the reasons why it's not on by default), and also tends to be broken by new OS versions. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 00:40:03 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 00:40:03 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.d831e269c4297227b3d60636b9663d12@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Old description: > Trying to install gnuplot on an M2 macbook pro running Monterey 12.6.1. > I've iterated a few times, and in the end, everything gets hung up on > this: > > {{{---> Computing dependencies for llvm-3.7. > Error: Cannot install llvm-3.7 for the arch 'x86_64' because > Error: its dependency libedit cannot build for the required arch. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port llvm-3.7 failed}}} > > Any advice on how to get llvm-3.7 installed as universal or for arm64 > explicitly? As far as I can tell, everything else seems to be in place. New description: Trying to install gnuplot on an M2 macbook pro running Monterey 12.6.1. I've iterated a few times, and in the end, everything gets hung up on this: {{{ ---> Computing dependencies for llvm-3.7. Error: Cannot install llvm-3.7 for the arch 'x86_64' because Error: its dependency libedit cannot build for the required arch. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port llvm-3.7 failed }}} Any advice on how to get llvm-3.7 installed as universal or for arm64 explicitly? As far as I can tell, everything else seems to be in place. -- Comment (by jmroot): There's very little to go on here, but without further information (like a log or the output of `port -v installed`), my guess would be that you migrated from an x86_64 machine and need to follow wiki:Migration. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 00:42:26 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 00:42:26 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366417=3A_python310_=403=2E10?= =?utf-8?q?=2E9_seems_to_install_static_libraries=2C_but_they_are?= =?utf-8?q?_faulty_=E2=80=93_why_at_all=3F?= In-Reply-To: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> References: <046.2532b222ea3b521b841bbcde2d761a80@macports.org> Message-ID: <061.ee91981c663571988a46032e7f32a27b@macports.org> #66417: python310 @3.10.9 seems to install static libraries, but they are faulty ? why at all? ------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: wontfix | Keywords: upstream Port: python310 | ------------------------+---------------------- Changes (by jmroot): * keywords: tiger, highsierra, monterey => upstream * status: new => closed * resolution: => wontfix Comment: I certainly didn't change this in the port, so questions and concerns about it are probably best taken upstream. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 01:29:58 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 01:29:58 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.d7d9708051c75cf6cffc50992095b16d@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by catap): Peter, may I ask you to replace patch `patch-balign-to-align.diff` to https://raw.githubusercontent.com/macports/macports- ports/dfa7bc0d278e0a26ad3fbcce5055406d700b3850/devel/icu-devel/files /patch-balign-to-align.diff ? Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 01:46:39 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 01:46:39 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.24037cab511c43b5ee16b8adc5c6adaa@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Comment (by reneeotten): the issue appears to be {{{122 :debug:archivefetch Fetching archive failed: The requested URL returned error: 404}}}. I doubt that has anything to do with the extract phase or trace-mode. There is however a problem with trace-mode, which is ticket [ticket:66358]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 02:24:45 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 02:24:45 -0000 Subject: [MacPorts] #66423: gstreamer1-gst-plugins-good +qt: build failure on macOS 13 Message-ID: <049.770e1400241fd75536cfc1bb8bf2ca29@macports.org> #66423: gstreamer1-gst-plugins-good +qt: build failure on macOS 13 --------------------------+----------------------------------------- Reporter: ShadSterling | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: gstreamer1-gst-plugins-good --------------------------+----------------------------------------- Build failed while reinstalling all ports after upgrading to Ventura The problem seems to be that macro `g_once_init_enter` is receiving a volatile parameter {{{ :info:build gstqsgtexture.cc:42:7: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') :info:build if (g_once_init_enter (&_debug)) { :info:build ^~~~~~~~~~~~~~~~~~~~~~~~~~~ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 02:24:58 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 02:24:58 -0000 Subject: [MacPorts] #66423: gstreamer1-gst-plugins-good +qt: build failure on macOS 13 In-Reply-To: <049.770e1400241fd75536cfc1bb8bf2ca29@macports.org> References: <049.770e1400241fd75536cfc1bb8bf2ca29@macports.org> Message-ID: <064.caaad29b8591c1b15bee140339905a11@macports.org> #66423: gstreamer1-gst-plugins-good +qt: build failure on macOS 13 ------------------------------------------+--------------------- Reporter: ShadSterling | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: gstreamer1-gst-plugins-good | ------------------------------------------+--------------------- Changes (by ShadSterling): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:32:54 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:32:54 -0000 Subject: [MacPorts] #58124: kerberos5 fails to build because asn1_mac.h was removed from libressl-devel In-Reply-To: <046.d55498afec4e757c8675bc9882857a3c@macports.org> References: <046.d55498afec4e757c8675bc9882857a3c@macports.org> Message-ID: <061.0ae408f520956b5b66c2cb3f9bfc8851@macports.org> #58124: kerberos5 fails to build because asn1_mac.h was removed from libressl-devel ------------------------+------------------------ Reporter: hakoyamah | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: kerberos5 | ------------------------+------------------------ Comment (by jerryyhom): I don't know if the above patch solved the issue, but the overall issue is now moot. This ticket may be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:40:54 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:40:54 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? Message-ID: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? ----------------------+----------------------------- Reporter: artkiver | Owner: (none) Type: request | Status: new Priority: Low | Milestone: MacPorts Future Component: ports | Version: Keywords: | Port: ----------------------+----------------------------- Hi there! So I went to install FFmpeg and balked at the number of dependencies it wants to install. e.g. {{{ % port -v rdeps ffmpeg-upstream }}} (then copy and paste that output into a file and run wc:) {{{ % wc 344 344 10972 }}} Or if running: {{{ % port -v install ---> Computing dependencies for ffmpeg............................................................................................................................................................... The following dependencies will be installed: }}} (omitting 158 ports listed) {{{ Continue? [Y/n]: }}} Some of these, seem, *excessive* to understate it. kerberos5? rsync? So, I decided to instead: {{{ % git clone https://git.ffmpeg.org/ffmpeg.git % cd ffmpeg % ./configure % make }}} Which seemed to function with 0 issues and produce a functional FFmpeg binary. Taking this one step further, I decided to create my own Portfile, and see if this was much different, and no surprise: it wasn't. Albeit, due to use of xz, the rdeps are still 8, but I am guessing even those could be whittled down if using a tar.gz instead of a .bz2? {{{ % port -v rdeps The following ports are dependencies of ffmpeg @5.1.2_0: bin:xz:xz port:gettext port:diffutils-for-muniversal port:libiconv port:gperf port:libtextstyle port:ncurses port:gettext-runtime port:gettext-tools-libs }}} Now, I am guessing probably a lot of things in the existing Portfile are maybe useful for older builds of OS X than Ventura? Maybe there is some default variant stuff that is bringing along a lot of unnecessary cruft? Obviously, there's also the +nonfree variant which focuses on things which shouldn't be redistributed, but even without that the default dependencies seem to be an awful lot. Is there a way to turn that off some of this extra cruft and have a more minimal installation? I mean, well, obviously the test Portfile I created is one possible way; but I mean more generally? Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:41:48 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:41:48 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.6cb7dd63a970c653624b44e1164d6dcd@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? -----------------------+----------------------------- Reporter: artkiver | Owner: (none) Type: request | Status: new Priority: Low | Milestone: MacPorts Future Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+----------------------------- Changes (by artkiver): * Attachment "Portfile.moreminimal" added. A more minimal Portfile which seems to function A-OK on macOS Ventura, with far fewer dependencies. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:42:14 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:42:14 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.0c68ffaefb7931c22d7a5f69c2630150@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? -----------------------+----------------------------- Reporter: artkiver | Owner: (none) Type: request | Status: new Priority: Low | Milestone: MacPorts Future Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+----------------------------- Changes (by artkiver): * Attachment "ffmpeg_rdeps" added. rdeps for existing FFmpeg which seem excessive -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:42:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:42:34 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.fee43177156d14327c7dd092888327b9@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: octave | ------------------------+--------------------------------- Comment (by wcvinyard): FWIW -- while we're waiting for all the packages to mature in the new apple chip environment. . . Like Ken, {sudo port install octave -docs} installs without error. The gui "Documentation" tab does indeed have documentation. You can also use the online documentation for 7.3.0 at: https://docs.octave.org/v7.3.0/index.html -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:42:43 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:42:43 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.51a954b0b6681c187e8839f76193a201@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? -----------------------+----------------------------- Reporter: artkiver | Owner: (none) Type: request | Status: new Priority: Low | Milestone: MacPorts Future Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+----------------------------- Changes (by artkiver): * Attachment "ffmpeg_dependencies" added. FFmpeg dependencies as encountered on my system when running port -v install ffmpeg -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 03:50:54 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 03:50:54 -0000 Subject: [MacPorts] #60102: kerberos5 @1.18 fails to build with libressl-devel 2.9.2. In-Reply-To: <046.6d01d04b9cf499820f45887295bbe0c9@macports.org> References: <046.6d01d04b9cf499820f45887295bbe0c9@macports.org> Message-ID: <061.80e122275c1b8aa0c3e88c2b18b57d3f@macports.org> #60102: kerberos5 @1.18 fails to build with libressl-devel 2.9.2. ------------------------+------------------------ Reporter: hakoyamah | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: haspatch Port: kerberos5 | ------------------------+------------------------ Comment (by jerryyhom): The problem was probably solved by this [https://github.com/macports /macports-ports/commit/c6d702d1cdf15a4e765bae6c7b50691c16359080 kerberos5 commit]. In any case, kerberos5 and libressl compatibility is available with a current patch. This ticket may be closed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 04:26:30 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 04:26:30 -0000 Subject: [MacPorts] #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) In-Reply-To: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> References: <046.820da8f54a352a556fe151abe3fff0c9@macports.org> Message-ID: <061.9739b9e16afb1bd8bff91ef6da047dde@macports.org> #66419: py-pypdf2 @2.11.2 - port extract phase does not work using base @2.8.99 (llatest) ------------------------+------------------------ Reporter: snowflake | Owner: reneeotten Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: fixed | Keywords: Port: py-pypdf2 | ------------------------+------------------------ Changes (by reneeotten): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"fa079f5c4a7415ed3964d22cb7d4e37137d0e767/macports-ports" fa079f5c4a7415ed3964d22cb7d4e37137d0e767/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fa079f5c4a7415ed3964d22cb7d4e37137d0e767" py-pypdf2: change to PyPI Closes: https://trac.macports.org/ticket/66419 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 04:59:45 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 04:59:45 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.56768765499c69ce5505c4c6524b6318@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Changes (by LudgerBreil209): * Attachment "main.2.log" added. main.log of run without -t option -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 05:02:22 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 05:02:22 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.14660fb5583a804a6e951b396fba036f@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Comment (by LudgerBreil209): I ran 'port install' again without the -t option, as I did on the first run. This run also failed with an error. I have attached the log file of this run. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 05:47:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 05:47:34 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.193cf5e3311327b49e02fe58f290a3ea@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: octave | ------------------------+--------------------------------- Comment (by gjolleyrogers): Thanks. I have Octave installed on my M1 studio. This problem came when I updated my NON-M1 MacBook Pro to Ventura. But, I take your point -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 08:13:27 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 08:13:27 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.1f4821ce4fafb05ee94b1bbeb97f9adf@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by jmroot): In [changeset:"8ae0d73589330693f3b17849fdd5e65f0f56a5c1/macports-base" 8ae0d73589330693f3b17849fdd5e65f0f56a5c1/macports-base] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-base" revision="8ae0d73589330693f3b17849fdd5e65f0f56a5c1" Add extract.rename option This restores the functionality of 7921b2e on an opt-in basis and without the semantic differences introduced by creating a symlink. See: https://trac.macports.org/ticket/66415 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 08:16:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 08:16:37 -0000 Subject: [MacPorts] #64696: kerberos5 @1.19.2: Undefined symbols _EVP_MD_CTX_destroy _EVP_MD_size _HMAC_CTX_cleanup _HMAC_CTX_init _EVP_MD_CTX_create In-Reply-To: <043.41deb603589494a2e80d4973821c19f4@macports.org> References: <043.41deb603589494a2e80d4973821c19f4@macports.org> Message-ID: <058.ffb23d5a76e4432b49c438664657e8ee@macports.org> #64696: kerberos5 @1.19.2: Undefined symbols _EVP_MD_CTX_destroy _EVP_MD_size _HMAC_CTX_cleanup _HMAC_CTX_init _EVP_MD_CTX_create ------------------------+------------------------ Reporter: JR1994 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: tiger Port: kerberos5 | ------------------------+------------------------ Comment (by jerryyhom): Is the following line still necessary? {{{configure.ldflags-delete -L${prefix}/lib}}} In [ticket:64696#comment:7 comment 7], the reporter commented out that line and built successfully with openssl. I also commented out that line and compiled kerberos5 v1.20.1; I have libressl installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 08:59:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 08:59:50 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 is missing a dependency on a fuse port In-Reply-To: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> References: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> Message-ID: <061.95c9480d01a619836cee34645cc588c5@macports.org> #66391: ext2fuse @0.8.1_3 is missing a dependency on a fuse port ------------------------+---------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ext2fuse | ------------------------+---------------------- Comment (by ra1nb0w): ext2fuse should choose the right fuse library based on which macOS version do you have. This doesn't work if you are manually forcing the installation of osxfuse or macfuse. Maybe, remove both and install only {{{ext2fuse}}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 09:00:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 09:00:25 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.b69803b563ccd91b229bc66aeddb490f@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Comment (by jmroot): The log contains: {{{ :info:build Please ensure Xcode packages are up-to-date ? try running 'xcodebuild -runFirstLaunch'. }}} Have you done this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 09:04:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 09:04:25 -0000 Subject: [MacPorts] #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined In-Reply-To: <049.1d82130b540711fe530066891970425e@macports.org> References: <049.1d82130b540711fe530066891970425e@macports.org> Message-ID: <064.9f5e639b69c6781ece189b1600895b2e@macports.org> #66385: SoapyRTLSDR fails to build with GCC: ld: unknown option: --no-undefined ---------------------------+---------------------- Reporter: barracuda156 | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: SoapyRTLSDR | ---------------------------+---------------------- Comment (by ra1nb0w): Probably you should contact the upstream developer of SoapySDR at https://github.com/pothosware/SoapySDR -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 09:12:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 09:12:25 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.462f393ea636d852a7de7acddae4a06d@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Changes (by jmroot): * cc: mascguy, dbevans, jeremyhu (added) * type: request => enhancement * port: => ffmpeg * milestone: MacPorts Future => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 09:44:14 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 09:44:14 -0000 Subject: [MacPorts] #65395: py-numpy: fails to build on macOS 10.14 In-Reply-To: <044.514a91cbaaabca55074203de187e664c@macports.org> References: <044.514a91cbaaabca55074203de187e664c@macports.org> Message-ID: <059.cc42ca3d8fdb512968725909abb95b77@macports.org> #65395: py-numpy: fails to build on macOS 10.14 -----------------------+----------------------- Reporter: ra1nb0w | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-numpy | -----------------------+----------------------- Changes (by ra1nb0w): * status: assigned => closed * resolution: => fixed Comment: Seems fixed. If arise again feel free to re-open. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 10:42:00 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 10:42:00 -0000 Subject: [MacPorts] #66391: ext2fuse @0.8.1_3 is missing a dependency on a fuse port In-Reply-To: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> References: <046.f5beda8185b129dc7080c4cbdb9f00ed@macports.org> Message-ID: <061.4bf4cb3c6bd09c6c47adb6323441d8aa@macports.org> #66391: ext2fuse @0.8.1_3 is missing a dependency on a fuse port ------------------------+---------------------- Reporter: ballapete | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ext2fuse | ------------------------+---------------------- Comment (by ballapete): Do other users know these details? Does `port` sort them out? `Portfile`(s) should make it possible that the software can be installed in a clever way by first installing the dependencies. This did not happen. Anyway, `High Sierra` is missing a `kernel extension (kext)`. It either does not build from `osxfuse` or is not contained in `macfuse`. And I do not have a need for `FUSE` now. So if you think it's OK as it is, then just close the ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 10:50:36 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 10:50:36 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.f07dab9aef9fea20ebcfc7eec065fe18@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): So I do not have to wait for a new version of `Portfile` but just substitute the `patch-balign-to-align.diff` file? And start building and testing right away? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 10:51:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 10:51:19 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.d1c7f0f46301f8a783f46f11c25ddc9e@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by catap): Yes, can you please do that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:05:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 11:05:19 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on PPC Tiger, Mac OS X 10.4.11, because ld is missing a _futimens function Message-ID: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> #66425: libdeflate @1.15 does not build on PPC Tiger, Mac OS X 10.4.11, because ld is missing a _futimens function -----------------------+------------------------ Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: libdeflate -----------------------+------------------------ {{{ make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build' [ 96%] Building C object programs/CMakeFiles/libdeflate-gzip.dir/gzip.c.o cd /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/programs && /opt/local/bin/gcc-apple-4.2 -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_POSIX_C_SOURCE=200809L -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/programs -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/libdeflate-1.15 -pipe -Os -DNDEBUG -I/opt/local/include -arch ppc -mmacosx-version- min=10.4 -Wall -Wdeclaration-after-statement -Wmissing-field-initializers -Wmissing-prototypes -Wshadow -Wstrict-prototypes -Wundef -std=gnu99 -MD -MT programs/CMakeFiles/libdeflate-gzip.dir/gzip.c.o -MF CMakeFiles /libdeflate-gzip.dir/gzip.c.o.d -o CMakeFiles/libdeflate-gzip.dir/gzip.c.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/libdeflate-1.15/programs/gzip.c /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/libdeflate-1.15/programs/gzip.c: In function 'restore_timestamps': /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/libdeflate-1.15/programs/gzip.c:364: warning: implicit declaration of function 'futimens' [100%] Linking C executable libdeflate-gzip cd /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/programs && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/libdeflate- gzip.dir/link.txt --verbose=ON /opt/local/bin/gcc-apple-4.2 -pipe -Os -DNDEBUG -I/opt/local/include -arch ppc -mmacosx-version-min=10.4 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names "CMakeFiles/libdeflate-gzip.dir/gzip.c.o" -o libdeflate-gzip libdeflate_prog_utils.a ../libdeflate.a Undefined symbols: "_futimens", referenced from: _restore_metadata in gzip.c.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [programs/libdeflate-gzip] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build' make[1]: *** [programs/CMakeFiles/libdeflate-gzip.dir/all] Error 2 }}} The declaration `extern int futimens(int fd, const struct timespec _times_in[2])` can be found here, `/opt/local/include/LegacySupport/sys/stat.h`, and `LegacySupport` is used. `gzip @1.12_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-04-12T01:17:21+0200'` is installed, it could be built from source here, so `libdeflate` should build too. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:06:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 11:06:20 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on PPC Tiger, Mac OS X 10.4.11, because ld is missing a _futimens function In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.72730f2f70eba411e75e7621aa1dacf9@macports.org> #66425: libdeflate @1.15 does not build on PPC Tiger, Mac OS X 10.4.11, because ld is missing a _futimens function -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: libdeflate | -------------------------+----------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Tiger, Mac OS X 10.4.11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:09:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 11:09:04 -0000 Subject: [MacPorts] #65742: Gnuradio gui stuck In-Reply-To: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> References: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> Message-ID: <063.fc234d84c6d28b46ba64425a08a891a1@macports.org> #65742: Gnuradio gui stuck --------------------------+----------------------- Reporter: adamgao1996 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: qtgui Port: gnuradio | --------------------------+----------------------- Comment (by ra1nb0w): probably the easiest way is to pull the PR from github https://github.com/macports/macports-ports/pull/14942 into the main ports repository. Essentially, clone https://github.com/macports/macports-ports.git somewhere. Configure {{{/opt/local/etc/macports/sources.conf}}} with the directory that you have cloned {{{file:///Users/[user]/sources/github/macports-ports [default]}}} Then checkout the PR {{{git fetch origin pull/14942/head:gnuradio-3.10}}} and select that branch {{{git checkout gnuradio-3.10}}} To maintain the repository up-to-date use {{{pull}}}/{{{rebase}}} git command. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:12:16 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 11:12:16 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.39485c47e15995a1813998f24f4115f5@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): I removed the dependancy to dead `Python 2.7`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 11:37:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 11:37:37 -0000 Subject: [MacPorts] #65735: kicad @6.0.6_0: 3D models fail to display In-Reply-To: <042.efa80a7f812ad3d215d9bf40867dd63c@macports.org> References: <042.efa80a7f812ad3d215d9bf40867dd63c@macports.org> Message-ID: <057.c605bd35ef2ecc3cd04e7e641f7796f0@macports.org> #65735: kicad @6.0.6_0: 3D models fail to display ---------------------+---------------------- Reporter: polpo | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: kicad | ---------------------+---------------------- Comment (by ra1nb0w): dl8dtl: you can use {{{export DYLD_PRINT_LIBRARIES=1}}} to list the loaded libraries. Use it in the terminal and then load the kicad 3d -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 12:01:48 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 12:01:48 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.5ca5b4d623a3c1ae7905784293e5de47@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): Build started some time ago with `/usr/bin/gnumake` and `/opt/local/bin/g++-mp-7 -std=c++11`, new patch succeeded? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 12:18:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 12:18:24 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens (was: libdeflate @1.15 does not build on PPC Tiger, Mac OS X 10.4.11, because ld is missing a _futimens function) In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.079eed30c8e220a90e71fe064d3fa6d8@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Changes (by jmroot): * keywords: tiger ppc => * status: new => assigned * cc: nickblack@?, herby.gillot@? (removed) * cc: dankamongmen (added) * owner: (none) => herbygillot Comment: It fails to build on 10.12 and older because `futimens` was added in 10.13. Configure actually checks for it, and there is code in `gzip.c` to fall back to using `futimes`, but it doesn't seem to have its logic quite right. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:52:39 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 14:52:39 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.967f056bd36de8cbf0ded1a2634702e3@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): The tests `CMake` performs report: {{{ -- Looking for futimens -- Looking for futimens - not found -- Looking for futimes -- Looking for futimes - found }}} and `?/libdeflate/work/build/CMakeFiles/CMakeError.log` contains: {{{ Determining if the futimens exist failed with the following output: Change Dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp Run Build Command(s):/usr/bin/make -f Makefile cmTC_3f020/fast && /usr/bin/make -f CMakeFiles/cmTC_3f020.dir/build.make CMakeFiles/cmTC_3f020.dir/build Building C object CMakeFiles/cmTC_3f020.dir/CheckSymbolExists.c.o /opt/local/bin/gcc-apple-4.2 -pipe -Os -DNDEBUG -I/opt/local/include -arch ppc -mmacosx-version-min=10.4 -o CMakeFiles/cmTC_3f020.dir/CheckSymbolExists.c.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c: In function 'main': /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:9: error: 'futimens' undeclared (first use in this function) /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:9: error: (Each undeclared identifier is reported only once /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:9: error: for each function it appears in.) make[1]: *** [CMakeFiles/cmTC_3f020.dir/CheckSymbolExists.c.o] Error 1 make: *** [cmTC_3f020/fast] Error 2 File /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c: /* */ #include #include int main(int argc, char** argv) { (void)argv; #ifndef futimens return ((int*)(&futimens))[argc]; #else (void)argc; return 0; #endif } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:53:26 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 14:53:26 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.7c3939f3cb1fd5d077c7c3d9ca922162@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Changes (by natelsonoptics): * Attachment "installed.txt" added. output of sudo port -v installed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:56:09 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 14:56:09 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.9ec8d6ef3bc205f1b14c9aabfe113edb@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Changes (by ballapete): * Attachment "CMakeError.log" added. /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeError.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:56:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 14:56:55 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.cafc1269537a8814efd38706d47af88a@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Changes (by ballapete): * Attachment "CMakeOutput.log" added. /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/CMakeFiles/CMakeOutput.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 14:57:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 14:57:42 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.6596aead0cbc1586191f88327acb4098@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Comment (by natelsonoptics): Thanks for taking a look, and apologies for the naive questions. I've attached the output of {{{sudo port -v installed}}}. This is not a migration; while I did migrate from a timemachine backup onto the M2 machine, I had never installed ports before. I initially tried following the simple installation instructions; after that failed, I looked at the list of tickets and followed this approach: {{{ sudo port clean gnuplot sudo port selfupdate sudo port upgrade outdated sudo port install gnuplot }}} After iterating that a couple of times, which cleaned up almost everything, now when I run {{{ sudo port -v install gnuplot }}} I get this: {{{ ---> Computing dependencies for gnuplot. ---> Cleaning gnuplot ---> Removing work directory for gnuplot ---> Scanning binaries for linking errors Could not open /opt/local/lib/libffi.6.dylib: Error opening or reading file (referenced from /opt/local/libexec/llvm-3.7/bin/FileCheck) ---> Found 160 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: llvm-3.7 @3.7.1 Continue? [Y/n]: }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 15:16:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 15:16:13 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.71c83729647db95f433c4548eb40826c@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Comment (by natelsonoptics): Actually, when I run that sequence again, when I try to upgrade outdated, I get this: {{{ Error: Cannot install llvm-9.0 for the arch 'x86_64' because Error: its dependency libedit cannot build for the required arch. Error: Problem while installing llvm-9.0 Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. }}} Clearly there are issues with calls to various previous versions of llvm somehow. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 15:36:58 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 15:36:58 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.f03f8825db47403e66c05da897e931e4@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by kencu): one of the deps requires rust, which brings in the flood? the minute you remove a library dep to reduce the overall deps, someone else will say they really needed that library? if you strip off deps into variants, then other ports have to dance to see if their needed ffmpeg variants are installed? I think we leave it alone. Once the buildbot comes, you won?t usually see all the build deps anyway? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 15:43:29 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 15:43:29 -0000 Subject: [MacPorts] #66426: [Port Request] oauth2c Message-ID: <044.cf347d0cf617efac46ade42ca6d7a7ab@macports.org> #66426: [Port Request] oauth2c ---------------------+-------------------- Reporter: wyuenho | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ---------------------+-------------------- oauth2c is a command-line tool that simplifies the process of experimenting with different grant types and client authentication methods for OAuth 2.0. https://github.com/cloudentity/oauth2c -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 16:44:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 16:44:19 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.e6a1907254de5ce5fc80a779b88870a7@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Comment (by kencu): You have a bunch of ancient installed ports from 2016 that are x86_64 architecture. They slipped in on you somehow. I would just start fresh, with: {{{ sudo port -f uninstall installed sudo port -v reclaim }}} and then install the ports you want. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 17:04:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 17:04:25 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.011101db8c59756b563bacab168f2e14@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by ballapete): Build succeeded, and test too, OK, one hour ago. Do you want any results? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:15:28 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 18:15:28 -0000 Subject: [MacPorts] #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 In-Reply-To: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> References: <051.ce973a05502c98b5418096a7c4f3f186@macports.org> Message-ID: <066.0c61b46db891a79ba487de2e8a47c94b@macports.org> #66422: failing to install gnuplot 5.4.3 apparently bc of llvm-3.7 -----------------------------+-------------------- Reporter: natelsonoptics | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuplot | -----------------------------+-------------------- Comment (by kencu): you could try and do a cleanup project, but it's hard to get it right, and to be honest just reinstalling is safer. The specific issue seems to be this ancient ld64 is still hanging around: {{{ ld64-latest @253.3_2+llvm37 }}} but even after cleaning that up, you may find issues. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:16:47 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 18:16:47 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake Message-ID: <045.ea01ce51c618fee2f44f337119c05027@macports.org> #66427: migrating macports to M1 fails to build cmake ----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ----------------------+-------------------- I am migrating my system from an old Intel MBP to a new M1 Pro based MBP (13.0.1 (22A400)). I am following the direction here: https://trac.macports.org/wiki/Migration to rebuild the ports. The issue I'm running into is that cmake is being built as a dependency, but the +universal variant is being built. This means that cmake is attempting to build for x86_64, and as part of the configure process, tries to run an x86_64 binary but this fails. I have not installed Rosetta (not sure if this would fix the issue or not), as I'm trying to make sure I get as many native binaries as possible before breaking down and using it. The output from restore_ports.tcl: {{{ ---> Computing dependencies for cmake ---> Fetching archive for cmake ---> Attempting to fetch cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from http://mirror.fcix.net/macports/packages/cmake ---> Attempting to fetch cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from https://packages.macports.org/cmake ---> Attempting to fetch cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/cmake ---> Configuring cmake Error: Failed to configure cmake: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cmake/cmake/main.log for details. upgrade tiff failed while executing "macports::_upgrade_mport_deps $mport $target" (procedure "mportexec" line 46) invoked from within "mportexec $workername $install_target" Unable to execute target 'install' for port 'qt4-mac': upgrade tiff failed while executing "install_ports $operationList" (file "./restore_ports.tcl" line 299) }}} Attached are the relevant logs as well. I'd expect that either cmake not support a universal variant, or the migration to not attempt to install universal variants if they don't work. I did notice a similar bug in https://trac.macports.org/ticket/66213 and I also noticed that the build systems don't actually build/test the universal variant of ports: https://build.macports.org/builders/ports- 12_arm64-builder/builds/73986/steps/install-port/logs/stdio which explains why this failure was not caught. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:17:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 18:17:13 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.fa9b7e34285f449b3e7230e2cdd138d7@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+-------------------- Changes (by jmgurney): * Attachment "main.log" added. cmake main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:18:29 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 18:18:29 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.bf11f5d6e31597dce006856eb317d846@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+-------------------- Changes (by jmgurney): * Attachment "cmake_bootstrap.log" added. cmake configure failure log, showing failure to run x86_64 binary -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:39:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 18:39:12 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.39973de9925cf59a5778aa2388f554ed@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+-------------------- Comment (by kencu): This is both a feature and a curse of the way MacPorts handles universal ports. For cmake, if you install it separately, like this: {{{ sudo port -v install cmake }}} before you run the restore script, at least that one will install without universal, and will then be ignored by the restore script as it will be seen to be already installed. (I am curious what else you have on your list that is calling for cmake to be installed as universal though -- you might run into troubles with more universal builds still -- perhaps you can spot the issue in your list of ports.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 18:44:41 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 18:44:41 -0000 Subject: [MacPorts] #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code In-Reply-To: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> References: <046.c5153ed69ae9f5f4fc4137d52531e76d@macports.org> Message-ID: <061.55103a46728b1738839fbed99347fadb@macports.org> #66258: icu @72.1 does not build on PPC Tiger, Mac OS X 10.4.11, because of problems with assembly code -------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: tiger ppc Port: icu | -------------------------+----------------------- Comment (by catap): Nope, thanks! I've pushed this patch to upstream. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:33:52 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 19:33:52 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.409588cb15b472e77c6a3fbf56463fd0@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Changes (by ryandesign): * keywords: libffi snow leopard patch can't find => snowleopard * version: => 2.8.0 Old description: > When trying to install libffi on Mac OS 10.6.8 I see this error: > > ---> Applying patches to libffi > Error: Failed to patch libffi: can't read "patch.cmd": Failed to locate > 'patch' in path: > '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its > MacPorts configuration time location, did you move it? New description: When trying to install libffi on Mac OS 10.6.8 I see this error: {{{ ---> Applying patches to libffi Error: Failed to patch libffi: can't read "patch.cmd": Failed to locate 'patch' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it? }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:35:33 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 19:35:33 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.10664a5d4213ca59d891bc749d802837@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Changes (by ryandesign): * port: => cmake Old description: > I am migrating my system from an old Intel MBP to a new M1 Pro based MBP > (13.0.1 (22A400)). > > I am following the direction here: > https://trac.macports.org/wiki/Migration to rebuild the ports. > > The issue I'm running into is that cmake is being built as a dependency, > but the +universal variant is being built. This means that cmake is > attempting to build for x86_64, and as part of the configure process, > tries to run an x86_64 binary but this fails. I have not installed > Rosetta (not sure if this would fix the issue or not), as I'm trying to > make sure I get as many native binaries as possible before breaking down > and using it. > > The output from restore_ports.tcl: > > {{{ > ---> Computing dependencies for cmake > ---> Fetching archive for cmake > ---> Attempting to fetch > cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from > http://mirror.fcix.net/macports/packages/cmake > ---> Attempting to fetch > cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from > https://packages.macports.org/cmake > ---> Attempting to fetch > cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from > https://ywg.ca.packages.macports.org/mirror/macports/packages/cmake > ---> Configuring cmake > Error: Failed to configure cmake: configure failure: command execution > failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cmake/cmake/main.log > for details. > upgrade tiff failed > while executing > "macports::_upgrade_mport_deps $mport $target" > (procedure "mportexec" line 46) > invoked from within > "mportexec $workername $install_target" > Unable to execute target 'install' for port 'qt4-mac': upgrade tiff > failed > while executing > "install_ports $operationList" > (file "./restore_ports.tcl" line 299) > }}} > > Attached are the relevant logs as well. > > I'd expect that either cmake not support a universal variant, or the > migration to not attempt to install universal variants if they don't > work. > > I did notice a similar bug in https://trac.macports.org/ticket/66213 and > I also noticed that the build systems don't actually build/test the > universal variant of ports: https://build.macports.org/builders/ports- > 12_arm64-builder/builds/73986/steps/install-port/logs/stdio which > explains why this failure was not caught. New description: I am migrating my system from an old Intel MBP to a new M1 Pro based MBP (13.0.1 (22A400)). I am following the direction here: wiki:Migration to rebuild the ports. The issue I'm running into is that cmake is being built as a dependency, but the +universal variant is being built. This means that cmake is attempting to build for x86_64, and as part of the configure process, tries to run an x86_64 binary but this fails. I have not installed Rosetta (not sure if this would fix the issue or not), as I'm trying to make sure I get as many native binaries as possible before breaking down and using it. The output from restore_ports.tcl: {{{ ---> Computing dependencies for cmake ---> Fetching archive for cmake ---> Attempting to fetch cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from http://mirror.fcix.net/macports/packages/cmake ---> Attempting to fetch cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from https://packages.macports.org/cmake ---> Attempting to fetch cmake-3.24.3_0+universal.darwin_22.arm64-x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/cmake ---> Configuring cmake Error: Failed to configure cmake: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cmake/cmake/main.log for details. upgrade tiff failed while executing "macports::_upgrade_mport_deps $mport $target" (procedure "mportexec" line 46) invoked from within "mportexec $workername $install_target" Unable to execute target 'install' for port 'qt4-mac': upgrade tiff failed while executing "install_ports $operationList" (file "./restore_ports.tcl" line 299) }}} Attached are the relevant logs as well. I'd expect that either cmake not support a universal variant, or the migration to not attempt to install universal variants if they don't work. I did notice a similar bug in #66213 and I also noticed that the build systems don't actually build/test the universal variant of ports: https://build.macports.org/builders/ports- 12_arm64-builder/builds/73986/steps/install-port/logs/stdio which explains why this failure was not caught. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:40:43 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 19:40:43 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.55e7a8c2927a15e1031e0efdb6dffa12@macports.org> #66420: soxr @0.1.3 Building on Ventura fails ----------------------+--------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: soxr | ----------------------+--------------------- Changes (by ryandesign): * keywords: => ventura Old description: > Building ffmpeg on Ventura (M1 chip) fails, due to problem with building > soxr: > > ''$sudo port -N install ffmpeg +nonfree''\\ > ''Computing dependencies for ffmpeg''\\ > ''Dependencies to be installed: soxr speex speexdsp svt-av1 yasm x264 zig > zvbi\\ > ''Fetching archive for soxr''\\ > ''Attempting to fetch soxr-0.1.3 .darwin 22.arm64.tbz2 from https: > //packages.macports.org/soxr''\\ > ''Attempting to fetch soxr-0.1.3_O. darwin 22.arm64.tbz2 from > https://cph.dk.packages.macports.org/soxr''\\ > ''Attempting to fetch soxr-0.1.3_0.darwin_22.arm64.tbz2 from > https://fra.de.packages.macports.org/soxr''\\ > ''Building soxr''\\ > ''Error. Failed to build soxr: command execution failed''\\ > > There is a bug report on soxr for a similar error (I believe) stating > that it will build with the universal flag. > > Hoping you can update the ffmpeg port to use this ? or perhaps it is more > complicated than that ? I'm not at home here, just guessing ? > > Thanks in advance and thanks for all the past work done in having this > port available! New description: Building ffmpeg on Ventura (M1 chip) fails, due to problem with building soxr: {{{ $sudo port -N install ffmpeg +nonfree Computing dependencies for ffmpeg Dependencies to be installed: soxr speex speexdsp svt-av1 yasm x264 zig zvbi Fetching archive for soxr Attempting to fetch soxr-0.1.3_0.darwin_22.arm64.tbz2 from https://packages.macports.org/soxr Attempting to fetch soxr-0.1.3_0.darwin_22.arm64.tbz2 from https://cph.dk.packages.macports.org/soxr Attempting to fetch soxr-0.1.3_0.darwin_22.arm64.tbz2 from https://fau.de.packages.macports.org/soxr Building soxr Error. Failed to build soxr: command execution failed }}} There is a bug report on soxr for a similar error (I believe) stating that it will build with the universal flag. Hoping you can update the ffmpeg port to use this ? or perhaps it is more complicated than that ? I'm not at home here, just guessing ? Thanks in advance and thanks for all the past work done in having this port available! -- Comment: To avoid typos, in the future please copy/paste error messages rather than retyping them. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:42:01 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 19:42:01 -0000 Subject: [MacPorts] #66428: helix 22.12: Budle runtime directory Message-ID: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> #66428: helix 22.12: Budle runtime directory -------------------------+-------------------- Reporter: pascalkuthe | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: helix -------------------------+-------------------- I suggest you raise this as a We recently revived a bug report upstream (helix-editor/helix#5090) from a user that was confused by the need to manually symlink the runtime directory and asked us to improve our documentation in that regard. We only document this requirement for manual builds because package manager usually provide a wrapper script that sets `HELIX_RUNTIME`. I wanted to submit a PR to fix the package but found myself unable to full fill all requirements as I do not own a mac and can not actually test this. Instead I attached an improved version below. Please not that I also readded the removed `--frozen` flag. We track the Cargo.lock in git and use it during testing for every commit. This should not be causing any issues. {{{ # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c -basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 PortSystem 1.0 PortGroup cargo 1.0 PortGroup github 1.0 github.setup helix-editor helix 22.12 revision 0 homepage https://helix-editor.com description A post-modern text editor. long_description \ {*}${description}. ${name} is a kakoune / neovim inspired editor, written \ in Rust. categories editors installs_libs no license MPL-2 maintainers {gmail.com:herby.gillot @herbygillot} \ openmaintainer # Helix's build process requires bit fetch.type git post-extract { system -W ${worksrcpath} "git submodule update --init" } destroot { xinstall -d ${destroot}${prefix}/share/${name}/ xinstall -m 0755 \ ${worksrcpath}/target/[cargo.rust_platform]/release/hx \ ${destroot}${prefix}/share/${name}/ copy ${worksrcpath}/runtime ${destroot}${prefix}/share/${name}/ # Wrapper script that sets HELIX_RUNTIME directory touch ${worksrcpath}/hx cat >> ${worksrcpath}/hx < MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:46:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 19:46:42 -0000 Subject: [MacPorts] #66428: helix 22.12: Budle runtime directory In-Reply-To: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> References: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> Message-ID: <063.8826be38d4a1cd2b6942f0d7c28b1e76@macports.org> #66428: helix 22.12: Budle runtime directory --------------------------+-------------------- Reporter: pascalkuthe | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: helix | --------------------------+-------------------- Description changed by pascalkuthe: Old description: > I suggest you raise this as a > > We recently revived a bug report upstream (helix-editor/helix#5090) from > a user that was confused by the need to manually symlink the runtime > directory and asked us to improve our documentation in that regard. > > We only document this requirement for manual builds because package > manager usually provide a wrapper script that sets `HELIX_RUNTIME`. > I wanted to submit a PR to fix the package but found myself unable to > full fill all requirements as I do not own a mac and can not actually > test this. > Instead I attached an improved version below. > > Please not that I also readded the removed `--frozen` flag. > We track the Cargo.lock in git and use it during testing for every > commit. This should not be causing any issues. > > {{{ > # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c > -basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 > > PortSystem 1.0 > PortGroup cargo 1.0 > PortGroup github 1.0 > > github.setup helix-editor helix 22.12 > revision 0 > > homepage https://helix-editor.com > > description A post-modern text editor. > > long_description \ > {*}${description}. ${name} is a kakoune / neovim inspired editor, > written \ > in Rust. > > categories editors > installs_libs no > license MPL-2 > maintainers {gmail.com:herby.gillot @herbygillot} \ > openmaintainer > > # Helix's build process requires bit > fetch.type git > > post-extract { > system -W ${worksrcpath} "git submodule update --init" > } > > destroot { > xinstall -d ${destroot}${prefix}/share/${name}/ > xinstall -m 0755 \ > ${worksrcpath}/target/[cargo.rust_platform]/release/hx \ > ${destroot}${prefix}/share/${name}/ > > copy ${worksrcpath}/runtime ${destroot}${prefix}/share/${name}/ > > # Wrapper script that sets HELIX_RUNTIME directory > touch ${worksrcpath}/hx > cat >> ${worksrcpath}/hx < #!/usr/bin/env sh > > HELIX_RUNTIME="${destroot}${prefix}/share/${name}/runtime" exec > ${destroot}${prefix}/share/${name}/hx "\$@" > EOF > chmod +x ${worksrcpath}/hx > xinstall -m 0755 \ > ${worksrcpath}/hx \ > ${destroot}${prefix}/bin/ > } > }}} New description: We recently revived a bug report upstream (https://github.com/helix- editor/helix/issues/5090) from a user that was confused by the need to manually symlink the runtime directory and asked us to improve our documentation in that regard. We only document this requirement for manual builds because package manager usually provide a wrapper script that sets `HELIX_RUNTIME`. I wanted to submit a PR to fix the package but found myself unable to full fill all requirements as I do not own a mac and can not actually test this. Instead I attached an improved version below. Please not that I also readded the removed `--frozen` flag. We track the Cargo.lock in git and use it during testing for every commit. This should not be causing any issues. {{{ # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c -basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 PortSystem 1.0 PortGroup cargo 1.0 PortGroup github 1.0 github.setup helix-editor helix 22.12 revision 0 homepage https://helix-editor.com description A post-modern text editor. long_description \ {*}${description}. ${name} is a kakoune / neovim inspired editor, written \ in Rust. categories editors installs_libs no license MPL-2 maintainers {gmail.com:herby.gillot @herbygillot} \ openmaintainer # Helix's build process requires bit fetch.type git post-extract { system -W ${worksrcpath} "git submodule update --init" } destroot { xinstall -d ${destroot}${prefix}/share/${name}/ xinstall -m 0755 \ ${worksrcpath}/target/[cargo.rust_platform]/release/hx \ ${destroot}${prefix}/share/${name}/ copy ${worksrcpath}/runtime ${destroot}${prefix}/share/${name}/ # Wrapper script that sets HELIX_RUNTIME directory touch ${worksrcpath}/hx cat >> ${worksrcpath}/hx < MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 19:55:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 19:55:50 -0000 Subject: [MacPorts] #65710: graphene @1.10.8_0+universal: graphene-1.0.pc differs and cannot be merged In-Reply-To: <045.a302736fc312313abb99c209899130ac@macports.org> References: <045.a302736fc312313abb99c209899130ac@macports.org> Message-ID: <060.f026c9d1dba29fd76081edbef81c62d0@macports.org> #65710: graphene @1.10.8_0+universal: graphene-1.0.pc differs and cannot be merged -----------------------+--------------------------------- Reporter: thetrial | Owner: dbevans Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: elcapitan legacy-os Port: graphene | -----------------------+--------------------------------- Comment (by thetrial): What happened to this? Any news or updates? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:05:16 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:05:16 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.84777638b2956262b786bbfd8031e9c5@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by programmingkidx): 'which patch' returns /usr/local/bin/patch. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:12:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:12:24 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.2fc6c1c7bdb7b8f8067067bd64450e83@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by programmingkidx): @jmroot, you are right, there is no /usr/bin/patch. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:22:03 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:22:03 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.1dd37014c9f83b6dfd8d83c014eb1dc9@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): Same failure on PPC Leoprad, Mac OS X 10.5.8: {{{ /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/libdeflate-1.15/programs/gzip.c:364: warning: implicit declaration of function ?futimens? [100%] Linking C executable libdeflate-gzip cd /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build/programs && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/libdeflate- gzip.dir/link.txt --verbose=ON /usr/bin/gcc-4.2 -pipe -Os -DNDEBUG -I/opt/local/include -arch ppc -mmacosx-version-min=10.5 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/opt/local/lib -Wl,-headerpad_max_install_names "CMakeFiles/libdeflate-gzip.dir/gzip.c.o" -o libdeflate-gzip -Wl,-rpath,/opt/local/lib libdeflate_prog_utils.a ../libdeflate.a Undefined symbols: "_futimens", referenced from: _restore_metadata in gzip.c.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [programs/libdeflate-gzip] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_archivers_libdeflate/libdeflate/work/build' }}} Isn't it just a simple `-lMacportsLegacySupport` that is missing? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:28:16 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:28:16 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.9fb8e4ada05bdfb8a6e786fb1ac1cf8b@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by programmingkidx): After creating a symbolic link to /usr/local/bin/patch in /usr/bin/ I was able to install libffi. I don't know why libffi's installation has to only use /usr/bin/patch. I thought using any version of the patch command would be ok. Maybe one day the strict requirement to use only /usr/bin/patch can be removed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:34:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:34:34 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.2f8d9ca8511328216d7efcad125f88ab@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by kencu): the question is why is your system broken? You should reinstall it? {{{ $ uname -a Darwin KensMacBookPro.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386 $ ls -la /usr/bin/patch -rwxr-xr-x 1 root wheel 201424 4 Apr 2011 /usr/bin/patch }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:36:00 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:36:00 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" when /usr/bin/patch is missing from OS installation (was: Failed to patch libffi: can't read "patch.cmd") In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.d528bd58e3c16c0586a20475a86a0690@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" when /usr/bin/patch is missing from OS installation ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:36:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:36:24 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" (was: Failed to patch libffi: can't read "patch.cmd" when /usr/bin/patch is missing from OS installation) In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.a4b6b8269fe8609030e3551339aac8e3@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by programmingkidx): Maybe I removed the system-supplied patch command to use a newer version of it somewhere else. I can't remember. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:53:49 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:53:49 -0000 Subject: [MacPorts] #66429: gettext-tools-libs fails to install on Mac OS 10.6 Message-ID: <052.762356ffe28083bb7a1e0b190faac668@macports.org> #66429: gettext-tools-libs fails to install on Mac OS 10.6 ---------------------------------+-------------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: gettext snowleopard | Port: gettext-tools-libs ---------------------------------+-------------------------------- While trying to install gettext-tools-libs I saw this error: Error: Failed to configure gettext-tools-libs: configure failure: command execution failed Here is an error from the log: dyld: Library not loaded: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib Referenced from: /opt/local/libexec/llvm-3.4/bin/clang Reason: Incompatible library version: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 configure:5552: $? = 133 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 21:54:29 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 21:54:29 -0000 Subject: [MacPorts] #66429: gettext-tools-libs fails to install on Mac OS 10.6 In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.9bc82695025e3e26528e48c23218078a@macports.org> #66429: gettext-tools-libs fails to install on Mac OS 10.6 ---------------------------------+--------------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: gettext snowleopard Port: gettext-tools-libs | ---------------------------------+--------------------------------- Changes (by programmingkidx): * Attachment "config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:01:57 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 22:01:57 -0000 Subject: [MacPorts] #66429: gettext-tools-libs fails to install on Mac OS 10.6 In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.7a83bd30e4643151ebc0c11b49351052@macports.org> #66429: gettext-tools-libs fails to install on Mac OS 10.6 ---------------------------------+--------------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: gettext snowleopard Port: gettext-tools-libs | ---------------------------------+--------------------------------- Comment (by kencu): oh oh, more weirdness -- here's mine: {{{ $ otool -L /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib (compatibility version 1.0.0, current version 3.7.1) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) /opt/local/lib/libffi.8.dylib (compatibility version 10.0.0, current version 10.0.0) /opt/local/libexec/libcxx-bootstrap/lib/libncurses.6.dylib (compatibility version 6.0.0, current version 6.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:08:27 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 22:08:27 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.4165cd1dd2ab673bee0a5f6037395cfb@macports.org> #66420: soxr @0.1.3 Building on Ventura fails ----------------------+--------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: soxr | ----------------------+--------------------- Comment (by cassii2): I had this same problem, here's my log file: https://pastebin.com/KseWMRrm -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:08:49 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 22:08:49 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.dbb70a88ee8c1a286c81dd69c5c1b3f4@macports.org> #66420: soxr @0.1.3 Building on Ventura fails ----------------------+--------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: soxr | ----------------------+--------------------- Changes (by cassii2): * Attachment "main.log" added. log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:31:03 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 22:31:03 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.157d5b10350c66bf52cc79f7b66dda85@macports.org> #66420: soxr @0.1.3 Building on Ventura fails ----------------------+--------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: soxr | ----------------------+--------------------- Comment (by kaestel): Replying to [comment:2 ryandesign]: > To avoid typos, in the future please copy/paste error messages rather than retyping them. Noted. The C/P cut the line-breaks and I got carried away. Sorry about the inconvenience. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 22:37:22 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 22:37:22 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.6f474db796e6ff0d7648ecc8cc310ebe@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by jmgurney): I actually had to install cmake earlier so that I could manually build the editor I use, so it's already installed: {{{ $ port installed | grep cmake cmake @3.24.3_0 (active) cmake-bootstrap @3.9.6_0 (active) }}} And yet I'm still getting the error. I still tried it: {{{ $ sudo port -v install cmake Password: Error: Requested variants "" do not match those the build was started with: "+universal". Error: Please use the same variants again, or run 'port clean cmake' first to remove the existing partially completed build. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port cmake failed $ sudo port clean cmake ---> Cleaning cmake $ sudo port -v install cmake ---> Computing dependencies for cmake. ---> Cleaning cmake ---> Removing work directory for cmake ---> Scanning binaries for linking errors Could not open /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit: Error opening or reading file (referenced from /opt/local/share/java/android-sdk- macosx/tools/emulator) Could not open /System/Library/Frameworks/JavaVM.framework/Versions/A/Frameworks/JavaNativeFoundation.framework/Versions/A/JavaNativeFoundation: Error opening or reading file (referenced from /Library/Java/JavaVirtualMachines/openjdk13-bootstrap/Contents/Home/lib/libawt.dylib) ---> Found 16 broken files, matching files to ports ---> Found 2 broken ports, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: android @23 openjdk13-bootstrap @13 Continue? [Y/n]: n }}} and then I tried to run the restore ports script again, and got the same thing. As for the dependency, it looks like it's from tiff via qt4-mac, but I don't know exactly. I did a quick peak at which packets are requested to be universal, and neither qt4-mac nor tiff are listed directly. Is there a way to make cmake NOT be universal? since it clearly breaks when done so, or lie about it being universal, and build only a single platform? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 23:08:36 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 23:08:36 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.479ff7c5d0aad93788f807a0329452db@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by kencu): if cmake is installed, Macports will not (should not) request it to be reinstalled +universal unless perhaps it is expressly written on your restore ports script as being universal, in which case I presume you'd remove that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 23:13:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 23:13:37 -0000 Subject: [MacPorts] #66429: gettext-tools-libs fails to install on Mac OS 10.6 In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.143650214d9f091b36ec221fcbf22947@macports.org> #66429: gettext-tools-libs fails to install on Mac OS 10.6 ---------------------------------+--------------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: gettext snowleopard Port: gettext-tools-libs | ---------------------------------+--------------------------------- Comment (by programmingkidx): So I tried to install clang 3.4 to see if this would fix the problem. When I did I ran into it failing because gettext-tools-libs would not install. This looks like a circular dependency issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 9 23:20:10 2022 From: noreply at macports.org (MacPorts) Date: Fri, 09 Dec 2022 23:20:10 -0000 Subject: [MacPorts] #66429: gettext-tools-libs fails to install on Mac OS 10.6 In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.d7e52d34ac67dee92ed16a66b958855d@macports.org> #66429: gettext-tools-libs fails to install on Mac OS 10.6 ---------------------------------+--------------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: gettext snowleopard Port: gettext-tools-libs | ---------------------------------+--------------------------------- Comment (by programmingkidx): Here is my otool -L /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib:\\ /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib (compatibility version 0.0.0, current version 0.0.0)\\ /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8)\\ /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11)\\ /opt/local/lib/libffi.6.dylib (compatibility version 7.0.0, current version 7.4.0)\\ /opt/local/lib/libncurses.6.dylib (compatibility version 6.0.0, current version 6.0.0)\\ /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 00:14:34 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 00:14:34 -0000 Subject: [MacPorts] #66430: xar patching fails Message-ID: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> #66430: xar patching fails -----------------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: patching failed snowleopard | Port: xar -----------------------------------------+-------------------- While trying to install xar I saw this error: ---> Applying patches to xar\\ Error: Failed to patch xar: error copying "/opt/local/share/automake-1.16/config.guess": no such file or directory This happened on Mac OS 10.6.8. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 00:15:53 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 00:15:53 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.aa856e16b4df9e58746b2d19d5fe0bed@macports.org> #66430: xar patching fails ------------------------------+----------------------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: patching failed snowleopard Port: xar | ------------------------------+----------------------------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 01:15:22 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 01:15:22 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.c2e7ebe009fe9212b610a5087f012d85@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by jmgurney): It was not: {{{ $ grep cmake myports.txt.orig cmake @3.22.4_0 (active) requested_variants='' platform='darwin 21' archs='x86_64' date='2022-06-02T11:45:52-0700' }}} I have not removed a number of ports because trying each one is too time consuming, but things seem to be advancing further. The only one that I dropped that was marked universal was: {{{ db48 @4.8.30_4+universal (active) requested_variants='+universal' platform='darwin 21' archs='arm64 x86_64' date='2022-06-02T11:54:37-0700' }}} the rest don't have a variant: {{{ $ diff myports.txt myports.txt.orig | grep '^>' | grep -v db48 | awk ' { if ($4 ~ /^requested_variants/) print $4; else print $5}' | sort -u requested_variants='' requested_variants='+llvm80' requested_variants='+qt4' requested_variants='+sql' }}} (myports.txt.orig was the original one before I started trimming things down, myports.txt is what I'm running now and has been running for a couple hours so far. I'll try to see which one of the ports is causing the breakage once things complete. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 02:31:00 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 02:31:00 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.94ad785c3b42bdcc2a72ebc32789d799@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Changes (by jmroot): * cc: michaelld (added) Comment: Installing Rosetta 2 would fix this failure, at least. Unfortunately cmake does want to run a binary it builds for each architecture, which also makes it impossible to build it arm64+x86_64 on x86_64 hardware. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 02:32:42 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 02:32:42 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.14aa5a3674db7b130d9e03a5c55b5946@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by jmroot): BTW, qt4-mac can't build as arm64, so it automatically builds as x86_64 instead, which pulls in universal dependencies. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 02:33:52 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 02:33:52 -0000 Subject: [MacPorts] #66428: helix 22.12: Budle runtime directory In-Reply-To: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> References: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> Message-ID: <063.71c14ba4c93380d93ae9b00792855e13@macports.org> #66428: helix 22.12: Budle runtime directory --------------------------+------------------------- Reporter: pascalkuthe | Owner: herbygillot Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: helix | --------------------------+------------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => herbygillot -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 02:36:18 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 02:36:18 -0000 Subject: [MacPorts] #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 (was: gettext-tools-libs fails to install on Mac OS 10.6) In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.39c50666388245fdbf961e0d54f4a969@macports.org> #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ------------------------------+------------------------- Reporter: programmingkidx | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: llvm-3.4 | ------------------------------+------------------------- Changes (by ryandesign): * status: new => assigned * cc: larryv (added) * owner: (none) => jeremyhu * keywords: gettext snowleopard => snowleopard * port: gettext-tools-libs => llvm-3.4 Old description: > While trying to install gettext-tools-libs I saw this error: > > Error: Failed to configure gettext-tools-libs: configure failure: command > execution failed > > Here is an error from the log: > > dyld: Library not loaded: > /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib > Referenced from: /opt/local/libexec/llvm-3.4/bin/clang > Reason: Incompatible library version: clang requires version 1.0.0 or > later, but libLLVM-3.4.dylib provides version 0.0.0 > ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 > configure:5552: $? = 133 New description: While trying to install gettext-tools-libs I saw this error: {{{ Error: Failed to configure gettext-tools-libs: configure failure: command execution failed }}} Here is an error from the log: {{{ dyld: Library not loaded: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib Referenced from: /opt/local/libexec/llvm-3.4/bin/clang Reason: Incompatible library version: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 configure:5552: $? = 133 }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 02:37:05 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 02:37:05 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.a17482d99cc59d061242faedc4d7b500@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Changes (by ryandesign): * keywords: patching failed snowleopard => snowleopard Old description: > While trying to install xar I saw this error: > > ---> Applying patches to xar\\ > Error: Failed to patch xar: error copying > "/opt/local/share/automake-1.16/config.guess": no such file or directory > > This happened on Mac OS 10.6.8. New description: While trying to install xar I saw this error: {{{ ---> Applying patches to xar Error: Failed to patch xar: error copying "/opt/local/share/automake-1.16/config.guess": no such file or directory }}} This happened on Mac OS 10.6.8. -- Comment: /opt/local/share/automake-1.16/config.guess should exist, provided by the automake port, which is a dependency of xar. Reinstall automake? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:29:16 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 03:29:16 -0000 Subject: [MacPorts] #66429: gettext-tools-libs fails to install on Mac OS 10.6 (was: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0) In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.af9d986425764c0edfed54bd62d38c9c@macports.org> #66429: gettext-tools-libs fails to install on Mac OS 10.6 ---------------------------------+--------------------------------- Reporter: programmingkidx | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: gettext snowleopard Port: gettext-tools-libs | ---------------------------------+--------------------------------- Changes (by jmroot): * cc: larryv (removed) * keywords: snowleopard => gettext snowleopard * port: llvm-3.4 => gettext-tools-libs Old description: > While trying to install gettext-tools-libs I saw this error: > > {{{ > Error: Failed to configure gettext-tools-libs: configure failure: command > execution failed > }}} > > Here is an error from the log: > > {{{ > dyld: Library not loaded: > /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib > Referenced from: /opt/local/libexec/llvm-3.4/bin/clang > Reason: Incompatible library version: clang requires version 1.0.0 or > later, but libLLVM-3.4.dylib provides version 0.0.0 > ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 > configure:5552: $? = 133 > }}} New description: While trying to install gettext-tools-libs I saw this error: Error: Failed to configure gettext-tools-libs: configure failure: command execution failed Here is an error from the log: dyld: Library not loaded: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib Referenced from: /opt/local/libexec/llvm-3.4/bin/clang Reason: Incompatible library version: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 configure:5552: $? = 133 -- Comment: The clang-3.4 port doesn't depend on gettext-tools-libs - unless of course you are missing /usr/bin/perl like you were missing /usr/bin/patch in #66414. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:31:33 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 03:31:33 -0000 Subject: [MacPorts] #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 (was: gettext-tools-libs fails to install on Mac OS 10.6) In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.2b13dfd9f1fe97a7f41c03869e7fce0f@macports.org> #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ------------------------------+------------------------- Reporter: programmingkidx | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: llvm-3.4 | ------------------------------+------------------------- Changes (by jmroot): * cc: larryv (added) * keywords: gettext snowleopard => snowleopard * port: gettext-tools-libs => llvm-3.4 Old description: > While trying to install gettext-tools-libs I saw this error: > > Error: Failed to configure gettext-tools-libs: configure failure: command > execution failed > > Here is an error from the log: > > dyld: Library not loaded: > /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib > Referenced from: /opt/local/libexec/llvm-3.4/bin/clang > Reason: Incompatible library version: clang requires version 1.0.0 or > later, but libLLVM-3.4.dylib provides version 0.0.0 > ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 > configure:5552: $? = 133 New description: While trying to install gettext-tools-libs I saw this error: {{{ Error: Failed to configure gettext-tools-libs: configure failure: command execution failed }}} Here is an error from the log: {{{ dyld: Library not loaded: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib Referenced from: /opt/local/libexec/llvm-3.4/bin/clang Reason: Incompatible library version: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ./configure: line 5543: 17094 Trace/BPT trap $CC --version 1>&5 configure:5552: $? = 133 }}} -- Comment: Ugh, ticket was edited while I wrote my comment, sorry. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:35:53 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 03:35:53 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.8cefa040eafff0c23f1ba40d5686fe88@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Comment (by jmroot): The log actually says {{{ :debug:configure upgrade autoconf failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:49:28 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 03:49:28 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.468e17de8ba15252365da7fe72597634@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by jmroot): Sounds like you didn't select UNIX subsystem (or whatever the installer calls it) when installing the OS. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 03:55:04 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 03:55:04 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.9e6f0b599785643f23b621509deb1c2e@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by jmroot): Actually I misremembered, that was no longer an option in the installer by 10.6. So no idea how you got into this state, but it's going to be a serious problem if parts of the base OS are missing. We can't possibly support such a configuration. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 06:22:25 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 06:22:25 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.b21ba62a47d73533c0d67bfc6d9927ea@macports.org> #66365: Failed to build libgcc-devel: command execution failed ---------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Comment (by slackero): Just to be more clear with this ticket: This bug reports is related to the Apple Silicon platform. The current Portfile differs between Intel (v13-20221204) and Arm (v12-20221202). If you check https://ports.macports.org/port/libgcc-devel/ you see v13-20221204 but on Arm it uses v12-20221202 only which is related to the commit https://github.com/iains/gcc-darwin- arm64/commit/d679055c574a09f11b860dfa596917919124120a. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:06:39 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:06:39 -0000 Subject: [MacPorts] #66241: gettext @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) In-Reply-To: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> References: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> Message-ID: <061.6ecb0323e4588b45dda853bd6a57246f@macports.org> #66241: gettext @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) ------------------------------------+------------------------ Reporter: bakergilx | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gettext, libtextstyle | ------------------------------------+------------------------ Changes (by judaew): * cc: judaew (added) * port: gettext => gettext, libtextstyle -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:07:44 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:07:44 -0000 Subject: [MacPorts] #66241: gettext, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) (was: gettext @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax)) In-Reply-To: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> References: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> Message-ID: <061.4f34ec7bb86a4ecf7af220a73ff96d65@macports.org> #66241: gettext, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) ------------------------------------+------------------------ Reporter: bakergilx | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gettext, libtextstyle | ------------------------------------+------------------------ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:08:03 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:08:03 -0000 Subject: [MacPorts] #66241: gettext, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) In-Reply-To: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> References: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> Message-ID: <061.5b67009f369b2894b326ce261fdb128f@macports.org> #66241: gettext, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) ------------------------------------+------------------------ Reporter: bakergilx | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gettext, libtextstyle | ------------------------------------+------------------------ Changes (by judaew): * Attachment "libtextstyle-config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:09:38 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:09:38 -0000 Subject: [MacPorts] #66241: gettext, gettext-tools-libs, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) (was: gettext, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax)) In-Reply-To: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> References: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> Message-ID: <061.55bd2bdefa5f5202c9d3a3750379bbde@macports.org> #66241: gettext, gettext-tools-libs, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) -------------------------------------------------+------------------------- Reporter: bakergilx | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gettext, gettext-tools-libs, | libtextstyle | -------------------------------------------------+------------------------- Changes (by judaew): * port: gettext, libtextstyle => gettext, gettext-tools-libs, libtextstyle -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:09:48 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:09:48 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.9bf3133185feeac062af0a85d09b41b5@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): In another log file I saw these lines that are missing here: {{{ MACPORTS_LEGACY_SUPPORT_CPPFLAGS='-isystem/opt/local/include/LegacySupport' MACPORTS_LEGACY_SUPPORT_ENABLED='1' MACPORTS_LEGACY_SUPPORT_LDFLAGS='-L/opt/local/lib -lMacportsLegacySupport' }}} which are probably introduced by this line in `Portfile`: {{{ PortGroup legacysupport 1.1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:11:01 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:11:01 -0000 Subject: [MacPorts] #66241: gettext, gettext-tools-libs, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) In-Reply-To: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> References: <046.4f250db31cad95d4436c2569070c1d6e@macports.org> Message-ID: <061.07cc6b7b6b7e1c5f036a545d279fb57d@macports.org> #66241: gettext, gettext-tools-libs, libtextstyle @0.21_0 Warning Configuration logfile contain indications of -Wimplicit-function-declaration (re_search, re_compile_pattern, re_set_syntax) -------------------------------------------------+------------------------- Reporter: bakergilx | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gettext, gettext-tools-libs, | libtextstyle | -------------------------------------------------+------------------------- Comment (by judaew): It's all related to gettext. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:16:12 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:16:12 -0000 Subject: [MacPorts] #66431: bash: Configuration logfiles contain indications of -Wimplicit-function-declaration in strchr and dup2 Message-ID: <043.ef83d265567921ac786c8942bb3c0692@macports.org> #66431: bash: Configuration logfiles contain indications of -Wimplicit-function- declaration in strchr and dup2 --------------------------------------------+---------------------- Reporter: judaew | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: wimplicit-function-declaration | Port: bash --------------------------------------------+---------------------- {{{ Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: strchr: found in bash-5.2/config.log dup2: found in bash-5.2/config.log }}} See WimplicitFunctionDeclaration. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:16:29 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:16:29 -0000 Subject: [MacPorts] #66431: bash: Configuration logfiles contain indications of -Wimplicit-function-declaration in strchr and dup2 In-Reply-To: <043.ef83d265567921ac786c8942bb3c0692@macports.org> References: <043.ef83d265567921ac786c8942bb3c0692@macports.org> Message-ID: <058.73bfe24e2204b78fee26c0a9e1a2399a@macports.org> #66431: bash: Configuration logfiles contain indications of -Wimplicit-function- declaration in strchr and dup2 ---------------------+-------------------------------------------- Reporter: judaew | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: bash | ---------------------+-------------------------------------------- Changes (by judaew): * Attachment "bash-config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:22:50 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:22:50 -0000 Subject: [MacPorts] #66432: xz: Configuration logfiles contain indications of -Wimplicit-function-declaration in CPU_COUNT and sched_getaffinity Message-ID: <043.647819bdaf29c9e723c83306579835d6@macports.org> #66432: xz: Configuration logfiles contain indications of -Wimplicit-function- declaration in CPU_COUNT and sched_getaffinity --------------------------------------------+------------------------ Reporter: judaew | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: wimplicit-function-declaration | Port: xz --------------------------------------------+------------------------ {{{ Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: CPU_COUNT: found in xz-5.2.9/config.log sched_getaffinity: found in xz-5.2.9/config.log }}} See WimplicitFunctionDeclaration. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:23:12 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:23:12 -0000 Subject: [MacPorts] #66432: xz: Configuration logfiles contain indications of -Wimplicit-function-declaration in CPU_COUNT and sched_getaffinity In-Reply-To: <043.647819bdaf29c9e723c83306579835d6@macports.org> References: <043.647819bdaf29c9e723c83306579835d6@macports.org> Message-ID: <058.bc998cc170402134a62836d9be14f527@macports.org> #66432: xz: Configuration logfiles contain indications of -Wimplicit-function- declaration in CPU_COUNT and sched_getaffinity ---------------------+-------------------------------------------- Reporter: judaew | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: xz | ---------------------+-------------------------------------------- Changes (by judaew): * Attachment "xz-config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:32:23 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:32:23 -0000 Subject: [MacPorts] #66433: m4: Configuration logfiles contain indications of -Wimplicit-function-declaration Message-ID: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> #66433: m4: Configuration logfiles contain indications of -Wimplicit-function- declaration --------------------------------------------+---------------------- Reporter: judaew | Owner: (none) Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: wimplicit-function-declaration | Port: m4 --------------------------------------------+---------------------- {{{ Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: re_search: found in m4-1.4.19/config.log re_compile_pattern: found in m4-1.4.19/config.log re_set_syntax: found in m4-1.4.19/config.log MIN: found in m4-1.4.19/config.log __fpending: found in m4-1.4.19/config.log strchr: found in m4-1.4.19/config.log }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:32:33 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:32:33 -0000 Subject: [MacPorts] #66433: m4: Configuration logfiles contain indications of -Wimplicit-function-declaration In-Reply-To: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> References: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> Message-ID: <058.04ae05ef2e2d2457651d5212c080957c@macports.org> #66433: m4: Configuration logfiles contain indications of -Wimplicit-function- declaration ---------------------+-------------------------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: m4 | ---------------------+-------------------------------------------- Changes (by judaew): * Attachment "xz-config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:34:22 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:34:22 -0000 Subject: [MacPorts] #66433: m4: Configuration logfiles contain indications of -Wimplicit-function-declaration In-Reply-To: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> References: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> Message-ID: <058.439bc4f226c785d6639f535304496e4b@macports.org> #66433: m4: Configuration logfiles contain indications of -Wimplicit-function- declaration ---------------------+-------------------------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: m4 | ---------------------+-------------------------------------------- Description changed by judaew: Old description: > {{{ > Warning: Configuration logfiles contain indications of -Wimplicit- > function-declaration; check that features were not accidentally disabled: > re_search: found in m4-1.4.19/config.log > re_compile_pattern: found in m4-1.4.19/config.log > re_set_syntax: found in m4-1.4.19/config.log > MIN: found in m4-1.4.19/config.log > __fpending: found in m4-1.4.19/config.log > strchr: found in m4-1.4.19/config.log > }}} New description: {{{ Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: re_search: found in m4-1.4.19/config.log re_compile_pattern: found in m4-1.4.19/config.log re_set_syntax: found in m4-1.4.19/config.log MIN: found in m4-1.4.19/config.log __fpending: found in m4-1.4.19/config.log strchr: found in m4-1.4.19/config.log }}} See WimplicitFunctionDeclaration. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:37:09 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:37:09 -0000 Subject: [MacPorts] #66434: libunistring: Configuration logfiles contain indications of -Wimplicit-function-declaration in alignof and MIN Message-ID: <043.6f15ba2b0b5518521542b1d880c56664@macports.org> #66434: libunistring: Configuration logfiles contain indications of -Wimplicit- function-declaration in alignof and MIN --------------------------------------------+-------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: wimplicit-function-declaration | Port: libunistring --------------------------------------------+-------------------------- {{{ Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: alignof: found in libunistring-1.1/config.log MIN: found in libunistring-1.1/config.log }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:37:18 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:37:18 -0000 Subject: [MacPorts] #66434: libunistring: Configuration logfiles contain indications of -Wimplicit-function-declaration in alignof and MIN In-Reply-To: <043.6f15ba2b0b5518521542b1d880c56664@macports.org> References: <043.6f15ba2b0b5518521542b1d880c56664@macports.org> Message-ID: <058.bd1ae597ecd4a1d87d5fe17d8329effa@macports.org> #66434: libunistring: Configuration logfiles contain indications of -Wimplicit- function-declaration in alignof and MIN ---------------------------+-------------------------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: libunistring | ---------------------------+-------------------------------------------- Changes (by judaew): * Attachment "libunistring-config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:39:09 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:39:09 -0000 Subject: [MacPorts] #66434: libunistring: Configuration logfiles contain indications of -Wimplicit-function-declaration in alignof and MIN In-Reply-To: <043.6f15ba2b0b5518521542b1d880c56664@macports.org> References: <043.6f15ba2b0b5518521542b1d880c56664@macports.org> Message-ID: <058.2495b57b07aa289edcac90e65031c580@macports.org> #66434: libunistring: Configuration logfiles contain indications of -Wimplicit- function-declaration in alignof and MIN ---------------------------+-------------------------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: libunistring | ---------------------------+-------------------------------------------- Description changed by judaew: Old description: > {{{ > Warning: Configuration logfiles contain indications of -Wimplicit- > function-declaration; check that features were not accidentally disabled: > alignof: found in libunistring-1.1/config.log > MIN: found in libunistring-1.1/config.log > }}} New description: {{{ Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: alignof: found in libunistring-1.1/config.log MIN: found in libunistring-1.1/config.log }}} See WimplicitFunctionDeclaration. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:41:31 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:41:31 -0000 Subject: [MacPorts] #66435: pkgconfig: Configuration logfiles contain indications of -Wimplicit-function-declaration Message-ID: <043.621bd4634ae46f9bcb4d7c72138e7331@macports.org> #66435: pkgconfig: Configuration logfiles contain indications of -Wimplicit- function-declaration --------------------------------------------+------------------------ Reporter: judaew | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: wimplicit-function-declaration | Port: pkgconfig --------------------------------------------+------------------------ {{{ ---> Configuring pkgconfig Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: pthread_cond_timedwait_monotonic_np: found in pkg- config-0.29.2/glib/config.log pthread_condattr_setclock: found in pkg-config-0.29.2/glib/config.log strcmp: found in pkg-config-0.29.2/glib/config.log exit: found in pkg-config-0.29.2/glib/config.log pthread_cond_timedwait_monotonic: found in pkg- config-0.29.2/glib/config.log }}} See WimplicitFunctionDeclaration. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:41:41 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:41:41 -0000 Subject: [MacPorts] #66435: pkgconfig: Configuration logfiles contain indications of -Wimplicit-function-declaration In-Reply-To: <043.621bd4634ae46f9bcb4d7c72138e7331@macports.org> References: <043.621bd4634ae46f9bcb4d7c72138e7331@macports.org> Message-ID: <058.802e17567159c51eea6a0c85a03992da@macports.org> #66435: pkgconfig: Configuration logfiles contain indications of -Wimplicit- function-declaration ------------------------+-------------------------------------------- Reporter: judaew | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: pkgconfig | ------------------------+-------------------------------------------- Changes (by judaew): * Attachment "pkgconfig-config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:42:48 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:42:48 -0000 Subject: [MacPorts] #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) In-Reply-To: <048.4862f7c021d74aba503c089a8538c3db@macports.org> References: <048.4862f7c021d74aba503c089a8538c3db@macports.org> Message-ID: <063.bfd84846fce30e5e9cf05b96401dd918@macports.org> #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) --------------------------+---------------------- Reporter: c-kloukinas | Owner: easye Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: slime | --------------------------+---------------------- Comment (by easye): In [changeset:"aa2a8b0c3f992a7d77659d873f369ffc46c19381/macports-ports" aa2a8b0c3f992a7d77659d873f369ffc46c19381/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="aa2a8b0c3f992a7d77659d873f369ffc46c19381" lang/slime: update to slime-2.27 Possibly addresses . }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:43:39 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:43:39 -0000 Subject: [MacPorts] #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) In-Reply-To: <048.4862f7c021d74aba503c089a8538c3db@macports.org> References: <048.4862f7c021d74aba503c089a8538c3db@macports.org> Message-ID: <063.879517ff3defc6ff149943fc69ed817b@macports.org> #66406: slime @2.20_1 cannot upgrade (missing arg in lisp function in hyperspec.el #1318 - with solution) --------------------------+-------------------- Reporter: c-kloukinas | Owner: easye Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: slime | --------------------------+-------------------- Changes (by easye): * status: assigned => closed * resolution: => fixed Comment: slime-2.27 committed in Closing this for now: lemme know if you still have problems with the newer version of SLIME. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:46:10 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:46:10 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.6c2b574eb60fc3b3b3364aa57e6a6858@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): By adding this line to `Portfile` I have now: {{{ libdeflate @1.14_0 requested_variants='' platform='darwin 9' archs='ppc' date='2022-09-18T19:17:07+0200' libdeflate @1.15_0 (active) requested_variants='' platform='darwin 9' archs='ppc' date='2022-12-10T10:42:04+0100' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 09:53:05 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 09:53:05 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.4262a2f4df6b5d365bd47bbfd8cd3db9@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by herbygillot): In [changeset:"1b0db84ddb25894c5f38ebda21221c1d08ce587c/macports-ports" 1b0db84ddb25894c5f38ebda21221c1d08ce587c/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1b0db84ddb25894c5f38ebda21221c1d08ce587c" libdeflate: use legacysupport pg See: https://trac.macports.org/ticket/66425 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 10:00:55 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 10:00:55 -0000 Subject: [MacPorts] #66410: ps2eps @1.70_0 stealth update In-Reply-To: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> References: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> Message-ID: <058.729fb5d6706d5d717eda0c8cf229493d@macports.org> #66410: ps2eps @1.70_0 stealth update ---------------------+-------------------- Reporter: hmeine | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ps2eps | ---------------------+-------------------- Changes (by easye): * cc: easiest (added) Comment: I can confirm that upgrading ps2eps is not currently working for me, due to differing checksums. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 10:01:12 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 10:01:12 -0000 Subject: [MacPorts] #66410: ps2eps @1.70_0 stealth update In-Reply-To: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> References: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> Message-ID: <058.ab08490f43c86ae40da003b22603fd3d@macports.org> #66410: ps2eps @1.70_0 stealth update ---------------------+-------------------- Reporter: hmeine | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ps2eps | ---------------------+-------------------- Changes (by easye): * cc: easiest (removed) * cc: easieste (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 10:03:23 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 10:03:23 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.f4bf66ccdd22c2c8007a2679713839b3@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by herbygillot): OK, `legacysupport` has been added in the previously referenced commit. I think this should resolve the issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 11:25:19 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 11:25:19 -0000 Subject: [MacPorts] #66436: cctools checksum fail Message-ID: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> #66436: cctools checksum fail --------------------+--------------------- Reporter: gplunk | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cctools --------------------+--------------------- I have no clue about this. I read the FAQ about checksum errors and found nothing that helped. sudo port install cctools ---> Computing dependencies for cctools ---> Fetching archive for cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://packages.macports.org/cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://fra.de.packages.macports.org/cctools ---> Fetching distfiles for cctools ---> Attempting to fetch ld64-530.tar.gz from https://opensource.apple.com/tarballs/ld64 ---> Attempting to fetch cctools-949.0.1.tar.gz from https://opensource.apple.com/tarballs/cctools ---> Verifying checksums for cctools Error: Checksum (rmd160) mismatch for ld64-530.tar.gz Error: Checksum (sha256) mismatch for ld64-530.tar.gz Error: Checksum (size) mismatch for ld64-530.tar.gz Error: Checksum (rmd160) mismatch for cctools-949.0.1.tar.gz Error: Checksum (sha256) mismatch for cctools-949.0.1.tar.gz Error: Checksum (size) mismatch for cctools-949.0.1.tar.gz Error: Failed to checksum cctools: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port cctools failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 12:00:34 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 12:00:34 -0000 Subject: [MacPorts] #66436: cctools checksum fail In-Reply-To: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> References: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> Message-ID: <058.30893a4ab2bd910f33d942b54fc61f07@macports.org> #66436: cctools checksum fail ----------------------+-------------------- Reporter: gplunk | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+-------------------- Comment (by gplunk): I looked into this more. I first determined the directory where the distribution files are supposed to be created port distfiles cctools This directory was in fact not even created. Is it possible that the checksum failed because it could not even download the distribution files? That is odd. So I downloaded the files manually (https://trac.macports.org/wiki/ProblemHotlist#fetch-failures), created the directory and put them there. Then I tried sudo port install cctools and it failed: ---> Computing dependencies for cctools ---> Fetching archive for cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://packages.macports.org/cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://fra.de.packages.macports.org/cctools ---> Fetching distfiles for cctools ---> Verifying checksums for cctools ---> Extracting cctools ---> Applying patches to cctools Warning: reinplace /^COMMON_SUBDIRS/s/ ld / / didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/Makefile Warning: reinplace s:"llvm-mc":"llvm-mc-mp-10": didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/cctools-949.0.1/as/driver.c ---> Configuring cctools ---> Building cctools Error: Failed to build cctools: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port cctools failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 12:46:55 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 12:46:55 -0000 Subject: [MacPorts] #66436: cctools @949.0.1_2 checksum mismatch (was: cctools checksum fail) In-Reply-To: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> References: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> Message-ID: <058.55ebd4248131ae44cf415844a8afb843@macports.org> #66436: cctools @949.0.1_2 checksum mismatch ----------------------+---------------------- Reporter: gplunk | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => jeremyhu Old description: > I have no clue about this. I read the FAQ about checksum errors and > found nothing that helped. > > sudo port install cctools > > ---> Computing dependencies for cctools > ---> Fetching archive for cctools > ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 > from https://nue.de.packages.macports.org/cctools > ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 > from https://packages.macports.org/cctools > ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 > from https://fra.de.packages.macports.org/cctools > ---> Fetching distfiles for cctools > ---> Attempting to fetch ld64-530.tar.gz from > https://opensource.apple.com/tarballs/ld64 > ---> Attempting to fetch cctools-949.0.1.tar.gz from > https://opensource.apple.com/tarballs/cctools > ---> Verifying checksums for cctools > Error: Checksum (rmd160) mismatch for ld64-530.tar.gz > Error: Checksum (sha256) mismatch for ld64-530.tar.gz > Error: Checksum (size) mismatch for ld64-530.tar.gz > Error: Checksum (rmd160) mismatch for cctools-949.0.1.tar.gz > Error: Checksum (sha256) mismatch for cctools-949.0.1.tar.gz > Error: Checksum (size) mismatch for cctools-949.0.1.tar.gz > Error: Failed to checksum cctools: Unable to verify file checksums > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > Error: Processing of port cctools failed New description: I have no clue about this. I read the FAQ about checksum errors and found nothing that helped. {{{ sudo port install cctools ---> Computing dependencies for cctools ---> Fetching archive for cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://packages.macports.org/cctools ---> Attempting to fetch cctools-949.0.1_2+llvm10.darwin_22.arm64.tbz2 from https://fra.de.packages.macports.org/cctools ---> Fetching distfiles for cctools ---> Attempting to fetch ld64-530.tar.gz from https://opensource.apple.com/tarballs/ld64 ---> Attempting to fetch cctools-949.0.1.tar.gz from https://opensource.apple.com/tarballs/cctools ---> Verifying checksums for cctools Error: Checksum (rmd160) mismatch for ld64-530.tar.gz Error: Checksum (sha256) mismatch for ld64-530.tar.gz Error: Checksum (size) mismatch for ld64-530.tar.gz Error: Checksum (rmd160) mismatch for cctools-949.0.1.tar.gz Error: Checksum (sha256) mismatch for cctools-949.0.1.tar.gz Error: Checksum (size) mismatch for cctools-949.0.1.tar.gz Error: Failed to checksum cctools: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port cctools failed }}} -- Comment: `https://opensource.apple.com/tarballs` is no longer serving the files; it now redirects to `https://github.com/apple-oss-distributions` which doesn't have identical files, though the extracted contents are probably the same. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:28:19 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 15:28:19 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. Message-ID: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. --------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: svt-av1 --------------------+------------------------ I'm seeing gn this configure error on Monterey Intel. {{{ :info:configure Executing: cd "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0 :debug:configure system: cd "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0 :info:configure CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. :info:configure Specify --help for usage, or press the help button on the CMake GUI. }}} Indeed the directory "SVT-AV1-1.4.0" does not exist. But "SVT- AV1-v1.4.0-5f32f7b4af71af8501810e4716eb1fbe89d80574" does. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:28:51 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 15:28:51 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.e1a8b8e9c9889d364ebaf3cc13e8f102@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Changes (by mf2k): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:29:14 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 15:29:14 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.94cd5d363ff8fa006bb01fb675016491@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Description changed by mf2k: Old description: > I'm seeing gn this configure error on Monterey Intel. > > {{{ > :info:configure Executing: cd "/opt/local/var/macports/build > /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && > /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" > -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" > -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" > -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" > -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" > -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW > -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST > -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make > -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON > -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev > -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" > -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" > /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- > av1/svt-av1/work/SVT-AV1-1.4.0 > :debug:configure system: cd "/opt/local/var/macports/build > /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && > /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" > -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" > -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" > -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" > -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" > -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW > -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST > -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make > -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON > -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev > -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" > -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" > /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- > av1/svt-av1/work/SVT-AV1-1.4.0 > :info:configure CMake Error: The source directory > "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- > av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. > :info:configure Specify --help for usage, or press the help button on the > CMake GUI. > }}} > > Indeed the directory "SVT-AV1-1.4.0" does not exist. But "SVT- > AV1-v1.4.0-5f32f7b4af71af8501810e4716eb1fbe89d80574" does. New description: I'm seeing this configure error on Monterey Intel. {{{ :info:configure Executing: cd "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0 :debug:configure system: cd "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0 :info:configure CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. :info:configure Specify --help for usage, or press the help button on the CMake GUI. }}} Indeed the directory "SVT-AV1-1.4.0" does not exist. But "SVT- AV1-v1.4.0-5f32f7b4af71af8501810e4716eb1fbe89d80574" does. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 15:45:18 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 15:45:18 -0000 Subject: [MacPorts] #66438: Error: Failed to configure spice-gtk: consult Message-ID: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> #66438: Error: Failed to configure spice-gtk: consult -----------------------+-------------------------- Reporter: ANONIMNIQ | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: virt-manager -----------------------+-------------------------- Error: Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt Error: Failed to configure spice-gtk: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port virt-manager failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:06:18 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 16:06:18 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.a204c0106c25648a047eac56e93461ab@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Comment (by programmingkidx): This issue has been resolved for me. Feel free to close the ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:32:49 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 16:32:49 -0000 Subject: [MacPorts] #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.1f40a138aab37c15758454d289724082@macports.org> #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ------------------------------+------------------------- Reporter: programmingkidx | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: llvm-3.4 | ------------------------------+------------------------- Comment (by programmingkidx): @jmroot I just checked and I do have /usr/bin/perl. Here is its output: $ /usr/bin/perl -v This is perl, v5.10.0 built for darwin-thread-multi-2level (with 2 registered patches, see perl -V for more detail) Copyright 1987-2007, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using "man perl" or "perldoc perl". If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. I made this small test program and it worked: {{{ #!/usr/bin/perl # Modules used use strict; use warnings; # Print function print("Hello World\n"); }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 16:46:38 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 16:46:38 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.29364dcff37ed472efdf9aa5011b45fa@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Comment (by programmingkidx): @ryandesign I ran 'sudo port install automake' and was told I had to reinstall all these ports: {{{ ---> Found 106 broken files, matching files to ports Warning: No port ld64-136 found in the index; can't rebuild ---> Found 27 broken ports, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: p7zip @9.04 db48 @4.8.30+java+universal opensp @1.5.2+universal openjade @1.3.2+universal icu @54.1+universal graphite2 @1.2.4+universal tiff @4.0.3+universal djvulibre @3.5.25+universal ilmbase @1.0.2+universal openexr @1.7.0+universal db46 @4.6.21+universal boost @1.57.0+no_single+no_static+python27+universal source-highlight @3.1.7+universal pcre @8.38+universal glib2 @2.48.0+universal harfbuzz @0.9.37+universal ImageMagick @6.9.0-0+universal+x11 libproxy @0.4.13+python27+universal gobject-introspection @1.48.0+universal p11-kit @0.23.2+universal gnutls @3.4.11+universal llvm-3.4 @3.4.2+universal ld64-127 @127.2+llvm34+universal cctools @862+llvm34+universal clang-3.4 @3.4.2+universal gperf @3.0.4 mesa @7.6.1+hw_render }}} I then said yes and libedit as fetched. It then failed to build. This is what it said: Error: Failed to configure libedit I looked at its log and saw this familar sight {{{ configure:3199: /opt/local/bin/clang-mp-3.4 --version >&5 dyld: Library not loaded: /opt/local/libexec/llvm-3.4/lib/libLLVM-3.4.dylib Referenced from: /opt/local/libexec/llvm-3.4/bin/clang Reason: Incompatible library version: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ./configure: line 3201: 552 Trace/BPT trap $CC --version 1>&5 configure:3210: $? = 133 }}} Is there anyone who has Mac OS 10.6 who can confirm anything I am seeing? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:13:37 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 17:13:37 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.f306680b5cb81ff959b1c0fe9c7571ec@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Comment (by kencu): your ports are extremely outdated. ld64-136 was removed about 5 years ago. Your libffi is several years out too. IMHO start over. deactivate everything, or better yet uninstall everything as much is broken, run selfupdate, then install what you want to install. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:14:45 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 17:14:45 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.473257d3808bf9c9a744e03314d12ffa@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Comment (by kencu): also make sure your macports.conf is current, not from 2016 or similar. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:42:15 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 17:42:15 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.5f01cd8b42c7b1c2350ca72cf6f44eee@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Description changed by mf2k: Old description: > I'm seeing this configure error on Monterey Intel. > > {{{ > :info:configure Executing: cd "/opt/local/var/macports/build > /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && > /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" > -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" > -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" > -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" > -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" > -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW > -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST > -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make > -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON > -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev > -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" > -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" > /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- > av1/svt-av1/work/SVT-AV1-1.4.0 > :debug:configure system: cd "/opt/local/var/macports/build > /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && > /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" > -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" > -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" > -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" > -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" > -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW > -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON > -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST > -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make > -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" > -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON > -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev > -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" > -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" > /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- > av1/svt-av1/work/SVT-AV1-1.4.0 > :info:configure CMake Error: The source directory > "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- > av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. > :info:configure Specify --help for usage, or press the help button on the > CMake GUI. > }}} > > Indeed the directory "SVT-AV1-1.4.0" does not exist. But "SVT- > AV1-v1.4.0-5f32f7b4af71af8501810e4716eb1fbe89d80574" does. New description: I'm seeing this configure error on Monterey Intel. {{{ :info:configure Executing: cd "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0 :debug:configure system: cd "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="13.0" -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk" /opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0 :info:configure CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt- av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. :info:configure Specify --help for usage, or press the help button on the CMake GUI. }}} Indeed the directory {{{SVT-AV1-1.4.0}}} does not exist. But {{{SVT- AV1-v1.4.0-5f32f7b4af71af8501810e4716eb1fbe89d80574}}} does. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:55:04 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 17:55:04 -0000 Subject: [MacPorts] #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile In-Reply-To: <046.555f7ae3c563228c6413868d979d4b78@macports.org> References: <046.555f7ae3c563228c6413868d979d4b78@macports.org> Message-ID: <061.6afa3549df1dc1cbca6ed5c7f9c44fdb@macports.org> #66418: cppcheck @2.9.3 does not build on PPC Tiger, Mac OS X 10.4.11, because of Extraneous text after `else' directive in Makefile ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: cppcheck | ------------------------+----------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"8c115a72c251e8b94b44e11a7f11be57cb33bd8a/macports-ports" 8c115a72c251e8b94b44e11a7f11be57cb33bd8a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8c115a72c251e8b94b44e11a7f11be57cb33bd8a" cppcheck: use newer gmake on Tiger closes: https://trac.macports.org/ticket/66418 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 17:55:04 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 17:55:04 -0000 Subject: [MacPorts] #66413: cppcheck @2.9.3 CXXFLAGS reinplace didn't change anything In-Reply-To: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> References: <046.e37b3f6462f1df242e8674e709ae199b@macports.org> Message-ID: <061.4b4e6262fa8095f272af088d0bcf4620@macports.org> #66413: cppcheck @2.9.3 CXXFLAGS reinplace didn't change anything ------------------------+---------------------------- Reporter: ballapete | Owner: kurthindenburg Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: cppcheck | ------------------------+---------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"588c79f87038ba29d24e0eb30d966d6d717bf2db/macports-ports" 588c79f87038ba29d24e0eb30d966d6d717bf2db/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="588c79f87038ba29d24e0eb30d966d6d717bf2db" cppcheck: use MP CXXFLAGS the Makefile has changed, the previous reinplace doesn't work now closes: https://trac.macports.org/ticket/66413 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 18:22:06 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 18:22:06 -0000 Subject: [MacPorts] #66283: compilers portgroup is not correctly testing for gcc_v In-Reply-To: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> References: <046.3131099f9893e4b1b8361e59a373e38f@macports.org> Message-ID: <061.92f61beb6dfa9d564f148e62275d3a00@macports.org> #66283: compilers portgroup is not correctly testing for gcc_v ---------------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: boost176, boost171 | ---------------------------------+-------------------- Changes (by kencu): * keywords: tiger ppc => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 18:22:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 18:22:56 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.4d3d6b7c90077c54e7999ed256aa6acb@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Comment (by mf2k): The difference between my setup and the builder, where it builds fine, is that I am using Xcode 14.1 with MACOSX13 SDK. The builder has Xcode 13.2 with MACOSX12 SDK. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 18:26:12 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 18:26:12 -0000 Subject: [MacPorts] #50716: libffi @3.2.1 fails to build on Intel 10.4.11 Tiger: Unknown pseudo-op: .balign In-Reply-To: <050.121d492607a092c1d86762756346991d@macports.org> References: <050.121d492607a092c1d86762756346991d@macports.org> Message-ID: <065.44b14f2f42cb893e5083b629b5c89693@macports.org> #50716: libffi @3.2.1 fails to build on Intel 10.4.11 Tiger: Unknown pseudo-op: .balign ----------------------+-------------------------------- Reporter: kujo3@? | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: tiger Port: libffi | ----------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: libffi builds on Tiger now -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:21:40 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:21:40 -0000 Subject: [MacPorts] #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link In-Reply-To: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> References: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> Message-ID: <061.78ff729a83058f42a7f23bc5df3fc3f9@macports.org> #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link ------------------------+--------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: leopard Port: qpdf | ------------------------+--------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"eefb1879f79653ad670db3b1f8d41748ff46ce49/macports-ports" eefb1879f79653ad670db3b1f8d41748ff46ce49/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="eefb1879f79653ad670db3b1f8d41748ff46ce49" qpdf: fix build on Tiger closes: https://trac.macports.org/ticket/62911 previously an issue with -latomic was identified, but this appears to have been fixed upstream as it no longer occurs }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:22:20 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:22:20 -0000 Subject: [MacPorts] #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link In-Reply-To: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> References: <046.0a6757b87bc8ff63c0cf2a535cf86d0e@macports.org> Message-ID: <061.b0a1af9e5c5eabc7fa49c9f9b15cb1df@macports.org> #62911: qpdf @10.3.1 cannot be built with gcc because -latomic is not included in the link ------------------------+--------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: leopard Port: qpdf | ------------------------+--------------------- Comment (by kencu): {{{ $ port -v installed qpdf The following ports are currently installed: qpdf @11.2.0_0+gnutls (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-12-10T12:20:09-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:24:28 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:24:28 -0000 Subject: [MacPorts] #44384: libpaper fails to build on OS X Tiger In-Reply-To: <058.e8c74b5eb89b5ec3244512d0d0d4c4a9@macports.org> References: <058.e8c74b5eb89b5ec3244512d0d0d4c4a9@macports.org> Message-ID: <073.1e655e100d1ecdd28a7bb35efcc15d9c@macports.org> #44384: libpaper fails to build on OS X Tiger --------------------------+-------------------------------- Reporter: djlambe11@? | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: fixed | Keywords: tiger Port: libpaper | --------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: fixed at some point {{{ $ port -v installed libpaper The following ports are currently installed: libpaper @1.1.28_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-12-06T22:01:04-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:26:11 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:26:11 -0000 Subject: [MacPorts] #46642: apple-gcc42 @5666.3_14 +bootstrap on Tiger PPC fails to build In-Reply-To: <070.41bc096a8934a51c3546e34b61faf8be@macports.org> References: <070.41bc096a8934a51c3546e34b61faf8be@macports.org> Message-ID: <085.75953ad7cd7bf1e31e5e32b73ddf273d@macports.org> #46642: apple-gcc42 @5666.3_14 +bootstrap on Tiger PPC fails to build -----------------------------+------------------------ Reporter: snipsnipsnip@? | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: tiger Port: apple-gcc42 | -----------------------------+------------------------ Changes (by kencu): * status: new => closed * resolution: => fixed Comment: fixed at some point in the last decade: {{{ $ port -v installed | grep gcc42 apple-gcc42 @5666.3_16+bootstrap requested_variants='' platform='darwin 8' archs='ppc' date='2022-01-12T11:44:12-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:27:30 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:27:30 -0000 Subject: [MacPorts] #46837: kerberos5 fails to build on 10.4ppc In-Reply-To: <056.15265161cdf7aaec021c4c620e2efac9@macports.org> References: <056.15265161cdf7aaec021c4c620e2efac9@macports.org> Message-ID: <071.96aa97ecbc2d8c018afccebfee2cc690@macports.org> #46837: kerberos5 fails to build on 10.4ppc --------------------------+--------------------------- Reporter: dsmithhfx@? | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: tiger powerpc Port: kerberos5 | --------------------------+--------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: fixed at some point: {{{ $ port -v installed kerberos5 The following ports are currently installed: kerberos5 @1.19.2_1 requested_variants='' platform='darwin 8' archs='ppc' date='2022-02-21T14:58:53-0800' kerberos5 @1.20_0 requested_variants='' platform='darwin 8' archs='ppc' date='2022-08-17T17:48:48-0700' kerberos5 @1.20.1_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-11-28T14:37:13-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:28:20 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:28:20 -0000 Subject: [MacPorts] #47006: kerberos5 @1.13 10.4 build failure unititialised object In-Reply-To: <044.a8a58e9cf15c030195270f93eec3c5ff@macports.org> References: <044.a8a58e9cf15c030195270f93eec3c5ff@macports.org> Message-ID: <059.abb13078a4f233e6309c9943cbc8120f@macports.org> #47006: kerberos5 @1.13 10.4 build failure unititialised object ------------------------+--------------------------- Reporter: geoffd2 | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: tiger powerpc Port: kerberos5 | ------------------------+--------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: fixed at some point: {{{ $ port -v installed kerberos5 The following ports are currently installed: kerberos5 @1.19.2_1 requested_variants='' platform='darwin 8' archs='ppc' date='2022-02-21T14:58:53-0800' kerberos5 @1.20_0 requested_variants='' platform='darwin 8' archs='ppc' date='2022-08-17T17:48:48-0700' kerberos5 @1.20.1_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-11-28T14:37:13-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:29:24 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:29:24 -0000 Subject: [MacPorts] #48437: kerberos5 @1.13.2: ld: -dylib_compatibility_version must be greater than zero In-Reply-To: <044.bf438637eef4d8ff228e966be195203b@macports.org> References: <044.bf438637eef4d8ff228e966be195203b@macports.org> Message-ID: <059.675e8b19b476e87bbef59bd6e81fcc64@macports.org> #48437: kerberos5 @1.13.2: ld: -dylib_compatibility_version must be greater than zero ------------------------+------------------------ Reporter: mrkapqa | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: tiger Port: kerberos5 | ------------------------+------------------------ Comment (by kencu): fixed at some point: {{{ $ port -v installed kerberos5 The following ports are currently installed: kerberos5 @1.19.2_1 requested_variants='' platform='darwin 8' archs='ppc' date='2022-02-21T14:58:53-0800' kerberos5 @1.20_0 requested_variants='' platform='darwin 8' archs='ppc' date='2022-08-17T17:48:48-0700' kerberos5 @1.20.1_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-11-28T14:37:13-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 20:38:23 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 20:38:23 -0000 Subject: [MacPorts] #58947: flac @1.3.3: error: sys/auxv.h: No such file or directory In-Reply-To: <049.953b1f4f5b0a6e9e806890af6e3498a8@macports.org> References: <049.953b1f4f5b0a6e9e806890af6e3498a8@macports.org> Message-ID: <064.97b3197f9f9ba7db6ee2cd9ba3ad596d@macports.org> #58947: flac @1.3.3: error: sys/auxv.h: No such file or directory ---------------------------+----------------------------------- Reporter: SerpentChris | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: fixed | Keywords: powerpc leopard tiger Port: flac | ---------------------------+----------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: https://github.com/macports/macports- ports/pull/6343/commits/cc5589233c6a6d6b12f812d3045487a59605b868 {{{ $ port -v installed flac The following ports are currently installed: flac @1.3.4_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-12-10T12:35:13-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 22:12:16 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 22:12:16 -0000 Subject: [MacPorts] #39346: kerberos5: build failure (10.4/Intel) In-Reply-To: <051.ebf23229d140f2d214fed7355f993840@macports.org> References: <051.ebf23229d140f2d214fed7355f993840@macports.org> Message-ID: <066.8f0dd66ab49f7305abedfb07685ae8c8@macports.org> #39346: kerberos5: build failure (10.4/Intel) ------------------------+------------------------ Reporter: onunez@? | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: tiger Port: kerberos5 | ------------------------+------------------------ Changes (by kencu): * status: new => closed * resolution: => fixed Comment: fixed at some point: {{{ $ port -v installed kerberos5 The following ports are currently installed: kerberos5 @1.19.1_0 requested_variants='' platform='darwin 8' archs='i386' date='2021-04-13T23:57:14-0700' kerberos5 @1.19.2_0 requested_variants='' platform='darwin 8' archs='i386' date='2021-09-01T01:48:40-0700' kerberos5 @1.19.2_1 requested_variants='' platform='darwin 8' archs='i386' date='2021-12-18T18:33:31-0800' kerberos5 @1.19.3_0 requested_variants='' platform='darwin 8' archs='i386' date='2022-04-19T03:19:48-0700' kerberos5 @1.20.1_0 (active) requested_variants='' platform='darwin 8' archs='i386' date='2022-12-10T14:19:20-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 22:13:02 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 22:13:02 -0000 Subject: [MacPorts] #48437: kerberos5 @1.13.2: ld: -dylib_compatibility_version must be greater than zero In-Reply-To: <044.bf438637eef4d8ff228e966be195203b@macports.org> References: <044.bf438637eef4d8ff228e966be195203b@macports.org> Message-ID: <059.4954dd58588f9f84a28ee6631ca20fe8@macports.org> #48437: kerberos5 @1.13.2: ld: -dylib_compatibility_version must be greater than zero ------------------------+------------------------ Reporter: mrkapqa | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: tiger Port: kerberos5 | ------------------------+------------------------ Changes (by kencu): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 10 22:21:48 2022 From: noreply at macports.org (MacPorts) Date: Sat, 10 Dec 2022 22:21:48 -0000 Subject: [MacPorts] #42656: kerberos5: error: 'decomp' may be used uninitialized in this function In-Reply-To: <047.a04a0c10ca2492e0cd89631e363a778e@macports.org> References: <047.a04a0c10ca2492e0cd89631e363a778e@macports.org> Message-ID: <062.78231fde13e5a270645272686af2e5d2@macports.org> #42656: kerberos5: error: 'decomp' may be used uninitialized in this function -------------------------+------------------------ Reporter: ryandesign | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.99 Resolution: fixed | Keywords: tiger Port: kerberos5 | -------------------------+------------------------ Changes (by kencu): * status: new => closed * resolution: => fixed Comment: fixed at some point: {{{ $ port -v installed kerberos5 The following ports are currently installed: kerberos5 @1.19.1_0 requested_variants='' platform='darwin 8' archs='i386' date='2021-04-13T23:57:14-0700' kerberos5 @1.19.2_0 requested_variants='' platform='darwin 8' archs='i386' date='2021-09-01T01:48:40-0700' kerberos5 @1.19.2_1 requested_variants='' platform='darwin 8' archs='i386' date='2021-12-18T18:33:31-0800' kerberos5 @1.19.3_0 requested_variants='' platform='darwin 8' archs='i386' date='2022-04-19T03:19:48-0700' kerberos5 @1.20.1_0 (active) requested_variants='' platform='darwin 8' archs='i386' date='2022-12-10T14:19:20-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 01:36:46 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 01:36:46 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.31a3886fad8a7e33d57879cc3275b944@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Comment (by programmingkidx): So I ran 'sudo port -fp uninstall installed'. This took out everything. Then I deleted the 'local' folder in the opt folder. I then installed MacPorts 2.8.0. Finally I tried to install xar. It appeared to have worked. Thank you Ken for the advice. So now I have to install everything again :( Maybe more of these packages could come as binary installs. It would save a ton of time. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 01:56:35 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 01:56:35 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.82bba75e8fdc69a16cbbd898038614a6@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Comment (by kencu): glad it's working! A large number of these builds are available on the MacPorts binaries server, but I saw you had quite a few universal ports, and there are fewer of those. Glad you're along for the SnowLeopard ride -- I know you can fix and PR things, and we'd all very much appreciate you tossing up any fixes you do along the way for us all to share in. I just fixed nearly all the outstanding Tiger tickets, and working on Leopard tickets now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 02:01:10 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 02:01:10 -0000 Subject: [MacPorts] #65434: rust ports: link crashes across macOS releases; 10.6 failure for cargo-c blocking downstream ports In-Reply-To: <044.84376b72077b04760827fb6561672a86@macports.org> References: <044.84376b72077b04760827fb6561672a86@macports.org> Message-ID: <059.788eb686b0ef9df15264b3c320a1d335@macports.org> #65434: rust ports: link crashes across macOS releases; 10.6 failure for cargo-c blocking downstream ports ---------------------------------+--------------------------------- Reporter: mascguy | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: libopenraw cargo-c | ---------------------------------+--------------------------------- Comment (by lukaso): Not sure if this is the same thing, but seems close. It is about building rav1e using MACOSX_DEPLOYMENT_TARGET. I've got these two bug reports: https://gitlab.gnome.org/GNOME/gimp/-/issues/8930 and https://github.com/xiph/rav1e/issues/3080 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 02:25:12 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 02:25:12 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 Message-ID: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 -----------------------------+------------------------ Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: irrlichtmt -----------------------------+------------------------ While trying to install irrlichtmt on Mac OS 10.6 I saw this error: Irrlicht/COpenGLDriver.cpp:2012:13: error: use of undeclared identifier 'GL_TEXTURE_CUBE_MAP_SEAMLESS'; did you mean 'OpenGLProcedures::TEXTURE_CUBE_MAP_SEAMLESS'? I was not able to determine when GL_TEXTURE_CUBE_MAP_SEAMLESS was added to Mac OS X. I think this symbol was added in OpenGL 3.2. According to this page "https://www.geeks3d.com/20121109/overview-of-opengl-support-on- os-x/" OpenGL 3.2 was not available on Mac OS 10.6. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 02:25:38 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 02:25:38 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.d0a6474ba049566a8b8c90f3bb12a760@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+-------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 02:29:01 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 02:29:01 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.cabe59886ab8a137fe7a604a5c76b96e@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by jmgurney): I would be nice if there was a more useful error message/explanation of what is going on. And/or warning that qt4-mac requires rosetta 2 to be installed instead of having users spend a day trying to figure out why things aren't working, etc. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 02:30:00 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 02:30:00 -0000 Subject: [MacPorts] #66287: boehmgc @8.2.2_0+universal: Failed to destroot boehmgc: bdw-gc.pc differs In-Reply-To: <043.7d29a66f7f9197b06ae1dfe631dd276b@macports.org> References: <043.7d29a66f7f9197b06ae1dfe631dd276b@macports.org> Message-ID: <058.7268a1e42b1879629726e1e398172968@macports.org> #66287: boehmgc @8.2.2_0+universal: Failed to destroot boehmgc: bdw-gc.pc differs ----------------------+-------------------- Reporter: beauby | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: boehmgc | ----------------------+-------------------- Comment (by jmgurney): I'm seeing this as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 03:41:19 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 03:41:19 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.df4106493180447908e821f173e68711@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by kencu): even though qt4-mac is building as x86_64, it should not force an already- installed cmake to be rebuilt as universal. If it does, then there is an error to fix. So far, you have not demonstrated that is happening. If you can demonstrate that is happening, I might have something to go on to start a fix. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 03:46:19 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 03:46:19 -0000 Subject: [MacPorts] #66427: migrating macports to M1 fails to build cmake In-Reply-To: <045.ea01ce51c618fee2f44f337119c05027@macports.org> References: <045.ea01ce51c618fee2f44f337119c05027@macports.org> Message-ID: <060.609ee810c6fbc94f016dd696ad182978@macports.org> #66427: migrating macports to M1 fails to build cmake -----------------------+-------------------- Reporter: jmgurney | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cmake | -----------------------+-------------------- Comment (by kencu): regarding qt4-mac needing x86_64, it should have given you that message when you tried to install it? although it may not have been clear what the issue was, as macports assumes in it?s logic that an arm machine will have rosetta installed and automatically falls back to x86_64. That might need some kind of clearer message, agreed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 04:17:52 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 04:17:52 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.6a3ed19b7a1f293b1c9adae6c1e21b37@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Comment (by jmroot): And you're running master, which no longer creates a symlink when worksrcdir doesn't exist (because it broke other things). Ideally the gitlab portgroup should ensure that `$worksrcdir` matches the extracted directory name one way or another, but you can get similar results like this: {{{ if {[info exists extract.rename]} { extract.rename yes } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 04:20:00 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 04:20:00 -0000 Subject: [MacPorts] #66438: spice-gtk configure failure (was: Error: Failed to configure spice-gtk: consult) In-Reply-To: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> References: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> Message-ID: <061.15dd501a55838b6efb621f85af14b5c4@macports.org> #66438: spice-gtk configure failure ------------------------+-------------------- Reporter: ANONIMNIQ | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: spice-gtk | ------------------------+-------------------- Changes (by jmroot): * port: virt-manager => spice-gtk Old description: > Error: Failed to configure spice-gtk: consult > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports > .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build > /meson-logs/meson-log.txt > Error: Failed to configure spice-gtk: configure failure: command > execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports > .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port virt-manager failed New description: {{{ Error: Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt Error: Failed to configure spice-gtk: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port virt-manager failed }}} -- Comment: Please attach the two logs mentioned in the error messages. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 04:25:08 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 04:25:08 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.2d128e69acb22fc0d01b61cc50f44e3a@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => l2dy -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 04:26:45 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 04:26:45 -0000 Subject: [MacPorts] #66414: Failed to patch libffi: can't read "patch.cmd" In-Reply-To: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> References: <052.f2cee289762cdf51347fbaec40b698fe@macports.org> Message-ID: <067.8e7e32973b86bc1363ddef06dcd49335@macports.org> #66414: Failed to patch libffi: can't read "patch.cmd" ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: snowleopard Port: libffi | ------------------------------+------------------------- Changes (by jmroot): * status: new => closed * resolution: => invalid -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:06:08 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:06:08 -0000 Subject: [MacPorts] #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' Message-ID: <047.b2a6f78403bc429024835ff15b37694e@macports.org> #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' ------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: py-m2r ------------------------+--------------------------------- I can't install py27-m2r: {{{ Executing: cd "/opt/bblocal/var/macports/build/_opt_bblocal_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- m2r/py27-m2r/work/m2r-0.2.1" && /opt/bblocal/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg build DEBUG: system: cd "/opt/bblocal/var/macports/build/_opt_bblocal_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- m2r/py27-m2r/work/m2r-0.2.1" && /opt/bblocal/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg build Traceback (most recent call last): File "setup.py", line 14, in from m2r import parse_from_file File "/opt/bblocal/var/macports/build/_opt_bblocal_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py-m2r/py27-m2r/work/miyakogi- m2r-7fe542c/m2r.py", line 59, in class RestBlockGrammar(mistune.BlockGrammar): AttributeError: 'module' object has no attribute 'BlockGrammar' Command failed: cd "/opt/bblocal/var/macports/build/_opt_bblocal_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- m2r/py27-m2r/work/m2r-0.2.1" && /opt/bblocal/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg build Exit code: 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:13:16 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:13:16 -0000 Subject: [MacPorts] #66430: xar patching fails In-Reply-To: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> References: <052.fbb664a3a6b621f07d0bc2e5b3fcbe28@macports.org> Message-ID: <067.2dc4f63c3621205c371c7ea19b521ed7@macports.org> #66430: xar patching fails ------------------------------+------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: snowleopard Port: xar | ------------------------------+------------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:13:48 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:13:48 -0000 Subject: [MacPorts] #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 In-Reply-To: <052.762356ffe28083bb7a1e0b190faac668@macports.org> References: <052.762356ffe28083bb7a1e0b190faac668@macports.org> Message-ID: <067.185aca007be207f0c8dff54ac9de9045@macports.org> #66429: llvm-3.4: clang requires version 1.0.0 or later, but libLLVM-3.4.dylib provides version 0.0.0 ------------------------------+------------------------- Reporter: programmingkidx | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: snowleopard Port: llvm-3.4 | ------------------------------+------------------------- Changes (by kencu): * status: assigned => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:20:08 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:20:08 -0000 Subject: [MacPorts] #66438: spice-gtk configure failure In-Reply-To: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> References: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> Message-ID: <061.e6f8de00d9baa29a4df6baac8ca5c0a0@macports.org> #66438: spice-gtk configure failure ------------------------+-------------------- Reporter: ANONIMNIQ | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: spice-gtk | ------------------------+-------------------- Description changed by ryandesign: Old description: > {{{ > Error: Failed to configure spice-gtk: consult > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports > .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build > /meson-logs/meson-log.txt > Error: Failed to configure spice-gtk: configure failure: command > execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports > .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there > is a bug. > Error: Processing of port virt-manager failed > }}} New description: {{{ Error: Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt Error: Failed to configure spice-gtk: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port virt-manager failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:22:24 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:22:24 -0000 Subject: [MacPorts] #66436: cctools @949.0.1_2 checksum mismatch In-Reply-To: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> References: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> Message-ID: <058.ddf4a0dabdb82bea67fd8793e9cf75ec@macports.org> #66436: cctools @949.0.1_2 checksum mismatch ----------------------+---------------------- Reporter: gplunk | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+---------------------- Comment (by ryandesign): Replying to [comment:1 gplunk]: > {{{ > Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/main.log for details. > }}} Please attach this file. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:23:27 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:23:27 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.e80c4b58d41fadbedeffb82acbee1e15@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Description changed by ryandesign: Old description: > While trying to install irrlichtmt on Mac OS 10.6 I saw this error: > > Irrlicht/COpenGLDriver.cpp:2012:13: error: use of undeclared identifier > 'GL_TEXTURE_CUBE_MAP_SEAMLESS'; did you mean > 'OpenGLProcedures::TEXTURE_CUBE_MAP_SEAMLESS'? > > I was not able to determine when GL_TEXTURE_CUBE_MAP_SEAMLESS was added > to Mac OS X. I think this symbol was added in OpenGL 3.2. According to > this page "https://www.geeks3d.com/20121109/overview-of-opengl-support- > on-os-x/" OpenGL 3.2 was not available on Mac OS 10.6. New description: While trying to install irrlichtmt on Mac OS 10.6 I saw this error: {{{ Irrlicht/COpenGLDriver.cpp:2012:13: error: use of undeclared identifier 'GL_TEXTURE_CUBE_MAP_SEAMLESS'; did you mean 'OpenGLProcedures::TEXTURE_CUBE_MAP_SEAMLESS'? }}} I was not able to determine when `GL_TEXTURE_CUBE_MAP_SEAMLESS` was added to Mac OS X. I think this symbol was added in OpenGL 3.2. According to this page "https://www.geeks3d.com/20121109/overview-of-opengl-support-on- os-x/" OpenGL 3.2 was not available on Mac OS 10.6. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:35:33 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:35:33 -0000 Subject: [MacPorts] #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' In-Reply-To: <047.b2a6f78403bc429024835ff15b37694e@macports.org> References: <047.b2a6f78403bc429024835ff15b37694e@macports.org> Message-ID: <062.3fc20f7c3649d917574764652c19f14c@macports.org> #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' ---------------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-m2r, py-mistune | ---------------------------------+--------------------------------- Changes (by ryandesign): * cc: stromnov (added) * port: py-m2r => py-m2r, py-mistune Comment: According to [https://github.com/Tribler/tribler/issues/6624 this tribler issue]: > the API in version 2.0.0 of mistune has changed, and for the m2r library to work correctly, we need to use a previous version of mistune (0.8.4) py-mistune was updated to 2.0.2 in April, reverted to 0.8.4 the next day, and updated to 2.0.4 in August. py-m2r could be updated to version 0.3.1 but only for python37 and later and it will not fix this problem; it still requires py-mistune < 2. py-m2r has been archived by its developer so there probably won't be further updates after that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 05:55:58 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 05:55:58 -0000 Subject: [MacPorts] #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' In-Reply-To: <047.b2a6f78403bc429024835ff15b37694e@macports.org> References: <047.b2a6f78403bc429024835ff15b37694e@macports.org> Message-ID: <062.fa5941da7e3fffefb4536fe214c0959a@macports.org> #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' ---------------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-m2r, py-mistune | ---------------------------------+--------------------------------- Comment (by ryandesign): Replying to [comment:1 ryandesign]: > According to [https://github.com/Tribler/tribler/issues/6624 this tribler issue]: > > > the API in version 2.0.0 of mistune has changed, and for the m2r library to work correctly, we need to use a previous version of mistune (0.8.4) Downgrading py27-mistune to 0.8.4 does fix the problem for me. (Not saying that's what we should do necessarily, just confirming that it's the same issue.) > py-mistune was updated to 2.0.2 in April, reverted to 0.8.4 the next day, because it broke py-nbconvert > and updated to 2.0.4 in August. but nobody who had the downgraded 0.8.4 received the 2.0.4 update because the `epoch` was decreased. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 06:20:57 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 06:20:57 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 Message-ID: <046.f46aa1d2036af425a7853ae711bda689@macports.org> #66441: Bogofilter missing, broken links, 404 -----------------------+------------------------------------ Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: claws-mail, bogofilter -----------------------+------------------------------------ The bogofilter package is no longer available at any of the currently used hosts: {{{ ---> Attempting to fetch bogofilter-1.2.5_1.darwin_14.x86_64.tbz2 from http://packages.macports.org/bogofilter ---> Attempting to fetch bogofilter-1.2.5_1.darwin_14.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/bogofilter ---> Attempting to fetch bogofilter-1.2.5_1.darwin_14.x86_64.tbz2 from http://pek.cn.packages.macports.org/macports/packages/bogofilter }}} All the hosts lead to a 404 (file missing) for this dependency package. This breaks the claws-mail package (and I'm guessing some others that rely on it as a dependency). The bogofilter package is available here: https://sourceforge.net/projects/bogofilter/files/bogofilter- stable/bogofilter-1.2.5.tar.xz/download Manually downloading and moving the package to "/opt/local/var/macports/distfiles/bogofilter/", and then running "sudo port install claws-mail" or "sudo port install bogofilter" again provides a temporary fix for users to circumvent the missing/broken package and be able to complete the installation. But the download links need to be fixed/updated in the package manager to repair this issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 06:51:43 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 06:51:43 -0000 Subject: [MacPorts] #66442: Libopenshot-audio fails to build Message-ID: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> #66442: Libopenshot-audio fails to build -----------------------+-------------------------------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: openshot-qt, libopenshot-audio -----------------------+-------------------------------------------- {{{ ---> Fetching archive for libopenshot-audio ---> Attempting to fetch libopenshot-audio-0.2.1_0.darwin_14.x86_64.tbz2 from http://packages.macports.org/libopenshot-audio ---> Attempting to fetch libopenshot-audio-0.2.1_0.darwin_14.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/libopenshot- audio ---> Attempting to fetch libopenshot-audio-0.2.1_0.darwin_14.x86_64.tbz2 from http://pek.cn.packages.macports.org/macports/packages/libopenshot- audio ---> Building libopenshot-audio Error: Failed to build libopenshot-audio: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_multimedia_libopenshot-audio /libopenshot-audio/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port openshot-qt failed }}} There seems to be a script error in the build process. Log attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 06:53:51 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 06:53:51 -0000 Subject: [MacPorts] #66442: Libopenshot-audio fails to build In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.467d241dd3fb1c8f451d97b5ba10f682@macports.org> #66442: Libopenshot-audio fails to build ---------------------------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: openshot-qt, libopenshot-audio | ---------------------------------------------+-------------------- Changes (by Rezzy-dev): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 07:54:28 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 07:54:28 -0000 Subject: [MacPorts] #66365: Failed to build libgcc-devel: command execution failed @12-20221202 gcc-darwin-arm64 (was: Failed to build libgcc-devel: command execution failed) In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.5c5eab9df27cce998ce5058503c94f8e@macports.org> #66365: Failed to build libgcc-devel: command execution failed @12-20221202 gcc- darwin-arm64 ---------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 07:55:43 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 07:55:43 -0000 Subject: [MacPorts] #66365: libgcc-devel @12-20221202: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) (was: Failed to build libgcc-devel: command execution failed @12-20221202 gcc-darwin-arm64) In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.28734793c6ab460b1cf0481d8a4f28ee@macports.org> #66365: libgcc-devel @12-20221202: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) ---------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:17:26 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 09:17:26 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.f32b0c66825a50b1822134a62a91d7a3@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Comment (by kencu): on 10.6 may need to go back to {{{irrlicht}}}, if it still works with minetest. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:41:36 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 09:41:36 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis Message-ID: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis ---------------------------------+------------------------ Reporter: thetrial | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: elcapitan legacy-os | Port: ccache ---------------------------------+------------------------ After an update of libhiredis, ccache was marked as broken but cannot be rebuilt ? due to a missing link to /opt/local/lib/libhiredis.1.0.0.dylib. Right would be /opt/local/lib/libhiredis.1.1.0.dylib. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 09:42:02 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 09:42:02 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.33057011c06ad4bcdee224ceb7ca833d@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+--------------------------------- Reporter: thetrial | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: ccache | -----------------------+--------------------------------- Changes (by thetrial): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 11:02:03 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 11:02:03 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.68d099f0f0974269385a857fa3efafc9@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Changes (by jmroot): * priority: High => Normal * port: claws-mail, bogofilter => bogofilter Comment: There are no binaries of bogofilter available for license reasons. That doesn't prevent installation because MacPorts will simply fall back to building from source. What is the actual error you are getting when you try to install? Can you attach the log? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 12:30:49 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 12:30:49 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" (was: Libopenshot-audio fails to build) In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.481a7d97b4a94b766da3f986fb0c5665@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Changes (by jmroot): * owner: (none) => ctreleaven * priority: High => Normal * status: new => assigned * port: openshot-qt, libopenshot-audio => libopenshot-audio -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 12:35:29 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 12:35:29 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.5742bc85067ca4cdbce34da3ea770756@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+------------------------ Reporter: thetrial | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ccache | -----------------------+------------------------ Changes (by jmroot): * cc: herbygillot, aeiouaeiouaeiouaeiouaeiouaeiou (added) * keywords: elcapitan legacy-os => Comment: All dependents of hiredis needed to be rev bumped when the major library version changed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 13:06:23 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 13:06:23 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.ea934b378e631514d54b519e623b3fb3@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+------------------------ Reporter: thetrial | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ccache | -----------------------+------------------------ Comment (by aeiouaeiouaeiouaeiouaeiouaeiou): The +doc variant is also broken because of a problem with asciidoctor: https://github.com/macports/macports-ports/pull/16937 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 13:48:35 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 13:48:35 -0000 Subject: [MacPorts] #66444: Error: Failed to build check: command execution failed Message-ID: <043.29d5883021f856e06e12ad72753c5ce9@macports.org> #66444: Error: Failed to build check: command execution failed -------------------------------------+-------------------- Reporter: Dekoz3 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: check.h check libcheck | Port: check -------------------------------------+-------------------- ~ % sudo port clean check ---> Cleaning check ~ % sudo port install check ---> Computing dependencies for check ---> Fetching archive for check ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from https://packages.macports.org/check ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from https://cph.dk.packages.macports.org/check ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/check ---> Fetching distfiles for check ---> Verifying checksums for check ---> Extracting check ---> Configuring check Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: strchr: found in libcheck-check-11970a7/config.log ---> Building check Error: Failed to build check: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_check/check/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port check failed ~ % -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:03:33 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:03:33 -0000 Subject: [MacPorts] #66444: Error: Failed to build check: command execution failed In-Reply-To: <043.29d5883021f856e06e12ad72753c5ce9@macports.org> References: <043.29d5883021f856e06e12ad72753c5ce9@macports.org> Message-ID: <058.5cc7a910fd0dcfc540d30ee0b11f8427@macports.org> #66444: Error: Failed to build check: command execution failed ---------------------+------------------------------------- Reporter: Dekoz3 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: check.h check libcheck Port: check | ---------------------+------------------------------------- Changes (by Dekoz3): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:18:13 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:18:13 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.f794ee83d88f32b7b88cd66db0d4cdcb@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+------------------------ Reporter: thetrial | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ccache | -----------------------+------------------------ Changes (by aeiouaeiouaeiouaeiouaeiouaeiou): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"a4050a50a11a66a11c65bbabde2edfc65a406202/macports-ports" a4050a50a11a66a11c65bbabde2edfc65a406202/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a4050a50a11a66a11c65bbabde2edfc65a406202" ccache: bump revision for hiredis update Closes: https://trac.macports.org/ticket/66443 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:19:47 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:19:47 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.437537f9cace310fe3f31ddcecbb515f@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Comment (by ctreleaven): I see that Openshot 3.0 was released yesterday. I will have a look at updating to that but I would not expect it to better support old versions of OSX. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:20:51 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:20:51 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.d0272cb4b982a2e96a9dc1192a61a8e3@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Comment (by programmingkidx): A solution to this problem might be:\\ a) we find an OpenGL programmer who can program around this missing symbol\\ b) we revert to a previous version of MineTest that could work on Mac OS 10.6.\\ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:22:00 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:22:00 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.97c61f9a562514711a4927ea4c3bad96@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Comment (by programmingkidx): I like option A better because it would mean newer software would be available to older versions of Mac OS X. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:41:32 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:41:32 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.d356e1b0925f0af705e067cabd68f623@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Comment (by Rezzy-dev): I've just gone through all the Mac builds of Openshot on the official site, and 2.3.3 seems to be the last version to run on Mac OS 10.10 (Yosemite). Anything after that seems to bug out one way or another, even in the official builds. I suggest packaging/offering the 2.3.3 build for Yosemite (and whatever version of libopenshot-audio it is using). https://github.com/OpenShot/openshot- qt/releases/download/v2.3.3/OpenShot-v2.3.3-x86_64.dmg Openshot seems to be very finicky about which version of the program runs with which release of OS X. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:50:18 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:50:18 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.0ddec86aca7d6a1af4a68d2fc472078c@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by Rezzy-dev): It's not a matter of binaries -- the source code, the tarball, is unavailable on all three hosts (they're all throwing a 'file not found', a 404 on the server), and so the build fails because bogofilter is set as a dependency to claws-mail, and its tarball can't be downloaded, so there's nothing to compile. The links to the bogofilter source need to be updated in the package manager. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 14:53:50 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 14:53:50 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.3d3fa86df7eb355c0e4ee1399da65b5e@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by Rezzy-dev): If you visit those links, there's nothing there -- no source: http://packages.macports.org/bogofilter/bogofilter-1.2.5_1.darwin_14.x86_64.tbz2 http://jog.id.packages.macports.org/macports/packages/bogofilter/bogofilter-1.2.5_1.darwin_14.x86_64.tbz2 http://pek.cn.packages.macports.org/macports/packages/bogofilter/bogofilter-1.2.5_1.darwin_14.x86_64.tbz2 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 15:24:09 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 15:24:09 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.b7462af3c29185845e6f2c1bbff79fa1@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Comment (by kencu): or on 10.6 may need to go back to irrlicht, if it still works with minetest. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 15:35:55 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 15:35:55 -0000 Subject: [MacPorts] #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated In-Reply-To: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> References: <048.bfc7d38a81cd5b15a0dbdd90ccfdd360@macports.org> Message-ID: <063.d774a8ec190b2a6ece1cf500ec00122c@macports.org> #66382: TeXShop @4.79 contains Sparkle updater, which reports that it's outdated -------------------------+------------------------------------------------- Reporter: | Owner: Marius Schamschula cooljeanius | Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: TeXShop | -------------------------+------------------------------------------------- Changes (by Marius Schamschula ): * owner: (none) => Marius Schamschula * status: new => closed * resolution: => fixed Comment: In [changeset:"68d191c8fd077f48c1654760b2ad6951f0785ca3/macports-ports" 68d191c8fd077f48c1654760b2ad6951f0785ca3/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="68d191c8fd077f48c1654760b2ad6951f0785ca3" TeXShop: update to 5.08, disable Sparkle Closes: https://trac.macports.org/ticket/66382 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:19:51 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 17:19:51 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.77b40fd02bee3fcd73844770d1865d1d@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by jmroot): Everything on packages.macports.org is binary archives. Fetching the source works fine: {{{ % sudo port -v checksum bogofilter Password: ---> Fetching distfiles for bogofilter ---> bogofilter-1.2.5.tar.xz does not exist in /opt/local/var/macports/distfiles/bogofilter ---> Attempting to fetch bogofilter-1.2.5.tar.xz from https://distfiles.macports.org/bogofilter % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 782k 100 782k 0 0 6192k 0 --:--:-- --:--:-- --:--:-- 6310k ---> Verifying checksums for bogofilter ---> Checksumming bogofilter-1.2.5.tar.xz }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:27:38 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 17:27:38 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails with ffmpeg from homebrew installed (was: soxr @0.1.3 Building on Ventura fails) In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.7c04c2f16dd516743308e5eb29279464@macports.org> #66420: soxr @0.1.3 Building on Ventura fails with ffmpeg from homebrew installed ----------------------+--------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: soxr | ----------------------+--------------------- Comment (by jmroot): {{{ :info:configure -- Found AVUTIL: /opt/homebrew/lib/libavutil.dylib }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:37:53 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 17:37:53 -0000 Subject: [MacPorts] #66444: check fails to build on Ventura: "'makeinfo' is missing on your system." (was: Error: Failed to build check: command execution failed) In-Reply-To: <043.29d5883021f856e06e12ad72753c5ce9@macports.org> References: <043.29d5883021f856e06e12ad72753c5ce9@macports.org> Message-ID: <058.a319519cf638db9bc72e3af9ec201f1e@macports.org> #66444: check fails to build on Ventura: "'makeinfo' is missing on your system." ------------------------+--------------------- Reporter: Dekoz3 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: ventura Port: check | ------------------------+--------------------- Changes (by jmroot): * keywords: check.h check libcheck => ventura * status: new => closed * resolution: => duplicate Old description: > ~ % sudo port clean check > ---> Cleaning check > ~ % sudo port install check > ---> Computing dependencies for check > ---> Fetching archive for check > ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from > https://packages.macports.org/check > ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from > https://cph.dk.packages.macports.org/check > ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from > https://nue.de.packages.macports.org/check > ---> Fetching distfiles for check > ---> Verifying checksums for check > ---> Extracting check > ---> Configuring check > Warning: Configuration logfiles contain indications of -Wimplicit- > function-declaration; check that features were not accidentally disabled: > strchr: found in libcheck-check-11970a7/config.log > ---> Building check > Error: Failed to build check: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_check/check/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > Error: Processing of port check failed > ~ % New description: {{{ ~ % sudo port clean check ---> Cleaning check ~ % sudo port install check ---> Computing dependencies for check ---> Fetching archive for check ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from https://packages.macports.org/check ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from https://cph.dk.packages.macports.org/check ---> Attempting to fetch check-0.15.2_0.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/check ---> Fetching distfiles for check ---> Verifying checksums for check ---> Extracting check ---> Configuring check Warning: Configuration logfiles contain indications of -Wimplicit- function-declaration; check that features were not accidentally disabled: strchr: found in libcheck-check-11970a7/config.log ---> Building check Error: Failed to build check: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_check/check/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port check failed ~ % }}} -- Comment: #66199 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:38:24 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 17:38:24 -0000 Subject: [MacPorts] #66199: check : missing build dependency 'texinfo' In-Reply-To: <043.ff0ad762f8f3abc2d53d8369d952bff6@macports.org> References: <043.ff0ad762f8f3abc2d53d8369d952bff6@macports.org> Message-ID: <058.6419a1488e7561d34bfae6b852ef024a@macports.org> #66199: check : missing build dependency 'texinfo' ---------------------+--------------------- Reporter: bll123 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: check | ---------------------+--------------------- Changes (by jmroot): * keywords: => ventura -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 17:52:02 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 17:52:02 -0000 Subject: [MacPorts] #66199: check : missing build dependency 'texinfo' In-Reply-To: <043.ff0ad762f8f3abc2d53d8369d952bff6@macports.org> References: <043.ff0ad762f8f3abc2d53d8369d952bff6@macports.org> Message-ID: <058.6a9addf25bba57beafac23a9d5751a84@macports.org> #66199: check : missing build dependency 'texinfo' ---------------------+--------------------- Reporter: bll123 | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: check | ---------------------+--------------------- Changes (by jmroot): * owner: (none) => jmroot * status: new => closed * resolution: => fixed Comment: In [changeset:"7a29a8b787929de77b17be7c28aea123c18936f2/macports-ports" 7a29a8b787929de77b17be7c28aea123c18936f2/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7a29a8b787929de77b17be7c28aea123c18936f2" check: use release tarball Fixes: https://trac.macports.org/ticket/66199 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:00:25 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 18:00:25 -0000 Subject: [MacPorts] #62994: various ports fail to install on Leopard due to gnulib issue: /confdir-14B---: No space left on device In-Reply-To: <042.b671bcafb6f6887862b544834b4b0efc@macports.org> References: <042.b671bcafb6f6887862b544834b4b0efc@macports.org> Message-ID: <057.cb370bad4b0ce08f2c02615e7ee323d0@macports.org> #62994: various ports fail to install on Leopard due to gnulib issue: /confdir- 14B---: No space left on device -------------------------------------------+---------------------- Reporter: kencu | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: leopard Port: m4 bison findutils coreutils | -------------------------------------------+---------------------- Comment (by kencu): In [changeset:"96c9d4293aaa701ee42f292ddae87740c2b45ff6/macports-ports" 96c9d4293aaa701ee42f292ddae87740c2b45ff6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="96c9d4293aaa701ee42f292ddae87740c2b45ff6" coreutils: fix build on Leopard there are several tests run during configure, for issues that do not occur on Darwin, that fail in an unusual fashion on Leopard. This failure does not appear to occur on any other systems. This patch avoids running these failing tests on Leopard. see: https://trac.macports.org/ticket/62994 closes: https://trac.macports.org/ticket/66028 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:00:25 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 18:00:25 -0000 Subject: [MacPorts] #66028: coreutils fails to build due to apparent path recursion In-Reply-To: <045.a11aa06c290c0b1045f72e1bf757b3a6@macports.org> References: <045.a11aa06c290c0b1045f72e1bf757b3a6@macports.org> Message-ID: <060.d1cb94c3b0ca4c1532b5f49ddef40755@macports.org> #66028: coreutils fails to build due to apparent path recursion ------------------------+--------------------- Reporter: rmottola | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: coreutils | ------------------------+--------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"96c9d4293aaa701ee42f292ddae87740c2b45ff6/macports-ports" 96c9d4293aaa701ee42f292ddae87740c2b45ff6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="96c9d4293aaa701ee42f292ddae87740c2b45ff6" coreutils: fix build on Leopard there are several tests run during configure, for issues that do not occur on Darwin, that fail in an unusual fashion on Leopard. This failure does not appear to occur on any other systems. This patch avoids running these failing tests on Leopard. see: https://trac.macports.org/ticket/62994 closes: https://trac.macports.org/ticket/66028 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:37:41 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 18:37:41 -0000 Subject: [MacPorts] #66076: gnuplot build failing on Ventura In-Reply-To: <044.ce28f232284c6948eeae6e6486ff8cde@macports.org> References: <044.ce28f232284c6948eeae6e6486ff8cde@macports.org> Message-ID: <059.86b895e39816dac360ba55d617ef77d8@macports.org> #66076: gnuplot build failing on Ventura ----------------------+--------------------- Reporter: pidloop | Owner: mojca Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: ventura Port: gnuplot | ----------------------+--------------------- Comment (by pidloop): gnuplot +aquaterm builds fine now. Thanks everyone. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 18:46:27 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 18:46:27 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.65d75136c57118a39dd9d71a2af44de4@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+------------------------ Reporter: thetrial | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ccache | -----------------------+------------------------ Comment (by thetrial): Wow, that was lightning-fast, thank you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 19:20:19 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 19:20:19 -0000 Subject: [MacPorts] #66445: py36-mongoengine: Error: No such port: py36-pymongo Message-ID: <047.e6363ad0586c9c96951c63965ebace84@macports.org> #66445: py36-mongoengine: Error: No such port: py36-pymongo ------------------------+--------------------------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-mongoengine py-pymongo ------------------------+--------------------------------------- https://build.macports.org/builders/jobs- mirror/builds/496844/steps/mirror/logs/stdio {{{ Error: No such port: py36-pymongo }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 19:27:22 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 19:27:22 -0000 Subject: [MacPorts] #16598: ettercap do not work on Mac OS X 10.5.5 In-Reply-To: <054.1f92d1ec579bbfccc6d1a1345072351d@macports.org> References: <054.1f92d1ec579bbfccc6d1a1345072351d@macports.org> Message-ID: <069.fd843e5355ad96928cc0a6fb0454ac84@macports.org> #16598: ettercap do not work on Mac OS X 10.5.5 ------------------------+-------------------------------- Reporter: monserg@? | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Resolution: fixed | Keywords: leopard Port: ettercap | ------------------------+-------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: fixed and works: {{{ $ port -v installed ettercap The following ports are currently installed: ettercap @0.8.3.1_1+gtk+plugins (active) requested_variants='' platform='darwin 9' archs='ppc' date='2022-12-11T11:14:47-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 19:29:48 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 19:29:48 -0000 Subject: [MacPorts] #66446: py38-ipyparallel: ImportError: cannot import name 'StaticModule' from 'setuptools.config' Message-ID: <047.abcbaa1e9edec92e8b2ef6c7dfa7c0bf@macports.org> #66446: py38-ipyparallel: ImportError: cannot import name 'StaticModule' from 'setuptools.config' ------------------------+---------------------------- Reporter: ryandesign | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-ipyparallel ------------------------+---------------------------- https://build.macports.org/builders/ports- 12_arm64-builder/builds/76128/steps/install-port/logs/stdio {{{ Executing: cd "/opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- ipyparallel/py38-ipyparallel/work/ipyparallel-7.0.1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 setup.py --no-user-cfg build -j8 DEBUG: system: cd "/opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- ipyparallel/py38-ipyparallel/work/ipyparallel-7.0.1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 setup.py --no-user-cfg build -j8 Traceback (most recent call last): File "setup.py", line 65, in from setupbase import wrap_installers, npm_builder, get_data_files File "/opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- ipyparallel/py38-ipyparallel/work/ipyparallel-7.0.1/setupbase.py", line 37, in from setuptools.config import StaticModule ImportError: cannot import name 'StaticModule' from 'setuptools.config' (/opt/local/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8 /site-packages/setuptools/config/__init__.py) Command failed: cd "/opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- ipyparallel/py38-ipyparallel/work/ipyparallel-7.0.1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 setup.py --no-user-cfg build -j8 Exit code: 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 21:07:09 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 21:07:09 -0000 Subject: [MacPorts] #66287: boehmgc @8.2.2_0+universal: Failed to destroot boehmgc: bdw-gc.pc differs In-Reply-To: <043.7d29a66f7f9197b06ae1dfe631dd276b@macports.org> References: <043.7d29a66f7f9197b06ae1dfe631dd276b@macports.org> Message-ID: <058.8ee8efe99c85902e90d1e8528b7759d4@macports.org> #66287: boehmgc @8.2.2_0+universal: Failed to destroot boehmgc: bdw-gc.pc differs ----------------------+-------------------- Reporter: beauby | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: boehmgc | ----------------------+-------------------- Comment (by beauby): Note: I provided a patch on GitHub (https://github.com/macports/macports- ports/pull/16717). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 21:12:34 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 21:12:34 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366330=3A_cfitsio_=404=2E2=2E0_?= =?utf-8?q?fails_to_build_on_10=2E5=2E8=3A_error=3A_redefinition_?= =?utf-8?q?of_typedef_=E2=80=98ParseData=E2=80=99?= In-Reply-To: <049.0fe2e16cf83c0f705210565de85c0781@macports.org> References: <049.0fe2e16cf83c0f705210565de85c0781@macports.org> Message-ID: <064.c54226e7a6e61e2bc5af1a3b3a4b3889@macports.org> #66330: cfitsio @4.2.0 fails to build on 10.5.8: error: redefinition of typedef ?ParseData? ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: Schamschula Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: powerpc, leopard, snowleopard Port: cfitsio | ---------------------------+------------------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"a296293b673cb610855f8790386b010ff44c85cb/macports-ports" a296293b673cb610855f8790386b010ff44c85cb/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a296293b673cb610855f8790386b010ff44c85cb" cfitsio: fix build on older systems required C11 typedef redefinitions closes: https://trac.macports.org/ticket/66330 fix /bin/cp patch to not use "-a" which is not supported on older systems use the fallback equivalent instead, as before }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 21:20:55 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 21:20:55 -0000 Subject: [MacPorts] #56347: cfitsio @3.440_0: install_name not set correctly in configure patch, leading to incorrect rev-upgrade behaviour In-Reply-To: <061.f16cffe6b93d1a7a5dfb6b804dc869d9@macports.org> References: <061.f16cffe6b93d1a7a5dfb6b804dc869d9@macports.org> Message-ID: <076.adbf8dd226273ffcae9fb4e29bf4835d@macports.org> #56347: cfitsio @3.440_0: install_name not set correctly in configure patch, leading to incorrect rev-upgrade behaviour ---------------------------------------+---------------------- Reporter: aszostak-partner-eso-org | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.4.2 Resolution: fixed | Keywords: haspatch Port: cfitsio | ---------------------------------------+---------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: fixed, likely by https://github.com/macports/macports- ports/commit/27a78d0fa499c233e4cb7e7136ad0080df81cdc2 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 21:43:42 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 21:43:42 -0000 Subject: [MacPorts] #66447: tuxmath fails to install due to missing file tuxmath_w_fonts-2.0.3.tar.gz Message-ID: <052.0890150200b75169623247ce4bc3fcc6@macports.org> #66447: tuxmath fails to install due to missing file tuxmath_w_fonts-2.0.3.tar.gz -----------------------------+--------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: tuxmath -----------------------------+--------------------- While trying to install tuxmath I saw this error: Error: Failed to fetch tuxmath: The requested URL returned error: 404 The file that the log said can't be downloaded is tuxmath_w_fonts-2.0.3.tar.gz. This happened on Mac OS 10.6. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 21:44:13 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 21:44:13 -0000 Subject: [MacPorts] #66447: tuxmath fails to install due to missing file tuxmath_w_fonts-2.0.3.tar.gz In-Reply-To: <052.0890150200b75169623247ce4bc3fcc6@macports.org> References: <052.0890150200b75169623247ce4bc3fcc6@macports.org> Message-ID: <067.2d6a7d39db47eb5ed4076c52e6589e33@macports.org> #66447: tuxmath fails to install due to missing file tuxmath_w_fonts-2.0.3.tar.gz ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tuxmath | ------------------------------+-------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 21:55:00 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 21:55:00 -0000 Subject: [MacPorts] #66448: Is the xz port missing for Apple Silicon? Message-ID: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> #66448: Is the xz port missing for Apple Silicon? --------------------+-------------------- Reporter: russes | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: xz --------------------+-------------------- Is the xz port missing for Apple Silicon? ---> Computing dependencies for xz ---> Fetching archive for xz ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://packages.macports.org/xz ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/xz ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/xz ---> Verifying checksums for xz Error: Failed to checksum xz: xz-5.2.9.tar.bz2 does not exist in /opt/local/var/macports/distfiles/xz Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_xz/xz/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. -- :info:archivefetch ---> xz-5.2.9_0.darwin_22.arm64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://packages.macports.org/xz :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/xz :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/xz :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 22:24:21 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 22:24:21 -0000 Subject: [MacPorts] #66449: libsdl_pango fails to install because a patch could not be applied Message-ID: <052.197e9b1473b1f8ed7aaa292a897ef880@macports.org> #66449: libsdl_pango fails to install because a patch could not be applied -----------------------------+-------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libsdl_pango -----------------------------+-------------------------- Installing libsdl_pango fails because of an issue with a patch. Here is what I saw in the log: {{{ :info:patch Hunk #1 FAILED at 723 (different line endings). :info:patch Hunk #2 FAILED at 743 (different line endings). :info:patch Hunk #3 FAILED at 762 (different line endings). :info:patch Hunk #4 FAILED at 1053 (different line endings). :info:patch Hunk #5 FAILED at 1067 (different line endings). :info:patch 5 out of 5 hunks FAILED -- saving rejects to file src/SDL_Pango.c.rej :info:patch patching file src/SDL_Pango.h :info:patch Hunk #1 FAILED at 109 (different line endings). :info:patch Hunk #2 FAILED at 157 (different line endings). :info:patch 2 out of 2 hunks FAILED -- saving rejects to file src/SDL_Pango.h.rej :info:patch Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_libsdl_pango/libsdl_pango/work/SDL_Pango-0.1.2" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/libsdl_pango/files /patch-SDL_Pango-0.1.2-API-adds.diff' :info:patch Exit code: 1 }}} This issue happened on Mac OS 10.6.8. I did check and I have the /usr/bin/patch program installed. It is version 2.7.5. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 22:24:53 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 22:24:53 -0000 Subject: [MacPorts] #66449: libsdl_pango fails to install because a patch could not be applied In-Reply-To: <052.197e9b1473b1f8ed7aaa292a897ef880@macports.org> References: <052.197e9b1473b1f8ed7aaa292a897ef880@macports.org> Message-ID: <067.7155cb9959b9ab7e38701a87efafaf36@macports.org> #66449: libsdl_pango fails to install because a patch could not be applied ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libsdl_pango | ------------------------------+-------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 22:27:42 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 22:27:42 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.3f79df8ba0a25a1a15f3a90b610f1096@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Comment (by programmingkidx): Sorry Ken I didn't acknowledge your idea. I didn't see the missing 'mt' at the end of irrlicht. Your idea sounds interesting. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 22:47:05 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 22:47:05 -0000 Subject: [MacPorts] #66450: xscorch fails to install - unknown argument: '-fthread-jumps' Message-ID: <052.4bb46f29f1011b32eacc6965f8336f74@macports.org> #66450: xscorch fails to install - unknown argument: '-fthread-jumps' -----------------------------+--------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: xscorch -----------------------------+--------------------- Building xscorch fails to build on Mac OS 10.6. This is the error I saw in the log: \\ :info:build clang: error: unknown argument: '-fthread-jumps' Here is a description of the option for GCC 3.4 found here: https://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html: {{{ -fthread-jumps Perform optimizations where we check to see if a jump branches to a location where another comparison subsumed by the first is found. If so, the first branch is redirected to either the destination of the second branch or a point immediately following it, depending on whether the condition is known to be true or false. Enabled at levels -O, -O2, -O3, -Os. }}} I could not find a reference to -fthread-jumps working with clang. This issue talks about how clang does not recognize a lot of flags (fthread-jumps included): https://github.com/pcsx2/pcsx2/issues/295 My guess is xscorch is meant to be built with GCC instead of Clang. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 11 22:47:36 2022 From: noreply at macports.org (MacPorts) Date: Sun, 11 Dec 2022 22:47:36 -0000 Subject: [MacPorts] #66450: xscorch fails to install - unknown argument: '-fthread-jumps' In-Reply-To: <052.4bb46f29f1011b32eacc6965f8336f74@macports.org> References: <052.4bb46f29f1011b32eacc6965f8336f74@macports.org> Message-ID: <067.a0cc7e8c6adab16ca307a14dec82b830@macports.org> #66450: xscorch fails to install - unknown argument: '-fthread-jumps' ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xscorch | ------------------------------+-------------------- Changes (by programmingkidx): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 00:11:45 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 00:11:45 -0000 Subject: [MacPorts] #65742: Gnuradio gui stuck In-Reply-To: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> References: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> Message-ID: <063.53bf8eee975ae2e6525afaf4a3169e01@macports.org> #65742: Gnuradio gui stuck --------------------------+----------------------- Reporter: adamgao1996 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: qtgui Port: gnuradio | --------------------------+----------------------- Comment (by J-in-MN): @ra1nb0w Thanks, I will try it out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 00:24:15 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 00:24:15 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.c7b4333c044345c6d9f248e70762f959@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Comment (by kencu): this seems to be happening on multiple systems I have tried. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 00:24:57 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 00:24:57 -0000 Subject: [MacPorts] #66451: Link to Micropolis should be added to /Applications/MacPorts folder Message-ID: <052.382535c676f4c6d0f981995b54406cd6@macports.org> #66451: Link to Micropolis should be added to /Applications/MacPorts folder -----------------------------+------------------------ Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: Micropolis -----------------------------+------------------------ Currently the game Micropolis is installed to /opt/local/bin. This makes finding the game hard for the average user. I suggest a link to this game be added to the /Applications/MacPorts folder like other games. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 00:25:26 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 00:25:26 -0000 Subject: [MacPorts] #66451: Link to Micropolis should be added to /Applications/MacPorts folder In-Reply-To: <052.382535c676f4c6d0f981995b54406cd6@macports.org> References: <052.382535c676f4c6d0f981995b54406cd6@macports.org> Message-ID: <067.248a1c8b17b275b3aa603667764f74b2@macports.org> #66451: Link to Micropolis should be added to /Applications/MacPorts folder ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Micropolis | ------------------------------+-------------------- Description changed by programmingkidx: Old description: > Currently the game Micropolis is installed to /opt/local/bin. This makes > finding the game hard for the average user. I suggest a link to this game > be added to the /Applications/MacPorts folder like other games. New description: Currently the game Micropolis is installed to /opt/local/bin. This makes finding the game hard for the average user. I suggest a link to this game be added to the /Applications/MacPorts folder like other games installed using MacPorts. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 01:40:36 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 01:40:36 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.3934b9aa38294470163f264362ff3630@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Comment (by kencu): probably broken by this commit, that removed the expat dep from python27-bootstrap and sterilized the environment, but left the configure args "-with-system-expat" and some others in place. https://github.com/macports/macports- ports/commit/d11c2377c9cff32cd5cb6a0ed11788cc46862c1a removing "-with-system-expat" fixes the build. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 02:09:49 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 02:09:49 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.109ea0dd85b90586c03ce79268cba391@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by Rezzy-dev): So the above tarball links are to a binary archive? MacPorts didn't fall back to downloading and installing from the source. When I tried to install claws-mail, it simply failed at installing the bogofilter dependency because it was unable to download the binary package from those 3 URLs, and aborted the whole installation as a result. So this is an oversight/bug in the claws-mail package setup, or inside MacPorts 2.8.0? I was able to circumvent it by manually downloading that package from the above sourceforge URL and placing it where the installation was looking for it. So the claws-mail installation definitely failed because the bogofilter binary package couldn't be downloaded. It looks like that fallback to building from source you're mentioning here didn't happen with this package for some reason. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 03:55:18 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 03:55:18 -0000 Subject: [MacPorts] #66448: Is the xz port missing for Apple Silicon? In-Reply-To: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> References: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> Message-ID: <058.4847fda7ed07222c9526cfa582da5d35@macports.org> #66448: Is the xz port missing for Apple Silicon? ---------------------+--------------------------- Reporter: russes | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: xz | ---------------------+--------------------------- Changes (by ryandesign): * keywords: => ventura arm64 Old description: > Is the xz port missing for Apple Silicon? > > ---> Computing dependencies for xz > ---> Fetching archive for xz > ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from > https://packages.macports.org/xz > ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from > http://mirror.fcix.net/macports/packages/xz > ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from > https://ywg.ca.packages.macports.org/mirror/macports/packages/xz > ---> Verifying checksums for xz > Error: Failed to checksum xz: xz-5.2.9.tar.bz2 does not exist in > /opt/local/var/macports/distfiles/xz > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_xz/xz/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > > -- > > :info:archivefetch ---> xz-5.2.9_0.darwin_22.arm64.tbz2 doesn't seem to > exist in /opt/local/var/macports/incoming/verified > :msg:archivefetch ---> Attempting to fetch > xz-5.2.9_0.darwin_22.arm64.tbz2 from https://packages.macports.org/xz > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 > :msg:archivefetch ---> Attempting to fetch > xz-5.2.9_0.darwin_22.arm64.tbz2 from > http://mirror.fcix.net/macports/packages/xz > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 > :msg:archivefetch ---> Attempting to fetch > xz-5.2.9_0.darwin_22.arm64.tbz2 from > https://ywg.ca.packages.macports.org/mirror/macports/packages/xz > :debug:archivefetch Fetching archive failed: The requested URL returned > error: 404 New description: Is the xz port missing for Apple Silicon? {{{ ---> Computing dependencies for xz ---> Fetching archive for xz ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://packages.macports.org/xz ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/xz ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/xz ---> Verifying checksums for xz Error: Failed to checksum xz: xz-5.2.9.tar.bz2 does not exist in /opt/local/var/macports/distfiles/xz Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_xz/xz/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. }}} -- {{{ :info:archivefetch ---> xz-5.2.9_0.darwin_22.arm64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://packages.macports.org/xz :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/xz :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch xz-5.2.9_0.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/xz :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 }}} -- Comment: For macOS Ventura, there are no binaries for Apple Silicon yet, and I've just started producing them for Intel. This shouldn't be a problem; MacPorts should then build from source on your system. Run `sudo port clean xz` and try again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 04:01:03 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 04:01:03 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.213b155312eb707495bb9fccd6b5d21e@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by ryandesign): We cannot know what happened if you don't attach the main.log file. Unless you tell it not to, MacPorts first tries to download a precompiled binary archive/package. As you've discovered, these are unavailable for bogofilter. If that fails, MacPorts then (unless you tell it not to) tries to download the source code distfile and build from that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 04:04:03 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 04:04:03 -0000 Subject: [MacPorts] #66451: Link to Micropolis should be added to /Applications/MacPorts folder In-Reply-To: <052.382535c676f4c6d0f981995b54406cd6@macports.org> References: <052.382535c676f4c6d0f981995b54406cd6@macports.org> Message-ID: <067.6cdf6f867df6f77de7046161b543670c@macports.org> #66451: Link to Micropolis should be added to /Applications/MacPorts folder ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: Micropolis | ------------------------------+-------------------- Comment (by ryandesign): /Applications/MacPorts should typically contain only macOS GUI applications. Micropolis isn't; it's an X11 application. However we have at times allowed X11 applications into the /Applications/MacPorts folder, so perhaps it can be done here. Users are expected to use the `port contents` command to find out what a port installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 04:06:07 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 04:06:07 -0000 Subject: [MacPorts] #66450: xscorch fails to install - unknown argument: '-fthread-jumps' In-Reply-To: <052.4bb46f29f1011b32eacc6965f8336f74@macports.org> References: <052.4bb46f29f1011b32eacc6965f8336f74@macports.org> Message-ID: <067.2b59ff30a3ba29f01e7393f045aa0bdb@macports.org> #66450: xscorch fails to install - unknown argument: '-fthread-jumps' ------------------------------+-------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xscorch | ------------------------------+-------------------- Description changed by ryandesign: Old description: > Building xscorch fails to build on Mac OS 10.6. This is the error I saw > in the log: \\ > :info:build clang: error: unknown argument: '-fthread-jumps' > > Here is a description of the option for GCC 3.4 found here: > https://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html: > > {{{ > -fthread-jumps > Perform optimizations where we check to see if a jump branches to a > location where another comparison subsumed by the first is found. If so, > the first branch is redirected to either the destination of the second > branch or a point immediately following it, depending on whether the > condition is known to be true or false. > > Enabled at levels -O, -O2, -O3, -Os. > }}} > > I could not find a reference to -fthread-jumps working with clang. > > This issue talks about how clang does not recognize a lot of flags > (fthread-jumps included): https://github.com/pcsx2/pcsx2/issues/295 > > My guess is xscorch is meant to be built with GCC instead of Clang. New description: Building xscorch fails to build on Mac OS 10.6. This is the error I saw in the log: {{{ :info:build clang: error: unknown argument: '-fthread-jumps' }}} Here is a description of the option for GCC 3.4 found here: https://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html: {{{ -fthread-jumps Perform optimizations where we check to see if a jump branches to a location where another comparison subsumed by the first is found. If so, the first branch is redirected to either the destination of the second branch or a point immediately following it, depending on whether the condition is known to be true or false. Enabled at levels -O, -O2, -O3, -Os. }}} I could not find a reference to `-fthread-jumps` working with clang. This issue talks about how clang does not recognize a lot of flags (fthread-jumps included): https://github.com/pcsx2/pcsx2/issues/295 My guess is xscorch is meant to be built with GCC instead of Clang. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 04:14:43 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 04:14:43 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.56b0cd63fa92f7ebd4a5715799705442@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Comment (by jmroot): I was never able to repro on 10.6. {{{ % port -v installed python27-bootstrap The following ports are currently installed: python27-bootstrap @2.7.18_10 (active) requested_variants='' platform='darwin 10' archs='x86_64' date='2022-10-22T15:51:34+1100' % otool -L /opt/local/libexec/python27-bootstrap/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /lib-dynload/pyexpat.so /opt/local/libexec/python27-bootstrap/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /lib-dynload/pyexpat.so: /usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 06:37:57 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 06:37:57 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.95265d48c9b1b0367aa328082d094bf9@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Comment (by kencu): It appears Tiger doesn't have libexpat. Let me look closer at Leopard and see what is going on there. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:02:06 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 10:02:06 -0000 Subject: [MacPorts] #65323: ccache configure failure on Mac OS Monterey M1 In-Reply-To: <044.219279a1eeac95919bff684a1c0a39ce@macports.org> References: <044.219279a1eeac95919bff684a1c0a39ce@macports.org> Message-ID: <059.f818e3ac52aae2bbe6f346b069b95c85@macports.org> #65323: ccache configure failure on Mac OS Monterey M1 -------------------------+------------------------ Reporter: coliban | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: worksforme | Keywords: Port: ccache | -------------------------+------------------------ Changes (by ryandesign): * status: assigned => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:05:06 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 10:05:06 -0000 Subject: [MacPorts] #63419: ccache: use "configure.ccache no" In-Reply-To: <045.d7411abe9c0cbcc3ba8ec3e46fb347ab@macports.org> References: <045.d7411abe9c0cbcc3ba8ec3e46fb347ab@macports.org> Message-ID: <060.3130b1cdad799294046199678d9d2631@macports.org> #63419: ccache: use "configure.ccache no" -----------------------+------------------------ Reporter: szhorvat | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ccache | -----------------------+------------------------ Comment (by ryandesign): The update of hiredis to 1.1.0 2 days ago again broke ccache (and everything else that uses hiredis) because of the library name change and the failure to revbump everything that linked with it. See #66443. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:08:21 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 10:08:21 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.52353f9e1a8f6f7f53a5a044d297cf7c@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+------------------------ Reporter: thetrial | Owner: ryandesign Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ccache | -----------------------+------------------------ Changes (by ryandesign): * status: closed => reopened * resolution: fixed => Comment: Replying to [comment:1 jmroot]: > All dependents of hiredis needed to be rev bumped when the major library version changed. ''All dependents'' of hiredis that link with the library need to be revbumped. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:09:09 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 10:09:09 -0000 Subject: [MacPorts] #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis In-Reply-To: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> References: <045.c2d91180ca88dd6264b1f75c14ba2c60@macports.org> Message-ID: <060.a43651f27aaad9712d09ef5e8492b572@macports.org> #66443: ccache @4.7.4_0+doc: Broken library link after update of libhiredis -----------------------+-------------------------------------------- Reporter: thetrial | Owner: aeiouaeiouaeiouaeiouaeiouaeiou Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ccache | -----------------------+-------------------------------------------- Changes (by ryandesign): * status: reopened => assigned * owner: ryandesign => aeiouaeiouaeiouaeiouaeiouaeiou * cc: aeiouaeiouaeiouaeiouaeiouaeiou (removed) * cc: ryandesign (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 10:53:39 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 10:53:39 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.a11678d5e5685e34e6a27a4eef2c5fc0@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by Rezzy-dev): > If that fails, MacPorts then (unless you tell it not to) tries to download the source code distfile and build from that. This didn't happen. MacPorts didn't proceed to try to build the bogofilter dependency from the source. Instead the claws-mail installation failed on each occasion, with the error message that the expected binary package is missing (that it's an HTML file). I'm using the default, stable 2.8.0 build of MacPorts for OS 10.10 'out of the box', with no extra configuration. (I've just installed it.) So every user who tries to install claws-mail will experience this. My guess is that the installer perhaps didn't proceed to building bogofilter from the source because the 404 page was downloaded instead of the binary package, and the hash on that didn't match the expected file (obviously), so it aborted the installation. > We cannot know what happened if you don't attach the main.log file. I didn't save the log, because it was my first time trying to install something through MacPorts. The next package I installed, zim, installed with all its dependencies without issue. Attempting to install claws-mail again, I encountered the same problem. Only after manually downloading and moving the binary package to the installer's expected location was the installation able to complete. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:02:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:02:13 -0000 Subject: [MacPorts] #66452: muniversal portgroups add unnecessary dep on diffutils-for-muniversal Message-ID: <047.b708a40d43d38b02b64a946dc53bb9dd@macports.org> #66452: muniversal portgroups add unnecessary dep on diffutils-for-muniversal ------------------------+------------------------ Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: muniversal ------------------------+------------------------ The muniversal portgroups add an unnecessary dependency on the diffutils- for-muniversal port when the universal variant has not been selected. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:02:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:02:19 -0000 Subject: [MacPorts] #66291: php-meminfo: PHP 8.1 support In-Reply-To: <048.e8e8d3ef850cff44e7b6494d9d03dedb@macports.org> References: <048.e8e8d3ef850cff44e7b6494d9d03dedb@macports.org> Message-ID: <063.1105f2796bb745e2e4867b54c6a717ee@macports.org> #66291: php-meminfo: PHP 8.1 support --------------------------+------------------------ Reporter: ConnectGrid | Owner: ryandesign Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: php-meminfo | --------------------------+------------------------ Changes (by ryandesign): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"bae53a7fa0353b5fb14f6d284a7ab184df0380c8/macports-ports" bae53a7fa0353b5fb14f6d284a7ab184df0380c8/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bae53a7fa0353b5fb14f6d284a7ab184df0380c8" php*: Add php82 subports Closes: https://trac.macports.org/ticket/66291 Closes: https://trac.macports.org/ticket/66399 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:02:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:02:19 -0000 Subject: [MacPorts] #66399: php82-zip is missing In-Reply-To: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> References: <041.3fa492d3b126a88226715751c1ad2a7a@macports.org> Message-ID: <056.443c102a2752df8018a30ca781293980@macports.org> #66399: php82-zip is missing ----------------------+------------------------ Reporter: temp | Owner: ryandesign Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: php-zip | ----------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"bae53a7fa0353b5fb14f6d284a7ab184df0380c8/macports-ports" bae53a7fa0353b5fb14f6d284a7ab184df0380c8/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bae53a7fa0353b5fb14f6d284a7ab184df0380c8" php*: Add php82 subports Closes: https://trac.macports.org/ticket/66291 Closes: https://trac.macports.org/ticket/66399 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:02:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:02:19 -0000 Subject: [MacPorts] #66431: bash: Configuration logfiles contain indications of -Wimplicit-function-declaration in strchr and dup2 In-Reply-To: <043.ef83d265567921ac786c8942bb3c0692@macports.org> References: <043.ef83d265567921ac786c8942bb3c0692@macports.org> Message-ID: <058.7de21083771ad332086761a1bf623cef@macports.org> #66431: bash: Configuration logfiles contain indications of -Wimplicit-function- declaration in strchr and dup2 ---------------------+-------------------------------------------- Reporter: judaew | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: bash | ---------------------+-------------------------------------------- Comment (by ryandesign): In [changeset:"b3aff1b7158e7d552d06315d36e687756b933f87/macports-ports" b3aff1b7158e7d552d06315d36e687756b933f87/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b3aff1b7158e7d552d06315d36e687756b933f87" bash: Suppress strchr warning See: https://trac.macports.org/ticket/66431 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:02:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:02:19 -0000 Subject: [MacPorts] #66433: m4: Configuration logfiles contain indications of -Wimplicit-function-declaration In-Reply-To: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> References: <043.6bf0db7f4bc00e2cda1c4182fedde3bf@macports.org> Message-ID: <058.757fe652abc1bf776d60a5d4855a0ae9@macports.org> #66433: m4: Configuration logfiles contain indications of -Wimplicit-function- declaration ---------------------+-------------------------------------------- Reporter: judaew | Owner: (none) Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: wimplicit-function-declaration Port: m4 | ---------------------+-------------------------------------------- Comment (by ryandesign): In [changeset:"261293da070868496074b2397abdc21a72982e09/macports-ports" 261293da070868496074b2397abdc21a72982e09/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="261293da070868496074b2397abdc21a72982e09" m4: Suppress strchr warning See: https://trac.macports.org/ticket/66433 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:02:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:02:19 -0000 Subject: [MacPorts] #65435: coreutils @9.x: fix implicit declaration warnings In-Reply-To: <044.998906ad1927524603357d235a9f1d58@macports.org> References: <044.998906ad1927524603357d235a9f1d58@macports.org> Message-ID: <059.622981cde8953ae71640d102e053414a@macports.org> #65435: coreutils @9.x: fix implicit declaration warnings ----------------------------------------+------------------------------ Reporter: mascguy | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: implicit pending Port: coreutils coreutils-devel | ----------------------------------------+------------------------------ Comment (by ryandesign): In [changeset:"00461b59e05039c16a0cda04485ae34045607f32/macports-ports" 00461b59e05039c16a0cda04485ae34045607f32/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="00461b59e05039c16a0cda04485ae34045607f32" coreutils*: Suppress strchr warning See: https://trac.macports.org/ticket/65435 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:05:21 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:05:21 -0000 Subject: [MacPorts] #64561: xxdiff isn't using the right compiler In-Reply-To: <047.39b4989a5803fd5f9d61ab86b9df7017@macports.org> References: <047.39b4989a5803fd5f9d61ab86b9df7017@macports.org> Message-ID: <062.38a2051ccc01f33359857d969f5a0bea@macports.org> #64561: xxdiff isn't using the right compiler -------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: Port: xxdiff | -------------------------+--------------------------------- Comment (by barracuda156): Replying to [ticket:64561 ryandesign]: > Yet: > {{{ > gnumake: /opt/local/bin/clang++-mp-9.0: No such file or directory > }}} Any idea why this may happen? I get these errors with R packahes here: https://github.com/macports/macports- ports/pull/16916#issuecomment-1345639054 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 11:31:09 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 11:31:09 -0000 Subject: [MacPorts] #66453: R: incorrect info re compiler in the portfile Message-ID: <049.d81f637be6af6fb844223c1a8815593a@macports.org> #66453: R: incorrect info re compiler in the portfile --------------------------+------------------------ Reporter: barracuda156 | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: R --------------------------+------------------------ The portfile has: {{{ # Note: gcc cannot be used for the C compiler. It will give: #:info:build In file included from /usr/include/dispatch/dispatch.h:51:0, #:info:build from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:15, #:info:build from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFPropertyList.h:13, #:info:build from langprefs.c:30: #:info:build /usr/include/dispatch/object.h:143:15: error: expected identifier or '(' before '^' token #:info:build typedef void (^dispatch_block_t)(void); #:info:build ^ #:info:build /usr/include/dispatch/object.h:362:3: error: unknown type name 'dispatch_block_t' #:info:build dispatch_block_t notification_block); #:info:build ^ # However, use of compiler.blacklist *gcc* would remove the GCC Fortran compilers too. }}} This may be true for some versions of macOS, but this is false in general. GCC certainly ''can'' be used as the C compiler with R. P. S. Also I wonder, why no `universal` for R? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:23:44 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:23:44 -0000 Subject: [MacPorts] #66453: R: incorrect info re compiler in the portfile In-Reply-To: <049.d81f637be6af6fb844223c1a8815593a@macports.org> References: <049.d81f637be6af6fb844223c1a8815593a@macports.org> Message-ID: <064.248dce318f0369852800859bee2443c0@macports.org> #66453: R: incorrect info re compiler in the portfile ---------------------------+------------------------ Reporter: barracuda156 | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------------+------------------------ Comment (by kencu): clang supports -fblocks by default on systems thst natively support blocks. gcc does not https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352 So that would be why that is there. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:49:02 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:49:02 -0000 Subject: [MacPorts] #64036: SoftHSMv2 port causes free-after-free In-Reply-To: <047.4067cede4c6d9acd50161a7e80501ed1@macports.org> References: <047.4067cede4c6d9acd50161a7e80501ed1@macports.org> Message-ID: <062.c8f284596b5a1904e5aa183abf98f21c@macports.org> #64036: SoftHSMv2 port causes free-after-free -------------------------+-------------------- Reporter: mouse07410 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: softhsm | -------------------------+-------------------- Comment (by iay): I have pinged the upstream developers again. I'll give it a couple of weeks and then I will probably try and do the cherry-pick operation. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:52:28 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:52:28 -0000 Subject: [MacPorts] #66453: R: incorrect info re compiler in the portfile In-Reply-To: <049.d81f637be6af6fb844223c1a8815593a@macports.org> References: <049.d81f637be6af6fb844223c1a8815593a@macports.org> Message-ID: <064.d32a3568d7de3e3df5341a855ffe6c2f@macports.org> #66453: R: incorrect info re compiler in the portfile ---------------------------+------------------------ Reporter: barracuda156 | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------------+------------------------ Comment (by barracuda156): Replying to [comment:1 kencu]: > clang supports -fblocks by default on systems thst natively support blocks. > > gcc does not > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352 > > So that would be why that is there. Well, I guess the statement should have it explicitly ??since it is easy to verify that GCC works perfectly fine with R at least on <10.7. (And on PPC it is the only choice out there.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:54:08 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:54:08 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.253ce57e6851c1bca6a226ce775f9a0e@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by jmroot): Replying to [comment:7 Rezzy-dev]: > MacPorts didn't proceed to try to build the bogofilter dependency from the source. Instead the claws-mail installation failed on each occasion, with the error message that the expected binary package is missing (that it's an HTML file). If you got a checksum mismatch and a message saying, "The non-matching file appears to be HTML," that relates to the source tarball, not a binary package. It would also have pointed you to the MisbehavingServers wiki page, which lists several ways that can happen. One of them is indeed that a mirror serves a 404 page with a 200 response code. We could remove a misbehaving mirror from the list, but we would need to know which of the many mirrors it was. > So every user who tries to install claws-mail will experience this. Possibly every user who gets the download from the same mirror that you got it from. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:54:52 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:54:52 -0000 Subject: [MacPorts] #66454: Configure & build fail on G4/PPC 10.5.8 Message-ID: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> #66454: Configure & build fail on G4/PPC 10.5.8 ---------------------------+--------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libopus ---------------------------+--------------------- Build fails as per summary. Config & build logs attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:55:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:55:13 -0000 Subject: [MacPorts] #66454: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.45d123b7614ad32718bd0bb893afb492@macports.org> #66454: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Changes (by xanda-escuyer): * Attachment "libopus-config.log" added. Configure log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 14:55:45 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 14:55:45 -0000 Subject: [MacPorts] #66454: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.d0347cd1d04ffe764d3e79e6db88af72@macports.org> #66454: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Changes (by xanda-escuyer): * Attachment "libopus-main.log" added. Build main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 15:00:34 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 15:00:34 -0000 Subject: [MacPorts] #66453: R: incorrect info re compiler in the portfile In-Reply-To: <049.d81f637be6af6fb844223c1a8815593a@macports.org> References: <049.d81f637be6af6fb844223c1a8815593a@macports.org> Message-ID: <064.8fffea355a4265f20a155d3204a0b110@macports.org> #66453: R: incorrect info re compiler in the portfile ---------------------------+------------------------ Reporter: barracuda156 | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: R | ---------------------------+------------------------ Comment (by kencu): true. I?m not sure if R tests for -fblocks before using it now ? previously it seemed to assume it was available on darwin. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 15:02:26 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 15:02:26 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 (was: Configure & build fail on G4/PPC 10.5.8) In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.de3b6d97fbbada5f388b6a04065e6f67@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 15:10:10 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 15:10:10 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.7195c31bc8f9a1625a6e17c89b8539d6@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by kencu): although ideally MacPorts would thoroughly support building universal ppc/i386 on Leopard systems, in practice there are many problems doing this, and nobody is really trying to fix them as many can?t be fixed with current compiler tools available. Your overall happiness on this system will be much higher if you build as ppc only, without universal as much as possible. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 17:39:28 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 17:39:28 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.9712c0793ea91de73cbdbe5009f665ae@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by xanda-escuyer): Thank you for reply. Building for 'PPC only' indeed makes life a lot easier - most ports build just fine this way. Unfortunately there is no option in some cases and this is one of them. :-( -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 18:00:24 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 18:00:24 -0000 Subject: [MacPorts] #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 In-Reply-To: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> References: <051.4d9ab017b33bec3ccd5eaee88d978b9a@macports.org> Message-ID: <066.a2e282693519d6cce1e79aecb5210444@macports.org> #66421: pinentry-mac @0.9.4_1 extract failed in trace mode on OSX Ventura 13.0.1 -----------------------------+---------------------- Reporter: LudgerBreil209 | Owner: Ionic Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: pinentry-mac | -----------------------------+---------------------- Comment (by LudgerBreil209): it worked with that. Oddly enough, some other module (as dependencies) have been created successfully before. Anyway, maybe you should put a note in the setup FAQ. Thanks a lot! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 18:36:16 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 18:36:16 -0000 Subject: [MacPorts] #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the cmake options In-Reply-To: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> References: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> Message-ID: <062.c6569bfd0315c25d9b0046e9a22faabc@macports.org> #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the cmake options --------------------------+------------------------------- Reporter: janngobble | Owner: (none) Type: enhancement | Status: new Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: hdr10+ HDR10_PLUS Port: x265 | --------------------------+------------------------------- Description changed by janngobble: Old description: > x265 w/o ENABLE_HDR10_PLUS=ON doesn't allow x265/ffmpeg to handle HDR10+ > inputs w/o dropping the extra json. > > "dhdr_info" is not honored in this situation. > > Adding the simple option of ENABLE_HDR10_PLUS=ON to the cmake options > allows this. New description: x265 w/o ENABLE_HDR10_PLUS=ON doesn't allow x265/ffmpeg to handle HDR10+ inputs w/o dropping the extra json. "dhdr_info" is not honored in this situation. Adding the simple option of ENABLE_HDR10_PLUS=ON to the cmake options allows this. Basically, this is what needs to be done - and I don't know who did this but It's already here and just needs to be incorporated: https://p.dnnr.de/ga2IAr7WWE4qiMbS {{{ diff --git a/multimedia/x265/Portfile b/multimedia/x265/Portfile index 99e435c5635..3a6a94f7c27 100644 --- a/multimedia/x265/Portfile +++ b/multimedia/x265/Portfile @@ -55,6 +55,9 @@ platform darwin 10 { } } +configure.args-append \ + -DENABLE_HDR10_PLUS=On + if {${universal_possible} && [variant_isset universal] && ![variant_isset highdepth]} { if {"x86_64" in ${configure.universal_archs} || "i386" in ${configure.universal_archs}} { @@ -99,15 +102,15 @@ variant highdepth conflicts universal description {Enable 10-bit and 12-bit enco configure { set configure.dir ${workpath}/10bit - configure.args -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF + configure.args -DENABLE_HDR10_PLUS=ON -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF portconfigure::configure_main set configure.dir ${workpath}/12bit - configure.args -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON + configure.args -DENABLE_HDR10_PLUS=ON -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON portconfigure::configure_main set configure.dir ${workpath}/build - configure.args -DEXTRA_LIB="x265_main10.a\;x265_main12.a" -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON + configure.args -DENABLE_HDR10_PLUS=ON -DEXTRA_LIB="x265_main10.a\;x265_main12.a" -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON portconfigure::configure_main } }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 18:36:46 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 18:36:46 -0000 Subject: [MacPorts] #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options (was: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the cmake options) In-Reply-To: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> References: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> Message-ID: <062.ba56487dfd09039bba132777f5df8dfe@macports.org> #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options --------------------------+------------------------------- Reporter: janngobble | Owner: (none) Type: enhancement | Status: new Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: hdr10+ HDR10_PLUS Port: x265 | --------------------------+------------------------------- Description changed by janngobble: Old description: > x265 w/o ENABLE_HDR10_PLUS=ON doesn't allow x265/ffmpeg to handle HDR10+ > inputs w/o dropping the extra json. > > "dhdr_info" is not honored in this situation. > > Adding the simple option of ENABLE_HDR10_PLUS=ON to the cmake options > allows this. > > Basically, this is what needs to be done - and I don't know who did this > but It's already here and just needs to be incorporated: > > https://p.dnnr.de/ga2IAr7WWE4qiMbS > > {{{ > diff --git a/multimedia/x265/Portfile b/multimedia/x265/Portfile > index 99e435c5635..3a6a94f7c27 100644 > --- a/multimedia/x265/Portfile > +++ b/multimedia/x265/Portfile > @@ -55,6 +55,9 @@ platform darwin 10 { > } > } > > +configure.args-append \ > + -DENABLE_HDR10_PLUS=On > + > if {${universal_possible} && [variant_isset universal] && > ![variant_isset highdepth]} { > > if {"x86_64" in ${configure.universal_archs} || "i386" in > ${configure.universal_archs}} { > @@ -99,15 +102,15 @@ variant highdepth conflicts universal description > {Enable 10-bit and 12-bit enco > configure { > > set configure.dir ${workpath}/10bit > - configure.args -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF > -DENABLE_SHARED=OFF -DENABLE_CLI=OFF > + configure.args -DENABLE_HDR10_PLUS=ON -DHIGH_BIT_DEPTH=ON > -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF > portconfigure::configure_main > > set configure.dir ${workpath}/12bit > - configure.args -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF > -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON > + configure.args -DENABLE_HDR10_PLUS=ON -DHIGH_BIT_DEPTH=ON > -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON > portconfigure::configure_main > > set configure.dir ${workpath}/build > - configure.args -DEXTRA_LIB="x265_main10.a\;x265_main12.a" > -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON > + configure.args -DENABLE_HDR10_PLUS=ON > -DEXTRA_LIB="x265_main10.a\;x265_main12.a" -DEXTRA_LINK_FLAGS=-L. > -DLINKED_10BIT=ON -DLINKED_12BIT=ON > portconfigure::configure_main > > } > }}} New description: x265 w/o ENABLE_HDR10_PLUS=ON doesn't allow x265/ffmpeg to handle HDR10+ inputs w/o dropping the extra json. "dhdr_info" is not honored in this situation. Adding the simple option of ENABLE_HDR10_PLUS=ON to the configuration options allows this. Basically, this is what needs to be done - and I don't know who did this but It's already here and just needs to be incorporated: https://p.dnnr.de/ga2IAr7WWE4qiMbS {{{ diff --git a/multimedia/x265/Portfile b/multimedia/x265/Portfile index 99e435c5635..3a6a94f7c27 100644 --- a/multimedia/x265/Portfile +++ b/multimedia/x265/Portfile @@ -55,6 +55,9 @@ platform darwin 10 { } } +configure.args-append \ + -DENABLE_HDR10_PLUS=On + if {${universal_possible} && [variant_isset universal] && ![variant_isset highdepth]} { if {"x86_64" in ${configure.universal_archs} || "i386" in ${configure.universal_archs}} { @@ -99,15 +102,15 @@ variant highdepth conflicts universal description {Enable 10-bit and 12-bit enco configure { set configure.dir ${workpath}/10bit - configure.args -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF + configure.args -DENABLE_HDR10_PLUS=ON -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF portconfigure::configure_main set configure.dir ${workpath}/12bit - configure.args -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON + configure.args -DENABLE_HDR10_PLUS=ON -DHIGH_BIT_DEPTH=ON -DEXPORT_C_API=OFF -DENABLE_SHARED=OFF -DENABLE_CLI=OFF -DMAIN12=ON portconfigure::configure_main set configure.dir ${workpath}/build - configure.args -DEXTRA_LIB="x265_main10.a\;x265_main12.a" -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON + configure.args -DENABLE_HDR10_PLUS=ON -DEXTRA_LIB="x265_main10.a\;x265_main12.a" -DEXTRA_LINK_FLAGS=-L. -DLINKED_10BIT=ON -DLINKED_12BIT=ON portconfigure::configure_main } }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 19:16:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 19:16:13 -0000 Subject: [MacPorts] #66445: py36-mongoengine: Error: No such port: py36-pymongo In-Reply-To: <047.e6363ad0586c9c96951c63965ebace84@macports.org> References: <047.e6363ad0586c9c96951c63965ebace84@macports.org> Message-ID: <062.7ea4a761629f75ddf50f0e6084a1351f@macports.org> #66445: py36-mongoengine: Error: No such port: py36-pymongo ----------------------------------------+------------------------ Reporter: ryandesign | Owner: neverpanic Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-mongoengine py-pymongo | ----------------------------------------+------------------------ Changes (by neverpanic): * owner: (none) => neverpanic * status: new => closed * resolution: => fixed Comment: In [changeset:"e64c627954b0209fa98eda94e501750891b983bb/macports-ports" e64c627954b0209fa98eda94e501750891b983bb/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e64c627954b0209fa98eda94e501750891b983bb" py-pymongoengine: Update to 0.24.2, add modern python, drop old python Also drop maintainership, I no longer use this. Closes: https://trac.macports.org/ticket/66445 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 19:37:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 19:37:13 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.40c51f1cab85cb71a18a64573adce18a@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by kencu): why is it that you need it universal, may I ask? In the libopus Portfile, it has already fixed this error, by the way: {{{ platform i386 { # checking How to get X86 CPU Info... configure: error: no supported Get CPU Info method, please disable intrinsics compiler.blacklist *gcc-4.* {clang < 500} } }}} however, that fix won't work if you're trying to build it on a PPC as universal, due to the way it's written.. And 100,000 other similar cases that make building universal i386/ppc on Leopard a problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:12:41 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 20:12:41 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.7624b7418d916022c07154b4a24d1949@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by michaelld): This works for `cmake`, but not `cmake-devel` ... Replying to [comment:11 jmroot]: > In [changeset:"8ae0d73589330693f3b17849fdd5e65f0f56a5c1/macports-base" 8ae0d73589330693f3b17849fdd5e65f0f56a5c1/macports-base] (master): {{{ $ sudo port -d patch cmake-devel [snip] DEBUG: system: cd "/opt/local/var/macports/build /_opt_sources_MacPorts_ports_github_macports_devel_cmake-devel/cmake- devel/work" && /opt/local/bin/lbzip2 -dc '/opt/sources/MacPorts/distfiles/cmake/cmake- 5676593be9bd3a26995f35b9db8fe5b9af8ea32e.tar.bz2' | /usr/bin/tar -xf - DEBUG: euid/egid changed to: 0/0 DEBUG: chowned /opt/local/var/macports/build /_opt_sources_MacPorts_ports_github_macports_devel_cmake-devel/cmake- devel/work to macports DEBUG: euid/egid changed to: 503/501 DEBUG: extract.rename: Renaming cmake- 5676593be9bd3a26995f35b9db8fe5b9af8ea32e -> cmake- 5676593be9bd3a26995f35b9db8fe5b9af8ea32e Error: Failed to extract cmake-devel: error renaming "/opt/local/var/macports/build /_opt_sources_MacPorts_ports_github_macports_devel_cmake-devel/cmake- devel/work/cmake-5676593be9bd3a26995f35b9db8fe5b9af8ea32e" to "/opt/local/var/macports/build /_opt_sources_MacPorts_ports_github_macports_devel_cmake-devel/cmake- devel/work/cmake-5676593be9bd3a26995f35b9db8fe5b9af8ea32e/cmake- 5676593be9bd3a26995f35b9db8fe5b9af8ea32e": trying to rename a volume or move a directory into itself DEBUG: Error code: NONE [snip] $ pushd $(port work cmake-devel) /opt/local/var/macports/build /_opt_sources_MacPorts_ports_github_macports_devel_cmake-devel/cmake- devel/work /opt/sources/MacPorts/ports/github_macports $ ll total 8 drwxrwxrwx 2 macports wheel 64 Dec 12 15:07 .home/ -rw-rw-rw- 1 macports wheel 143 Dec 12 15:07 .macports.cmake- devel.state drwxrwxrwx 2 macports wheel 64 Dec 12 15:07 .tmp/ drwxrwxrwx 29 macports wheel 928 Nov 30 08:57 cmake- 5676593be9bd3a26995f35b9db8fe5b9af8ea32e/ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 20:29:15 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 20:29:15 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.d428413b4595d44cb485c553a22eee2a@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by michaelld): The `ll` above is what I see when using `port` still using the old linking method ... meaning, it doesn't actually do anything for this style of `worksrcdir` ... hopefully this helps fix the issue! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:06:17 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:06:17 -0000 Subject: [MacPorts] #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options In-Reply-To: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> References: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> Message-ID: <062.8102b83b65354b0c66251febe9652821@macports.org> #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options --------------------------+------------------------------- Reporter: janngobble | Owner: (none) Type: enhancement | Status: new Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: hdr10+ HDR10_PLUS Port: x265 | --------------------------+------------------------------- Comment (by eborisch): Pull request: https://github.com/macports/macports-ports/pull/16961 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:27:12 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:27:12 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.515018ab0baf3c775e0985d923ea75fb@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by xanda-escuyer): Thanks for your interest. To answer the question: We don't need it universal per se; our ultimate aim is to build [https://ports.macports.org/port/ReadyMedia/details ReadyMedia] However, from the port health for ReadyMedia, it seems PPC is unknown. Setting the universal flag was an attempt to see if it was possible/feasible to achieve this as {{{ReadyMedia}}} requires a {{{universal}}} build of {{{ffmpeg}}} (and hence {{{libopus}}} as reported above). Of course if we are barking up the wrong tree then please accept our apologies; it's not our way to create unnecessary work especially for volunteers such as yourself. :-) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:31:50 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:31:50 -0000 Subject: [MacPorts] #66456: openems @v 20220331-d260025a install failure with CSXCAD Message-ID: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> #66456: openems @v 20220331-d260025a install failure with CSXCAD ----------------------+--------------------- Reporter: esteimle | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: openems ----------------------+--------------------- I tried to install openems with the command sudo port install openEMS but it failed while trying to build CSXCAD: {{{ ---> Verifying checksums for CSXCAD ---> Extracting CSXCAD ---> Applying patches to CSXCAD ---> Configuring CSXCAD ---> Building CSXCAD Error: Failed to build CSXCAD: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_CSXCAD/CSXCAD/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port openEMS failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:33:51 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:33:51 -0000 Subject: [MacPorts] #66456: openems @v 20220331-d260025a install failure with CSXCAD In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.f667d517a4a551c4d09108d322705cce@macports.org> #66456: openems @v 20220331-d260025a install failure with CSXCAD -----------------------+-------------------- Reporter: esteimle | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openems | -----------------------+-------------------- Changes (by esteimle): * Attachment "main.log" added. /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_CSXCAD/CSXCAD/main.log. Log file mentioned in error. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:43:40 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:43:40 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. Message-ID: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------------------+---------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: libgcc12, mpc, gcc12, libgcc | Port: libgcc12 ------------------------------------------+---------------------- I've attached my config.log, but the relevant part is likely this: {{{ configure:8226: /usr/bin/clang -arch x86_64 -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -I/opt/local/include -I/opt/local/include -I/opt/local/include -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk conftest.c >&5 In file included from conftest.c:10: /opt/local/include/mpc.h:287:35: error: unknown type name 'FILE' __MPC_DECLSPEC void mpcr_out_str (FILE *f, mpcr_srcptr r); ^ 1 error generated. configure:8226: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define LT_OBJDIR ".libs/" | /* end confdefs.h. */ | #include | int | main () | { | | #if MPC_VERSION < MPC_VERSION_NUM(0,8,0) | choke me | #endif | | ; | return 0; | } configure:8251: result: no configure:8309: error: Building GCC requires GMP 4.2+, MPFR 3.1.0+ and MPC 0.8.0+. Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify their locations. Source code for these libraries can be found at their respective hosting sites as well as at https://gcc.gnu.org/pub/gcc/infrastructure/. See also http://gcc.gnu.org/install/prerequisites.html for additional info. If you obtained GMP, MPFR and/or MPC from a vendor distribution package, make sure that you have installed both the libraries and the header files. They may be located in separate packages. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:44:00 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:44:00 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.6dfcbf0d26d7f55bf1f3db482457cecc@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. -----------------------+------------------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: libgcc12, mpc, gcc12, libgcc Port: libgcc12 | -----------------------+------------------------------------------ Changes (by ragnese): * Attachment "config.log" added. config.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 21:51:23 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 21:51:23 -0000 Subject: [MacPorts] #66458: libgcc12 @12.2.0 fails to configure - include mpc.h broken Message-ID: <043.7b85032f12a905f17df502f8cc2ea631@macports.org> #66458: libgcc12 @12.2.0 fails to configure - include mpc.h broken --------------------+----------------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: libgcc12 libmpc --------------------+----------------------------- One of the configure checks for libgcc12 is failing. It is checking MPC version is >= 0.8.0, but instead has trouble compiling the check driver. The build seems to be choking on a simple include of . {{{ $ port build libgcc12 /usr/bin/clang -arch x86_64 -c -pipe -Os -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk -I/opt/local/include -I/opt/local/include -I/opt/local/include -I/opt/local/include -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk conftest.c In file included from conftest.c:10: /opt/local/include/mpc.h:287:35: error: unknown type name 'FILE' __MPC_DECLSPEC void mpcr_out_str (FILE *f, mpcr_srcptr r); ^ 1 error generated. configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define LT_OBJDIR ".libs/" | /* end confdefs.h. */ | #include | int | main () | { | | #if MPC_VERSION < MPC_VERSION_NUM(0,8,0) | choke me | #endif | | ; | return 0; | } }}} Can be reproduced with just an include: {{{ $ cat x.c #include $ /usr/bin/clang -arch x86_64 -c -pipe -Os -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk -I/opt/local/include x.c In file included from x.c:1: /opt/local/include/mpc.h:287:35: error: unknown type name 'FILE' __MPC_DECLSPEC void mpcr_out_str (FILE *f, mpcr_srcptr r); ^ }}} System: OS 13, xcodebuild -version "Xcode 14.1, Build version 14B47b" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 22:28:17 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 22:28:17 -0000 Subject: [MacPorts] #66439: irrlichtmt fails to install on Mac OS 10.6 In-Reply-To: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> References: <052.a7360ee740629a2adb81f61fe4896ac4@macports.org> Message-ID: <067.544704d6177620c53d4a67a36da12601@macports.org> #66439: irrlichtmt fails to install on Mac OS 10.6 ------------------------------+---------------------- Reporter: programmingkidx | Owner: l2dy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: irrlichtmt | ------------------------------+---------------------- Comment (by aeiouaeiouaeiouaeiouaeiouaeiou): Minetest is no longer compatible with Irrlicht. https://github.com/minetest/minetest/commit/16a30556dfa8e27c82d026bd63467f82d2e37a1c -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 23:04:48 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 23:04:48 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.e9f15c7d9cd4db6478b29d621795ae1e@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by kencu): I see. By the standard methods MacPorts will have trouble building this as universal on either an Intel or PPC system, but there may be ways to do it. I'll see if I can come up with something for you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 00:17:35 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 00:17:35 -0000 Subject: [MacPorts] #65312: bowtie v 1.2.3 In-Reply-To: <045.fe4a4f47ca1d1a7e5edb931a1cd9009b@macports.org> References: <045.fe4a4f47ca1d1a7e5edb931a1cd9009b@macports.org> Message-ID: <060.b721ee703f8c80091d51ef69478cf1f0@macports.org> #65312: bowtie v 1.2.3 -----------------------+--------------------------------- Reporter: Minhas61 | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: bowtie | -----------------------+--------------------------------- Changes (by catap): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"30032d091fbf93d8da5cf5a1f1ec758ce3023a8a/macports-ports" 30032d091fbf93d8da5cf5a1f1ec758ce3023a8a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="30032d091fbf93d8da5cf5a1f1ec758ce3023a8a" bowtie: update to 1.3.1 Closes: https://trac.macports.org/ticket/65312 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 02:51:36 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 02:51:36 -0000 Subject: [MacPorts] #66458: libgcc12 @12.2.0 fails to configure - include mpc.h broken In-Reply-To: <043.7b85032f12a905f17df502f8cc2ea631@macports.org> References: <043.7b85032f12a905f17df502f8cc2ea631@macports.org> Message-ID: <058.af18114723735c76b1c2d8c47fab283c@macports.org> #66458: libgcc12 @12.2.0 fails to configure - include mpc.h broken ------------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libgcc12 libmpc | ------------------------------+-------------------- Comment (by thaumkid): I had the same issue - to fix it, I had to modify /opt/local/include/mpc.h and after line 24, insert the line, "#include ". Afterwards, port install libgcc12 was successful -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 03:03:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 03:03:18 -0000 Subject: [MacPorts] #66141: py310-awscrt @0.14.0_0: build fatal warning: -undefined dynamic_lookup may not work with chained fixups In-Reply-To: <046.f5c2a5747aec2f67f6907ffb02bee3f3@macports.org> References: <046.f5c2a5747aec2f67f6907ffb02bee3f3@macports.org> Message-ID: <061.1c0d2ce73054a91aaefe6e9dd1704c4b@macports.org> #66141: py310-awscrt @0.14.0_0: build fatal warning: -undefined dynamic_lookup may not work with chained fixups ------------------------+---------------------- Reporter: ianthrive | Owner: dgilman Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: py-awscrt | ------------------------+---------------------- Comment (by jre21): dgilman: Can you please update this port to the latest upstream version (currently 0.16.1)? Per https://github.com/awslabs/aws-crt- python/issues/410#issuecomment-1347441002 and my own testing later in that thread, updating awscrt to 0.15.2 should resolve this build failure. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 03:26:03 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 03:26:03 -0000 Subject: [MacPorts] #66448: Is the xz port missing for Apple Silicon? In-Reply-To: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> References: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> Message-ID: <058.62c34f05122f0caf9720427f1bc6dec3@macports.org> #66448: Is the xz port missing for Apple Silicon? ---------------------+--------------------------- Reporter: russes | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: xz | ---------------------+--------------------------- Comment (by russes): Thanks. Close this ticket, but leave it for others to find. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 03:29:42 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 03:29:42 -0000 Subject: [MacPorts] #66448: Is the xz port missing for Apple Silicon? In-Reply-To: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> References: <043.eabcb41898582a4dd6bc46c4fef80d89@macports.org> Message-ID: <058.13a2f8e64f73ef7de3cb7e1e0756a9fc@macports.org> #66448: Is the xz port missing for Apple Silicon? -------------------------+--------------------------- Reporter: russes | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura arm64 Port: xz | -------------------------+--------------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 05:11:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 05:11:08 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.afd1f53c3c0e2a7243ecaf8ca6cedca0@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by jmroot): This is probably something that should be handled in the gitlab portgroup. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 05:29:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 05:29:15 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.47cc615f948c3fa487d4f6fdf2cd3a5c@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by jmroot): For that matter, why is cmake (not -devel) using gitlab generated downloads at all? There are proper release tarballs on GitHub and that's where https://cmake.org/download/ is pointing now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:17:51 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 06:17:51 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.0a2b0e84fcec7618be164aba55928985@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by kencu): This can work. Add this to the Portfile, below the place where configure.args is already specified: {{{ configure.args-append --disable-rtcd }}} and building on Leopard PPC will build universal as i386/ppc: {{{ $ port -v installed libopus The following ports are currently installed: libopus @1.3.1_0+universal (active) requested_variants='+universal' platform='darwin 9' archs='i386 ppc' date='2022-12-12T22:12:46-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 06:19:44 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 06:19:44 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.3b75fe966ec5e8bd9a30b876c2fcc6e3@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by kencu): There is a more complicated fix, that copies in the cpuid.h file from a newer version of gcc, such as gcc7, specifies it in an include path, and disables PIC, but that might be excessively complicated considering the application here and the fact that this code won't be running on state-of- the-art Intel processors. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:23:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 07:23:23 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' (was: openems @v 20220331-d260025a install failure with CSXCAD) In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.f2b6d67bb82cd71d3cf19df09d18c15c@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+---------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: CSXCAD | -----------------------+---------------------- Changes (by jmroot): * owner: (none) => ra1nb0w * status: new => assigned * port: openems => CSXCAD -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:25:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 07:25:18 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.f1ef6a01957154ef286a025bdfefdb29@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. -----------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 | -----------------------+--------------------- Changes (by jmroot): * keywords: libgcc12, mpc, gcc12, libgcc => ventura -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:25:50 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 07:25:50 -0000 Subject: [MacPorts] #66458: libgcc12 @12.2.0 fails to configure - include mpc.h broken In-Reply-To: <043.7b85032f12a905f17df502f8cc2ea631@macports.org> References: <043.7b85032f12a905f17df502f8cc2ea631@macports.org> Message-ID: <058.4e47e540b6056036efacb18543644f2e@macports.org> #66458: libgcc12 @12.2.0 fails to configure - include mpc.h broken ------------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: libgcc12 libmpc | ------------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate Comment: #66457 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 07:26:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 07:26:18 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.f43bc43d5c05d619b7829d8ddd6a4544@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Changes (by jmroot): * port: libgcc12 => libgcc12 libmpc -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 12 15:29:12 2022 From: noreply at macports.org (MacPorts) Date: Mon, 12 Dec 2022 15:29:12 -0000 Subject: [MacPorts] #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the cmake options Message-ID: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the cmake options -------------------------------+-------------------- Reporter: janngobble | Owner: (none) Type: enhancement | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: hdr10+ HDR10_PLUS | Port: x265 -------------------------------+-------------------- x265 w/o ENABLE_HDR10_PLUS=ON doesn't allow x265/ffmpeg to handle HDR10+ inputs w/o dropping the extra json. "dhdr_info" is not honored in this situation. Adding the simple option of ENABLE_HDR10_PLUS=ON to the cmake options allows this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:25:34 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 09:25:34 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.f85eff39c4cbaeca5251847d23fe592e@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Comment (by freedomtan): Quick solution is to add `#include `, then there won't be `FILE` problem -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:35:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 09:35:31 -0000 Subject: [MacPorts] #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file Message-ID: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: git -------------------------+-------------------- {{{ Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0" && /usr/bin/patch -p1 < '/opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/devel/git/files /patch-ignore-fsmonitor-daemon-backend.diff' DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0" && /usr/bin/patch -p1 < '/opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/devel/git/files /patch-ignore-fsmonitor-daemon-backend.diff' patching file Makefile Hunk #1 FAILED at 2016. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0" && /usr/bin/patch -p1 < '/opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/devel/git/files /patch-ignore-fsmonitor-daemon-backend.diff' Exit code: 1 Error: Failed to patch git: command execution failed DEBUG: Error code: CHILDSTATUS 6143 1 DEBUG: Backtrace: command execution failed while executing "system {*}$notty {*}$callback {*}$nice $fullcmdstring" invoked from within "command_exec patch "" "< '$patch'"" (procedure "portpatch::patch_main" line 41) invoked from within "$procedure $targetname" Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/main.log for details. }}} `Makefile` has now: {{{ 2148 ifdef FSMONITOR_DAEMON_BACKEND 2149 COMPAT_CFLAGS += -DHAVE_FSMONITOR_DAEMON_BACKEND 2150 COMPAT_OBJS += compat/fsmonitor/fsm- listen-$(FSMONITOR_DAEMON_BACKEND).o 2151 COMPAT_OBJS += compat/fsmonitor/fsm- health-$(FSMONITOR_DAEMON_BACKEND).o 2152 COMPAT_OBJS += compat/fsmonitor/fsm- ipc-$(FSMONITOR_DAEMON_BACKEND).o 2153 endif 2154 2155 ifdef FSMONITOR_OS_SETTINGS 2156 COMPAT_CFLAGS += -DHAVE_FSMONITOR_OS_SETTINGS 2157 COMPAT_OBJS += compat/fsmonitor/fsm- settings-$(FSMONITOR_OS_SETTINGS).o 2158 COMPAT_OBJS += compat/fsmonitor/fsm-path- utils-$(FSMONITOR_OS_SETTINGS).o 2159 endif }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:36:11 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 09:36:11 -0000 Subject: [MacPorts] #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file In-Reply-To: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> References: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> Message-ID: <061.350fc17fadfb8fe12f6cb9618a9e1b2b@macports.org> #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: git | ------------------------+------------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Leopard -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:52:20 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 09:52:20 -0000 Subject: [MacPorts] #66460: Libgcc12 not working on MacOS Ventura (arm64). Message-ID: <044.787d544b393140a7a73637907158ddd9@macports.org> #66460: Libgcc12 not working on MacOS Ventura (arm64). --------------------------------------+----------------------------- Reporter: ftroisi | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.8.99 Keywords: Libgcc12, Ventura, arm64 | Port: libgcc12 --------------------------------------+----------------------------- Dear MacPort, I was trying to install the port gcc12 on my MacMini (with M1 CPU), running Ventura OS. I ran into the following error with the dependency port Libgcc12: ---> Fetching archive for libgcc12 ---> Attempting to fetch libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from https://cph.dk.packages.macports.org/libgcc12 ---> Attempting to fetch libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/libgcc12 ---> Attempting to fetch libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc12 ---> Fetching distfiles for libgcc12 ---> Attempting to fetch gcc-12.2.0.tar.xz from ftp://ftp.gwdg.de/pub/linux/gcc/releases/gcc-12.2.0/ ---> Attempting to fetch gcc-12.2.0.tar.xz from https://cph.dk.distfiles.macports.org/gcc12 ---> Verifying checksums for libgcc12 ---> Extracting libgcc12 ---> Applying patches to libgcc12 ---> Configuring libgcc12 Error: Failed to configure libgcc12: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/work/build/config.log Error: Failed to configure libgcc12: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gcc12 failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 09:59:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 09:59:43 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.3d1398ef7765b5b4ae83532445cca99d@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Comment (by cjones051073): Note I am unable to run macOS 13 myself (no hardware that supports it) but I can also reproduce this on macOS12, so probably related to an Xcode update that both macOS12 and 13 now use. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:00:28 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:00:28 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.d9afad77c7ab9a7bce22672471cd4be6@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Comment (by cjones051073): b.t.w. just including stdio.h in the test does not seem enough {{{ configure:8227: /usr/bin/clang -arch x86_64 -c -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -I/opt/local/include -I/opt/local/include -I/opt/local/include -I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk conftest.c >&5 In file included from conftest.c:10: /opt/local/include/mpc.h:287:35: error: unknown type name 'FILE' __MPC_DECLSPEC void mpcr_out_str (FILE *f, mpcr_srcptr r); ^ 1 error generated. configure:8227: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define LT_OBJDIR ".libs/" | /* end confdefs.h. */ | #include | #include | int | main () | { | | #if MPC_VERSION < MPC_VERSION_NUM(0,8,0) | choke me | #endif | | ; | return 0; | } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:03:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:03:15 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.995a916ce1299a0d251cf4364ae801e6@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+---------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: CSXCAD | -----------------------+---------------------- Comment (by ra1nb0w): sorry for the inconvenience. Now, it is fixed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:03:16 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:03:16 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.8c9b8529363fdeebb562a97bea07fd3a@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+--------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: CSXCAD | -----------------------+--------------------- Changes (by Davide Gerhard ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"988da34948a987d408cc5718df7357eb65d1c0e1/macports-ports" 988da34948a987d408cc5718df7357eb65d1c0e1/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="988da34948a987d408cc5718df7357eb65d1c0e1" CSXCAD: update commit to 633597648 Closes: https://trac.macports.org/ticket/66456 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:13:03 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:13:03 -0000 Subject: [MacPorts] #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options In-Reply-To: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> References: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> Message-ID: <062.ea4505fbcb34bc77a5f2d7fc1e4695ab@macports.org> #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options --------------------------+-------------------- Reporter: janngobble | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: x265 | --------------------------+-------------------- Changes (by neverpanic): * keywords: hdr10+ HDR10_PLUS => * priority: High => Normal -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:20:07 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:20:07 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.3e2487afc537ceb00cbd0d0298c649fa@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Comment (by cjones051073): Issue is easy to reproduce standalone {{{ Oberon ~/Downloads > cat conftest.c #include #include int main () { #if MPC_VERSION < MPC_VERSION_NUM(0,8,0) choke me #endif return 0; } Oberon ~/Downloads > clang -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -I/opt/local/include conftest.c In file included from conftest.c:1: /opt/local/include/mpc.h:287:35: error: unknown type name 'FILE' __MPC_DECLSPEC void mpcr_out_str (FILE *f, mpcr_srcptr r); ^ 1 error generated. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:22:54 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:22:54 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.2405f2ec99c4eb99957b41b0d84f6137@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Comment (by cjones051073): Also now seen in the new macOS 13 buildbots https://ports.macports.org/port/libgcc12/builds/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:28:19 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:28:19 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.8d88ac3977e3b6414add7b6d47211ac3@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Changes (by cjones051073): * cc: kencu (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:28:54 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:28:54 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.0e7f0a7cad02eb8e731b47d65a86883f@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+--------------------- Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc12 libmpc | ------------------------------+--------------------- Comment (by cjones051073): Ken, any thoughts here ? Do you know if Iain is aware of this or not ? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:31:14 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:31:14 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 Message-ID: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: leopard ppc | Port: graphviz-devel -------------------------+---------------------------- I am reorganising the installed `ports` in order to get rid of `requested variants` when they are already the `default variants`. Maybe I made a mistake by `selfupdate`ing this morning before continuing. After forcibly `uninstall`ing `graphviz` (was `deactivate`d before) and `graphviz-devel` `port` has its own ideas and tries to install `graphviz` instead of `graphviz-devel` when I ask it to: {{{ port -vds install graphviz-devel +gdk_pixbuf +poppler +rsvg }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:32:13 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:32:13 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 In-Reply-To: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> References: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> Message-ID: <061.04bbf48df69f614eec6486743710644b@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -----------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz-devel | -----------------------------+------------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Leopard -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:46:54 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:46:54 -0000 Subject: [MacPorts] #66462: port cannot install again graphviz on PPC Leopard, Mac OS X 10.5.6 Message-ID: <046.08f27338a5462eb4661ebef7c02215e7@macports.org> #66462: port cannot install again graphviz on PPC Leopard, Mac OS X 10.5.6 -------------------------+---------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: leopard ppc | Port: graphviz -------------------------+---------------------- Because `installing graphviz-devel` does not work, I am trying to install `graphviz +gdk_pixbuf +poppler +rsvg`, which fails: {{{ Error: Requested variants "+pangocairo+x11" do not match those the build was started with: "+gdk_pixbuf+pangocairo+poppler+rsvg+x11". Error: Please use the same variants again, or run 'port clean graphviz' first to remove the existing partially completed build. Error: Problem while installing graphviz DEBUG: upgrade librsvg failed while executing "macports::_upgrade_mport_deps $mport $target" (procedure "mportexec" line 46) invoked from within "mportexec $workername $target" Error: Unable to execute port: upgrade librsvg failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:47:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:47:31 -0000 Subject: [MacPorts] #66462: port cannot install again graphviz on PPC Leopard, Mac OS X 10.5.6 In-Reply-To: <046.08f27338a5462eb4661ebef7c02215e7@macports.org> References: <046.08f27338a5462eb4661ebef7c02215e7@macports.org> Message-ID: <061.0a842c1d395f20f4ca071eb7be3d27b9@macports.org> #66462: port cannot install again graphviz on PPC Leopard, Mac OS X 10.5.6 ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz | ------------------------+------------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Leopard -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:56:13 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:56:13 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.b8c8d372a80836482e8ef0e3811b04ef@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Changes (by cjones051073): * keywords: ventura => ventura monterey -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 10:59:30 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 10:59:30 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.90e98e78f99a55443a6d859d9d1b63a5@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by cjones051073): OK, my mistake. stdio.h needs to be included *before* mpc.h {{{ Oberon ~/Downloads > cat conftest.c #include #include int main () { #if MPC_VERSION < MPC_VERSION_NUM(0,8,0) choke me #endif return 0; } Oberon ~/Downloads > clang -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -I/opt/local/include conftest.c Oberon ~/Downloads > }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 11:25:59 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 11:25:59 -0000 Subject: [MacPorts] #66457: libgcc12 build fails during configure test for MPC dep. In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.42a9466139f2f39863f7a37ddcaccf89@macports.org> #66457: libgcc12 build fails during configure test for MPC dep. ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by cjones051073): I have pushed https://github.com/macports/macports- ports/commit/9332dbb202005f90c4aa5c9e069edeb4d804d117 The issue is, I think, with limbic as `mpc.h` directly uses FILE it should directly first include `stdio.h` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 12:03:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 12:03:43 -0000 Subject: [MacPorts] #66460: Libgcc12 not working on MacOS Ventura (arm64). In-Reply-To: <044.787d544b393140a7a73637907158ddd9@macports.org> References: <044.787d544b393140a7a73637907158ddd9@macports.org> Message-ID: <059.82d7fabb046ccfeaff179e27abe13abb@macports.org> #66460: Libgcc12 not working on MacOS Ventura (arm64). ------------------------+-------------------------------------- Reporter: ftroisi | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.8.99 Resolution: duplicate | Keywords: Libgcc12, Ventura, arm64 Port: libgcc12 | ------------------------+-------------------------------------- Changes (by cjones051073): * status: new => closed * resolution: => duplicate Comment: You have not really posted enough information to be sure of the issue (you should attach the complete log) but I strongly suspect this is a duplicate of https://trac.macports.org/ticket/66457 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 12:05:57 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 12:05:57 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE (was: libgcc12 build fails during configure test for MPC dep.) In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.179623b17dd191d97c7aad5982deeb11@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 12:50:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 12:50:43 -0000 Subject: [MacPorts] #66460: Libgcc12 not working on MacOS Ventura (arm64). In-Reply-To: <044.787d544b393140a7a73637907158ddd9@macports.org> References: <044.787d544b393140a7a73637907158ddd9@macports.org> Message-ID: <059.de5ed3a55b565e17019c6dddb18351c5@macports.org> #66460: Libgcc12 not working on MacOS Ventura (arm64). ------------------------+-------------------------------------- Reporter: ftroisi | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.8.99 Resolution: duplicate | Keywords: Libgcc12, Ventura, arm64 Port: libgcc12 | ------------------------+-------------------------------------- Changes (by ftroisi): * Attachment "config.log" added. Here I attach the config.log file generate by the failure of the installation of libgcc12 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 13:26:12 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 13:26:12 -0000 Subject: [MacPorts] #66460: Libgcc12 not working on MacOS Ventura (arm64). In-Reply-To: <044.787d544b393140a7a73637907158ddd9@macports.org> References: <044.787d544b393140a7a73637907158ddd9@macports.org> Message-ID: <059.0d71bdb515805ca817b76f1e86e0f594@macports.org> #66460: Libgcc12 not working on MacOS Ventura (arm64). ------------------------+---------------------------- Reporter: ftroisi | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: duplicate | Keywords: ventura, arm64 Port: libgcc12 | ------------------------+---------------------------- Changes (by jmroot): * keywords: Libgcc12, Ventura, arm64 => ventura, arm64 * milestone: MacPorts Future => Old description: > Dear MacPort, I was trying to install the port gcc12 on my MacMini (with > M1 CPU), running Ventura OS. I ran into the following error with the > dependency port Libgcc12: > > ---> Fetching archive for libgcc12 > ---> Attempting to fetch > libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from > https://cph.dk.packages.macports.org/libgcc12 > ---> Attempting to fetch > libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from > https://nue.de.packages.macports.org/libgcc12 > ---> Attempting to fetch > libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from > https://packages.macports.org/libgcc12 > ---> Fetching distfiles for libgcc12 > ---> Attempting to fetch gcc-12.2.0.tar.xz from > ftp://ftp.gwdg.de/pub/linux/gcc/releases/gcc-12.2.0/ > ---> Attempting to fetch gcc-12.2.0.tar.xz from > https://cph.dk.distfiles.macports.org/gcc12 > ---> Verifying checksums for libgcc12 > ---> Extracting libgcc12 > ---> Applying patches to libgcc12 > ---> Configuring libgcc12 > Error: Failed to configure libgcc12: consult > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/work/build/config.log > Error: Failed to configure libgcc12: configure failure: command execution > failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > Error: Processing of port gcc12 failed New description: Dear MacPort, I was trying to install the port gcc12 on my MacMini (with M1 CPU), running Ventura OS. I ran into the following error with the dependency port Libgcc12: {{{ ---> Fetching archive for libgcc12 ---> Attempting to fetch libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from https://cph.dk.packages.macports.org/libgcc12 ---> Attempting to fetch libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from https://nue.de.packages.macports.org/libgcc12 ---> Attempting to fetch libgcc12-12.2.0_2+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc12 ---> Fetching distfiles for libgcc12 ---> Attempting to fetch gcc-12.2.0.tar.xz from ftp://ftp.gwdg.de/pub/linux/gcc/releases/gcc-12.2.0/ ---> Attempting to fetch gcc-12.2.0.tar.xz from https://cph.dk.distfiles.macports.org/gcc12 ---> Verifying checksums for libgcc12 ---> Extracting libgcc12 ---> Applying patches to libgcc12 ---> Configuring libgcc12 Error: Failed to configure libgcc12: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/work/build/config.log Error: Failed to configure libgcc12: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc12/libgcc12/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gcc12 failed }}} -- Comment: {{{ In file included from conftest.c:10: /opt/local/include/mpc.h:287:35: error: unknown type name 'FILE' }}} So yes, it's a duplicate. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 13:51:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 13:51:43 -0000 Subject: [MacPorts] #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file In-Reply-To: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> References: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> Message-ID: <061.6ed516a478767a827eb77b5e9932af4c@macports.org> #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: git | ------------------------+------------------------- Comment (by herbygillot): The patch file has been updated. Can you do another `port selfupdate` and try again? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 13:57:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 13:57:15 -0000 Subject: [MacPorts] #66463: Failed to configure openvdb: boost176 must be installed with +python39. Message-ID: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> #66463: Failed to configure openvdb: boost176 must be installed with +python39. ----------------------------------------+-------------------- Reporter: Davidpmorrow | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: openvdb boost176 +python39 | Port: ----------------------------------------+-------------------- This is occurring while installing openvdb on a 2017 iMac running macOS Monterey 12.6.1. Ive tried multiple times with rev-upgrade. Ive also tried to install boost separately. Any suggestions as to why I can't upgrade to boost176? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 15:51:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 15:51:15 -0000 Subject: [MacPorts] #66463: Failed to configure openvdb: boost176 must be installed with +python39. In-Reply-To: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> References: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> Message-ID: <064.6cc4004f87cc59ab410af530d6e1df90@macports.org> #66463: Failed to configure openvdb: boost176 must be installed with +python39. ---------------------------+--------------------------------- Reporter: Davidpmorrow | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: openvdb | ---------------------------+--------------------------------- Changes (by jmroot): * cc: jasonliu-- (added) * keywords: openvdb boost176 +python39 => * status: new => assigned * port: => openvdb * owner: (none) => MarcusCalhoun-Lopez -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 15:51:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 15:51:49 -0000 Subject: [MacPorts] #66463: Failed to configure openvdb: boost176 must be installed with +python39. In-Reply-To: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> References: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> Message-ID: <064.65dfe16aebb41fc4e38c30da8462c6e8@macports.org> #66463: Failed to configure openvdb: boost176 must be installed with +python39. ---------------------------+--------------------------------- Reporter: Davidpmorrow | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: openvdb | ---------------------------+--------------------------------- Comment (by kencu): the default python variant has not been updated in openvdb to match the default python variant in boost. It should be. For now, until it is updated, you can install openvdb with the python variant that matches boost's default (3.10) like this: {{{ sudo port clean openvdb sudo port uninstall openvdb sudo port -v install openvdb +python310 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 16:18:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 16:18:09 -0000 Subject: [MacPorts] #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options In-Reply-To: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> References: <047.b4866e38bc637e0ec29dae7f11ab17a9@macports.org> Message-ID: <062.420b82c8d85d266a145dd01f9b26f351@macports.org> #66455: Update x265 port file to add (HDR10+): ENABLE_HDR10_PLUS=ON to the configuration options --------------------------+------------------------ Reporter: janngobble | Owner: janngobble Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: x265 | --------------------------+------------------------ Changes (by janngobble): * status: new => closed * owner: (none) => janngobble * resolution: => fixed Comment: In [changeset:"248df78fa70d79978f5f7cafe62f8ed2ff272d50/macports-ports" 248df78fa70d79978f5f7cafe62f8ed2ff272d50/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="248df78fa70d79978f5f7cafe62f8ed2ff272d50" x265: enable HDR10+ parsing (#16961) closes: https://trac.macports.org/ticket/66455 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 16:30:21 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 16:30:21 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.4ff3ba1d79d1c0bc02ee09e2d004e77f@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Comment (by kencu): Leopard builds through and seems fine -- it has {{{/usr/include/expat.h}}} and the library. Only Tiger doesn't have it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:04:58 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 17:04:58 -0000 Subject: [MacPorts] #66464: ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software Message-ID: <046.df111525b4170d7d0f210c858917b3db@macports.org> #66464: ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software -------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: ImageMagick -------------------------+------------------------- There are two `configure options` that do not seem to fit into the Mac world: `--with-dps` and not `--without-raqm`. Display PostScript was developed on NeXT, but never used in Mac OS X or macOS, its successor(s). So its activation makes no sense. Similarly Raqm, which seems to be a product for MS Windows. Besides both softwares are not (yet) supported by MacPorts. It would accelerate building ImageMagick when it would be `configure`d `--without-dps --without-raqm`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 17:12:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 17:12:55 -0000 Subject: [MacPorts] #66464: ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software In-Reply-To: <046.df111525b4170d7d0f210c858917b3db@macports.org> References: <046.df111525b4170d7d0f210c858917b3db@macports.org> Message-ID: <061.fb24a57c81e00952bf8183d84a11344d@macports.org> #66464: ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software --------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: ImageMagick | --------------------------+------------------------- Comment (by ballapete): Similarly `FLIF, the Free Lossless Image Format`, can be sorted out by using `--without-flif`. It's also not supported by MacPorts. And if installed by other means, would `port` be able to find it? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 18:31:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 18:31:15 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.5e0502b54645075356660d09929f31ee@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by kencu): Replying to [comment:10 cjones051073]: > Ken, any thoughts here ? Do you know if Iain is aware of this or not ? I don't see anything yet on his pages, no. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 18:52:26 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 18:52:26 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.dd73d5dd6cce21efe6d6ae45c57218ed@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by cjones051073): Thanks. I am more inclined to consider this an issue with libmpc than gcc, as its header directly refers to FILE but does not explicitly include the header that declaresnit, which breaks the ?include what you use? principle. Yes it appears some recent Xcode change appears to have exposed this, but i think the core issue is there. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:05:04 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 19:05:04 -0000 Subject: [MacPorts] #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory In-Reply-To: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> References: <046.9c2bc65a43b60f62a32d230f599c484a@macports.org> Message-ID: <061.7546ddd1d4b665fad939a5e8ef835dd9@macports.org> #66415: cmake @3.24.3 - patch does not work - attempts to patch an empty directory ------------------------+---------------------- Reporter: snowflake | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: cmake | ------------------------+---------------------- Comment (by michaelld): Interesting & good point! Well, Kitware has their own gitlab instance running at `https://gitlab.kitware.com/` ... that's what those Portfiles are using. Looking at the downloads, I see that they go direct to Github ... I'll look into changing them over to that download method instead. good catch! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 19:56:32 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 19:56:32 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.9bcfaca67d370c146e6dfdbde92b427f@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Comment (by ctreleaven): There are only 2 reported users of OpenShot according to our user statistics...and I'm one! I won't be putting a lot of effort into supporting old OSX versions. Especially when a dmg can be downloaded from upstream. Sorry. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 20:01:10 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 20:01:10 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.f6f518281bb25987bb684f22fc94a0ef@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Comment (by ctreleaven): I have attempted to update OpenShot to version 3.0.0 but it fails to launch. I've reported upstream: https://github.com/OpenShot/openshot-qt/issues/5039 I've spent several hours trying to track down the problem but my almost complete lack of experience with Python is a handicap. Hopefully upstream won't ignore me like they did last year. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 20:17:20 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 20:17:20 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.41bcd0cc8a7a4fcd6744133fc45ba4af@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by Gcenx): This wasn?t an Xcode related change as this also affected one of my users on macOS Mojave. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 20:46:50 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 20:46:50 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.83166bc3384c49cce38ae3da46f25f19@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by cjones051073): Interesting....\ I can only then presume maybe it was an issue introduced with the update from 121.to 1.3.0 that happened a few days back.. https://github.com/macports/macports- ports/commit/af6232833ada36aafff504cd4e181fca5cc759a7 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 20:57:07 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 20:57:07 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.d823c873269d7bb52e08729ac2386bc7@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by Gcenx): Replying to [comment:18 cjones051073]: > Interesting.... > > I can only then presume maybe it was an issue introduced with the update from 1.2.1 to 1.3.0 that happened a few days back.. > > > https://github.com/macports/macports- ports/commit/af6232833ada36aafff504cd4e181fca5cc759a7 I?d think that?s correct as I?d built mingw-w64 on macOS Ventura before this without issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:14:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 21:14:09 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.ca23014472d3ff197184f226cbc12e8a@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by rieder): same issue here -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:45:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 21:45:43 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 In-Reply-To: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> References: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> Message-ID: <061.a82b83eab00183288593b5443a151019@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -----------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz-devel | -----------------------------+------------------------- Comment (by ballapete): I encountered a similar inability to follow my orders when invoked `port` to `install gttk2 gtk3` before going to sleep. Before I had both packages uninstalled. At daylight I fouund out that `gtk2` had been installed with a `requested_variants` flag that I want to get rid of: {{{ pete 194 /\ port -v installed gtk2 The following ports are currently installed: gtk2 @2.24.33_3+x11 (active) requested_variants='+x11' platform='darwin 9' archs='ppc' date='2022-12-13T04:18:55+0100' }}} I'll attach the compile command used in GNU Emacs as a screenshot. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 21:47:56 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 21:47:56 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 In-Reply-To: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> References: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> Message-ID: <061.7de1a4d414dcc153554800e78515b3b7@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -----------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz-devel | -----------------------------+------------------------- Changes (by ballapete): * Attachment "install gtk2 gtk3.png" added. Screenshot of the compile command used in GNU Emacs -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:52:25 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 22:52:25 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade Message-ID: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade --------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: ffmpeg --------------------+-------------------- {{{ :info:configure ERROR: x265 not found using pkg-config }}} please see attached main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:53:17 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 22:53:17 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.86afd0c80edcb71b92965a50c8ac62e7@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade ---------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg | ---------------------+-------------------- Changes (by tehcog): * Attachment "ffmpeg_main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 22:53:52 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 22:53:52 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.0dcc469862b6c033c3f25f99db5ebd93@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade ---------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg | ---------------------+-------------------- Comment (by tehcog): Thanks for your help. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:07:54 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 23:07:54 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.125ea48aab77184e8022fe633ce67a86@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Comment (by Rezzy-dev): Thanks for the effort, Craig, I really appreciate it. And I understand why this is frustrating. I think Catalina may be too old for the 3.0.0 release of Openshot. I would try an earlier release for Catalina: a version after 2.3.3. That error seems like it's not finding the Python libraries -- which could be due to a Python version mismatch. As for the user statistic on this site, I don't believe they are an accurate representation about the number of active users. For one, that second person is not me: so there's already 3 of us! Not all users bother to sign up to the bug report system or even know how to, and so many users opt out of monitoring these days (because online companies/corporations have been abusing their surveillance and data-hoarding powers/abilities). So I am certain that there are way more than 3 active users of Openshot on MacPorts. And there would be even more if the port worked reliably (which is tricky, because Openshot itself doesn't work reliably across OS X versions -- each version of Openshot is specifically tied to a Mac OS version, it seems, without that being clearly documented anywhere). I am curious, though, as to why MacPorts doesn't offer the native Mac app bundle/download for a package if it is officially available (such as in the case of Openshot here). It should at least notify the user that a native Mac version/alternative of the app is available. It would be a nice feature to have. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:23:07 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 23:23:07 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.b5aeafb59209bc729a50f01db7814bc5@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Changes (by cjones051073): * status: new => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:27:34 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 23:27:34 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.3ef3766b3fc2349880df8c6326a49e59@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bogofilter | -------------------------+-------------------- Comment (by Rezzy-dev): So my first statement/assessment was correct, then. Those 3 broken links are to the source package -- I've just checked the contents of the tarball, and it's source, not binary. The port is broken because the source tarball is missing from the MacPorts mirrors for bogofilter. And I believe the mirror that served the HTML page as a download is: ?http://packages.macports.org/ If you check the contents (code) of the page, you'll see all it is serving is a non-standard (non-Apache) HTML file with the numbers 404 in it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:51:11 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 23:51:11 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 In-Reply-To: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> References: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> Message-ID: <061.d3e0532965538c5520121cb9a8efb1b3@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -----------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz-devel | -----------------------------+------------------------- Comment (by ryandesign): The first issue (installing graphviz-devel installs graphviz) is #55393. If you want the +rsvg variant, install graphviz-devel without the +rsvg variant first. The second issue (gtk2 installed with the +x11 variant marked requested) should only happen if you requested the +x11 variant. You showed in the image that you did not request it on the command line. Did you perhaps request it in variants.conf? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 13 23:58:14 2022 From: noreply at macports.org (MacPorts) Date: Tue, 13 Dec 2022 23:58:14 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 In-Reply-To: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> References: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> Message-ID: <061.623403223d497ff2ea7a010664928deb@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -----------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz-devel | -----------------------------+------------------------- Comment (by ballapete): No. These are the files on Leoprad: {{{ -r--r--r-- 1 root admin 461 1. Sep 2014 /opt/local/etc/macports/variants.conf -rw-r--r-- 1 root admin 461 26. Feb 2015 /opt/mports/trunk/base/doc/variants.conf }}} All the examples are left as comments: {{{ # $Id: variants.conf 106817 2013-06-08 20:54:25Z larryv at macports.org $ # MacPorts system-wide global variants configuration file. # Any variants listed here are applied to all port builds. As on the # command line, variants may be either enabled (+) or disabled (-), and # unsupported variants are simply ignored. # # Each line must be a space- or tab-delimited list of zero or more # variants. # # Example: # -x11 +no_x11 +quartz # +gcc48 # +universal # $Id: variants.conf 106817 2013-06-08 20:54:25Z larryv at macports.org $ # MacPorts system-wide global variants configuration file. # Any variants listed here are applied to all port builds. As on the # command line, variants may be either enabled (+) or disabled (-), and # unsupported variants are simply ignored. # # Each line must be a space- or tab-delimited list of zero or more # variants. # # Example: # -x11 +no_x11 +quartz # +gcc48 # +universal }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 01:07:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 01:07:41 -0000 Subject: [MacPorts] #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" In-Reply-To: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> References: <046.87a054c112949c4fd964f841a3d3ca21@macports.org> Message-ID: <061.e537c532b98b8685ba1786bc5d9c3469@macports.org> #66442: libopenshot-audio @0.2.1 fails to build on <= 10.10: "The 10.11 SDK (Xcode 7.3.1+) is required to build JUCE apps" --------------------------------+------------------------ Reporter: Rezzy-dev | Owner: ctreleaven Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libopenshot-audio | --------------------------------+------------------------ Comment (by ctreleaven): I haven't tested, but I think the problem with the upstream packaged application may be due to the Qt version. Each Qt version is only (officially) supported on a couple of macOS releases. So the bundled version of Qt may be the limiting factor. An advantage of MacPorts is that our Qt portgroup goes through some gymnastics to match the Qt version to the macOS version. That _should_ help us to support the app on older OS releases for longer. Nonetheless, one of the Openshot libraries relies on features that were introduced in OSX 10.9 so that's the earliest that can possibly run it. I do understand that our opt-in statistics are incomplete. Still not a big user base. Re distributing upstream dmg's via MacPorts, I can't speak for the project as a whole. However, my view is that we're not adding much value by doing so. Packaging OpenShot, for instance, the way we do means that the application can benefit from updates to any of the components earlier rather than waiting for upstream to issue a new release. That has the downside that sometimes dependency updates cause things to break. In general, however, I think the benefits outweigh the potential risk. Homebrew has many more packages that just deliver the upstream dmg. OTOH, they really only support current OS releases. Different philosophies, neither one is "right". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 02:49:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 02:49:49 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.6758ffd439ccb994c98c9078f1549368@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade ---------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg | ---------------------+-------------------- Comment (by RobK88): The x265 upgrade also breaks `ffmpeg @4.4.2_3+gpl2+libdc1394+nonfree+x11` on Lion. It also looks like the x265 upgrade breaks `libheif` too. See below. {{{ ---> Scanning binaries for linking errors ---> Found 12 broken files, matching files to ports ---> Found 2 broken ports, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: libheif @1.13.0 ffmpeg @4.4.2+gpl2+libdc1394+nonfree+x11 Continue? [Y/n]: Y ---> Computing dependencies for libheif ---> Cleaning libheif ---> Computing dependencies for ffmpeg ---> Cleaning ffmpeg ---> Scanning binaries for linking errors ---> Found 12 broken files, matching files to ports ---> Found 2 broken ports, determining rebuild order ---> Rebuilding in order libheif @1.13.0_0 ffmpeg @4.4.2_3+gpl2+libdc1394+nonfree+x11 ---> Computing dependencies for libheif ---> Fetching distfiles for libheif ---> Verifying checksums for libheif ---> Extracting libheif ---> Configuring libheif ---> Building libheif ---> Staging libheif into destroot ---> Unable to uninstall libheif @1.13.0_0, the following ports depend on it: ---> gd2 @2.3.3_1+x11 ---> ImageMagick @6.9.11-60_3+x11 Warning: Uninstall forced. Proceeding despite dependencies. ---> Deactivating libheif @1.13.0_0 ---> Cleaning libheif ---> Uninstalling libheif @1.13.0_0 ---> Cleaning libheif ---> Computing dependencies for libheif ---> Installing libheif @1.13.0_0 ---> Activating libheif @1.13.0_0 ---> Cleaning libheif ---> Computing dependencies for ffmpeg ---> Fetching distfiles for ffmpeg ---> Verifying checksums for ffmpeg ---> Extracting ffmpeg ---> Applying patches to ffmpeg ---> Configuring ffmpeg Error: Failed to configure ffmpeg: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log for details. Error: rev-upgrade failed: Error rebuilding ffmpeg Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. bash-3.2$ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 03:03:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 03:03:48 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.d1deaa9334765c58e749272c1594e8f0@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+--------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: CSXCAD | -----------------------+--------------------- Comment (by esteimle): Thank you for the fix. How do I test it? I tried to install it again and also to clear with sudo port -f clean --all all. But it still fails -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 03:44:27 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 03:44:27 -0000 Subject: [MacPorts] #66466: libiodbc: Build errors, mostly from drvconn.c Message-ID: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> #66466: libiodbc: Build errors, mostly from drvconn.c ---------------------+---------------------- Reporter: gregyao | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: libiodbc ---------------------+---------------------- sudo port install libiodbc fails at Build. The make errors identified in main.log are beyond my skillset, and I would appreciate your help in installing the port. (libiodbc is being installed as a dependency for port kde4-kile.) Thanks in advance. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 03:45:29 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 03:45:29 -0000 Subject: [MacPorts] #66466: libiodbc: Build errors, mostly from drvconn.c In-Reply-To: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> References: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> Message-ID: <059.ac3d0f11db6db83d5636dbcbce43d028@macports.org> #66466: libiodbc: Build errors, mostly from drvconn.c -----------------------+-------------------- Reporter: gregyao | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libiodbc | -----------------------+-------------------- Changes (by gregyao): * Attachment "221214.libiodbc.install.fail.main.log" added. main.log in response to sudo port install libiodbc -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 03:54:59 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 03:54:59 -0000 Subject: [MacPorts] #66466: libiodbc @3.52.15_2+libodbc+x11: Build errors, mostly from drvconn.c (was: libiodbc: Build errors, mostly from drvconn.c) In-Reply-To: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> References: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> Message-ID: <059.f7aa6964b2d7617a92cd00b363846f2b@macports.org> #66466: libiodbc @3.52.15_2+libodbc+x11: Build errors, mostly from drvconn.c -----------------------+-------------------- Reporter: gregyao | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libiodbc | -----------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 04:55:46 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 04:55:46 -0000 Subject: [MacPorts] #66467: Unable to install gdb on OSX 13.0.1 (ARM) +universal Message-ID: <051.e7e7d9fff1e7c407b6b181a4a29e894c@macports.org> #66467: Unable to install gdb on OSX 13.0.1 (ARM) +universal ----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gdb ----------------------------+-------------------- Getting the following error Error: Failed to destroot gdb: no files matched glob pattern "g*" main.log is attached -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 04:56:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 04:56:54 -0000 Subject: [MacPorts] #66467: Unable to install gdb on OSX 13.0.1 (ARM) +universal In-Reply-To: <051.e7e7d9fff1e7c407b6b181a4a29e894c@macports.org> References: <051.e7e7d9fff1e7c407b6b181a4a29e894c@macports.org> Message-ID: <066.5f3f4b8e815d2941d9ced79b10a8dafc@macports.org> #66467: Unable to install gdb on OSX 13.0.1 (ARM) +universal -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gdb | -----------------------------+-------------------- Changes (by sudheerhebbale): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 05:00:24 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 05:00:24 -0000 Subject: [MacPorts] #66468: installation if xalanc fails on mac os 13.0.1 (ARM) Message-ID: <051.2839a4b592f739696ad218f43103f9ed@macports.org> #66468: installation if xalanc fails on mac os 13.0.1 (ARM) ----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: xalanc ----------------------------+-------------------- The following error gets generated Error: Failed to build xalanc: command execution failed main.log is attached -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 05:00:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 05:00:41 -0000 Subject: [MacPorts] #66468: installation if xalanc fails on mac os 13.0.1 (ARM) In-Reply-To: <051.2839a4b592f739696ad218f43103f9ed@macports.org> References: <051.2839a4b592f739696ad218f43103f9ed@macports.org> Message-ID: <066.ec0f500fbb2b23eaba17d0a571881328@macports.org> #66468: installation if xalanc fails on mac os 13.0.1 (ARM) -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xalanc | -----------------------------+-------------------- Changes (by sudheerhebbale): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 06:35:53 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 06:35:53 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.0ddc1a37b7446491894726992f4578a5@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by chrisd-mso): I'm having the same problem on an ARM64 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 06:53:30 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 06:53:30 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.85f14ce0eb394c18d3b4de96f8a224b2@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+--------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: CSXCAD | -----------------------+--------------------- Comment (by ra1nb0w): you need to update the ports repository with {{{sudo port sync}}} before {{{clean}}} and {{{install}}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:02:27 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:02:27 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.94355f005a4007778174c33b235157e7@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Comment (by aeiouaeiouaeiouaeiouaeiouaeiou): Confirmed on macOS 10.8 as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:22:31 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:22:31 -0000 Subject: [MacPorts] #66469: rev-upgrade failed: Error rebuilding ffmpeg Message-ID: <045.a97eef96e10fcf9148e0280193d59327@macports.org> #66469: rev-upgrade failed: Error rebuilding ffmpeg ----------------------+---------------------------------- Reporter: silvsims | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: ffmpeg @4.4.2_3+gpl2 ----------------------+---------------------------------- The following ports will be rebuilt: ffmpeg @4.4.2+gpl2 ---> Computing dependencies for ffmpeg ---> Fetching distfiles for ffmpeg ---> Verifying checksums for ffmpeg ---> Extracting ffmpeg ---> Applying patches to ffmpeg ---> Configuring ffmpeg Error: Failed to configure ffmpeg: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log for details. Error: rev-upgrade failed: Error rebuilding ffmpeg -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:22:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:22:51 -0000 Subject: [MacPorts] #66469: rev-upgrade failed: Error rebuilding ffmpeg In-Reply-To: <045.a97eef96e10fcf9148e0280193d59327@macports.org> References: <045.a97eef96e10fcf9148e0280193d59327@macports.org> Message-ID: <060.d31baa9993de7bcecdd03efd63b64b1e@macports.org> #66469: rev-upgrade failed: Error rebuilding ffmpeg -----------------------------------+-------------------- Reporter: silvsims | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg @4.4.2_3+gpl2 | -----------------------------------+-------------------- Changes (by silvsims): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:31:25 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:31:25 -0000 Subject: [MacPorts] #66441: Bogofilter missing, broken links, 404 In-Reply-To: <046.f46aa1d2036af425a7853ae711bda689@macports.org> References: <046.f46aa1d2036af425a7853ae711bda689@macports.org> Message-ID: <061.95090f94467a4ad66a10090c8e7e9e55@macports.org> #66441: Bogofilter missing, broken links, 404 -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: Port: bogofilter | -------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => worksforme Comment: No, I stand by everything I said previously in this ticket. The source archive (`bogofilter-1.2.5.tar.xz`) does not come from packages.macports.org and there is no attempt to download it from there. MacPorts first attempts to download the binary archive (`bogofilter-1.2.5_1.darwin_14.x86_64.tbz2`) from packages.macports.org and a couple of its mirrors, and when that fails, it downloads the source instead, from distfiles.macports.org, its mirrors, or one of the many sourceforge mirrors (chosen based on ping time.) This is what that looks like (actual output from running this on my machine): {{{ % sudo port install bogofilter ---> Computing dependencies for bogofilter ---> Fetching archive for bogofilter ---> Attempting to fetch bogofilter-1.2.5_1.darwin_21.x86_64.tbz2 from file:///opt/local/var/macports/packages/bogofilter ---> Attempting to fetch bogofilter-1.2.5_1.darwin_21.x86_64.tbz2 from https://packages.macports.org/bogofilter ---> Attempting to fetch bogofilter-1.2.5_1.darwin_21.x86_64.tbz2 from https://kmq.jp.packages.macports.org/bogofilter ---> Fetching distfiles for bogofilter ---> Attempting to fetch bogofilter-1.2.5.tar.xz from https://distfiles.macports.org/bogofilter ---> Verifying checksums for bogofilter ---> Extracting bogofilter ---> Applying patches to bogofilter ---> Configuring bogofilter ---> Building bogofilter ---> Staging bogofilter into destroot ---> Installing bogofilter @1.2.5_1 ---> Activating bogofilter @1.2.5_1 ---> Cleaning bogofilter }}} If packages.macports.org were serving a 200 response for files it doesn't have, an error would be happening before the distfile is downloaded for every port that lacks binaries, and it is not. We're not going to get any further here unless you can get your problem to happen again and provide the terminal output and log. Feel free to reopen if and when you are able to do so. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:40:31 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:40:31 -0000 Subject: [MacPorts] #66466: libiodbc @3.52.15_2+libodbc+x11: Build errors, mostly from drvconn.c In-Reply-To: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> References: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> Message-ID: <059.bbf5ad73fbee9836da0751282bc3dd05@macports.org> #66466: libiodbc @3.52.15_2+libodbc+x11: Build errors, mostly from drvconn.c -----------------------+---------------------- Reporter: gregyao | Owner: nerdling Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libiodbc | -----------------------+---------------------- Changes (by jmroot): * cc: snc@? (removed) * status: new => assigned * owner: (none) => nerdling -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:41:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:41:49 -0000 Subject: [MacPorts] #66467: Unable to install gdb on OSX 13.0.1 (ARM) +universal In-Reply-To: <051.e7e7d9fff1e7c407b6b181a4a29e894c@macports.org> References: <051.e7e7d9fff1e7c407b6b181a4a29e894c@macports.org> Message-ID: <066.44e53d766b805517dbefb2d5517e1108@macports.org> #66467: Unable to install gdb on OSX 13.0.1 (ARM) +universal -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: gdb | -----------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate Comment: #63761 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 07:44:14 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 07:44:14 -0000 Subject: [MacPorts] #66468: xalanc @1.11_1 configure fails on mac os 13.0.1 (ARM) (was: installation if xalanc fails on mac os 13.0.1 (ARM)) In-Reply-To: <051.2839a4b592f739696ad218f43103f9ed@macports.org> References: <051.2839a4b592f739696ad218f43103f9ed@macports.org> Message-ID: <066.a5d0ab4686deb1e4dbf31b7e1184c7af@macports.org> #66468: xalanc @1.11_1 configure fails on mac os 13.0.1 (ARM) -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: arm64 Port: xalanc | -----------------------------+-------------------- Changes (by jmroot): * keywords: => arm64 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 09:25:59 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 09:25:59 -0000 Subject: [MacPorts] #66468: xalanc @1.11_1 configure fails on mac os 13.0.1 (ARM) In-Reply-To: <051.2839a4b592f739696ad218f43103f9ed@macports.org> References: <051.2839a4b592f739696ad218f43103f9ed@macports.org> Message-ID: <066.e5cedb52eeb855d3b2fcd031d921d8e3@macports.org> #66468: xalanc @1.11_1 configure fails on mac os 13.0.1 (ARM) -----------------------------+-------------------- Reporter: sudheerhebbale | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: arm64 Port: xalanc | -----------------------------+-------------------- Changes (by jmroot): * status: new => closed * owner: (none) => jmroot * resolution: => fixed Comment: In [changeset:"4a9316d56735c0f4c087b3eb830f7b2e207f2dfb/macports-ports" 4a9316d56735c0f4c087b3eb830f7b2e207f2dfb/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4a9316d56735c0f4c087b3eb830f7b2e207f2dfb" xalanc: update to 1.12 Fixes: https://trac.macports.org/ticket/66468 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 09:34:04 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 09:34:04 -0000 Subject: [MacPorts] #66469: ffmpeg @4.4.2_3+gpl2 configure failure (was: rev-upgrade failed: Error rebuilding ffmpeg) In-Reply-To: <045.a97eef96e10fcf9148e0280193d59327@macports.org> References: <045.a97eef96e10fcf9148e0280193d59327@macports.org> Message-ID: <060.55d751819600730531c91805029b7eda@macports.org> #66469: ffmpeg @4.4.2_3+gpl2 configure failure ------------------------+-------------------- Reporter: silvsims | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: ffmpeg | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate * port: ffmpeg @4.4.2_3+gpl2 => ffmpeg Old description: > The following ports will be rebuilt: ffmpeg @4.4.2+gpl2 > ---> Computing dependencies for ffmpeg > ---> Fetching distfiles for ffmpeg > ---> Verifying checksums for ffmpeg > ---> Extracting ffmpeg > ---> Applying patches to ffmpeg > ---> Configuring ffmpeg > Error: Failed to configure ffmpeg: configure failure: command execution > failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log > for details. > Error: rev-upgrade failed: Error rebuilding ffmpeg New description: {{{ The following ports will be rebuilt: ffmpeg @4.4.2+gpl2 ---> Computing dependencies for ffmpeg ---> Fetching distfiles for ffmpeg ---> Verifying checksums for ffmpeg ---> Extracting ffmpeg ---> Applying patches to ffmpeg ---> Configuring ffmpeg Error: Failed to configure ffmpeg: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log for details. Error: rev-upgrade failed: Error rebuilding ffmpeg }}} -- Comment: {{{ x265 not found using pkg-config }}} Dup of #66465. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 09:53:34 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 09:53:34 -0000 Subject: [MacPorts] #55393: graphviz +rsvg depends on graphviz; circular dependency; prevents installation In-Reply-To: <046.6e1663e08968544151fc8b7b432267c7@macports.org> References: <046.6e1663e08968544151fc8b7b432267c7@macports.org> Message-ID: <061.802df927ee6aa511c9d0412611860364@macports.org> #55393: graphviz +rsvg depends on graphviz; circular dependency; prevents installation ------------------------+------------------------ Reporter: rhstanton | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: graphviz | ------------------------+------------------------ Comment (by ballapete): Replying to [comment:6 ryandesign]: > I have absolutely no idea. All I can tell you is that MacPorts behavior is undefined when a circular dependency exists. In my case, #66461, it would work when `port` would understand that `graphviz` and `graphviz-devel` are equivalent and when there is a need to install either this or that, then install what the user wants ? otherwise `port` would not have been invoked and could continue to sleep. If the user does not request a particular (set of) variant(s) install the default one. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 11:16:03 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 11:16:03 -0000 Subject: [MacPorts] #66470: gtk2 @2.24.33_3 has a problem with patched configure script Message-ID: <046.88a0606b3e36d0d1112504496d082718@macports.org> #66470: gtk2 @2.24.33_3 has a problem with patched configure script -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: gtk2 -------------------------+-------------------- {{{ checking for catalogs to be installed... af am ang ar as ast az az_IR be be at latin bg bn bn_IN br bs ca ca at valencia crh cs cy da de dz el en_CA en_GB eo es et eu fa fi fr ga gl gu he hi hr hu hy ia id io is it ja ka kk kn ko ku li lt lv mai mi mk ml mn mr ms my nb nds ne nl nn nso oc or pa pl ps pt pt_BR ro ru rw si sk sl sq sr sr at latin sr at ije sv ta te th tk tr tt ug uk ur uz uz at cyrillic vi wa xh yi zh_CN zh_HK zh_TW checking for extra flags to get ANSI library prototypes... ./configure: line 22096: ac_fn_c_try_run: command not found configure: WARNING: No ANSI prototypes found in library. (-std1 didn't work.) }}} The corresponing heavily patched code is this: {{{ 21982 if test "$gt_cv_have_gettext" = "yes"; then 21983 if test "x$ALL_LINGUAS" = "x"; then 21984 LINGUAS= 21985 else 21986 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for catalogs to be installed" >&5 21987 printf %s "checking for catalogs to be installed... " >&6; } 21988 NEW_LINGUAS= 21989 for presentlang in $ALL_LINGUAS; do 21990 useit=no 21991 if test "%UNSET%" != "${LINGUAS-%UNSET%}"; then 21992 desiredlanguages="$LINGUAS" 21993 else 21994 desiredlanguages="$ALL_LINGUAS" 21995 fi 21996 for desiredlang in $desiredlanguages; do 21997 # Use the presentlang catalog if desiredlang is 21998 # a. equal to presentlang, or 21999 # b. a variant of presentlang (because in this case, 22000 # presentlang can be used as a fallback for messages 22001 # which are not translated in the desiredlang catalog). 22002 case "$desiredlang" in 22003 "$presentlang"*) useit=yes;; 22004 esac 22005 done 22006 if test $useit = yes; then 22007 NEW_LINGUAS="$NEW_LINGUAS $presentlang" 22008 fi 22009 done 22010 LINGUAS=$NEW_LINGUAS 22011 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $LINGUAS" >&5 22012 printf "%s\n" "$LINGUAS" >&6; } 22013 fi 22014 22015 if test -n "$LINGUAS"; then 22016 for lang in $LINGUAS; do CATALOGS="$CATALOGS $lang$CATOBJEXT"; done 22017 fi 22018 fi 22019 22020 MKINSTALLDIRS= 22021 if test -n "$ac_aux_dir"; then 22022 MKINSTALLDIRS="$ac_aux_dir/mkinstalldirs" 22023 fi 22024 if test -z "$MKINSTALLDIRS"; then 22025 MKINSTALLDIRS="\$(top_srcdir)/mkinstalldirs" 22026 fi 22027 22028 22029 test -d po || mkdir po 22030 if test "x$srcdir" != "x."; then 22031 if test "x`echo $srcdir | sed 's@/.*@@'`" = "x"; then 22032 posrcprefix="$srcdir/" 22033 else 22034 posrcprefix="../$srcdir/" 22035 fi 22036 else 22037 posrcprefix="../" 22038 fi 22039 rm -f po/POTFILES 22040 sed -e "/^#/d" -e "/^\$/d" -e "s,.*, $posrcprefix& \\\\," -e "\$s/\(.*\) \\\\/\1/" \ 22041 < $srcdir/po/POTFILES.in > po/POTFILES 22042 22043 LIBS="$LIBS $INTLLIBS" 22044 ac_config_commands="$ac_config_commands default-2" 22045 22046 22047 test -d po-properties || mkdir po-properties 22048 if test "x$srcdir" != "x."; then 22049 if test "x`echo $srcdir | sed 's@/.*@@'`" = "x"; then 22050 popropsrcprefix="$srcdir/" 22051 else 22052 popropsrcprefix="../$srcdir/" 22053 fi 22054 else 22055 popropsrcprefix="../" 22056 fi 22057 rm -f po-properties/POTFILES 22058 sed -e "/^#/d" -e "/^\$/d" -e "s,.*, $popropsrcprefix& \\\\," -e "\$s/\(.*\) \\\\/\1/" \ 22059 < $srcdir/po-properties/POTFILES.in > po-properties/POTFILES 22060 22061 glib_save_prefix="$prefix" 22062 glib_save_exec_prefix="$exec_prefix" 22063 glib_save_datarootdir="$datarootdir" 22064 test "x$prefix" = xNONE && prefix=$ac_default_prefix 22065 test "x$exec_prefix" = xNONE && exec_prefix=$prefix 22066 datarootdir=`eval echo "${datarootdir}"` 22067 if test "x$CATOBJEXT" = "x.mo" ; then 22068 localedir=`eval echo "${libdir}/locale"` 22069 else 22070 localedir=`eval echo "${datadir}/locale"` 22071 fi 22072 prefix="$glib_save_prefix" 22073 exec_prefix="$glib_save_exec_prefix" 22074 datarootdir="$glib_save_datarootdir" 22075 22076 printf "%s\n" "#define GTK_LOCALEDIR \"$localedir\"" >>confdefs.h 22077 22078 22079 22080 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for extra flags to get ANSI library prototypes" >&5 22081 printf %s "checking for extra flags to get ANSI library prototypes... " >&6; } 22082 22083 gtk_save_LIBS=$LIBS 22084 LIBS="$LIBS -lm" 22085 if test "$cross_compiling" = yes 22086 then : 22087 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5 22088 printf "%s\n" "none needed" >&6; } 22089 22090 else $as_nop 22091 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 22092 /* end confdefs.h. */ 22093 #include 22094 int main (void) { return (log(1) != log(1.)); } 22095 _ACEOF 22096 if ac_fn_c_try_run "$LINENO" 22097 then : 22098 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: none needed" >&5 22099 printf "%s\n" "none needed" >&6; } 22100 else $as_nop 22101 gtk_save_CFLAGS="$CFLAGS" 22102 CFLAGS="$CFLAGS -std1" 22103 if test "$cross_compiling" = yes 22104 then : 22105 true 22106 22107 else $as_nop 22108 22109 # ac_fn_c_try_run LINENO 22110 # ---------------------- 22111 # Try to run conftest.$ac_ext, and return whether this succeeded. Assumes that 22112 # executables *can* be run. 22113 ac_fn_c_try_run () 22114 { 22115 as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack 22116 if { { ac_try="$ac_link" 22117 case "(($ac_try" in 22118 *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; 22119 *) ac_try_echo=$ac_try;; 22120 esac 22121 eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" 22122 printf "%s\n" "$ac_try_echo"; } >&5 22123 (eval "$ac_link") 2>&5 22124 ac_status=$? 22125 printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 22126 test $ac_status = 0; } && { ac_try='./conftest$ac_exeext' 22127 { { case "(($ac_try" in 22128 *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;; 22129 *) ac_try_echo=$ac_try;; 22130 esac 22131 eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\"" 22132 printf "%s\n" "$ac_try_echo"; } >&5 22133 (eval "$ac_try") 2>&5 22134 ac_status=$? 22135 printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5 22136 test $ac_status = 0; }; } 22137 then : 22138 ac_retval=0 22139 else $as_nop 22140 printf "%s\n" "$as_me: program exited with status $ac_status" >&5 22141 printf "%s\n" "$as_me: failed program was:" >&5 22142 sed 's/^/| /' conftest.$ac_ext >&5 22143 22144 ac_retval=$ac_status 22145 fi 22146 rm -rf conftest.dSYM conftest_ipa8_conftest.oo 22147 eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno 22148 as_fn_set_status $ac_retval 22149 22150 } # ac_fn_c_try_run 22151 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 22152 /* end confdefs.h. */ 22153 #include 22154 int main (void) { return (log(1) != log(1.)); } 22155 _ACEOF 22156 if ac_fn_c_try_run "$LINENO" 22157 then : 22158 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: -std1" >&5 22159 printf "%s\n" "-std1" >&6; } 22160 else $as_nop 22161 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: " >&5 22162 printf "%s\n" "" >&6; } 22163 CFLAGS="$gtk_save_CFLAGS" 22164 { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: No ANSI prototypes found in library. (-std1 didn't work.)" >&5 22165 printf "%s\n" "$as_me: WARNING: No ANSI prototypes found in library. (-std1 didn't work.)" >&2;} 22166 fi 22167 rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ 22168 conftest.$ac_objext conftest.beam conftest.$ac_ext 22169 fi 22170 22171 fi 22172 rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ 22173 conftest.$ac_objext conftest.beam conftest.$ac_ext 22174 fi }}} Originally it was these 48 lines: {{{ 20944 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for extra flags to get ANSI library prototypes" >&5 20945 $as_echo_n "checking for extra flags to get ANSI library prototypes... " >&6; } 20946 20947 gtk_save_LIBS=$LIBS 20948 LIBS="$LIBS -lm" 20949 if test "$cross_compiling" = yes; then : 20950 { $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5 20951 $as_echo "none needed" >&6; } 20952 20953 else 20954 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 20955 /* end confdefs.h. */ 20956 #include 20957 int main (void) { return (log(1) != log(1.)); } 20958 _ACEOF 20959 if ac_fn_c_try_run "$LINENO"; then : 20960 { $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5 20961 $as_echo "none needed" >&6; } 20962 else 20963 gtk_save_CFLAGS="$CFLAGS" 20964 CFLAGS="$CFLAGS -std1" 20965 if test "$cross_compiling" = yes; then : 20966 true 20967 20968 else 20969 cat confdefs.h - <<_ACEOF >conftest.$ac_ext 20970 /* end confdefs.h. */ 20971 #include 20972 int main (void) { return (log(1) != log(1.)); } 20973 _ACEOF 20974 if ac_fn_c_try_run "$LINENO"; then : 20975 { $as_echo "$as_me:${as_lineno-$LINENO}: result: -std1" >&5 20976 $as_echo "-std1" >&6; } 20977 else 20978 { $as_echo "$as_me:${as_lineno-$LINENO}: result: " >&5 20979 $as_echo "" >&6; } 20980 CFLAGS="$gtk_save_CFLAGS" 20981 { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: No ANSI prototypes found in library. (-std1 didn't work.)" >&5 20982 $as_echo "$as_me: WARNING: No ANSI prototypes found in library. (-std1 didn't work.)" >&2;} 20983 fi 20984 rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ 20985 conftest.$ac_objext conftest.beam conftest.$ac_ext 20986 fi 20987 20988 fi 20989 rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \ 20990 conftest.$ac_objext conftest.beam conftest.$ac_ext 20991 fi }}} `gtk2` is still in the process of building? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 11:17:45 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 11:17:45 -0000 Subject: [MacPorts] #66470: gtk2 @2.24.33_3 has a problem with patched configure script In-Reply-To: <046.88a0606b3e36d0d1112504496d082718@macports.org> References: <046.88a0606b3e36d0d1112504496d082718@macports.org> Message-ID: <061.2dffdc0cd622f491ca553c839c146553@macports.org> #66470: gtk2 @2.24.33_3 has a problem with patched configure script ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: gtk2 | ------------------------+------------------------- Changes (by ballapete): * Attachment "config.log" added. config.log from configure run on PPC Leopard, Mac OS X 10.5.8 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 11:50:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 11:50:47 -0000 Subject: [MacPorts] #66471: x265 or ffmpeg problem Message-ID: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> #66471: x265 or ffmpeg problem --------------------+------------------------------ Reporter: rufty | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: x265 (or ffmpeg) --------------------+------------------------------ I've just upgraded x265 and this triggered ffmpeg to rebuild, but the configure step fails with: ":info:configure ERROR: x265 not found using pkg-config" So I think this is x265 not ffmpeg. OSX 10.13.6 + macports 2.8.0 $ port installed | grep x265 x265 @3.4_0+highdepth x265 @3.4_1+highdepth (active) $ port installed | grep ffmpeg ffmpeg @4.4.2_3+gpl2 (active) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:04:01 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 12:04:01 -0000 Subject: [MacPorts] #66472: texlive-bin @2022.62882_2 produces an ld warning while building HINT/hitex Message-ID: <046.b01934e6f17c42c60339dc7bed88a024@macports.org> #66472: texlive-bin @2022.62882_2 produces an ld warning while building HINT/hitex -------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: texlive-bin -------------------------+------------------------- {{{ CWEBINPUTS=/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/hitexdir AM_V_P=: /bin/sh ./tangle-sh hitex-tangle ./ctangle hitex tangle-sh: CWEBINPUTS=/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/hitexdir TEXMFCNF=/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/../kpathsea ./ctangle hitex warning: kpathsea: configuration file texmf.cnf not found in these directories: /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/../kpathsea. /opt/local/bin/gcc-mp-7 -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c -I./w2c -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive- bin/work/build/texk -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/libmd5 -DINIT -DSTAT -isystem/opt/local/include -Wimplicit -Wreturn-type -pipe -Os -arch ppc -MT hitex-hitex.o -MD -MP -MF .deps/hitex-hitex.Tpo -c -o hitex-hitex.o `test -f 'hitex.c' || echo '/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/'`hitex.c mv -f .deps/hitex-hitex.Tpo .deps/hitex-hitex.Po /bin/sh ./libtool --tag=CC --mode=link /opt/local/bin/gcc-mp-7 -Wimplicit -Wreturn-type -pipe -Os -arch ppc -Wl,-headerpad_max_install_names -arch ppc -o hitex hitex-hitables.o hitex-hiput.o hitex-hitex.o /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive- bin/work/build/texk/kpathsea/libkpathsea.la -lz libmd5.a libmd5.a libtool: link: /opt/local/bin/gcc-mp-7 -Wimplicit -Wreturn-type -pipe -Os -arch ppc -Wl,-headerpad_max_install_names -arch ppc -o .libs/hitex hitex- hitables.o hitex-hiput.o hitex-hitex.o /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive- bin/work/build/texk/kpathsea/.libs/libkpathsea.dylib -lz libmd5.a ld: warning: 32-bit absolute address out of range (0x10004F908 max is 4GB): from _source_filename_stack + 0x00000000 (0x0004DA94) to 0x10004F908 /opt/local/bin/gcc-mp-7 -DHAVE_CONFIG_H -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c -I./w2c -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive- bin/work/build/texk -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk -I/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/hitexdir -isystem/opt/local/include -Wimplicit -Wreturn-type -pipe -Os -arch ppc -MT hishrink-hitables.o -MD -MP -MF .deps/hishrink-hitables.Tpo -c -o hishrink-hitables.o `test -f 'hitables.c' || echo '/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work /texlive-source-2022.62882-stripped/texk/web2c/'`hitables.c }}} The `kpathsea: configuration file texmf.cnf not found` come quite often and can surely be neglected, but the `ld: warning` seems to be serious? (In the end the port built and was installed. Running `/opt/local/libexec/texlive/binaries/hitex --help` seems to work ? no knowledge of HINT!) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 12:16:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 12:16:50 -0000 Subject: [MacPorts] #65573: libgcc12: build fails for macOS 12.6 and 13 Beta In-Reply-To: <048.d6318c8ed0d17c20d18a89f82ab5240a@macports.org> References: <048.d6318c8ed0d17c20d18a89f82ab5240a@macports.org> Message-ID: <063.a9b95e54bc307954cc7944c7d1e569fc@macports.org> #65573: libgcc12: build fails for macOS 12.6 and 13 Beta --------------------------+---------------------- Reporter: adamgao1996 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: monterey Port: libgcc12 | --------------------------+---------------------- Changes (by cjones051073): * status: new => closed * resolution: => fixed Comment: This issue now appears resolved, as gcc12 builds fine using the latest Xcodes on macos 12 and 13 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 13:34:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 13:34:54 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366286=3A_gettext-tools-libs=3A?= =?utf-8?q?_builld_failure_=E2=80=9CSource_option_6_is_no_longer_?= =?utf-8?q?supported=2E_Use_7_or_later=2E=E2=80=9D?= In-Reply-To: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> References: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> Message-ID: <062.f227666e5f655cdf4cec65b0fd91c04d@macports.org> #66286: gettext-tools-libs: builld failure ?Source option 6 is no longer supported. Use 7 or later.? -------------------------+------------------------ Reporter: vrepetenko | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: gettext | -------------------------+------------------------ Comment (by vrepetenko): the problem is fixed by last macOS/Xcode command line update. ticket can be closed. thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:15:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 15:15:58 -0000 Subject: [MacPorts] #66017: Upgrade py310-numba from 0.55.2_0 to 0.56.3 In-Reply-To: <046.38b91ec087d51d8670669829ab495b87@macports.org> References: <046.38b91ec087d51d8670669829ab495b87@macports.org> Message-ID: <061.2d105f72d6573483ac96d0f59632e803@macports.org> #66017: Upgrade py310-numba from 0.55.2_0 to 0.56.3 --------------------------+---------------------- Reporter: NickFabry | Owner: stromnov Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: py310-numba | --------------------------+---------------------- Changes (by NickFabry): * owner: (none) => stromnov * status: new => assigned Comment: Looks like py310-numba was upgraded to 0.56.4, so this ticket is no longer necessary... but I don't know how to close it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:21:16 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 15:21:16 -0000 Subject: [MacPorts] #66361: ps2eps: Building Fails For Darwin 22 In-Reply-To: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> References: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> Message-ID: <059.a9c232b901b118df2c0a546ecb092ae0@macports.org> #66361: ps2eps: Building Fails For Darwin 22 ----------------------+-------------------- Reporter: maierh7 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ps2eps | ----------------------+-------------------- Comment (by rieder): I also noticed this -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:23:36 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 15:23:36 -0000 Subject: [MacPorts] #66361: ps2eps: Building Fails For Darwin 22 In-Reply-To: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> References: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> Message-ID: <059.9d6afb01615f1a03f4a98b462a77adff@macports.org> #66361: ps2eps: Building Fails For Darwin 22 ----------------------+-------------------- Reporter: maierh7 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ps2eps | ----------------------+-------------------- Changes (by rieder): * Attachment "main.log" added. logfile -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:37:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 15:37:58 -0000 Subject: [MacPorts] #66227: freecad @0.18.5_1: Undefined symbols: "boost::python::detail::init_module(char const*, void (*)())" In-Reply-To: <043.a8a67da4fad70599c1a8cb7bcaab84e5@macports.org> References: <043.a8a67da4fad70599c1a8cb7bcaab84e5@macports.org> Message-ID: <058.e335ef51baf8cce797c9d4d3fa1623c0@macports.org> #66227: freecad @0.18.5_1: Undefined symbols: "boost::python::detail::init_module(char const*, void (*)())" ----------------------+---------------------- Reporter: petrrr | Owner: mbrethen Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: freecad | ----------------------+---------------------- Changes (by catap): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"8ad869a0ee7843e63bc8926ea63b430dd08f2375/macports-ports" 8ad869a0ee7843e63bc8926ea63b430dd08f2375/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8ad869a0ee7843e63bc8926ea63b430dd08f2375" freecad: fix build Closes: https://trac.macports.org/ticket/66227 Closes: https://trac.macports.org/ticket/60039 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 15:37:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 15:37:58 -0000 Subject: [MacPorts] #60039: freecad @0.18.4_0+gcc9: Could NOT find Boost (missing: python) In-Reply-To: <050.b063d6ad8706f9b08de6cea1e0747259@macports.org> References: <050.b063d6ad8706f9b08de6cea1e0747259@macports.org> Message-ID: <065.10ab61905b1209087a60a513bfa6e701@macports.org> #60039: freecad @0.18.4_0+gcc9: Could NOT find Boost (missing: python) ----------------------------+---------------------- Reporter: informatimago | Owner: mbrethen Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: Port: freecad | ----------------------------+---------------------- Changes (by catap): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"8ad869a0ee7843e63bc8926ea63b430dd08f2375/macports-ports" 8ad869a0ee7843e63bc8926ea63b430dd08f2375/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8ad869a0ee7843e63bc8926ea63b430dd08f2375" freecad: fix build Closes: https://trac.macports.org/ticket/66227 Closes: https://trac.macports.org/ticket/60039 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:07:43 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 16:07:43 -0000 Subject: [MacPorts] #39812: tests for scotch 6.0.0 are failing In-Reply-To: <041.476b924faff6f69b7f950cece10ee2ff@macports.org> References: <041.476b924faff6f69b7f950cece10ee2ff@macports.org> Message-ID: <056.7b5a09dbdb3ff64d90c13cb69c1a363a@macports.org> #39812: tests for scotch 6.0.0 are failing ---------------------+-------------------------------- Reporter: mkae | Owner: macports-tickets@? Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: scotch | ---------------------+-------------------------------- Changes (by catap): * status: new => closed * resolution: => fixed Comment: In [changeset:"8af09a3558b46007f31d3c8dd4e1eba936bfd0a6/macports-ports" 8af09a3558b46007f31d3c8dd4e1eba936bfd0a6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8af09a3558b46007f31d3c8dd4e1eba936bfd0a6" scotch: fix tests Closes: https://trac.macports.org/ticket/39812 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:17:23 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 16:17:23 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.fa9f20d1b9ad213a0eeb4bfd17fdc9ff@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+--------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: CSXCAD | -----------------------+--------------------- Comment (by esteimle): that worked. Thanks again I really appreciate the help! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:39:22 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 16:39:22 -0000 Subject: [MacPorts] #66017: Upgrade py310-numba from 0.55.2_0 to 0.56.3 In-Reply-To: <046.38b91ec087d51d8670669829ab495b87@macports.org> References: <046.38b91ec087d51d8670669829ab495b87@macports.org> Message-ID: <061.7144133e31cf1438f714940cfe59690b@macports.org> #66017: Upgrade py310-numba from 0.55.2_0 to 0.56.3 --------------------------+---------------------- Reporter: NickFabry | Owner: stromnov Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: Port: py310-numba | --------------------------+---------------------- Changes (by reneeotten): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 16:51:34 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 16:51:34 -0000 Subject: [MacPorts] #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' In-Reply-To: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> References: <045.e103ba63ac85bead1243a0d3f0747774@macports.org> Message-ID: <060.d9f1d177993803a4472b6fe814a788b9@macports.org> #66456: CSXCAD @20221205-c79d6b75_0 build failure: no member named 'setlocale' in namespace 'std' -----------------------+--------------------- Reporter: esteimle | Owner: ra1nb0w Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: CSXCAD | -----------------------+--------------------- Comment (by ra1nb0w): my pleasure. have a nice day. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:05:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:05:50 -0000 Subject: [MacPorts] #66438: spice-gtk configure failure In-Reply-To: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> References: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> Message-ID: <061.5c5512e41c830220e38515458ddc226f@macports.org> #66438: spice-gtk configure failure ------------------------+-------------------- Reporter: ANONIMNIQ | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: spice-gtk | ------------------------+-------------------- Comment (by ANONIMNIQ): Replying to [comment:2 ryandesign]:Build started at 2022-12-14T18:02:54.201560 Main binary: /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/p$ Build Options: -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard$ Python system: Darwin The Meson build system Version: 0.63.3 Source dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync$ Build dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.$ Build type: native build Running command: /opt/local/var/macports/build/_opt_local_var_macports_sources_$ --- stdout --- 0.41 --- stderr --- Project name: spice-gtk Project version: 0.41 ----- Detecting compiler via: /usr/bin/clang --version -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:12:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:12:48 -0000 Subject: [MacPorts] #66438: spice-gtk configure failure In-Reply-To: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> References: <046.e515b65a4b60a609459d7f412777fdf9@macports.org> Message-ID: <061.0fa1a17129e0b90bbd3807ae28bb7f1c@macports.org> #66438: spice-gtk configure failure ------------------------+-------------------- Reporter: ANONIMNIQ | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: spice-gtk | ------------------------+-------------------- Comment (by ANONIMNIQ): version:1 :debug:clean Starting logging for spice-gtk @0.41_0+x11 :debug:sysinfo macOS 13.0 (darwin/22.1.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0 :debug:clean Attempting ln -sf /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/gnome /spice-gtk/work :debug:clean dropping privileges: euid changed to 502, egid changed to 501. :debug:main Executing org.macports.main (spice-gtk) :debug:main Privilege de-escalation not attempted as not running as root. :debug:archivefetch archivefetch phase started at Sat Dec 10 17:26:10 +0000 2022 :msg:archivefetch ---> Fetching archive for spice-gtk :debug:archivefetch Executing org.macports.archivefetch (spice-gtk) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 502/501 :info:archivefetch ---> spice-gtk-0.41_0+x11.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://packages.macports.org /spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://nue.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://fra.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:fetch fetch phase started at Sat Dec 10 17:26:11 +0000 2022 :notice:fetch ---> Fetching distfiles for spice-gtk :debug:fetch elevating privileges for fetch: euid changed to 0, egid changed to 0. :debug:fetch dropping privileges: euid changed to 502, egid changed to 501. :debug:fetch Executing org.macports.fetch (spice-gtk) :info:fetch ---> spice-gtk-0.41.tar.xz does not exist in /opt/local/var/macports/distfiles/spice-gtk :notice:fetch ---> Attempting to fetch spice-gtk-0.41.tar.xz from https://distfiles.macports.org/spice-gtk :debug:fetch Privilege de-escalation not attempted as not running as root. :debug:checksum checksum phase started at Sat Dec 10 17:26:12 +0000 2022 :notice:checksum ---> Verifying checksums for spice-gtk :debug:checksum Executing org.macports.checksum (spice-gtk) :info:checksum ---> Checksumming spice-gtk-0.41.tar.xz :debug:checksum Calculated (rmd160) is 4f66fd847ec37fc51fd9d36ef690d7f8629e0392 :debug:checksum Correct (rmd160) checksum for spice-gtk-0.41.tar.xz :debug:checksum Calculated (sha256) is d8f8b5cbea9184702eeb8cc276a67d72acdb6e36e7c73349fb8445e5bca0969f :debug:checksum Correct (sha256) checksum for spice-gtk-0.41.tar.xz :debug:checksum Calculated (size) is 827320 :debug:checksum Correct (size) checksum for spice-gtk-0.41.tar.xz :debug:checksum Privilege de-escalation not attempted as not running as root. :debug:extract extract phase started at Sat Dec 10 17:26:12 +0000 2022 :notice:extract ---> Extracting spice-gtk :debug:extract setting option extract.cmd to /opt/local/bin/xz :debug:extract Executing org.macports.extract (spice-gtk) :info:extract ---> Extracting spice-gtk-0.41.tar.xz :debug:extract setting option extract.args to '/opt/local/var/macports/distfiles/spice-gtk/spice-gtk-0.41.tar.xz' :debug:extract Environment: :debug:extract CC_PRINT_OPTIONS='YES' :debug:extract CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:extract CPATH='/opt/local/include' :debug:extract DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:extract LIBRARY_PATH='/opt/local/lib' :debug:extract MACOSX_DEPLOYMENT_TARGET='13.0' :debug:extract SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:extract Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work" && /opt/local/bin/xz -dc '/opt/local/var/macports/distfiles/spice-gtk/spice- gtk-0.41.tar.xz' | /usr/bin/tar -xf - :debug:extract system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work" && /opt/local/bin/xz -dc '/opt/local/var/macports/distfiles/spice-gtk/spice- gtk-0.41.tar.xz' | /usr/bin/tar -xf - :debug:extract euid/egid changed to: 0/0 :debug:extract chowned /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work to macports :debug:extract euid/egid changed to: 502/501 :debug:extract Privilege de-escalation not attempted as not running as root. :debug:patch patch phase started at Sat Dec 10 17:26:12 +0000 2022 :debug:patch Executing org.macports.patch (spice-gtk) :notice:patch ---> Applying patches to spice-gtk :info:patch ---> Applying patch-meson-python.diff :debug:patch Environment: :debug:patch CC_PRINT_OPTIONS='YES' :debug:patch CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:patch CPATH='/opt/local/include' :debug:patch DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:patch LIBRARY_PATH='/opt/local/lib' :debug:patch MACOSX_DEPLOYMENT_TARGET='13.0' :debug:patch SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:patch Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/gnome /spice-gtk/files/patch-meson-python.diff' :debug:patch system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/gnome /spice-gtk/files/patch-meson-python.diff' :info:patch patching file 'src/meson.build' :info:patch patching file 'subprojects/spice-common/meson.build' :debug:patch Executing proc-post-org.macports.patch-patch-0 :info:patch ---> Patching meson.build: s|@@PYTHON_BIN@@|/opt/local/bin/python3.9|g :debug:patch Executing reinplace: /usr/bin/sed s|@@PYTHON_BIN@@|/opt/local/bin/python3.9|g @file17 :debug:patch euid/egid changed to: 0/0 :debug:patch chowned /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41/src/meson.build to macports :debug:patch euid/egid changed to: 502/501 :debug:patch euid/egid changed to: 0/0 :debug:patch setting attributes on /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41/src/meson.build :debug:patch euid/egid changed to: 502/501 :info:patch ---> Patching meson.build: s|@@PYTHON_BIN@@|/opt/local/bin/python3.9|g :debug:patch Executing reinplace: /usr/bin/sed s|@@PYTHON_BIN@@|/opt/local/bin/python3.9|g @file17 :debug:patch euid/egid changed to: 0/0 :debug:patch chowned /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41/subprojects/spice-common/meson.build to macports :debug:patch euid/egid changed to: 502/501 :debug:patch euid/egid changed to: 0/0 :debug:patch setting attributes on /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41/subprojects/spice-common/meson.build :debug:patch euid/egid changed to: 502/501 :debug:patch Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Sat Dec 10 17:26:12 +0000 2022 :notice:configure ---> Configuring spice-gtk :debug:configure Preferred compilers: clang macports-clang-14 macports- clang-13 macports-clang-12 macports-clang-11 macports-clang-10 macports- clang-9.0 :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Active variants check for source-type install considers depends_fetch depends_extract depends_lib depends_build depends_run: xz spice-protocol gtk3 json-glib libpixman lz4 libjpeg-turbo gstreamer1 gstreamer1-gst-plugins-base libepoxy libusb libopus openssl asciidoc intltool pkgconfig python39 py39-six py39-parsing vala meson ninja :debug:configure gtk3 is installed with the following variants: +x11 :debug:configure required: x11, forbidden: quartz :debug:configure accepted :debug:configure Executing org.macports.configure (spice-gtk) :debug:configure Environment: :debug:configure CC='/usr/bin/clang' :debug:configure CC_PRINT_OPTIONS='YES' :debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:configure CFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure CPATH='/opt/local/include' :debug:configure CPPFLAGS='-I/opt/local/include -D_XOPEN_SOURCE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :debug:configure CXX='/usr/bin/clang++' :debug:configure CXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:configure F90FLAGS='-pipe -Os -m64' :debug:configure FCFLAGS='-pipe -Os -m64' :debug:configure FFLAGS='-pipe -Os -m64' :debug:configure INSTALL='/usr/bin/install -c' :debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure LIBRARY_PATH='/opt/local/lib' :debug:configure MACOSX_DEPLOYMENT_TARGET='13.0' :debug:configure OBJC='/usr/bin/clang' :debug:configure OBJCFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure OBJCXX='/usr/bin/clang++' :debug:configure OBJCXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure The Meson build system :info:configure Version: 0.63.3 :info:configure Source dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 :info:configure Build dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Build type: native build :info:configure Project name: spice-gtk :info:configure Project version: 0.41 :info:configure C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure Host machine cpu family: x86_64 :info:configure Host machine cpu: x86_64 :info:configure Executing subproject spice-common :info:configure spice-common| Project name: spice-common :info:configure spice-common| Project version: undefined :info:configure spice-common| C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure spice-common| C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure spice-common| Has header "alloca.h" : YES :info:configure spice-common| Has header "arpa/inet.h" : YES :info:configure spice-common| Has header "dlfcn.h" : YES :info:configure spice-common| Has header "inttypes.h" : YES :info:configure spice-common| Has header "netinet/in.h" : YES :info:configure spice-common| Has header "stdlib.h" : YES :info:configure spice-common| Has header "sys/socket.h" : YES :info:configure spice-common| Has header "sys/stat.h" : YES :info:configure spice-common| Has header "sys/types.h" : YES :info:configure spice-common| Has header "unistd.h" : YES :info:configure spice-common| Has header "regex.h" : YES :info:configure spice-common| Has header "sys/mman.h" : YES :info:configure spice-common| Checking for function "alloca" : YES :info:configure spice-common| Checking for function "sigaction" : YES :info:configure spice-common| Checking for function "drand48" : YES :info:configure spice-common| Checking for function "setlinebuf" : YES :info:configure spice-common| Library m found: YES :info:configure spice-common| Found pkg-config: /opt/local/bin/pkg-config (0.29.2) :info:configure spice-common| Run-time dependency spice-protocol found: YES 0.14.3 :info:configure spice-common| Run-time dependency glib-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency pixman-1 found: YES 0.38.4 :info:configure spice-common| Run-time dependency openssl found: YES 3.0.7 :info:configure spice-common| Run-time dependency gio-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency opus found: YES 1.3.1 :info:configure subprojects/spice-common/meson.build:130:2: ERROR: ['/opt/local/bin/python3.9']> is not a valid python or it is missing distutils :info:configure A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Exit code: 1 :error:configure Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :error:configure Failed to configure spice-gtk: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "$procedure $targetname" :error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. version:1 :debug:main Starting logging for spice-gtk @0.41_0+x11 :debug:sysinfo macOS 13.0 (darwin/22.1.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0 :debug:main dropping privileges: euid changed to 502, egid changed to 501. :debug:main Executing org.macports.main (spice-gtk) :debug:main Privilege de-escalation not attempted as not running as root. :debug:archivefetch archivefetch phase started at Sat Dec 10 17:28:57 +0000 2022 :msg:archivefetch ---> Fetching archive for spice-gtk :debug:archivefetch Executing org.macports.archivefetch (spice-gtk) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 502/501 :info:archivefetch ---> spice-gtk-0.41_0+x11.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://packages.macports.org /spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://nue.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://fra.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.fetch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.checksum (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.extract (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.patch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Sat Dec 10 17:28:58 +0000 2022 :notice:configure ---> Configuring spice-gtk :debug:configure Preferred compilers: clang macports-clang-14 macports- clang-13 macports-clang-12 macports-clang-11 macports-clang-10 macports- clang-9.0 :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Active variants check for source-type install considers depends_fetch depends_extract depends_lib depends_build depends_run: xz spice-protocol gtk3 json-glib libpixman lz4 libjpeg-turbo gstreamer1 gstreamer1-gst-plugins-base libepoxy libusb libopus openssl asciidoc intltool pkgconfig python39 py39-six py39-parsing vala meson ninja :debug:configure gtk3 is installed with the following variants: +x11 :debug:configure required: x11, forbidden: quartz :debug:configure accepted :debug:configure Executing org.macports.configure (spice-gtk) :debug:configure Environment: :debug:configure CC='/usr/bin/clang' :debug:configure CC_PRINT_OPTIONS='YES' :debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:configure CFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure CPATH='/opt/local/include' :debug:configure CPPFLAGS='-I/opt/local/include -D_XOPEN_SOURCE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :debug:configure CXX='/usr/bin/clang++' :debug:configure CXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:configure F90FLAGS='-pipe -Os -m64' :debug:configure FCFLAGS='-pipe -Os -m64' :debug:configure FFLAGS='-pipe -Os -m64' :debug:configure INSTALL='/usr/bin/install -c' :debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure LIBRARY_PATH='/opt/local/lib' :debug:configure MACOSX_DEPLOYMENT_TARGET='13.0' :debug:configure OBJC='/usr/bin/clang' :debug:configure OBJCFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure OBJCXX='/usr/bin/clang++' :debug:configure OBJCXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure The Meson build system :info:configure Version: 0.63.3 :info:configure Source dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 :info:configure Build dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Build type: native build :info:configure Project name: spice-gtk :info:configure Project version: 0.41 :info:configure C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure Host machine cpu family: x86_64 :info:configure Host machine cpu: x86_64 :info:configure Executing subproject spice-common :info:configure spice-common| Project name: spice-common :info:configure spice-common| Project version: undefined :info:configure spice-common| C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure spice-common| C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure spice-common| Has header "alloca.h" : YES :info:configure spice-common| Has header "arpa/inet.h" : YES :info:configure spice-common| Has header "dlfcn.h" : YES :info:configure spice-common| Has header "inttypes.h" : YES :info:configure spice-common| Has header "netinet/in.h" : YES :info:configure spice-common| Has header "stdlib.h" : YES :info:configure spice-common| Has header "sys/socket.h" : YES :info:configure spice-common| Has header "sys/stat.h" : YES :info:configure spice-common| Has header "sys/types.h" : YES :info:configure spice-common| Has header "unistd.h" : YES :info:configure spice-common| Has header "regex.h" : YES :info:configure spice-common| Has header "sys/mman.h" : YES :info:configure spice-common| Checking for function "alloca" : YES :info:configure spice-common| Checking for function "sigaction" : YES :info:configure spice-common| Checking for function "drand48" : YES :info:configure spice-common| Checking for function "setlinebuf" : YES :info:configure spice-common| Library m found: YES :info:configure spice-common| Found pkg-config: /opt/local/bin/pkg-config (0.29.2) :info:configure spice-common| Run-time dependency spice-protocol found: YES 0.14.3 :info:configure spice-common| Run-time dependency glib-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency pixman-1 found: YES 0.38.4 :info:configure spice-common| Run-time dependency openssl found: YES 3.0.7 :info:configure spice-common| Run-time dependency gio-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency opus found: YES 1.3.1 :info:configure subprojects/spice-common/meson.build:130:2: ERROR: ['/opt/local/bin/python3.9']> is not a valid python or it is missing distutils :info:configure A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Exit code: 1 :error:configure Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :error:configure Failed to configure spice-gtk: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "$procedure $targetname" :error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. version:1 :debug:clean Starting logging for spice-gtk @0.41_0+x11 :debug:sysinfo macOS 13.0 (darwin/22.1.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0 :debug:clean Attempting ln -sf /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/gnome /spice-gtk/work :debug:clean dropping privileges: euid changed to 502, egid changed to 501. :debug:main Executing org.macports.main (spice-gtk) :debug:main Privilege de-escalation not attempted as not running as root. :debug:archivefetch archivefetch phase started at Sat Dec 10 17:38:41 +0000 2022 :msg:archivefetch ---> Fetching archive for spice-gtk :debug:archivefetch Executing org.macports.archivefetch (spice-gtk) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 502/501 :info:archivefetch ---> spice-gtk-0.41_0+x11.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://packages.macports.org /spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://nue.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://fra.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.fetch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.checksum (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.extract (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.patch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Sat Dec 10 17:38:42 +0000 2022 :notice:configure ---> Configuring spice-gtk :debug:configure Preferred compilers: clang macports-clang-14 macports- clang-13 macports-clang-12 macports-clang-11 macports-clang-10 macports- clang-9.0 :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Active variants check for source-type install considers depends_fetch depends_extract depends_lib depends_build depends_run: xz spice-protocol gtk3 json-glib libpixman lz4 libjpeg-turbo gstreamer1 gstreamer1-gst-plugins-base libepoxy libusb libopus openssl asciidoc intltool pkgconfig python39 py39-six py39-parsing vala meson ninja :debug:configure gtk3 is installed with the following variants: +x11 :debug:configure required: x11, forbidden: quartz :debug:configure accepted :debug:configure Executing org.macports.configure (spice-gtk) :debug:configure Environment: :debug:configure CC='/usr/bin/clang' :debug:configure CC_PRINT_OPTIONS='YES' :debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:configure CFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure CPATH='/opt/local/include' :debug:configure CPPFLAGS='-I/opt/local/include -D_XOPEN_SOURCE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :debug:configure CXX='/usr/bin/clang++' :debug:configure CXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:configure F90FLAGS='-pipe -Os -m64' :debug:configure FCFLAGS='-pipe -Os -m64' :debug:configure FFLAGS='-pipe -Os -m64' :debug:configure INSTALL='/usr/bin/install -c' :debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure LIBRARY_PATH='/opt/local/lib' :debug:configure MACOSX_DEPLOYMENT_TARGET='13.0' :debug:configure OBJC='/usr/bin/clang' :debug:configure OBJCFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure OBJCXX='/usr/bin/clang++' :debug:configure OBJCXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure The Meson build system :info:configure Version: 0.63.3 :info:configure Source dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 :info:configure Build dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Build type: native build :info:configure Project name: spice-gtk :info:configure Project version: 0.41 :info:configure C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure Host machine cpu family: x86_64 :info:configure Host machine cpu: x86_64 :info:configure Executing subproject spice-common :info:configure spice-common| Project name: spice-common :info:configure spice-common| Project version: undefined :info:configure spice-common| C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure spice-common| C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure spice-common| Has header "alloca.h" : YES :info:configure spice-common| Has header "arpa/inet.h" : YES :info:configure spice-common| Has header "dlfcn.h" : YES :info:configure spice-common| Has header "inttypes.h" : YES :info:configure spice-common| Has header "netinet/in.h" : YES :info:configure spice-common| Has header "stdlib.h" : YES :info:configure spice-common| Has header "sys/socket.h" : YES :info:configure spice-common| Has header "sys/stat.h" : YES :info:configure spice-common| Has header "sys/types.h" : YES :info:configure spice-common| Has header "unistd.h" : YES :info:configure spice-common| Has header "regex.h" : YES :info:configure spice-common| Has header "sys/mman.h" : YES :info:configure spice-common| Checking for function "alloca" : YES :info:configure spice-common| Checking for function "sigaction" : YES :info:configure spice-common| Checking for function "drand48" : YES :info:configure spice-common| Checking for function "setlinebuf" : YES :info:configure spice-common| Library m found: YES :info:configure spice-common| Found pkg-config: /opt/local/bin/pkg-config (0.29.2) :info:configure spice-common| Run-time dependency spice-protocol found: YES 0.14.3 :info:configure spice-common| Run-time dependency glib-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency pixman-1 found: YES 0.38.4 :info:configure spice-common| Run-time dependency openssl found: YES 3.0.7 :info:configure spice-common| Run-time dependency gio-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency opus found: YES 1.3.1 :info:configure subprojects/spice-common/meson.build:130:2: ERROR: ['/opt/local/bin/python3.9']> is not a valid python or it is missing distutils :info:configure A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Exit code: 1 :error:configure Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :error:configure Failed to configure spice-gtk: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "$procedure $targetname" :error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. version:1 :debug:main Starting logging for spice-gtk @0.41_0+x11 :debug:sysinfo macOS 13.0 (darwin/22.1.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0 :debug:main dropping privileges: euid changed to 502, egid changed to 501. :debug:main Executing org.macports.main (spice-gtk) :debug:main Privilege de-escalation not attempted as not running as root. :debug:archivefetch archivefetch phase started at Sat Dec 10 17:40:09 +0000 2022 :msg:archivefetch ---> Fetching archive for spice-gtk :debug:archivefetch Executing org.macports.archivefetch (spice-gtk) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 502/501 :info:archivefetch ---> spice-gtk-0.41_0+x11.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://packages.macports.org /spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://nue.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://fra.de.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.fetch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.checksum (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.extract (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.patch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Sat Dec 10 17:40:09 +0000 2022 :notice:configure ---> Configuring spice-gtk :debug:configure Preferred compilers: clang macports-clang-14 macports- clang-13 macports-clang-12 macports-clang-11 macports-clang-10 macports- clang-9.0 :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Active variants check for source-type install considers depends_fetch depends_extract depends_lib depends_build depends_run: xz spice-protocol gtk3 json-glib libpixman lz4 libjpeg-turbo gstreamer1 gstreamer1-gst-plugins-base libepoxy libusb libopus openssl asciidoc intltool pkgconfig python39 py39-six py39-parsing vala meson ninja :debug:configure gtk3 is installed with the following variants: +x11 :debug:configure required: x11, forbidden: quartz :debug:configure accepted :debug:configure Executing org.macports.configure (spice-gtk) :debug:configure Environment: :debug:configure CC='/usr/bin/clang' :debug:configure CC_PRINT_OPTIONS='YES' :debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:configure CFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure CPATH='/opt/local/include' :debug:configure CPPFLAGS='-I/opt/local/include -D_XOPEN_SOURCE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :debug:configure CXX='/usr/bin/clang++' :debug:configure CXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:configure F90FLAGS='-pipe -Os -m64' :debug:configure FCFLAGS='-pipe -Os -m64' :debug:configure FFLAGS='-pipe -Os -m64' :debug:configure INSTALL='/usr/bin/install -c' :debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure LIBRARY_PATH='/opt/local/lib' :debug:configure MACOSX_DEPLOYMENT_TARGET='13.0' :debug:configure OBJC='/usr/bin/clang' :debug:configure OBJCFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure OBJCXX='/usr/bin/clang++' :debug:configure OBJCXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure The Meson build system :info:configure Version: 0.63.3 :info:configure Source dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 :info:configure Build dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Build type: native build :info:configure Project name: spice-gtk :info:configure Project version: 0.41 :info:configure C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure Host machine cpu family: x86_64 :info:configure Host machine cpu: x86_64 :info:configure Executing subproject spice-common :info:configure spice-common| Project name: spice-common :info:configure spice-common| Project version: undefined :info:configure spice-common| C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure spice-common| C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure spice-common| Has header "alloca.h" : YES :info:configure spice-common| Has header "arpa/inet.h" : YES :info:configure spice-common| Has header "dlfcn.h" : YES :info:configure spice-common| Has header "inttypes.h" : YES :info:configure spice-common| Has header "netinet/in.h" : YES :info:configure spice-common| Has header "stdlib.h" : YES :info:configure spice-common| Has header "sys/socket.h" : YES :info:configure spice-common| Has header "sys/stat.h" : YES :info:configure spice-common| Has header "sys/types.h" : YES :info:configure spice-common| Has header "unistd.h" : YES :info:configure spice-common| Has header "regex.h" : YES :info:configure spice-common| Has header "sys/mman.h" : YES :info:configure spice-common| Checking for function "alloca" : YES :info:configure spice-common| Checking for function "sigaction" : YES :info:configure spice-common| Checking for function "drand48" : YES :info:configure spice-common| Checking for function "setlinebuf" : YES :info:configure spice-common| Library m found: YES :info:configure spice-common| Found pkg-config: /opt/local/bin/pkg-config (0.29.2) :info:configure spice-common| Run-time dependency spice-protocol found: YES 0.14.3 :info:configure spice-common| Run-time dependency glib-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency pixman-1 found: YES 0.38.4 :info:configure spice-common| Run-time dependency openssl found: YES 3.0.7 :info:configure spice-common| Run-time dependency gio-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency opus found: YES 1.3.1 :info:configure subprojects/spice-common/meson.build:130:2: ERROR: ['/opt/local/bin/python3.9']> is not a valid python or it is missing distutils :info:configure A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Exit code: 1 :error:configure Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :error:configure Failed to configure spice-gtk: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "$procedure $targetname" :error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. version:1 :debug:main Starting logging for spice-gtk @0.41_0+x11 :debug:sysinfo macOS 13.0.1 (darwin/22.1.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 14.1.0.0.1.1666437224 :debug:sysinfo SDK 13 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0 :debug:main dropping privileges: euid changed to 502, egid changed to 501. :debug:main Executing org.macports.main (spice-gtk) :debug:main Privilege de-escalation not attempted as not running as root. :debug:archivefetch archivefetch phase started at Wed Dec 14 18:02:49 +0000 2022 :msg:archivefetch ---> Fetching archive for spice-gtk :debug:archivefetch Executing org.macports.archivefetch (spice-gtk) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 502/501 :info:archivefetch ---> spice-gtk-0.41_0+x11.darwin_22.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://packages.macports.org /spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://mse.uk.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: The requested URL returned error: 404 :msg:archivefetch ---> Attempting to fetch spice- gtk-0.41_0+x11.darwin_22.x86_64.tbz2 from https://ema.uk.packages.macports.org/spice-gtk :debug:archivefetch Fetching archive failed: SSL: no alternative certificate subject name matches target host name 'ema.uk.packages.macports.org' :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.fetch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.checksum (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.extract (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:archivefetch Skipping completed org.macports.patch (spice-gtk) :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Wed Dec 14 18:02:53 +0000 2022 :notice:configure ---> Configuring spice-gtk :debug:configure Preferred compilers: clang macports-clang-14 macports- clang-13 macports-clang-12 macports-clang-11 macports-clang-10 macports- clang-9.0 :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Active variants check for source-type install considers depends_fetch depends_extract depends_lib depends_build depends_run: xz spice-protocol gtk3 json-glib libpixman lz4 libjpeg-turbo gstreamer1 gstreamer1-gst-plugins-base libepoxy libusb libopus openssl asciidoc intltool pkgconfig python39 py39-six py39-parsing vala meson ninja :debug:configure gtk3 is installed with the following variants: +x11 :debug:configure required: x11, forbidden: quartz :debug:configure accepted :debug:configure Executing org.macports.configure (spice-gtk) :debug:configure Environment: :debug:configure CC='/usr/bin/clang' :debug:configure CC_PRINT_OPTIONS='YES' :debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice- gtk/work/.CC_PRINT_OPTIONS' :debug:configure CFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure CPATH='/opt/local/include' :debug:configure CPPFLAGS='-I/opt/local/include -D_XOPEN_SOURCE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :debug:configure CXX='/usr/bin/clang++' :debug:configure CXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure DEVELOPER_DIR='/Library/Developer/CommandLineTools' :debug:configure F90FLAGS='-pipe -Os -m64' :debug:configure FCFLAGS='-pipe -Os -m64' :debug:configure FFLAGS='-pipe -Os -m64' :debug:configure INSTALL='/usr/bin/install -c' :debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure LIBRARY_PATH='/opt/local/lib' :debug:configure MACOSX_DEPLOYMENT_TARGET='13.0' :debug:configure OBJC='/usr/bin/clang' :debug:configure OBJCFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure OBJCXX='/usr/bin/clang++' :debug:configure OBJCXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64' :debug:configure SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure The Meson build system :info:configure Version: 0.63.3 :info:configure Source dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 :info:configure Build dir: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Build type: native build :info:configure Project name: spice-gtk :info:configure Project version: 0.41 :info:configure C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure Host machine cpu family: x86_64 :info:configure Host machine cpu: x86_64 :info:configure Executing subproject spice-common :info:configure spice-common| Project name: spice-common :info:configure spice-common| Project version: undefined :info:configure spice-common| C compiler for the host machine: /usr/bin/clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") :info:configure spice-common| C linker for the host machine: /usr/bin/clang ld64 820.1 :info:configure spice-common| Has header "alloca.h" : YES :info:configure spice-common| Has header "arpa/inet.h" : YES :info:configure spice-common| Has header "dlfcn.h" : YES :info:configure spice-common| Has header "inttypes.h" : YES :info:configure spice-common| Has header "netinet/in.h" : YES :info:configure spice-common| Has header "stdlib.h" : YES :info:configure spice-common| Has header "sys/socket.h" : YES :info:configure spice-common| Has header "sys/stat.h" : YES :info:configure spice-common| Has header "sys/types.h" : YES :info:configure spice-common| Has header "unistd.h" : YES :info:configure spice-common| Has header "regex.h" : YES :info:configure spice-common| Has header "sys/mman.h" : YES :info:configure spice-common| Checking for function "alloca" : YES :info:configure spice-common| Checking for function "sigaction" : YES :info:configure spice-common| Checking for function "drand48" : YES :info:configure spice-common| Checking for function "setlinebuf" : YES :info:configure spice-common| Library m found: YES :info:configure spice-common| Found pkg-config: /opt/local/bin/pkg-config (0.29.2) :info:configure spice-common| Run-time dependency spice-protocol found: YES 0.14.3 :info:configure spice-common| Run-time dependency glib-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency pixman-1 found: YES 0.38.4 :info:configure spice-common| Run-time dependency openssl found: YES 3.0.7 :info:configure spice-common| Run-time dependency gio-2.0 found: YES 2.70.5 :info:configure spice-common| Run-time dependency opus found: YES 1.3.1 :info:configure subprojects/spice-common/meson.build:130:2: ERROR: ['/opt/local/bin/python3.9']> is not a valid python or it is missing distutils :info:configure A full log can be found at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41" && /opt/local/bin/meson --prefix=/opt/local -Dgtk_doc=disabled -Dpolkit=disabled -Dsasl=disabled -Dsmartcard=disabled -Dusbredir=disabled -Dwebdav=disabled /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/spice- gtk-0.41 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build :info:configure Exit code: 1 :error:configure Failed to configure spice-gtk: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/work/build /meson-logs/meson-log.txt :error:configure Failed to configure spice-gtk: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed :debug:configure while executing :debug:configure "$procedure $targetname" :error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_gnome_spice-gtk/spice-gtk/main.log for details. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:30:44 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:30:44 -0000 Subject: [MacPorts] #66471: x265 or ffmpeg problem In-Reply-To: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> References: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> Message-ID: <057.3b51cbf98e8339d4ab96eaefa09f8d14@macports.org> #66471: x265 or ffmpeg problem -------------------------------+-------------------- Reporter: rufty | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: x265 (or ffmpeg) | -------------------------------+-------------------- Changes (by kickingvegas): * Attachment "main.log" added. main.log from Ventura -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:31:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:31:35 -0000 Subject: [MacPorts] #66471: x265 or ffmpeg problem In-Reply-To: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> References: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> Message-ID: <057.730392f080a8c4947ece6efe9517e41b@macports.org> #66471: x265 or ffmpeg problem -------------------------------+-------------------- Reporter: rufty | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: x265 (or ffmpeg) | -------------------------------+-------------------- Comment (by kickingvegas): Seeing same issue on Ventura (13.1) Attached /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:39:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:39:50 -0000 Subject: [MacPorts] #66473: plantuml failing to build on Ventura 13.1 Message-ID: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> #66473: plantuml failing to build on Ventura 13.1 --------------------------+-------------------- Reporter: kickingvegas | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: --------------------------+-------------------- plantuml failing to install on Ventura 13.1. Causes macOS crash log for java. abbreviated /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/main.log {{{ :info:build > Task :compileJava :info:build Note: Some input files use or override a deprecated API. :info:build Note: Recompile with -Xlint:deprecation for details. :info:build Note: Some input files use unchecked or unsafe operations. :info:build Note: Recompile with -Xlint:unchecked for details. :info:build > Task :processResources UP-TO-DATE :info:build > Task :classes :info:build > Task :jar :info:build > Task :javadoc UP-TO-DATE :info:build > Task :javadocJar :info:build > Task :sourcesJar :info:build > Task :assemble :info:build > Task :compileTestJava :info:build > Task :processTestResources UP-TO-DATE :info:build > Task :testClasses :info:build > Task :test FAILED :info:build FAILURE: Build failed with an exception. :info:build * What went wrong: :info:build Execution failed for task ':test'. :info:build > Process 'Gradle Test Executor 1' finished with non-zero exit value 133 :info:build This problem might be caused by incorrect test process configuration. :info:build Please refer to the test execution section in the User Manual at https://docs.gradle.org/7.6/userguide/java_testing.html#sec:test_execution :info:build * Try: :info:build > Run with --stacktrace option to get the stack trace. :info:build > Run with --info or --debug option to get more log output. :info:build > Run with --scan to get full insights. :info:build * Get more help at https://help.gradle.org :info:build BUILD FAILED in 14s :info:build 9 actionable tasks: 6 executed, 3 up-to-date :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/work/plantuml-1.2022.12" && /opt/local/bin/gradle build :info:build Exit code: 1 :error:build Failed to build plantuml: command execution failed :debug:build Error code: CHILDSTATUS 73811 1 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/main.log for details. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:40:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:40:37 -0000 Subject: [MacPorts] #66473: plantuml failing to build on Ventura 13.1 In-Reply-To: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> References: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> Message-ID: <064.b2e23f095e4677f549db3a3a41da0c26@macports.org> #66473: plantuml failing to build on Ventura 13.1 ---------------------------+-------------------- Reporter: kickingvegas | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------------+-------------------- Changes (by kickingvegas): * Attachment "main.log" added. ventura main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:43:11 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:43:11 -0000 Subject: [MacPorts] #66473: plantuml failing to build on Ventura 13.1 In-Reply-To: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> References: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> Message-ID: <064.17d559fb782921a0edd410c74d774c50@macports.org> #66473: plantuml failing to build on Ventura 13.1 ---------------------------+-------------------- Reporter: kickingvegas | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------------+-------------------- Changes (by kickingvegas): * Attachment "java-crash.log" added. macOS crash log for java -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 18:45:31 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 18:45:31 -0000 Subject: [MacPorts] #66473: plantuml failing to build on Ventura 13.1 In-Reply-To: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> References: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> Message-ID: <064.a8543b96653d06c983a884c47c712c55@macports.org> #66473: plantuml failing to build on Ventura 13.1 ---------------------------+-------------------- Reporter: kickingvegas | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: plantuml | ---------------------------+-------------------- Changes (by kickingvegas): * port: => plantuml Old description: > plantuml failing to install on Ventura 13.1. Causes macOS crash log for > java. > > abbreviated > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/main.log > > {{{ > :info:build > Task :compileJava > :info:build Note: Some input files use or override a deprecated API. > :info:build Note: Recompile with -Xlint:deprecation for details. > :info:build Note: Some input files use unchecked or unsafe operations. > :info:build Note: Recompile with -Xlint:unchecked for details. > :info:build > Task :processResources UP-TO-DATE > :info:build > Task :classes > :info:build > Task :jar > :info:build > Task :javadoc UP-TO-DATE > :info:build > Task :javadocJar > :info:build > Task :sourcesJar > :info:build > Task :assemble > :info:build > Task :compileTestJava > :info:build > Task :processTestResources UP-TO-DATE > :info:build > Task :testClasses > :info:build > Task :test FAILED > :info:build FAILURE: Build failed with an exception. > :info:build * What went wrong: > :info:build Execution failed for task ':test'. > :info:build > Process 'Gradle Test Executor 1' finished with non-zero > exit value 133 > :info:build This problem might be caused by incorrect test process > configuration. > :info:build Please refer to the test execution section in the User > Manual at > https://docs.gradle.org/7.6/userguide/java_testing.html#sec:test_execution > :info:build * Try: > :info:build > Run with --stacktrace option to get the stack trace. > :info:build > Run with --info or --debug option to get more log output. > :info:build > Run with --scan to get full insights. > :info:build * Get more help at https://help.gradle.org > :info:build BUILD FAILED in 14s > :info:build 9 actionable tasks: 6 executed, 3 up-to-date > :info:build Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/work/plantuml-1.2022.12" > && /opt/local/bin/gradle build > :info:build Exit code: 1 > :error:build Failed to build plantuml: command execution failed > :debug:build Error code: CHILDSTATUS 73811 1 > :debug:build Backtrace: command execution failed > :debug:build while executing > :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" > :debug:build invoked from within > :debug:build "command_exec -callback > portprogress::target_progress_callback build" > :debug:build (procedure "portbuild::build_main" line 8) > :debug:build invoked from within > :debug:build "$procedure $targetname" > :error:build See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/main.log > for details. > }}} New description: plantuml failing to install on Ventura 13.1. Causes macOS crash log for java. abbreviated /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/main.log using openjdk18 @18.0.2.1_0+release+server (active) port. {{{ :info:build > Task :compileJava :info:build Note: Some input files use or override a deprecated API. :info:build Note: Recompile with -Xlint:deprecation for details. :info:build Note: Some input files use unchecked or unsafe operations. :info:build Note: Recompile with -Xlint:unchecked for details. :info:build > Task :processResources UP-TO-DATE :info:build > Task :classes :info:build > Task :jar :info:build > Task :javadoc UP-TO-DATE :info:build > Task :javadocJar :info:build > Task :sourcesJar :info:build > Task :assemble :info:build > Task :compileTestJava :info:build > Task :processTestResources UP-TO-DATE :info:build > Task :testClasses :info:build > Task :test FAILED :info:build FAILURE: Build failed with an exception. :info:build * What went wrong: :info:build Execution failed for task ':test'. :info:build > Process 'Gradle Test Executor 1' finished with non-zero exit value 133 :info:build This problem might be caused by incorrect test process configuration. :info:build Please refer to the test execution section in the User Manual at https://docs.gradle.org/7.6/userguide/java_testing.html#sec:test_execution :info:build * Try: :info:build > Run with --stacktrace option to get the stack trace. :info:build > Run with --info or --debug option to get more log output. :info:build > Run with --scan to get full insights. :info:build * Get more help at https://help.gradle.org :info:build BUILD FAILED in 14s :info:build 9 actionable tasks: 6 executed, 3 up-to-date :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/work/plantuml-1.2022.12" && /opt/local/bin/gradle build :info:build Exit code: 1 :error:build Failed to build plantuml: command execution failed :debug:build Error code: CHILDSTATUS 73811 1 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_plantuml/plantuml/main.log for details. }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:08:45 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 19:08:45 -0000 Subject: [MacPorts] #66471: x265 or ffmpeg problem In-Reply-To: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> References: <042.8cf8786f63629ef13d39400f06d57a5c@macports.org> Message-ID: <057.51555388bb2f58d163a949ed344b1767@macports.org> #66471: x265 or ffmpeg problem --------------------------+-------------------- Reporter: rufty | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: x265 ffmpeg | --------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate * port: x265 (or ffmpeg) => x265 ffmpeg Comment: #66465 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:09:11 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 19:09:11 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade (was: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure on mavericks after x265 3.4_0 < 3.4_1 upgrade) In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.84f49d9aa8dfe5cf51f454389b45ac02@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade ---------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg | ---------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:13:23 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 19:13:23 -0000 Subject: [MacPorts] #66473: plantuml failing to build on Ventura 13.1 In-Reply-To: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> References: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> Message-ID: <064.d087a668c6c36ac519dfdbb647472a3a@macports.org> #66473: plantuml failing to build on Ventura 13.1 ---------------------------+---------------------- Reporter: kickingvegas | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: plantuml | ---------------------------+---------------------- Changes (by jmroot): * owner: (none) => judaew * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:28:59 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 19:28:59 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.4f0bb11783c2bcfed32a3b767816b1c9@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by herbygillot): Can someone confirm that this is resolved now? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:40:21 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 19:40:21 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.b3f219ba4b4a2d70c56ebfd0603f7f3a@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): After having rebuilt `texlive-bin` and `OpenBLAS`, starting yesterday, I `selfupdate`d shortly and am `upgrad`ing. There is no update of `libdeflate` listed ? was its `Portfile` changed and has it now a more up- to-date timestamp? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 19:43:29 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 19:43:29 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.75e2c20e63cca6d76cce5a82ebc2e837@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): `1596 2022-12-10 11:29` seems to be a newer version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 20:07:16 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 20:07:16 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.a79274b3d175db56a3322132b4d2f2ea@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by herbygillot): OK, I bumped revision on `libdeflate` - it should now show up as updated. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 21:30:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 21:30:49 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.6fa5140bda7ae84f55a2851004020245@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade ---------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg | ---------------------+-------------------- Changes (by jmroot): * cc: kencu, janngobble (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 21:31:14 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 21:31:14 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.ca3649849c84204defa7be2b0ea8ba09@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Changes (by jmroot): * port: ffmpeg => ffmpeg x265 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 22:31:53 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 22:31:53 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.12e5d715b0830f344aa6410b54bcb004@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by janngobble): This seems to be something to do with libx265.dylib not being built. @KenCu, could this have something to do w/c++11? Zhenfu Shi had issues over on GitHub with the library not being built, but as he said, -DENABLE_SHARED=OFF was there before this change. (I didn't add it and have no idea why that would be needed for this one addition). So, why would this change cause that file to disappear? One more thing: @tehcog's build doesn't have "highdepth" - which is the only place my change applies. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 23:46:38 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 23:46:38 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.c586a4e5658f087787b738f71ea42825@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): Yeah, I know -- one little thing, should be just fine, but the whole house of cards comes falling down... I built libx265 locally before I committed the PR. The new configure argument requires c++11 https://bitbucket.org/multicoreware/x265_git/src/4da1198a94028026ce96ba1781d3c7842e74e173/source/CMakeLists.txt#lines-227 so the Portfile was set to require a compiler that can deliver that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 23:49:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 23:49:35 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.c3e9620e08a72b7990c03bed7996be3f@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): according to this the new version built on every system, and has the file {{{ /opt/local/lib/libx265.dylib }}} so must be something else TBD. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 14 23:50:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 14 Dec 2022 23:50:41 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.6d41772d10297a3897f47f7d4ad00983@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by tehcog): Replying to [comment:10 janngobble]: > > One more thing: @tehcog's build doesn't have "highdepth" - which is the only place my change applies. > ????this is the version of x265 that I had installed prior to the upgrade: {{{ The following ports are currently installed: x265 @3.4_0+highdepth (active) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:01:43 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:01:43 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.b069ad817d06c7eeab94c3ca53ff5c92@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by janngobble): Replying to [comment:13 tehcog]: > Replying to [comment:10 janngobble]: > > > > One more thing: @tehcog's build doesn't have "highdepth" - which is the only place my change applies. > > > > ????this is the version of x265 that I had installed prior to the upgrade: > > {{{ > The following ports are currently installed: > x265 @3.4_0+highdepth (active) > }}} understood. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:06:41 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:06:41 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.ad7f8806b38d34f1213054e51523007e@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by tehcog): Replying to [comment:12 kencu]: > according to this the new version built on every system, and has the file > > {{{ > /opt/local/lib/libx265.dylib > }}} > > so must be something else TBD. this is what I have for the dylib: {{{ xxxx::xxXXXxx { /opt/local/lib }-> lal | rg4 x265 2178:.rwxr-xr-x 18M root admin 7 Feb 2021 libx265.192.dylib 2179:.rw-r--r-- 20M root admin 7 Feb 2021 libx265.a 2180:lrwxr-xr-x 17 root admin 7 Feb 2021 libx265.dylib -> libx265.192.dylib }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:23:24 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:23:24 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.b6bd43a876e408116dc3ba2135ceb0f4@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): {{{ffmpeg +gpl2+jack+nonfree+x11}}} configures just fine for me on Ventura Intel with the new libx265 installed. Building it now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:24:04 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:24:04 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.cb0691e0f03ee867017107a7628aba1e@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): maybe someone with a system that won't configure it can post up their config.log so I can take a look. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:25:18 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:25:18 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.04057a603c1f37ba2a9b7e9b0a859480@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by janngobble): Replying to [comment:17 kencu]: > maybe someone with a system that won't configure it can post up their config.log so I can take a look. @tehcog? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:33:11 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:33:11 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.c825d93790dbcc8cf27b6d3fd3713f6c@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): built no problem: {{{ % port -v installed x265 | grep active x265 @3.4_1 (active) requested_variants='' platform='darwin 22' archs='x86_64' date='2022-12-14T15:55:03-0800' % port -v installed ffmpeg The following ports are currently installed: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 (active) requested_variants='+gpl2+jack+nonfree+x11' platform='darwin 22' archs='x86_64' date='2022-12-14T16:27:45-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:33:33 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:33:33 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA (was: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade) In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.294626db63965a660a6ea383458f524f@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:38:47 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:38:47 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.c145c86b71c1d36750d2d92825ec316f@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by mouse07410): First, on my machine (MacOS 12.6.2 with Xcode-14.2) it does **not** create {{{libx265.dylib}}}: {{{ $ sudo port install x265 +highdepth ---> Computing dependencies for x265 ---> Fetching archive for x265 ---> Attempting to fetch x265-3.4_1+highdepth.darwin_21.x86_64.tbz2 from https://packages.macports.org/x265 ---> Attempting to fetch x265-3.4_1+highdepth.darwin_21.x86_64.tbz2 from https://nue.de.packages.macports.org/x265 ---> Attempting to fetch x265-3.4_1+highdepth.darwin_21.x86_64.tbz2 from http://atl.us.packages.macports.org/x265 ---> Fetching distfiles for x265 ---> Verifying checksums for x265 ---> Extracting x265 ---> Applying patches to x265 ---> Configuring x265 ---> Building x265 ---> Staging x265 into destroot ---> Installing x265 @3.4_1+highdepth ---> Activating x265 @3.4_1+highdepth ---> Cleaning x265 ---> Scanning binaries for linking errors ---> Found 7 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: ffmpeg @4.4.2+gpl2+gpl3+libdc1394+librtmp+nonfree Continue? [Y/n]: ---> Computing dependencies for ffmpeg ---> Cleaning ffmpeg ---> Scanning binaries for linking errors ---> Found 7 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order ---> Rebuilding in order ffmpeg @4.4.2_3+gpl2+gpl3+libdc1394+librtmp+nonfree ---> Computing dependencies for ffmpeg ---> Fetching distfiles for ffmpeg ---> Verifying checksums for ffmpeg ---> Extracting ffmpeg ---> Applying patches to ffmpeg ---> Configuring ffmpeg Error: Failed to configure ffmpeg: configure failure: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log for details. Error: rev-upgrade failed: Error rebuilding ffmpeg Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. $ ll /opt/local/lib/libx265.dylib ls: /opt/local/lib/libx265.dylib: No such file or directory $ fd libx265.dylib /opt/local/lib $ fd libx265.dylib /opt/local $ fd libx265. /opt/local /opt/local/lib/libx265.a /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-4.4.2/libavcodec/libx265.c $ port contents x265 Port x265 contains: /opt/local/bin/x265 /opt/local/include/hdr10plus.h /opt/local/include/x265.h /opt/local/include/x265_config.h /opt/local/lib/libhdr10plus.a /opt/local/lib/libx265.a /opt/local/lib/pkgconfig/x265.pc $ }}} Second, the complaint seems to be about inability to locate x265 **using pkg-config**? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:48:06 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:48:06 -0000 Subject: [MacPorts] #66141: py310-awscrt @0.14.0_0: build fatal warning: -undefined dynamic_lookup may not work with chained fixups In-Reply-To: <046.f5c2a5747aec2f67f6907ffb02bee3f3@macports.org> References: <046.f5c2a5747aec2f67f6907ffb02bee3f3@macports.org> Message-ID: <061.5b7d6343d3541fd4840341c00d33b219@macports.org> #66141: py310-awscrt @0.14.0_0: build fatal warning: -undefined dynamic_lookup may not work with chained fixups ------------------------+--------------------- Reporter: ianthrive | Owner: dgilman Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: py-awscrt | ------------------------+--------------------- Changes (by dgilman): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"55ed0210930aaaf0dfc98fd7b85c065928d64b87/macports-ports" 55ed0210930aaaf0dfc98fd7b85c065928d64b87/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="55ed0210930aaaf0dfc98fd7b85c065928d64b87" py-awscrt: update to 0.16.1 Closes: https://trac.macports.org/ticket/66141 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:49:38 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:49:38 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.aa78c2218c2a09d699661406385ef0c1@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): OK, I see I don't have the "highdepth" option set on x265. Let me try that, perhaps that will bring out the error. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:50:55 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:50:55 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.e36573174acca73815dbca77b5ce26cd@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by tehcog): Replying to [comment:18 janngobble]: > Replying to [comment:17 kencu]: > > maybe someone with a system that won't configure it can post up their config.log so I can take a look. > > @tehcog? Here you go ... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 00:51:34 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 00:51:34 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.b989d661738bafb2e4a55287a6bded29@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Changes (by tehcog): * Attachment "ffmpeg_config.log" added. config.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 01:09:05 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 01:09:05 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.74227897fd2cf21e04cf906a88e897fe@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"0eff7719b2539fef4798a1a63d213254ed9d7668/macports-ports" 0eff7719b2539fef4798a1a63d213254ed9d7668/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0eff7719b2539fef4798a1a63d213254ed9d7668" x265: revert ENABLE_HDR10_PLUS completely broke the build of x265 closes: https://trac.macports.org/ticket/66465 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 01:10:15 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 01:10:15 -0000 Subject: [MacPorts] #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA In-Reply-To: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> References: <043.7a62ab0d938d58d333e3dfa159daaccd@macports.org> Message-ID: <058.f0bd9a6859167931750d9aeeffadd87e@macports.org> #66465: ffmpeg @4.4.2_3+gpl2+jack+nonfree+x11 fails to configure after x265 3.4_0 < 3.4_1 upgrade on some systems TBA --------------------------+-------------------- Reporter: tehcog | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ffmpeg x265 | --------------------------+-------------------- Comment (by kencu): Reverted this until somebody can figure out how to enable ENABLE_HDR10_PLUS without breaking x265. Apologies for committing this in the first place -- I thought it was OK but I was wrong. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 03:30:11 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 03:30:11 -0000 Subject: [MacPorts] #65742: Gnuradio gui stuck In-Reply-To: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> References: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> Message-ID: <063.eae4609b23c19ae6fbc91aa85a00fce6@macports.org> #65742: Gnuradio gui stuck --------------------------+----------------------- Reporter: adamgao1996 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: qtgui Port: gnuradio | --------------------------+----------------------- Comment (by J-in-MN): @ra1nb0w Unfortunately I can't get this to work. `port -d sync` fails with DEBUG: /usr/bin/git pull --rebase --autostash DEBUG: system -W /Users//Downloads/macports-ports: /usr/bin/git pull --rebase --autostash There is no tracking information for the current branch. Please specify which branch you want to rebase against. See git-pull(1) for details. git pull If you wish to set tracking information for this branch you can do so with: git branch --set-upstream-to=origin/ gnuradio-3.10 Command failed: /usr/bin/git pull --rebase --autostash Exit code: 1 Trying `git branch -u gnuradio-3.10` gives warning: not setting branch 'gnuradio-3.10' as its own upstream -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 05:55:55 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 05:55:55 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.1e8f39024ccb0dbb1a4f1406a6adae84@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Changes (by chrisd-mso): * Attachment "bsdmake.diff" added. diff file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 07:52:03 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 07:52:03 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.ea4b933d7d28d0e6b2fe43221d80cff3@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): At night it built with `Portfile` from Saturday. Now another `selfupdate` is running and I'll run an `upgrade`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 08:15:46 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 08:15:46 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.2ae188ff46fb2e5f8a165b74508d1ad4@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): It also worked to `upgrade`. This is on PPC Mac OS X 10.5.8, Leopard. I'll boot into PPC Tiger, Mac OS X 10.4.11, after backup with TimeMachine. Then I'll `upgrade` old Tiger ports of which `libdeflate` will be one? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 09:59:18 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 09:59:18 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.24ab2d43f131d74a8546edf59811488e@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by artkiver): Since there was some Rust related chatter on the macports-dev list, I mentioned this ticket there as well. Sergey Fedorov replied as follows: "FFMpeg can certainly be compiled without Rust, including the latest (upstream) version. Perhaps a component that is pulling in Rust should rather be made an optional variant for all systems ? it is hardly justified to have it as the default, IMHO." So, Sergey and I seem to be of a similar mindset. To be honest, I am not entirely sure why there are three separate FFmpeg ports especially since two of them are both an older version? I suppose a ffmpeg-minimal is another possibility, but creating a 4th Portfile, when it seems as if it might be better to clean up the existing 3 separate, yet very closely related, ports might make more sense? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 10:33:08 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 10:33:08 -0000 Subject: [MacPorts] #66474: pango @1.50.7 has a problem with gi-docgen and Python on PPC Leopard, Mac OS X 10.5.8 Message-ID: <046.64c1245decf2e0a7506869f60c01adf2@macports.org> #66474: pango @1.50.7 has a problem with gi-docgen and Python on PPC Leopard, Mac OS X 10.5.8 -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard ppc | Port: pango -------------------------+-------------------- {{{ Dependency sysprof-capture-4 skipped: feature sysprof disabled Run-time dependency gi-docgen found: NO (tried pkgconfig, framework and cmake) Looking for a fallback subproject for the dependency gi-docgen Executing subproject gi-docgen gi-docgen| Project name: gi-docgen gi-docgen| Project version: 2022.2 gi-docgen| subprojects/gi-docgen/meson.build:10:0: Exception: ['/usr/bin/python']> is not a valid python or it is missing distutils Subproject subprojects/gi-docgen is buildable: NO (disabling) Dependency gi-docgen from subproject gi-docgen found: NO (subproject failed to configure) Configuring config.h using configuration }}} An up-to-date version of `gi-docgen` is installed: `gi-docgen @2022.2_0 (active) requested_variants='' platform='darwin 9' archs='noarch' date='2022-12-02T18:25:18+0100'`. Why does it fail to detect that? And why is ancient Apple `Python 2.5.1` used to try building `gi-docgen`? Nevertheless `pango` built and was installed: `pango @1.50.7_0+quartz+x11 (active) requested_variants='' platform='darwin 9' archs='ppc' date='2022-12-15T11:25:49+0100'`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:15:03 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 11:15:03 -0000 Subject: [MacPorts] #66457: libmpc Header mpc.h fails to include stdio.h required for FILE In-Reply-To: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> References: <044.03013d004a8a8c2209a93b3bf1fb504b@macports.org> Message-ID: <059.4964d7c821a273a0005969d837d82cfa@macports.org> #66457: libmpc Header mpc.h fails to include stdio.h required for FILE ------------------------------+------------------------------ Reporter: ragnese | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: ventura monterey Port: libgcc12 libmpc | ------------------------------+------------------------------ Comment (by cjones051073): Just to note upstream have indeed already released 1.3.1 that addresses this https://www.multiprecision.org/mpc/ For whatever reason though the source for version 1.3.1 is not yet available to the GNU sites the port file fetches it from, so we cannot update to this version quite yet. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:35:44 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 11:35:44 -0000 Subject: [MacPorts] #66226: clang-15: Too many clang dependencies In-Reply-To: <047.8de9602d10658845dfc940e3e87e69b7@macports.org> References: <047.8de9602d10658845dfc940e3e87e69b7@macports.org> Message-ID: <062.2e003278768fccf55162fe0bf8e0be24@macports.org> #66226: clang-15: Too many clang dependencies -------------------------+-------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: clang-15 | -------------------------+-------------------- Comment (by cjones051073): I am afraid but this bootstrapping is inevitable. clang 15 cannot be built with clang 11, its too old, which is why clang 13 is used. clang 13 in turn needs clang 11 to be built. I see no obvious way out of this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 11:39:11 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 11:39:11 -0000 Subject: [MacPorts] #66226: clang-15: Too many clang dependencies In-Reply-To: <047.8de9602d10658845dfc940e3e87e69b7@macports.org> References: <047.8de9602d10658845dfc940e3e87e69b7@macports.org> Message-ID: <062.ae23ed190317003cb1a9de3f90be102e@macports.org> #66226: clang-15: Too many clang dependencies -------------------------+-------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: clang-15 | -------------------------+-------------------- Comment (by cjones051073): Just to add, the depending on clang 13 from clang 15 (should be) a built dep only. So it is not correct that a user installing the clang 15 binary tarballs needs to install clang 13 as well. Only users building from source would need this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 13:55:00 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 13:55:00 -0000 Subject: [MacPorts] #63622: openssl3: buildbot failures related to AVX-512 instruction set In-Reply-To: <044.a7092f99993f8eda1044093ad97c8468@macports.org> References: <044.a7092f99993f8eda1044093ad97c8468@macports.org> Message-ID: <059.17c3e79c9afde5d230f44cd258f5d896@macports.org> #63622: openssl3: buildbot failures related to AVX-512 instruction set -----------------------+--------------------- Reporter: mascguy | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: avx Port: openssl3 | -----------------------+--------------------- Comment (by neverpanic): In [changeset:"c6b052fa65dfd079ebf3a4fc369488718f8547ad/macports-ports" c6b052fa65dfd079ebf3a4fc369488718f8547ad/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c6b052fa65dfd079ebf3a4fc369488718f8547ad" openssl3: Drop patch incorporated upstream This was fixed upstream in c95e2030c34646176b4843b5f0f48720d896f427 which is part of 3.0.6. See: https://trac.macports.org/ticket/63622 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 15:19:12 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 15:19:12 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.12d9523409ea463e7ee126147d9f1f99@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by kencu): the prebuilt intel version of ffmpeg for ventura is already on the packages server. The arm version will be soon coming. rust is now needed for a number of ports, and it?s use is increasing steadily. for context. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 15:26:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 15:26:13 -0000 Subject: [MacPorts] #66226: clang-15: Too many clang dependencies In-Reply-To: <047.8de9602d10658845dfc940e3e87e69b7@macports.org> References: <047.8de9602d10658845dfc940e3e87e69b7@macports.org> Message-ID: <062.495c07b26598e4b91c23684411bf4cb4@macports.org> #66226: clang-15: Too many clang dependencies -------------------------+-------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: clang-15 | -------------------------+-------------------- Comment (by kencu): clang11-bootstrap was supposed to be a partial solution to all these deps, building with minimal deps and then bootstrapping the new toolchain from a newer base. I don?t know if it can build clang-14? maybe? but should build clang-13 without trouble. I never got around to finishing the plan before Chris took over, though. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 15:45:20 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 15:45:20 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.5cdde4c6a77dadd2ce820a4dd4a62a3b@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by artkiver): Hi Ken, thank you for replying. I think we may be contending with a miscommunication? I am not interested in prebuilt versions and which architectures they are for, that is not the crux of the issue. Moreover, the CI build system still has Leopard G4/G5 systems in its tooling, so the fact that FFmpeg binaries are lacking for aarch64/Apple M1/M2 Silicon (which has now been out for over two years) while regrettable, seems as if it is also not relevant to what I wish to focus on in this ticket. If Rust is needed now, for a number of ports, that also: seems irrelevant. It is *NOT* necessary to build FFmpeg from source from the upstream project. So, that is not meaningful context. If people need Rust, they should be installing Rust, not FFmpeg. If people need FFmpeg and there is a variant which has Rust as a dependency, that variant, should NOT be a default. Does that make it clearer? I have already provided an example of a functioning Portfile for FFmpeg which does not require Rust. I will submit it as a PR for ffmpeg-devel if conversations continue this way, seeing how jeremyhu (whom I have already removed as a maintainer for libressl and libressl-devel) and the other port maintainers are not responding with anything meaningful nor pertinent. As it currently stands, there are 3 ffmpeg ports in the tree, when arguably at most there should be two (how is ffmpeg-devel different than ffmpeg-upstream for example?) and it is conceivable that even those could be reduced to one with proper use of variants. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 16:08:45 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 16:08:45 -0000 Subject: [MacPorts] #66475: Build coreutils with Legacy Support? Message-ID: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> #66475: Build coreutils with Legacy Support? ----------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: leopard, tiger | Port: coreutils ----------------------------+----------------------- I tried to build `coreutils with Legacy Support set active`. The software built. The `configure step` shows some differences (differences are either marked with a blank line or a bullet character ?): {{{ ---> Configuring coreutils (the traditional way) | ---> Configuring coreutils (with Legacy Support) DEBUG: Preferred compilers: gcc-4.2 llvm-gcc-4.2 apple-gcc-4.2 gcc-4.0 macports-gcc-7 macports-gcc-6 macports-gcc-5 macports-clang-7.0 macports- clang-6.0 macports-clang-5.0 macports-clang-3.7 macports-clang-3.4 DEBUG: Using compiler 'Xcode GCC 4.2' | DEBUG: Using compiler 'Xcode GCC 4.2' DEBUG: Executing org.macports.configure (coreutils) | DEBUG: Executing org.macports.configure (coreutils) DEBUG: Environment: | DEBUG: Environment: CC='/usr/bin/gcc-4.2' | CC='/usr/bin/gcc-4.2' CC_PRINT_OPTIONS='YES' | CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_coreutils/coreutils/work/.CC_PRINT_OPTIONS' CFLAGS='-pipe -Os -arch ppc' | CFLAGS='-pipe -Os -arch ppc' CPATH='/opt/local/include' | CPATH='/opt/local/include' | CPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport' ?CPPFLAGS='-I/opt/local/include' | CPPFLAGS='-isystem/opt/local/include/LegacySupport -I/opt/local/include' CXX='/usr/bin/g++-4.2' | CXX='/usr/bin/g++-4.2' CXXFLAGS='-pipe -Os -arch ppc' | CXXFLAGS='-pipe -Os -arch ppc' | C_INCLUDE_PATH='/opt/local/include/LegacySupport' DEVELOPER_DIR='/Developer' | DEVELOPER_DIR='/Developer' F90FLAGS='-pipe -Os -m32' | F90FLAGS='-pipe -Os -m32' FCFLAGS='-pipe -Os -m32' | FCFLAGS='-pipe -Os -m32' FFLAGS='-pipe -Os -m32' | FFLAGS='-pipe -Os -m32' FORCE_UNSAFE_CONFIGURE='1' | FORCE_UNSAFE_CONFIGURE='1' INSTALL='/usr/bin/install -c' | INSTALL='/usr/bin/install -c' ?LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc' | LDFLAGS='-Wl,-headerpad_max_install_names -L/opt/local/lib -lMacportsLegacySupport -arch ppc' LIBRARY_PATH='/opt/local/lib' | LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.5' | MACOSX_DEPLOYMENT_TARGET='10.5' | MACPORTS_LEGACY_SUPPORT_CPPFLAGS='-isystem/opt/local/include/LegacySupport' | MACPORTS_LEGACY_SUPPORT_ENABLED='1' | MACPORTS_LEGACY_SUPPORT_LDFLAGS='-L/opt/local/lib -lMacportsLegacySupport' OBJC='/usr/bin/gcc-4.2' | OBJC='/usr/bin/gcc-4.2' OBJCFLAGS='-pipe -Os -arch ppc' | OBJCFLAGS='-pipe -Os -arch ppc' | OBJCPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport' OBJCXX='/usr/bin/g++-4.2' | OBJCXX='/usr/bin/g++-4.2' OBJCXXFLAGS='-pipe -Os -arch ppc' | OBJCXXFLAGS='-pipe -Os -arch ppc' | OBJC_INCLUDE_PATH='/opt/local/include/LegacySupport' Executing: cd "..../coreutils/work/coreutils-9.1" && ./configure --prefix=/opt/local --disable-silent-rules --program-prefix=g --disable- year2038 DEBUG: system: cd "..../coreutils/work/coreutils-9.1" && ./configure --prefix=/opt/local --disable-silent-rules --program-prefix=g --disable- year2038 checking for a BSD-compatible install... /usr/bin/install -c | checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes | checking whether build environment is sane... yes checking for a race-free mkdir -p... /opt/local/bin/gmkdir -p | checking for a race-free mkdir -p... /opt/local/bin/gmkdir -p checking for gawk... gawk | checking for gawk... gawk checking whether make sets $(MAKE)... yes | checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes | checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes | checking whether make supports nested variables... (cached) yes checking for gcc... /usr/bin/gcc-4.2 | checking for gcc... /usr/bin/gcc-4.2 checking whether the C compiler works... yes | checking whether the C compiler works... yes checking for C compiler default output file name... a.out | checking for C compiler default output file name... a.out checking for suffix of executables... | checking for suffix of executables... checking whether we are cross compiling... no | checking whether we are cross compiling... no checking for suffix of object files... o | checking for suffix of object files... o checking whether the compiler supports GNU C... yes | checking whether the compiler supports GNU C... yes checking whether /usr/bin/gcc-4.2 accepts -g... yes | checking whether /usr/bin/gcc-4.2 accepts -g... yes checking for /usr/bin/gcc-4.2 option to enable C11 features... unsupported | checking for /usr/bin/gcc-4.2 option to enable C11 features... unsupported checking for /usr/bin/gcc-4.2 option to enable C99 features... -std=gnu99 | checking for /usr/bin/gcc-4.2 option to enable C99 features... -std=gnu99 checking whether /usr/bin/gcc-4.2 -std=gnu99 understands -c and -o together... yes | checking whether /usr/bin/gcc-4.2 -std=gnu99 understands -c and -o together... yes checking whether the compiler is clang... no | checking whether the compiler is clang... no checking for compiler option needed when checking for declarations... none | checking for compiler option needed when checking for declarations... none checking whether make supports the include directive... yes (GNU style) | checking whether make supports the include directive... yes (GNU style) checking dependency style of /usr/bin/gcc-4.2 -std=gnu99... gcc3 | checking dependency style of /usr/bin/gcc-4.2 -std=gnu99... gcc3 checking how to run the C preprocessor... /usr/bin/gcc-4.2 -std=gnu99 -E | checking how to run the C preprocessor... /usr/bin/gcc-4.2 -std=gnu99 -E checking for grep that handles long lines and -e... /opt/local/bin/ggrep | checking for grep that handles long lines and -e... /opt/local/bin/ggrep checking for egrep... /opt/local/bin/ggrep -E | checking for egrep... /opt/local/bin/ggrep -E checking whether /usr/bin/gcc-4.2 -std=gnu99 needs -traditional... no | checking whether /usr/bin/gcc-4.2 -std=gnu99 needs -traditional... no checking for ranlib... ranlib | checking for ranlib... ranlib checking whether ln -s works... yes | checking whether ln -s works... yes checking for stdio.h... yes | checking for stdio.h... yes checking for stdlib.h... yes | checking for stdlib.h... yes checking for string.h... yes | checking for string.h... yes checking for inttypes.h... yes | checking for inttypes.h... yes checking for stdint.h... yes | checking for stdint.h... yes checking for strings.h... yes | checking for strings.h... yes checking for sys/stat.h... yes | checking for sys/stat.h... yes checking for sys/types.h... yes | checking for sys/types.h... yes checking for unistd.h... yes | checking for unistd.h... yes checking for wchar.h... yes | checking for wchar.h... yes checking for minix/config.h... no | checking for minix/config.h... no checking for arpa/inet.h... yes | checking for arpa/inet.h... yes checking for features.h... no | checking for features.h... no checking for sys/socket.h... yes | checking for sys/socket.h... yes checking for xlocale.h... yes | checking for xlocale.h... yes checking for sys/param.h... yes | checking for sys/param.h... yes checking for dirent.h... yes | checking for dirent.h... yes checking for fnmatch.h... yes | checking for fnmatch.h... yes checking for stdio_ext.h... no | checking for stdio_ext.h... no checking for sys/vfs.h... no | checking for sys/vfs.h... no checking for sys/fs_types.h... no | checking for sys/fs_types.h... no checking for netdb.h... yes | checking for netdb.h... yes checking for netinet/in.h... yes | checking for netinet/in.h... yes checking for getopt.h... yes | checking for getopt.h... yes checking for sys/cdefs.h... yes | checking for sys/cdefs.h... yes checking for termios.h... yes | checking for termios.h... yes checking for sys/time.h... yes | checking for sys/time.h... yes checking for grp.h... yes | checking for grp.h... yes checking for threads.h... no | checking for threads.h... no checking for iconv.h... yes | checking for iconv.h... yes checking for limits.h... yes | checking for limits.h... yes checking for crtdefs.h... no | checking for crtdefs.h... no checking for wctype.h... yes | checking for wctype.h... yes checking for langinfo.h... yes | checking for langinfo.h... yes checking for math.h... yes | checking for math.h... yes checking for sys/mman.h... yes | checking for sys/mman.h... yes checking for sys/statvfs.h... yes | checking for sys/statvfs.h... yes checking for priv.h... no | checking for priv.h... no checking for sys/select.h... yes | checking for sys/select.h... yes checking for pthread.h... yes | checking for pthread.h... yes checking for utmp.h... yes | checking for utmp.h... yes checking for utmpx.h... yes | checking for utmpx.h... yes checking for malloc.h... no | checking for malloc.h... no checking for selinux/selinux.h... no | checking for selinux/selinux.h... no checking for sys/ioctl.h... yes | checking for sys/ioctl.h... yes checking for sys/random.h... yes | checking for sys/random.h... yes checking for sys/resource.h... yes | checking for sys/resource.h... yes checking for sys/uio.h... yes | checking for sys/uio.h... yes checking for sys/utsname.h... yes | checking for sys/utsname.h... yes checking for sys/wait.h... yes | checking for sys/wait.h... yes checking for utime.h... yes | checking for utime.h... yes checking for semaphore.h... yes | checking for semaphore.h... yes checking for hurd.h... no | checking for hurd.h... no checking for linux/falloc.h... no | checking for linux/falloc.h... no checking for linux/fs.h... no | checking for linux/fs.h... no checking for paths.h... yes | checking for paths.h... yes checking for stropts.h... no | checking for stropts.h... no checking for sys/mtio.h... yes | checking for sys/mtio.h... yes checking for sys/systeminfo.h... no | checking for sys/systeminfo.h... no checking for syslog.h... yes | checking for syslog.h... yes checking for pwd.h... yes | checking for pwd.h... yes checking for OS.h... no | checking for OS.h... no checking for vfork.h... no | checking for vfork.h... no checking whether it is safe to define __EXTENSIONS__... yes | checking whether it is safe to define __EXTENSIONS__... yes checking whether _XOPEN_SOURCE should be defined... no | checking whether _XOPEN_SOURCE should be defined... no checking build system type... powerpc-apple-darwin9.8.0 | checking build system type... powerpc-apple-darwin9.8.0 checking host system type... powerpc-apple-darwin9.8.0 | checking host system type... powerpc-apple-darwin9.8.0 checking for Minix Amsterdam compiler... no | checking for Minix Amsterdam compiler... no checking for ar... ar | checking for ar... ar checking for _LARGEFILE_SOURCE value needed for large files... no | checking for _LARGEFILE_SOURCE value needed for large files... no checking for special C compiler options needed for large files... no | checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no | checking for _FILE_OFFSET_BITS value needed for large files... no configure: autobuild project... GNU coreutils | configure: autobuild project... GNU coreutils configure: autobuild revision... 9.1 | configure: autobuild revision... 9.1 configure: autobuild hostname... Leopard | configure: autobuild hostname... Leopard configure: autobuild timestamp... 20221215T104619Z | configure: autobuild timestamp... 20221215T125618Z checking for fchmod... yes | checking for fchmod... yes ?checking for posix_memalign... no | checking for posix_memalign... yes checking for pathconf... yes | checking for pathconf... yes checking for btowc... yes | checking for btowc... yes checking for uselocale... yes | checking for uselocale... yes checking for canonicalize_file_name... no | checking for canonicalize_file_name... no ?checking for faccessat... no | checking for faccessat... yes checking for realpath... yes | checking for realpath... yes checking for lstat... yes | checking for lstat... yes ?checking for readlinkat... no | checking for readlinkat... yes checking for chown... yes | checking for chown... yes checking for fchown... yes | checking for fchown... yes checking for _set_invalid_parameter_handler... no | checking for _set_invalid_parameter_handler... no checking for fchdir... yes | checking for fchdir... yes ?checking for fdopendir... no | checking for fdopendir... yes checking for explicit_bzero... no | checking for explicit_bzero... no checking for memset_s... no | checking for memset_s... no checking for posix_fadvise... no | checking for posix_fadvise... no ?checking for fchmodat... no | checking for fchmodat... yes checking for lchmod... yes | checking for lchmod... yes checking for fcntl... yes | checking for fcntl... yes checking for symlink... yes | checking for symlink... yes checking for mempcpy... no | checking for mempcpy... no checking for fnmatch... yes | checking for fnmatch... yes checking for mbsrtowcs... yes | checking for mbsrtowcs... yes checking for fpurge... yes | checking for fpurge... yes checking for __fpurge... no | checking for __fpurge... no checking for __freadahead... no | checking for __freadahead... no checking for __freading... no | checking for __freading... no checking for __freadptr... no | checking for __freadptr... no checking for __freadptrinc... no | checking for __freadptrinc... no checking for __fseterr... no | checking for __fseterr... no ?checking for fstatat... no | checking for fstatat... yes checking for fsync... yes | checking for fsync... yes checking for strtof... yes | checking for strtof... yes checking for ftruncate... yes | checking for ftruncate... yes ?checking for openat... no | checking for openat... yes checking for fstatfs... yes | checking for fstatfs... yes ?checking for futimens... no | checking for futimens... yes ?checking for getdelim... no | checking for getdelim... yes checking for getdtablesize... yes | checking for getdtablesize... yes checking for microuptime... no | checking for microuptime... no checking for nanouptime... no | checking for nanouptime... no checking for getlogin... yes | checking for getlogin... yes checking for flockfile... yes | checking for flockfile... yes checking for funlockfile... yes | checking for funlockfile... yes checking for getpass... yes | checking for getpass... yes checking for __fsetlocking... no | checking for __fsetlocking... no checking for getprogname... yes | checking for getprogname... yes checking for getexecname... no | checking for getexecname... no checking for getrandom... no | checking for getrandom... no ?checking for timespec_get... no | checking for timespec_get... yes checking for timespec_getres... no | checking for timespec_getres... no checking for gettimeofday... yes | checking for gettimeofday... yes checking for getusershell... yes | checking for getusershell... yes checking for isblank... yes | checking for isblank... yes checking for iswcntrl... yes | checking for iswcntrl... yes checking for iswblank... yes | checking for iswblank... yes checking for link... yes | checking for link... yes checking for readlink... yes | checking for readlink... yes ?checking for linkat... no | checking for linkat... yes checking for mbsinit... yes | checking for mbsinit... yes checking for mbrtowc... yes | checking for mbrtowc... yes checking for mbrlen... yes | checking for mbrlen... yes checking for mbslen... no | checking for mbslen... no checking for isascii... yes | checking for isascii... yes checking for mprotect... yes | checking for mprotect... yes checking for getgrouplist... yes | checking for getgrouplist... yes ?checking for mkdirat... no | checking for mkdirat... yes checking for mkfifoat... no | checking for mkfifoat... no checking for mknodat... no | checking for mknodat... no checking for mknod... yes | checking for mknod... yes checking for mkostemp... no | checking for mkostemp... no checking for mkstemp... yes | checking for mkstemp... yes checking for nl_langinfo... yes | checking for nl_langinfo... yes checking for pipe... yes | checking for pipe... yes checking for pipe2... no | checking for pipe2... no checking for pselect... yes | checking for pselect... yes checking for pthread_sigmask... yes | checking for pthread_sigmask... yes checking for utmpname... no | checking for utmpname... no checking for utmpxname... yes | checking for utmpxname... yes checking for iswctype... yes | checking for iswctype... yes ?checking for renameat... no | checking for renameat... yes checking for renameat2... no | checking for renameat2... no checking for fpathconf... yes | checking for fpathconf... yes checking for setenv... yes | checking for setenv... yes checking for settimeofday... yes | checking for settimeofday... yes checking for stime... no | checking for stime... no checking for sigaction... yes | checking for sigaction... yes checking for sigaltstack... yes | checking for sigaltstack... yes checking for siginterrupt... yes | checking for siginterrupt... yes checking for snprintf... yes | checking for snprintf... yes checking for stpncpy... no | checking for stpncpy... no checking for strerror_r... yes | checking for strerror_r... yes checking for __xpg_strerror_r... no | checking for __xpg_strerror_r... no checking for strtoimax... yes | checking for strtoimax... yes checking for strtold... yes | checking for strtold... yes checking for strtoumax... yes | checking for strtoumax... yes ?checking for symlinkat... no | checking for symlinkat... yes checking for localtime_r... yes | checking for localtime_r... yes checking for timegm... yes | checking for timegm... yes ?checking for unlinkat... no | checking for unlinkat... yes checking for futimes... yes | checking for futimes... yes checking for futimesat... no | checking for futimesat... no ?checking for utimensat... no | checking for utimensat... yes checking for lutimes... yes | checking for lutimes... yes checking for vasnprintf... no | checking for vasnprintf... no checking for wcrtomb... yes | checking for wcrtomb... yes checking for wcwidth... yes | checking for wcwidth... yes checking for wcswidth... yes | checking for wcswidth... yes checking for wmempcpy... no | checking for wmempcpy... no checking for pause... yes | checking for pause... yes checking for getegid... yes | checking for getegid... yes checking for getrusage... yes | checking for getrusage... yes checking for duplocale... yes | checking for duplocale... yes checking for newlocale... yes | checking for newlocale... yes checking for freelocale... yes | checking for freelocale... yes checking for secure_getenv... no | checking for secure_getenv... no checking for getuid... yes | checking for getuid... yes checking for geteuid... yes | checking for geteuid... yes checking for getgid... yes | checking for getgid... yes checking for sleep... yes | checking for sleep... yes checking for catgets... yes | checking for catgets... yes checking for shutdown... yes | checking for shutdown... yes checking for usleep... yes | checking for usleep... yes checking for mquery... no | checking for mquery... no checking for pstat_getprocvm... no | checking for pstat_getprocvm... no checking for wctob... yes | checking for wctob... yes checking for directio... no | checking for directio... no checking for setitimer... yes | checking for setitimer... yes checking for setrlimit... yes | checking for setrlimit... yes checking for prctl... no | checking for prctl... no checking for endgrent... yes | checking for endgrent... yes checking for endpwent... yes | checking for endpwent... yes checking for fallocate... no | checking for fallocate... no checking for iswspace... yes | checking for iswspace... yes checking for mkfifo... yes | checking for mkfifo... yes checking for setgroups... yes | checking for setgroups... yes checking for sethostname... yes | checking for sethostname... yes checking for sync... yes | checking for sync... yes checking for syncfs... no | checking for syncfs... no checking for sysctl... yes | checking for sysctl... yes checking for sysinfo... no | checking for sysinfo... no checking for tcgetpgrp... yes | checking for tcgetpgrp... yes checking for getgrgid_nomembers... no | checking for getgrgid_nomembers... no checking for getgrnam_nomembers... no | checking for getgrnam_nomembers... no checking for getgrent_nomembers... no | checking for getgrent_nomembers... no checking for fork... yes | checking for fork... yes checking for vfork... yes | checking for vfork... yes checking for size_t... yes | checking for size_t... yes checking for working alloca.h... yes | checking for working alloca.h... yes checking for alloca... yes | checking for alloca... yes checking whether the preprocessor supports include_next... yes | checking whether the preprocessor supports include_next... yes checking whether source code line length is unlimited... yes | checking whether source code line length is unlimited... yes checking for d_ino member in directory struct... yes | checking for d_ino member in directory struct... yes checking for long file names... yes | checking for long file names... yes checking for C/C++ restrict keyword... no | checking for C/C++ restrict keyword... no checking whether uses 'inline' correctly... yes | checking whether uses 'inline' correctly... yes checking for nl_langinfo and CODESET... yes | checking for nl_langinfo and CODESET... yes checking for a traditional french locale... fr_FR.ISO8859-1 | checking for a traditional french locale... fr_FR.ISO8859-1 checking whether uselocale works... yes | checking whether uselocale works... yes checking whether malloc is ptrdiff_t safe... no | checking whether malloc is ptrdiff_t safe... no checking whether malloc, realloc, calloc set errno on failure... yes | checking whether malloc, realloc, calloc set errno on failure... yes checking whether lstat correctly handles trailing slash... no | checking whether lstat correctly handles trailing slash... no checking whether // is distinct from /... no | checking whether // is distinct from /... no checking whether realpath works... no | checking whether realpath works... no checking for uid_t in sys/types.h... yes | checking for uid_t in sys/types.h... yes checking for unistd.h... (cached) yes | checking for unistd.h... (cached) yes checking for working chown... yes | checking for working chown... yes checking whether chown dereferences symlinks... yes | checking whether chown dereferences symlinks... yes checking whether chown honors trailing slash... no | checking whether chown honors trailing slash... no checking whether chown always updates ctime... yes | checking whether chown always updates ctime... yes checking whether is self-contained... yes | checking whether is self-contained... yes checking for shutdown... (cached) yes | checking for shutdown... (cached) yes checking whether defines the SHUT_* macros... yes | checking whether defines the SHUT_* macros... yes checking for struct sockaddr_storage... yes | checking for struct sockaddr_storage... yes checking for sa_family_t... yes | checking for sa_family_t... yes checking for struct sockaddr_storage.ss_family... yes | checking for struct sockaddr_storage.ss_family... yes checking for inline... inline | checking for inline... inline checking whether linux/if_alg.h has struct sockaddr_alg.... no | checking whether linux/if_alg.h has struct sockaddr_alg.... no checking whether byte ordering is bigendian... yes | checking whether byte ordering is bigendian... yes checking for /usr/bin/gcc-4.2 -std=gnu99 options needed to detect all undeclared functions... none needed | checking for /usr/bin/gcc-4.2 -std=gnu99 options needed to detect all undeclared functions... none needed checking if environ is properly declared... no | checking if environ is properly declared... no checking for complete errno.h... no | checking for complete errno.h... no checking for EMULTIHOP value... yes | checking for EMULTIHOP value... yes checking for ENOLINK value... yes | checking for ENOLINK value... yes checking for EOVERFLOW value... yes | checking for EOVERFLOW value... yes checking whether strerror_r is declared... yes | checking whether strerror_r is declared... yes checking whether strerror_r returns char *... no | checking whether strerror_r returns char *... no checking type of array argument to getgroups... gid_t | checking type of array argument to getgroups... gid_t checking whether ctype.h defines __header_inline... no | checking whether ctype.h defines __header_inline... no checking whether fchdir is declared... yes | checking whether fchdir is declared... yes checking for working fcntl.h... no (bad O_NOATIME) | checking for working fcntl.h... no (bad O_NOATIME) checking for pid_t... yes | checking for pid_t... yes checking for mode_t... yes | checking for mode_t... yes checking for promoted mode_t type... int | checking for promoted mode_t type... int checking whether fdatasync is declared... no | checking whether fdatasync is declared... no checking whether strmode is declared... yes | checking whether strmode is declared... yes checking for mbstate_t... yes | checking for mbstate_t... yes checking whether frexp() can be used without linking with libm... yes | checking whether frexp() can be used without linking with libm... yes checking whether alarm is declared... yes | checking whether alarm is declared... yes checking whether long double and double are the same... no | checking whether long double and double are the same... no checking whether stdin defaults to large file offsets... yes | checking whether stdin defaults to large file offsets... yes checking whether fseeko is declared... yes | checking whether fseeko is declared... yes checking for fseeko... yes | checking for fseeko... yes checking whether fflush works on input streams... no | checking whether fflush works on input streams... no checking whether stat file-mode macros are broken... no | checking whether stat file-mode macros are broken... no checking for nlink_t... yes | checking for nlink_t... yes checking whether ftello is declared... yes | checking whether ftello is declared... yes checking whether ungetc works on arbitrary bytes... yes | checking whether ungetc works on arbitrary bytes... yes checking for ftello... yes | checking for ftello... yes checking whether ftello works... yes | checking whether ftello works... yes ?checking for O_CLOEXEC... no | checking for O_CLOEXEC... yes checking for library containing gethostbyname... none required | checking for library containing gethostbyname... none required checking for gethostbyname... yes | checking for gethostbyname... yes checking for library containing getservbyname... none required | checking for library containing getservbyname... none required checking for getservbyname... yes | checking for getservbyname... yes checking for library containing inet_ntop... none required | checking for library containing inet_ntop... none required checking whether inet_ntop is declared... yes | checking whether inet_ntop is declared... yes checking for IPv4 sockets... yes | checking for IPv4 sockets... yes checking for IPv6 sockets... yes | checking for IPv6 sockets... yes checking whether getcwd (NULL, 0) allocates memory for result... yes | checking whether getcwd (NULL, 0) allocates memory for result... yes checking for getcwd with POSIX signature... yes | checking for getcwd with POSIX signature... yes checking whether getcwd is declared... yes | checking whether getcwd is declared... yes ?checking whether getdelim is declared... no | checking whether getdelim is declared... yes checking whether getdtablesize is declared... yes | checking whether getdtablesize is declared... yes checking for arithmetic hrtime_t... no | checking for arithmetic hrtime_t... no ?checking whether getline is declared... no | checking whether getline is declared... yes checking whether getlogin is declared... yes | checking whether getlogin is declared... yes checking for ssize_t... yes | checking for ssize_t... yes checking for getopt.h... (cached) yes | checking for getopt.h... (cached) yes checking for getopt_long_only... yes | checking for getopt_long_only... yes checking whether getopt is POSIX compatible... no | checking whether getopt is POSIX compatible... no checking whether fflush_unlocked is declared... no | checking whether fflush_unlocked is declared... no checking whether flockfile is declared... yes | checking whether flockfile is declared... yes checking whether fputs_unlocked is declared... no | checking whether fputs_unlocked is declared... no checking whether funlockfile is declared... yes | checking whether funlockfile is declared... yes checking whether putc_unlocked is declared... yes | checking whether putc_unlocked is declared... yes checking for struct timeval... yes | checking for struct timeval... yes checking for wide-enough struct timeval.tv_sec member... yes | checking for wide-enough struct timeval.tv_sec member... yes checking for pthread.h... (cached) yes | checking for pthread.h... (cached) yes checking for pthread_kill in -lpthread... yes | checking for pthread_kill in -lpthread... yes checking whether POSIX threads API is available... yes | checking whether POSIX threads API is available... yes checking whether setlocale (LC_ALL, NULL) is multithread-safe... no | checking whether setlocale (LC_ALL, NULL) is multithread-safe... no checking whether setlocale (category, NULL) is multithread-safe... yes | checking whether setlocale (category, NULL) is multithread-safe... yes checking whether imported symbols can be declared weak... no | checking whether imported symbols can be declared weak... no checking for ld used by /usr/bin/gcc-4.2 -std=gnu99... /.../gcc/-apple- darwin9/4.2.1/ld | checking for ld used by /usr/bin/gcc-4.2 -std=gnu99... /.../gcc/powerpc-apple-darwin9/4.2.1/ld checking if the linker (/usr/libexec/gcc/powerpc-apple-darwin9/4.2.1/ld) is GNU ld... no | checking if the linker (/usr/libexec/gcc/powerpc- apple-darwin9/4.2.1/ld) is GNU ld... no checking for shared library run path origin... done | checking for shared library run path origin... done checking 32-bit host C ABI... yes | checking 32-bit host C ABI... yes checking for ELF binary format... no | checking for ELF binary format... no checking for the common suffixes of directories in the library search path... lib,lib,lib | checking for the common suffixes of directories in the library search path... lib,lib,lib checking for iconv... yes | checking for iconv... yes checking for working iconv... yes | checking for working iconv... yes checking how to link with libiconv... -liconv | checking how to link with libiconv... -liconv checking whether iconv is compatible with its POSIX signature... yes | checking whether iconv is compatible with its POSIX signature... yes checking for off_t... yes | checking for off_t... yes checking whether limits.h has WORD_BIT, BOOL_WIDTH etc.... no | checking whether limits.h has WORD_BIT, BOOL_WIDTH etc.... no checking for wint_t... yes | checking for wint_t... yes checking whether wint_t is large enough... yes | checking whether wint_t is large enough... yes checking whether the compiler produces multi-arch binaries... no | checking whether the compiler produces multi-arch binaries... no checking whether stdint.h conforms to C99... no | checking whether stdint.h conforms to C99... no checking for sys/inttypes.h... no | checking for sys/inttypes.h... no checking for sys/bitypes.h... no | checking for sys/bitypes.h... no checking for bit size of ptrdiff_t... 32 | checking for bit size of ptrdiff_t... 32 checking for bit size of size_t... 32 | checking for bit size of size_t... 32 checking for bit size of sig_atomic_t... 32 | checking for bit size of sig_atomic_t... 32 checking for bit size of wchar_t... 32 | checking for bit size of wchar_t... 32 checking for bit size of wint_t... 32 | checking for bit size of wint_t... 32 checking whether sig_atomic_t is signed... yes | checking whether sig_atomic_t is signed... yes checking whether wchar_t is signed... yes | checking whether wchar_t is signed... yes checking whether wint_t is signed... yes | checking whether wint_t is signed... yes checking for ptrdiff_t integer literal suffix... | checking for ptrdiff_t integer literal suffix... checking for size_t integer literal suffix... ul | checking for size_t integer literal suffix... ul checking for sig_atomic_t integer literal suffix... | checking for sig_atomic_t integer literal suffix... checking for wchar_t integer literal suffix... | checking for wchar_t integer literal suffix... checking for wint_t integer literal suffix... | checking for wint_t integer literal suffix... checking whether INT32_MAX < INTMAX_MAX... yes | checking whether INT32_MAX < INTMAX_MAX... yes checking whether INT64_MAX == LONG_MAX... no | checking whether INT64_MAX == LONG_MAX... no checking whether UINT32_MAX < UINTMAX_MAX... yes | checking whether UINT32_MAX < UINTMAX_MAX... yes checking whether UINT64_MAX == ULONG_MAX... no | checking whether UINT64_MAX == ULONG_MAX... no checking where to find the exponent in a 'double'... word 0 bit 20 | checking where to find the exponent in a 'double'... word 0 bit 20 checking where to find the exponent in a 'float'... word 0 bit 23 | checking where to find the exponent in a 'float'... word 0 bit 23 checking whether iswcntrl works... yes | checking whether iswcntrl works... yes checking for towlower... yes | checking for towlower... yes checking for wctype_t... yes | checking for wctype_t... yes checking for wctrans_t... yes | checking for wctrans_t... yes checking for a traditional japanese locale... ja_JP.eucJP | checking for a traditional japanese locale... ja_JP.eucJP checking for a french Unicode locale... fr_FR.UTF-8 | checking for a french Unicode locale... fr_FR.UTF-8 checking for a transitional chinese locale... zh_CN.GB18030 | checking for a transitional chinese locale... zh_CN.GB18030 checking whether langinfo.h defines CODESET... yes | checking whether langinfo.h defines CODESET... yes checking whether langinfo.h defines T_FMT_AMPM... yes | checking whether langinfo.h defines T_FMT_AMPM... yes checking whether langinfo.h defines ALTMON_1... no | checking whether langinfo.h defines ALTMON_1... no checking whether langinfo.h defines ERA... yes | checking whether langinfo.h defines ERA... yes checking whether langinfo.h defines YESEXPR... yes | checking whether langinfo.h defines YESEXPR... yes checking for wchar_t... yes | checking for wchar_t... yes checking for good max_align_t... no | checking for good max_align_t... no checking whether NULL can be used in arbitrary expressions... yes | checking whether NULL can be used in arbitrary expressions... yes checking whether locale.h defines locale_t... no | checking whether locale.h defines locale_t... no checking whether locale.h conforms to POSIX:2001... yes | checking whether locale.h conforms to POSIX:2001... yes checking whether struct lconv is properly defined... yes | checking whether struct lconv is properly defined... yes checking whether imported symbols can be declared weak... (cached) no | checking whether imported symbols can be declared weak... (cached) no checking for multithread API to use... posix | checking for multithread API to use... posix checking for a sed that does not truncate output... /opt/local/bin/gsed | checking for a sed that does not truncate output... /opt/local/bin/gsed checking whether malloc (0) returns nonnull... yes | checking whether malloc (0) returns nonnull... yes checking whether NAN macro works... yes | checking whether NAN macro works... yes checking whether HUGE_VAL works... yes | checking whether HUGE_VAL works... yes checking whether mbrtowc handles incomplete characters... yes | checking whether mbrtowc handles incomplete characters... yes checking whether mbrtowc works as well as mbtowc... yes | checking whether mbrtowc works as well as mbtowc... yes checking whether mbrtowc handles a NULL pwc argument... yes | checking whether mbrtowc handles a NULL pwc argument... yes checking whether mbrtowc handles a NULL string argument... yes | checking whether mbrtowc handles a NULL string argument... yes checking whether mbrtowc has a correct return value... yes | checking whether mbrtowc has a correct return value... yes checking whether mbrtowc returns 0 when parsing a NUL character... yes | checking whether mbrtowc returns 0 when parsing a NUL character... yes checking whether mbrtowc stores incomplete characters... no | checking whether mbrtowc stores incomplete characters... no checking whether mbrtowc works on empty input... yes | checking whether mbrtowc works on empty input... yes checking whether the C locale is free of encoding errors... yes | checking whether the C locale is free of encoding errors... yes checking for mmap... yes | checking for mmap... yes checking for MAP_ANONYMOUS... yes | checking for MAP_ANONYMOUS... yes checking whether memchr works... yes | checking whether memchr works... yes checking whether memrchr is declared... no | checking whether memrchr is declared... no checking whether defines MIN and MAX... no | checking whether defines MIN and MAX... no checking whether defines MIN and MAX... yes | checking whether defines MIN and MAX... yes checking whether time_t is signed... yes | checking whether time_t is signed... yes checking for working mktime... yes | checking for working mktime... yes checking whether struct tm is in sys/time.h or time.h... time.h | checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_zone... yes | checking for struct tm.tm_zone... yes checking for struct tm.tm_gmtoff... yes | checking for struct tm.tm_gmtoff... yes checking for compound literals... yes | checking for compound literals... yes checking for external symbol _system_configuration... no | checking for external symbol _system_configuration... no checking for desired default level of POSIX conformance... none-specified | checking for desired default level of POSIX conformance... none- specified checking whether is self-contained... yes | checking whether is self-contained... yes checking for pthread_t... yes | checking for pthread_t... yes checking for pthread_spinlock_t... no | checking for pthread_spinlock_t... no checking for PTHREAD_CREATE_DETACHED... yes | checking for PTHREAD_CREATE_DETACHED... yes checking for PTHREAD_MUTEX_RECURSIVE... yes | checking for PTHREAD_MUTEX_RECURSIVE... yes checking for PTHREAD_MUTEX_ROBUST... no | checking for PTHREAD_MUTEX_ROBUST... no checking for PTHREAD_PROCESS_SHARED... yes | checking for PTHREAD_PROCESS_SHARED... yes checking for sigset_t... yes | checking for sigset_t... yes checking whether rmdir works... yes | checking whether rmdir works... yes checking whether unlink honors trailing slashes... no | checking whether unlink honors trailing slashes... no checking whether unlink of a parent directory fails as it should... no | checking whether unlink of a parent directory fails as it should... no checking for sched.h... yes | checking for sched.h... yes checking for struct sched_param... yes | checking for struct sched_param... yes checking for library containing setsockopt... none needed | checking for library containing setsockopt... none needed checking for library containing setfilecon... no | checking for library containing setfilecon... no checking whether setenv is declared... yes | checking whether setenv is declared... yes checking for search.h... yes | checking for search.h... yes checking for tsearch... yes | checking for tsearch... yes checking for volatile sig_atomic_t... yes | checking for volatile sig_atomic_t... yes checking for sighandler_t... no | checking for sighandler_t... no checking whether snprintf returns a byte count as in C99... yes | checking whether snprintf returns a byte count as in C99... yes checking whether snprintf is declared... yes | checking whether snprintf is declared... yes checking for stdbool.h that conforms to C99... yes | checking for stdbool.h that conforms to C99... yes checking for _Bool... yes | checking for _Bool... yes checking whether fcloseall is declared... no | checking whether fcloseall is declared... no checking which flavor of printf attribute matches inttypes macros... system | checking which flavor of printf attribute matches inttypes macros... system checking whether ecvt is declared... yes | checking whether ecvt is declared... yes checking whether fcvt is declared... yes | checking whether fcvt is declared... yes checking whether gcvt is declared... yes | checking whether gcvt is declared... yes checking whether stpncpy is declared... no | checking whether stpncpy is declared... no checking whether strdup is declared... yes | checking whether strdup is declared... yes checking whether strerror(0) succeeds... no | checking whether strerror(0) succeeds... no checking whether strncat works... yes | checking whether strncat works... yes ?checking whether strnlen is declared... no | checking whether strnlen is declared... yes checking whether strsignal is declared... yes | checking whether strsignal is declared... yes checking whether ldexp() can be used without linking with libm... yes | checking whether ldexp() can be used without linking with libm... yes checking whether strtoimax is declared... yes | checking whether strtoimax is declared... yes checking whether strtoumax is declared... yes | checking whether strtoumax is declared... yes checking whether declares ioctl... yes | checking whether declares ioctl... yes checking for struct utsname... yes | checking for struct utsname... yes checking for struct timespec in ... yes | checking for struct timespec in ... yes ?checking for TIME_UTC in ... no | checking for TIME_UTC in ... yes checking whether execvpe is declared... no | checking whether execvpe is declared... no checking whether clearerr_unlocked is declared... yes | checking whether clearerr_unlocked is declared... yes checking whether feof_unlocked is declared... yes | checking whether feof_unlocked is declared... yes checking whether ferror_unlocked is declared... yes | checking whether ferror_unlocked is declared... yes checking whether fgets_unlocked is declared... no | checking whether fgets_unlocked is declared... no checking whether fputc_unlocked is declared... no | checking whether fputc_unlocked is declared... no checking whether fread_unlocked is declared... no | checking whether fread_unlocked is declared... no checking whether fwrite_unlocked is declared... no | checking whether fwrite_unlocked is declared... no checking whether getc_unlocked is declared... yes | checking whether getc_unlocked is declared... yes checking whether getchar_unlocked is declared... yes | checking whether getchar_unlocked is declared... yes checking whether putchar_unlocked is declared... yes | checking whether putchar_unlocked is declared... yes checking whether unsetenv is declared... yes | checking whether unsetenv is declared... yes checking whether the utimes function works... yes | checking whether the utimes function works... yes checking for inttypes.h... yes | checking for inttypes.h... yes checking for stdint.h... yes | checking for stdint.h... yes checking for intmax_t... yes | checking for intmax_t... yes checking whether snprintf truncates the result as in C99... yes | checking whether snprintf truncates the result as in C99... yes checking for snprintf... (cached) yes | checking for snprintf... (cached) yes ?checking for strnlen... no | checking for strnlen... yes checking for wcslen... yes | checking for wcslen... yes ?checking for wcsnlen... no | checking for wcsnlen... yes checking for mbrtowc... (cached) yes | checking for mbrtowc... (cached) yes checking for wcrtomb... (cached) yes | checking for wcrtomb... (cached) yes checking whether _snprintf is declared... no | checking whether _snprintf is declared... no checking whether printf supports size specifiers as in C99... yes | checking whether printf supports size specifiers as in C99... yes checking whether printf supports 'long double' arguments... yes | checking whether printf supports 'long double' arguments... yes checking whether printf supports infinite 'double' arguments... yes | checking whether printf supports infinite 'double' arguments... yes checking whether printf supports infinite 'long double' arguments... yes | checking whether printf supports infinite 'long double' arguments... yes checking whether printf supports the 'a' and 'A' directives... no | checking whether printf supports the 'a' and 'A' directives... no checking whether printf supports the 'F' directive... yes | checking whether printf supports the 'F' directive... yes checking whether printf supports the 'n' directive... yes | checking whether printf supports the 'n' directive... yes checking whether printf supports the 'ls' directive... yes | checking whether printf supports the 'ls' directive... yes checking whether printf supports the grouping flag... yes | checking whether printf supports the grouping flag... yes checking whether printf supports the left-adjust flag correctly... yes | checking whether printf supports the left-adjust flag correctly... yes checking whether printf supports the zero flag correctly... no | checking whether printf supports the zero flag correctly... no checking whether printf supports large precisions... yes | checking whether printf supports large precisions... yes checking whether printf survives out-of-memory conditions... yes | checking whether printf survives out-of-memory conditions... yes ?checking whether wcsdup is declared... no | checking whether wcsdup is declared... yes checking whether wcwidth is declared... yes | checking whether wcwidth is declared... yes checking whether wcwidth works reasonably in UTF-8 locales... no | checking whether wcwidth works reasonably in UTF-8 locales... no checking POSIX termios... yes | checking POSIX termios... yes checking whether use of TIOCGWINSZ requires termios.h... yes | checking whether use of TIOCGWINSZ requires termios.h... yes checking for C compiler option to allow warnings... -Wno-error | checking for C compiler option to allow warnings... -Wno-error checking for C++ compiler option to allow warnings... -Wno-error | checking for C++ compiler option to allow warnings... -Wno-error checking for LC_MESSAGES... yes | checking for LC_MESSAGES... yes checking whether uselocale works... (cached) yes | checking whether uselocale works... (cached) yes checking for fake locale system (OpenBSD)... no | checking for fake locale system (OpenBSD)... no checking for Solaris 11.4 locale system... no | checking for Solaris 11.4 locale system... no checking for getlocalename_l... no | checking for getlocalename_l... no checking for CFPreferencesCopyAppValue... yes | checking for CFPreferencesCopyAppValue... yes checking for CFLocaleCopyPreferredLanguages... yes | checking for CFLocaleCopyPreferredLanguages... yes checking for library needed for semaphore functions... none | checking for library needed for semaphore functions... none checking for sys/acl.h... yes | checking for sys/acl.h... yes checking for library containing acl_get_file... none required | checking for library containing acl_get_file... none required checking for acl_get_file... yes | checking for acl_get_file... yes checking for acl_get_fd... yes | checking for acl_get_fd... yes checking for acl_set_file... yes | checking for acl_set_file... yes checking for acl_set_fd... yes | checking for acl_set_fd... yes checking for acl_free... yes | checking for acl_free... yes checking for acl_from_mode... no | checking for acl_from_mode... no checking for acl_from_text... yes | checking for acl_from_text... yes checking for acl_delete_def_file... yes | checking for acl_delete_def_file... yes checking for acl_extended_file... no | checking for acl_extended_file... no checking for acl_delete_fd_np... yes | checking for acl_delete_fd_np... yes checking for acl_delete_file_np... yes | checking for acl_delete_file_np... yes checking for acl_copy_ext_native... yes | checking for acl_copy_ext_native... yes checking for acl_create_entry_np... yes | checking for acl_create_entry_np... yes checking for acl_to_short_text... no | checking for acl_to_short_text... no checking for acl_free_text... no | checking for acl_free_text... no checking for working acl_get_file... yes | checking for working acl_get_file... yes checking for acl/libacl.h... no | checking for acl/libacl.h... no checking for acl_entries... no | checking for acl_entries... no checking for ACL_FIRST_ENTRY... yes | checking for ACL_FIRST_ENTRY... yes checking for ACL_TYPE_EXTENDED... yes | checking for ACL_TYPE_EXTENDED... yes checking for alloca as a compiler built-in... yes | checking for alloca as a compiler built-in... yes checking whether to enable assertions... yes | checking whether to enable assertions... yes checking whether btowc(0) is correct... yes | checking whether btowc(0) is correct... yes checking whether btowc(EOF) is correct... yes | checking whether btowc(EOF) is correct... yes checking for __builtin_expect... yes | checking for __builtin_expect... yes checking for byteswap.h... no | checking for byteswap.h... no checking for strtod_l... yes | checking for strtod_l... yes checking for strtold_l... yes | checking for strtold_l... yes checking whether this system supports file names of any length... no | checking whether this system supports file names of any length... no ?checking for library containing clock_gettime... no | checking for library containing clock_gettime... none required ?checking for clock_getres... no | checking for clock_getres... yes ?checking for clock_gettime... no | checking for clock_gettime... yes checking for clock_settime... no | checking for clock_settime... no checking for closedir... yes | checking for closedir... yes checking for copy_file_range... no | checking for copy_file_range... no checking whether openssl is GPL compatible... yes | checking whether openssl is GPL compatible... yes checking for MD5 in -lcrypto... yes | checking for MD5 in -lcrypto... yes checking for openssl/md5.h... yes | checking for openssl/md5.h... yes checking whether openssl is GPL compatible... (cached) yes | checking whether openssl is GPL compatible... (cached) yes checking for SHA1 in -lcrypto... yes | checking for SHA1 in -lcrypto... yes checking for openssl/sha.h... yes | checking for openssl/sha.h... yes checking whether openssl is GPL compatible... (cached) yes | checking whether openssl is GPL compatible... (cached) yes checking for SHA256 in -lcrypto... yes | checking for SHA256 in -lcrypto... yes checking for openssl/sha.h... (cached) yes | checking for openssl/sha.h... (cached) yes checking whether openssl is GPL compatible... (cached) yes | checking whether openssl is GPL compatible... (cached) yes checking for SHA512 in -lcrypto... yes | checking for SHA512 in -lcrypto... yes checking for openssl/sha.h... (cached) yes | checking for openssl/sha.h... (cached) yes checking for d_ino member in directory struct... (cached) yes | checking for d_ino member in directory struct... (cached) yes checking for d_type member in directory struct... yes | checking for d_type member in directory struct... yes checking for dirfd... no | checking for dirfd... no checking whether dirfd is declared... yes | checking whether dirfd is declared... yes checking whether dirfd is a macro... yes | checking whether dirfd is a macro... yes checking whether // is distinct from /... (cached) no | checking whether // is distinct from /... (cached) no checking whether dup works... yes | checking whether dup works... yes checking whether dup2 works... yes | checking whether dup2 works... yes checking for error_at_line... no | checking for error_at_line... no checking for euidaccess... no | checking for euidaccess... no checking for libgen.h... yes | checking for libgen.h... yes checking for getgroups... yes | checking for getgroups... yes checking for working getgroups... yes | checking for working getgroups... yes checking for library containing eaccess... no | checking for library containing eaccess... no checking for eaccess... no | checking for eaccess... no checking for explicit_memset... no | checking for explicit_memset... no checking for access... yes | checking for access... yes | checking whether fchmodat works... yes ?checking for fchownat... no | checking for fchownat... yes | checking whether fchownat works with AT_SYMLINK_NOFOLLOW... yes | checking whether fchownat works with an empty file name... yes checking whether fflush works on input streams... (cached) no | checking whether fflush works on input streams... (cached) no checking whether fcntl handles F_DUPFD correctly... yes | checking whether fcntl handles F_DUPFD correctly... yes checking whether fcntl understands F_DUPFD_CLOEXEC... no | checking whether fcntl understands F_DUPFD_CLOEXEC... no checking for fdatasync... no | checking for fdatasync... no checking whether fdopen sets errno... yes | checking whether fdopen sets errno... yes ?checking whether fdopendir is declared... no | checking whether fdopendir is declared... yes | checking whether fdopendir works... yes | checking whether fflush works on input streams... (cached) no checking whether fflush works on input streams... (cached) no | checking for getxattr with XATTR_NAME_POSIX_ACL macros... no checking for getxattr with XATTR_NAME_POSIX_ACL macros... no | checking for struct stat.st_blocks... yes checking for struct stat.st_blocks... yes | checking for flexible array member... yes checking for flexible array member... yes | checking whether conversion from 'int' to 'long double' works... yes checking whether conversion from 'int' to 'long double' works... yes | checking for working GNU fnmatch... no checking for working GNU fnmatch... no | checking whether fopen recognizes a trailing slash... yes checking whether fopen recognizes a trailing slash... yes | checking whether fopen supports the mode character 'x'... yes checking whether fopen supports the mode character 'x'... yes | checking whether fopen supports the mode character 'e'... no checking whether fopen supports the mode character 'e'... no | checking for __fpending... no checking for __fpending... no | checking whether fpurge is declared... yes checking whether fpurge is declared... yes | checking whether fpurge works... no checking whether fpurge works... no | checking whether free is known to preserve errno... no checking whether free is known to preserve errno... no | checking whether freopen works on closed fds... yes checking whether freopen works on closed fds... yes | checking whether frexp works... yes checking whether frexp works... yes | checking whether frexpl is declared... yes checking whether frexpl is declared... yes | checking whether frexpl() can be used without linking with libm... yes checking whether frexpl() can be used without linking with libm... yes | checking whether frexpl works... no checking whether frexpl works... no | checking for fseeko... (cached) yes checking for fseeko... (cached) yes | checking whether fflush works on input streams... (cached) no checking whether fflush works on input streams... (cached) no | checking for _fseeki64... no checking for _fseeki64... no | checking whether fstatat (..., 0) works... yes | checking for sys/mount.h... yes checking for sys/mount.h... yes | checking for statvfs function (SVR4)... no checking for statvfs function (SVR4)... no | checking for two-argument statfs with statfs.f_frsize member... no checking for two-argument statfs with statfs.f_frsize member... no | checking for 3-argument statfs function (DEC OSF/1)... no checking for 3-argument statfs function (DEC OSF/1)... no | checking for two-argument statfs with statfs.f_bsize member (AIX, 4.3BSD)... yes checking for two-argument statfs with statfs.f_bsize member (AIX, 4.3BSD)... yes | checking for sys/fs/s5param.h... no checking for sys/fs/s5param.h... no | checking for sys/statfs.h... no checking for sys/statfs.h... no | checking for statfs that truncates block counts... no checking for statfs that truncates block counts... no | checking for ftello... (cached) yes checking for ftello... (cached) yes | checking whether ftello works... (cached) yes checking whether ftello works... (cached) yes | checking for fts_open... yes checking for fts_open... yes | checking whether futimens works... no | checking for library containing getaddrinfo... none required checking for library containing getaddrinfo... none required | checking for getaddrinfo... yes checking for getaddrinfo... yes | checking whether gai_strerror is declared... yes checking whether gai_strerror is declared... yes | checking whether gai_strerrorA is declared... no checking whether gai_strerrorA is declared... no | checking for gai_strerror with POSIX signature... yes checking for gai_strerror with POSIX signature... yes | checking for struct sockaddr.sa_len... yes checking for struct sockaddr.sa_len... yes | checking whether getaddrinfo is declared... yes checking whether getaddrinfo is declared... yes | checking whether freeaddrinfo is declared... yes checking whether freeaddrinfo is declared... yes | checking whether getnameinfo is declared... yes checking whether getnameinfo is declared... yes | checking for struct addrinfo... yes checking for struct addrinfo... yes | checking whether getcwd handles long file names properly... yes checking whether getcwd handles long file names properly... yes | checking for getpagesize... yes checking for getpagesize... yes | checking whether getcwd succeeds when 4k < cwd_length < 16k... yes checking whether getcwd succeeds when 4k < cwd_length < 16k... yes | checking for working getdelim function... yes ?checking for flockfile... (cached) yes | ?checking for funlockfile... (cached) yes | ?checking whether getc_unlocked is declared... (cached) yes | checking whether getdtablesize works... yes | checking whether getdtablesize works... yes checking for getgroups... (cached) yes | checking for getgroups... (cached) yes checking for working getgroups... (cached) yes | checking for working getgroups... (cached) yes checking whether getgroups handles negative values... yes | checking whether getgroups handles negative values... yes checking for gethostname... yes | checking for gethostname... yes checking for HOST_NAME_MAX... 256 | checking for HOST_NAME_MAX... 256 checking whether gethrtime is declared... no | checking whether gethrtime is declared... no ?checking whether CLOCK_MONOTONIC or CLOCK_REALTIME is defined... no | checking whether CLOCK_MONOTONIC or CLOCK_REALTIME is defined... yes ?checking for getline... no | checking for getline... yes | checking for working getline function... yes checking for getloadavg... yes | checking for getloadavg... yes checking for sys/loadavg.h... no | checking for sys/loadavg.h... no checking whether getloadavg is declared... yes | checking whether getloadavg is declared... yes checking for getpagesize... (cached) yes | checking for getpagesize... (cached) yes checking whether getpagesize is declared... yes | checking whether getpagesize is declared... yes checking for getpass without length limitations... no | checking for getpass without length limitations... no checking whether __fsetlocking is declared... no | checking whether __fsetlocking is declared... no checking for tcgetattr... yes | checking for tcgetattr... yes checking for tcsetattr... yes | checking for tcsetattr... yes checking whether program_invocation_name is declared... no | checking whether program_invocation_name is declared... no checking whether program_invocation_short_name is declared... no | checking whether program_invocation_short_name is declared... no checking whether __argv is declared... no | checking whether __argv is declared... no checking whether __progname is defined in default libraries... yes | checking whether __progname is defined in default libraries... yes checking for gettimeofday with POSIX signature... yes | checking for gettimeofday with POSIX signature... yes checking whether getusershell is declared... yes | checking whether getusershell is declared... yes checking for group_member... no | checking for group_member... no checking host operating system... Darwin | checking host operating system... Darwin checking for library containing gethostbyname... (cached) none required | checking for library containing gethostbyname... (cached) none required checking for gethostbyname... (cached) yes | checking for gethostbyname... (cached) yes checking for library containing inet_ntop... (cached) none required | checking for library containing inet_ntop... (cached) none required checking whether inet_ntop is declared... (cached) yes | checking whether inet_ntop is declared... (cached) yes checking whether the compiler generally respects inline... yes | checking whether the compiler generally respects inline... yes checking for isapipe... no | checking for isapipe... no checking whether pipes are FIFOs (and for their link count)... yes (0) | checking whether pipes are FIFOs (and for their link count)... yes (0) checking whether isnan(double) can be used without linking with libm... yes | checking whether isnan(double) can be used without linking with libm... yes checking whether isnan(float) can be used without linking with libm... yes | checking whether isnan(float) can be used without linking with libm... yes checking whether isnan(float) works... yes | checking whether isnan(float) works... yes checking whether isnan(long double) can be used without linking with libm... yes | checking whether isnan(long double) can be used without linking with libm... yes checking whether isnanl works... yes | checking whether isnanl works... yes checking whether iswblank is declared... yes | checking whether iswblank is declared... yes checking whether iswdigit is ISO C compliant... yes | checking whether iswdigit is ISO C compliant... yes checking whether iswxdigit is ISO C compliant... yes | checking whether iswxdigit is ISO C compliant... yes checking for lchown... yes | checking for lchown... yes checking for C compiler flag to ignore unused libraries... none | checking for C compiler flag to ignore unused libraries... none checking whether the compiler supports the __inline keyword... yes | checking whether the compiler supports the __inline keyword... yes checking for gmp.h... yes | checking for gmp.h... yes checking for libgmp... yes | checking for libgmp... yes checking how to link with libgmp... -lgmp | checking how to link with libgmp... -lgmp checking whether link obeys POSIX... no | checking whether link obeys POSIX... no checking for __xpg4... no | checking for __xpg4... no checking whether link(2) dereferences a symlink... yes | checking whether link(2) dereferences a symlink... yes | checking whether linkat() can link symlinks... no | checking whether linkat handles trailing slash correctly... yes checking for pthread_rwlock_t... yes | checking for pthread_rwlock_t... yes checking whether pthread_rwlock_rdlock prefers a writer to a reader... yes | checking whether pthread_rwlock_rdlock prefers a writer to a reader... yes checking whether lseek detects pipes... yes | checking whether lseek detects pipes... yes checking whether mbrtowc handles incomplete characters... (cached) yes | checking whether mbrtowc handles incomplete characters... (cached) yes checking whether mbrtowc works as well as mbtowc... (cached) yes | checking whether mbrtowc works as well as mbtowc... (cached) yes checking whether mbrtowc handles a NULL pwc argument... (cached) yes | checking whether mbrtowc handles a NULL pwc argument... (cached) yes checking whether mbrtowc handles a NULL string argument... (cached) yes | checking whether mbrtowc handles a NULL string argument... (cached) yes checking whether mbrtowc has a correct return value... (cached) yes | checking whether mbrtowc has a correct return value... (cached) yes checking whether mbrtowc returns 0 when parsing a NUL character... (cached) yes | checking whether mbrtowc returns 0 when parsing a NUL character... (cached) yes checking whether mbrtowc stores incomplete characters... (cached) no | checking whether mbrtowc stores incomplete characters... (cached) no checking whether mbrtowc works on empty input... (cached) yes | checking whether mbrtowc works on empty input... (cached) yes checking whether the C locale is free of encoding errors... (cached) yes | checking whether the C locale is free of encoding errors... (cached) yes checking whether mbrtowc handles incomplete characters... (cached) yes | checking whether mbrtowc handles incomplete characters... (cached) yes checking whether mbrtowc works as well as mbtowc... (cached) yes | checking whether mbrtowc works as well as mbtowc... (cached) yes checking whether mbrtowc handles incomplete characters... (cached) yes | checking whether mbrtowc handles incomplete characters... (cached) yes checking whether mbrtowc works as well as mbtowc... (cached) yes | checking whether mbrtowc works as well as mbtowc... (cached) yes checking whether mbsrtowcs works... yes | checking whether mbsrtowcs works... yes checking whether mbswidth is declared in ... no | checking whether mbswidth is declared in ... no checking for mbstate_t... (cached) yes | checking for mbstate_t... (cached) yes checking for mbtowc... yes | checking for mbtowc... yes checking for mempcpy... (cached) no | checking for mempcpy... (cached) no checking for memrchr... no | checking for memrchr... no checking whether mkdir handles trailing slash... yes | checking whether mkdir handles trailing slash... yes checking whether mkdir handles trailing dot... yes | checking whether mkdir handles trailing dot... yes checking for mkfifo... yes | checking for mkfifo... yes checking whether mkfifo rejects trailing slashes... no | checking whether mkfifo rejects trailing slashes... no checking whether mknod can create fifo without root privileges... yes | checking whether mknod can create fifo without root privileges... yes checking for working mkstemp... yes | checking for working mkstemp... yes checking for __mktime_internal... no | checking for __mktime_internal... no checking for listmntent... no | checking for listmntent... no checking for sys/ucred.h... yes | checking for sys/ucred.h... yes checking for sys/mount.h... (cached) yes | checking for sys/mount.h... (cached) yes checking for mntent.h... no | checking for mntent.h... no checking for sys/fs_types.h... (cached) no | checking for sys/fs_types.h... (cached) no checking for struct fsstat.f_fstypename... no | checking for struct fsstat.f_fstypename... no checking for library containing getmntent... no | checking for library containing getmntent... no checking for getmntent... no | checking for getmntent... no checking for mntctl function and struct vmount... no | checking for mntctl function and struct vmount... no checking for getfsstat function... no | checking for getfsstat function... no checking for FIXME existence of three headers... no | checking for FIXME existence of three headers... no checking for getmntinfo function... yes | checking for getmntinfo function... yes checking whether getmntinfo returns statvfs structures... no | checking whether getmntinfo returns statvfs structures... no checking for sys/mntent.h... no | checking for sys/mntent.h... no checking for sys/mkdev.h... no | checking for sys/mkdev.h... no checking for sys/sysmacros.h... no | checking for sys/sysmacros.h... no checking for struct statfs.f_fstypename... yes | checking for struct statfs.f_fstypename... yes checking for library containing nanosleep... none required | checking for library containing nanosleep... none required checking for working nanosleep... yes | checking for working nanosleep... yes checking whether is self-contained... yes | checking whether is self-contained... yes checking whether YESEXPR works... yes | checking whether YESEXPR works... yes checking for sys/pstat.h... no | checking for sys/pstat.h... no checking for sys/sysmp.h... no | checking for sys/sysmp.h... no checking for sys/param.h... (cached) yes | checking for sys/param.h... (cached) yes checking for sys/sysctl.h... yes | checking for sys/sysctl.h... yes checking for sched_getaffinity... no | checking for sched_getaffinity... no checking for sched_getaffinity_np... no | checking for sched_getaffinity_np... no checking for pstat_getdynamic... no | checking for pstat_getdynamic... no checking for sysmp... no | checking for sysmp... no checking for sysctl... (cached) yes | checking for sysctl... (cached) yes checking for obstacks that work with any size object... no | checking for obstacks that work with any size object... no checking whether open recognizes a trailing slash... no | checking whether open recognizes a trailing slash... no checking for opendir... yes | checking for opendir... yes checking for bison... bison | checking for bison... bison checking for bison 2.4 or newer... 3.8.2, ok | checking for bison 2.4 or newer... 3.8.2, ok checking for struct tm.tm_zone... (cached) yes | checking for struct tm.tm_zone... (cached) yes checking for Perl 5.005 or newer... perl | checking for Perl 5.005 or newer... perl checking for sys/pstat.h... (cached) no | checking for sys/pstat.h... (cached) no checking for sys/sysmp.h... (cached) no | checking for sys/sysmp.h... (cached) no checking for sys/sysinfo.h... no | checking for sys/sysinfo.h... no checking for machine/hal_sysinfo.h... no | checking for machine/hal_sysinfo.h... no checking for sys/table.h... no | checking for sys/table.h... no checking for sys/param.h... (cached) yes | checking for sys/param.h... (cached) yes checking for sys/systemcfg.h... no | checking for sys/systemcfg.h... no checking for sys/sysctl.h... (cached) yes | checking for sys/sysctl.h... (cached) yes checking for pstat_getstatic... no | checking for pstat_getstatic... no checking for pstat_getdynamic... (cached) no | checking for pstat_getdynamic... (cached) no checking for sysmp... (cached) no | checking for sysmp... (cached) no checking for getsysinfo... no | checking for getsysinfo... no checking for sysctl... (cached) yes | checking for sysctl... (cached) yes checking for table... yes | checking for table... yes checking for sysinfo... (cached) no | checking for sysinfo... (cached) no checking for struct sysinfo.mem_unit... no | checking for struct sysinfo.mem_unit... no checking for a shell that conforms to POSIX... /bin/sh | checking for a shell that conforms to POSIX... /bin/sh | checking whether posix_memalign works for large alignments... yes checking whether frexp works... (cached) yes | checking whether frexp works... (cached) yes checking whether ldexp can be used without linking with libm... (cached) yes | checking whether ldexp can be used without linking with libm... (cached) yes checking whether frexpl() can be used without linking with libm... (cached) yes | checking whether frexpl() can be used without linking with libm... (cached) yes checking whether frexpl works... (cached) no | checking whether frexpl works... (cached) no checking whether ldexpl() can be used without linking with libm... yes | checking whether ldexpl() can be used without linking with libm... yes checking whether ldexpl works... no | checking whether ldexpl works... no checking for getppriv... no | checking for getppriv... no checking whether program_invocation_name is declared... (cached) no | checking whether program_invocation_name is declared... (cached) no checking whether program_invocation_short_name is declared... (cached) no | checking whether program_invocation_short_name is declared... (cached) no checking whether signature of pselect conforms to POSIX... yes | checking whether signature of pselect conforms to POSIX... yes checking whether pselect detects invalid fds... yes | checking whether pselect detects invalid fds... yes checking for pthread_mutexattr_getrobust... no | checking for pthread_mutexattr_getrobust... no checking whether pthread_create exists as a global function... yes | checking whether pthread_create exists as a global function... yes checking whether pthread_mutex_timedlock is declared... no | checking whether pthread_mutex_timedlock is declared... no checking whether pthread_sigmask is a macro... no | checking whether pthread_sigmask is a macro... no checking whether pthread_sigmask works without -lpthread... yes | checking whether pthread_sigmask works without -lpthread... yes checking whether pthread_sigmask returns error numbers... yes | checking whether pthread_sigmask returns error numbers... yes checking whether pthread_sigmask unblocks signals correctly... guessing yes | checking whether pthread_sigmask unblocks signals correctly... guessing yes checking for putenv compatible with GNU and SVID... no | checking for putenv compatible with GNU and SVID... no checking whether _putenv is declared... no | checking whether _putenv is declared... no checking for raise... yes | checking for raise... yes checking for sigprocmask... yes | checking for sigprocmask... yes checking for rawmemchr... no | checking for rawmemchr... no checking for readdir... yes | checking for readdir... yes checking whether readlink signature is correct... yes | checking whether readlink signature is correct... yes checking whether readlink handles trailing slash correctly... no | checking whether readlink handles trailing slash correctly... no checking whether readlink truncates results correctly... yes | checking whether readlink truncates results correctly... yes | checking whether readlinkat signature is correct... yes checking whether getutent is declared... no | checking whether getutent is declared... no checking for struct utmpx.ut_user... yes | checking for struct utmpx.ut_user... yes checking for struct utmp.ut_user... no | checking for struct utmp.ut_user... no checking for struct utmpx.ut_name... no | checking for struct utmpx.ut_name... no checking for struct utmp.ut_name... yes | checking for struct utmp.ut_name... yes checking for struct utmpx.ut_type... yes | checking for struct utmpx.ut_type... yes checking for struct utmp.ut_type... no | checking for struct utmp.ut_type... no checking for struct utmpx.ut_pid... yes | checking for struct utmpx.ut_pid... yes checking for struct utmp.ut_pid... no | checking for struct utmp.ut_pid... no checking for struct utmpx.ut_id... yes | checking for struct utmpx.ut_id... yes checking for struct utmp.ut_id... no | checking for struct utmp.ut_id... no checking for struct utmpx.ut_exit... no | checking for struct utmpx.ut_exit... no checking for struct utmp.ut_exit... no | checking for struct utmp.ut_exit... no checking for struct utmpx.ut_exit.ut_exit... no | checking for struct utmpx.ut_exit.ut_exit... no checking for struct utmp.ut_exit.ut_exit... no | checking for struct utmp.ut_exit.ut_exit... no checking for struct utmpx.ut_exit.e_exit... no | checking for struct utmpx.ut_exit.e_exit... no checking for struct utmp.ut_exit.e_exit... no | checking for struct utmp.ut_exit.e_exit... no checking for struct utmpx.ut_exit.ut_termination... no | checking for struct utmpx.ut_exit.ut_termination... no checking for struct utmp.ut_exit.ut_termination... no | checking for struct utmp.ut_exit.ut_termination... no checking for struct utmpx.ut_exit.e_termination... no | checking for struct utmpx.ut_exit.e_termination... no checking for struct utmp.ut_exit.e_termination... no | checking for struct utmp.ut_exit.e_termination... no checking whether realloc (0, 0) returns nonnull... yes | checking whether realloc (0, 0) returns nonnull... yes checking for reallocarray... no | checking for reallocarray... no checking for working re_compile_pattern... no | checking for working re_compile_pattern... no checking for libintl.h... yes | checking for libintl.h... yes checking whether isblank is declared... yes | checking whether isblank is declared... yes checking whether rename honors trailing slash on destination... no | checking whether rename honors trailing slash on destination... no checking whether rename honors trailing slash on source... no | checking whether rename honors trailing slash on source... no checking whether rename manages hard links correctly... yes | checking whether rename manages hard links correctly... yes checking whether rename manages existing destinations correctly... yes | checking whether rename manages existing destinations correctly... yes checking for linux/fs.h... (cached) no | checking for linux/fs.h... (cached) no checking for linux/fs.h... (cached) no | checking for linux/fs.h... (cached) no checking for rewinddir... yes | checking for rewinddir... yes checking whether rmdir works... (cached) yes | checking whether rmdir works... (cached) yes checking for rpmatch... no | checking for rpmatch... no checking for nl_langinfo and YESEXPR... yes | checking for nl_langinfo and YESEXPR... yes checking whether select supports a 0 argument... yes | checking whether select supports a 0 argument... yes checking whether select detects invalid fds... yes | checking whether select detects invalid fds... yes checking for selinux/flask.h... no | checking for selinux/flask.h... no checking for library containing getservbyname... (cached) none required | checking for library containing getservbyname... (cached) none required checking for getservbyname... (cached) yes | checking for getservbyname... (cached) yes checking whether setenv validates arguments... no | checking whether setenv validates arguments... no checking whether setlocale (LC_ALL, NULL) is multithread-safe... (cached) no | checking whether setlocale (LC_ALL, NULL) is multithread-safe... (cached) no checking whether setlocale (category, NULL) is multithread-safe... (cached) yes | checking whether setlocale (category, NULL) is multithread-safe... (cached) yes checking whether imported symbols can be declared weak... (cached) no | checking whether imported symbols can be declared weak... (cached) no checking whether the -Werror option is usable... yes | checking whether the -Werror option is usable... yes checking for simple visibility declarations... yes | checking for simple visibility declarations... yes checking for sig2str... no | checking for sig2str... no checking for struct sigaction.sa_sigaction... yes | checking for struct sigaction.sa_sigaction... yes checking for signbit macro... yes | checking for signbit macro... yes checking for signbit compiler built-ins... yes | checking for signbit compiler built-ins... yes checking for sigprocmask... (cached) yes | checking for sigprocmask... (cached) yes checking for stdint.h... (cached) yes | checking for stdint.h... (cached) yes checking for SIZE_MAX... yes | checking for SIZE_MAX... yes checking for smack_new_label_from_self in -lsmack... no | checking for smack_new_label_from_self in -lsmack... no checking for snprintf... (cached) yes | checking for snprintf... (cached) yes checking whether snprintf respects a size of 1... yes | checking whether snprintf respects a size of 1... yes checking whether printf supports POSIX/XSI format strings with positions... yes | checking whether printf supports POSIX/XSI format strings with positions... yes checking for socklen_t... yes | checking for socklen_t... yes checking for ssize_t... (cached) yes | checking for ssize_t... (cached) yes checking whether stat handles trailing slashes on files... no | checking whether stat handles trailing slashes on files... no checking for struct stat.st_atim.tv_nsec... no | checking for struct stat.st_atim.tv_nsec... no checking for struct stat.st_atimespec.tv_nsec... yes | checking for struct stat.st_atimespec.tv_nsec... yes checking for struct stat.st_birthtimespec.tv_nsec... no | checking for struct stat.st_birthtimespec.tv_nsec... no checking for struct stat.st_birthtimensec... no | checking for struct stat.st_birthtimensec... no checking for struct stat.st_birthtim.tv_nsec... no | checking for struct stat.st_birthtim.tv_nsec... no checking for working stdalign.h... no | checking for working stdalign.h... no checking for va_copy... yes | checking for va_copy... yes checking for stpcpy... yes | checking for stpcpy... yes | checking for working strnlen... yes checking for strsignal... yes | checking for strsignal... yes checking whether strsignal always returns a string... yes | checking whether strsignal always returns a string... yes checking whether strstr works... yes | checking whether strstr works... yes checking whether strtod obeys C99... no | checking whether strtod obeys C99... no checking for nl_langinfo... (cached) yes | checking for nl_langinfo... (cached) yes checking whether strtoimax works... yes | checking whether strtoimax works... yes checking whether strtold obeys POSIX... no | checking whether strtold obeys POSIX... no checking for nl_langinfo... (cached) yes | checking for nl_langinfo... (cached) yes checking for strtoll... yes | checking for strtoll... yes checking whether strtoll works... no | checking whether strtoll works... no checking for strtoull... yes | checking for strtoull... yes checking whether strtoull works... no | checking whether strtoull works... no checking whether symlink handles trailing slash correctly... no | checking whether symlink handles trailing slash correctly... no | checking whether symlinkat handles trailing slash correctly... no checking whether localtime_r is declared... yes | checking whether localtime_r is declared... yes checking whether localtime_r is compatible with its POSIX signature... yes | checking whether localtime_r is compatible with its POSIX signature... yes checking whether localtime works even near extrema... yes | checking whether localtime works even near extrema... yes checking for timezone_t... no | checking for timezone_t... no checking whether timer_settime is declared... no | checking whether timer_settime is declared... no checking for uname... yes | checking for uname... yes checking whether unlink honors trailing slashes... (cached) no | checking whether unlink honors trailing slashes... (cached) no checking whether unlink of a parent directory fails as it should... (cached) no | checking whether unlink of a parent directory fails as it should... (cached) no checking whether a running program can be unlinked... yes | checking whether a running program can be unlinked... yes checking for unsetenv... yes | checking for unsetenv... yes checking for unsetenv() return type... int | checking for unsetenv() return type... int checking whether unsetenv obeys POSIX... yes | checking whether unsetenv obeys POSIX... yes checking for /proc/uptime... no | checking for /proc/uptime... no checking for utime... yes | checking for utime... yes checking whether utime handles trailing slashes on files... no | checking whether utime handles trailing slashes on files... no | checking whether utimensat works... no checking for variable-length arrays... yes | checking for variable-length arrays... yes checking for ptrdiff_t... yes | checking for ptrdiff_t... yes checking for vasprintf... yes | checking for vasprintf... yes checking for vasprintf... (cached) yes | checking for vasprintf... (cached) yes checking for nl_langinfo... (cached) yes | checking for nl_langinfo... (cached) yes checking for ptrdiff_t... (cached) yes | checking for ptrdiff_t... (cached) yes checking for nl_langinfo... (cached) yes | checking for nl_langinfo... (cached) yes checking for ptrdiff_t... (cached) yes | checking for ptrdiff_t... (cached) yes checking whether mbrtowc handles incomplete characters... (cached) yes | checking whether mbrtowc handles incomplete characters... (cached) yes checking whether mbrtowc works as well as mbtowc... (cached) yes | checking whether mbrtowc works as well as mbtowc... (cached) yes checking whether wcrtomb works in the C locale... yes | checking whether wcrtomb works in the C locale... yes checking whether wcrtomb return value is correct... yes | checking whether wcrtomb return value is correct... yes checking whether wcwidth is declared... (cached) yes | checking whether wcwidth is declared... (cached) yes checking whether wcwidth works reasonably in UTF-8 locales... (cached) no | checking whether wcwidth works reasonably in UTF-8 locales... (cached) no checking whether use of TIOCGWINSZ requires sys/ioctl.h... no | checking whether use of TIOCGWINSZ requires sys/ioctl.h... no checking whether use of TIOCGWINSZ requires termios.h... (cached) yes | checking whether use of TIOCGWINSZ requires termios.h... (cached) yes checking whether use of struct winsize requires sys/ptem.h... no | checking whether use of struct winsize requires sys/ptem.h... no checking for wmemchr... yes | checking for wmemchr... yes checking for stdint.h... (cached) yes | checking for stdint.h... (cached) yes checking for atoll... yes | checking for atoll... yes checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a turkish Unicode locale... none | checking for a turkish Unicode locale... none checking whether byte ordering is bigendian... (cached) yes | checking whether byte ordering is bigendian... (cached) yes checking for library containing inet_pton... none required | checking for library containing inet_pton... none required checking whether inet_pton is declared... yes | checking whether inet_pton is declared... yes checking whether byte ordering is bigendian... (cached) yes | checking whether byte ordering is bigendian... (cached) yes checking for ioctl... yes | checking for ioctl... yes checking for ioctl with POSIX signature... no | checking for ioctl with POSIX signature... no checking where to find the exponent in a 'double'... (cached) word 0 bit 20 | checking where to find the exponent in a 'double'... (cached) word 0 bit 20 checking where to find the exponent in a 'float'... (cached) word 0 bit 23 | checking where to find the exponent in a 'float'... (cached) word 0 bit 23 checking where to find the exponent in a 'long double'... word 0 bit 20 | checking where to find the exponent in a 'long double'... word 0 bit 20 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional japanese locale... (cached) ja_JP.eucJP | checking for a traditional japanese locale... (cached) ja_JP.eucJP checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional japanese locale... (cached) ja_JP.eucJP | checking for a traditional japanese locale... (cached) ja_JP.eucJP checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional japanese locale... (cached) ja_JP.eucJP | checking for a traditional japanese locale... (cached) ja_JP.eucJP checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for a turkish Unicode locale... (cached) none | checking for a turkish Unicode locale... (cached) none checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional japanese locale... (cached) ja_JP.eucJP | checking for a traditional japanese locale... (cached) ja_JP.eucJP checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking whether perror matches strerror... yes | checking whether perror matches strerror... yes checking whether sched_yield is declared... yes | checking whether sched_yield is declared... yes checking for __secure_getenv... no | checking for __secure_getenv... no checking for issetugid... yes | checking for issetugid... yes checking whether setlocale supports the C locale... yes | checking whether setlocale supports the C locale... yes checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional japanese locale... (cached) ja_JP.eucJP | checking for a traditional japanese locale... (cached) ja_JP.eucJP checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking whether sleep is declared... yes | checking whether sleep is declared... yes checking for working sleep... yes | checking for working sleep... yes checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for pthread_atfork... yes | checking for pthread_atfork... yes checking for sys/single_threaded.h... no | checking for sys/single_threaded.h... no checking whether tmpfile works... yes | checking whether tmpfile works... yes checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking for useconds_t... yes | checking for useconds_t... yes checking whether usleep allows large arguments... yes | checking whether usleep allows large arguments... yes checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking for a french Unicode locale... (cached) fr_FR.UTF-8 | checking for a french Unicode locale... (cached) fr_FR.UTF-8 checking for a traditional japanese locale... (cached) ja_JP.eucJP | checking for a traditional japanese locale... (cached) ja_JP.eucJP checking for a transitional chinese locale... (cached) zh_CN.GB18030 | checking for a transitional chinese locale... (cached) zh_CN.GB18030 checking whether wctob works... yes | checking whether wctob works... yes checking whether wctob is declared... yes | checking whether wctob is declared... yes checking for working volatile... yes | checking for working volatile... yes checking for unsigned long long int... yes | checking for unsigned long long int... yes checking for sys/sysctl.h... (cached) yes | checking for sys/sysctl.h... (cached) yes checking whether geteuid is declared... yes | checking whether geteuid is declared... yes checking whether getuid is declared... yes | checking whether getuid is declared... yes checking whether getgrgid is declared... yes | checking whether getgrgid is declared... yes checking whether getpwuid is declared... yes | checking whether getpwuid is declared... yes checking whether ttyname is declared... yes | checking whether ttyname is declared... yes checking whether setregid is declared... yes | checking whether setregid is declared... yes checking for attr/error_context.h... no | checking for attr/error_context.h... no checking for attr/libattr.h... no | checking for attr/libattr.h... no configure: WARNING: libattr development library was not found or not usable. | configure: WARNING: libattr development library was not found or not usable. configure: WARNING: GNU coreutils will be built without xattr support. | configure: WARNING: GNU coreutils will be built without xattr support. checking for struct stat.st_author... no | checking for struct stat.st_author... no checking for ino_t... yes | checking for ino_t... yes checking for major_t... no | checking for major_t... no checking for minor_t... no | checking for minor_t... no checking for mode_to_security_class... no | checking for mode_to_security_class... no checking for inotify_init... no | checking for inotify_init... no checking for nfs/vfs.h... no | checking for nfs/vfs.h... no checking for struct statfs.f_namelen... no | checking for struct statfs.f_namelen... no checking for struct statfs.f_namemax... no | checking for struct statfs.f_namemax... no checking for struct statfs.f_type... yes | checking for struct statfs.f_type... yes checking for struct statfs.f_frsize... no | checking for struct statfs.f_frsize... no checking for cap_get_file in -lcap... no | checking for cap_get_file in -lcap... no configure: WARNING: libcap library was not found or not usable. | configure: WARNING: libcap library was not found or not usable. configure: WARNING: GNU coreutils will be built without capability support. | configure: WARNING: GNU coreutils will be built without capability support. checking for working fork... yes | checking for working fork... yes checking for working vfork... (cached) yes | checking for working vfork... (cached) yes checking for chroot... yes | checking for chroot... yes checking for gethostid... yes | checking for gethostid... yes checking for sigsuspend... yes | checking for sigsuspend... yes checking whether use of struct winsize requires sys/ptem.h... (cached) no | checking whether use of struct winsize requires sys/ptem.h... (cached) no checking whether localtime caches TZ... no | checking whether localtime caches TZ... no checking for fclonefileat... no | checking for fclonefileat... no checking for getattrat... no | checking for getattrat... no checking for statx... no | checking for statx... no checking for initgroups... yes | checking for initgroups... yes checking for syslog... yes | checking for syslog... yes checking for 3-argument setpriority function... yes | checking for 3-argument setpriority function... yes checking ut_host in struct utmp... yes | checking ut_host in struct utmp... yes checking for sysctl... (cached) yes | checking for sysctl... (cached) yes checking for sys/sysctl.h... (cached) yes | checking for sys/sysctl.h... (cached) yes checking whether we can get the system boot time... yes | checking whether we can get the system boot time... yes checking POSIX termios... (cached) yes | checking POSIX termios... (cached) yes checking whether use of TIOCGWINSZ requires sys/ioctl.h... (cached) no | checking whether use of TIOCGWINSZ requires sys/ioctl.h... (cached) no checking whether termios.h needs _XOPEN_SOURCE... no | checking whether termios.h needs _XOPEN_SOURCE... no checking c_line in struct termios... no | checking c_line in struct termios... no checking whether use of struct winsize requires sys/ptem.h... (cached) no | checking whether use of struct winsize requires sys/ptem.h... (cached) no checking whether use of TIOCGWINSZ requires termios.h... (cached) yes | checking whether use of TIOCGWINSZ requires termios.h... (cached) yes checking whether strsignal is declared... (cached) yes | checking whether strsignal is declared... (cached) yes checking whether sys_siglist is declared... yes | checking whether sys_siglist is declared... yes checking whether _sys_siglist is declared... no | checking whether _sys_siglist is declared... no checking whether __sys_siglist is declared... no | checking whether __sys_siglist is declared... no checking whether C compiler handles -Werror... yes | checking whether C compiler handles -Werror... yes checking whether C compiler handles -errwarn... no | checking whether C compiler handles -errwarn... no checking whether this system supports stdbuf... yes | checking whether this system supports stdbuf... yes checking if __get_cpuid available... no | checking if __get_cpuid available... no checking if pclmul intrinsic exists... no | checking if pclmul intrinsic exists... no checking if __get_cpuid_count exists... no | checking if __get_cpuid_count exists... no checking if avx2 intrinstics exists... no | checking if avx2 intrinstics exists... no checking whether NLS is requested... yes | checking whether NLS is requested... yes checking for msgfmt... /opt/local/bin/msgfmt | checking for msgfmt... /opt/local/bin/msgfmt checking for gmsgfmt... /opt/local/bin/msgfmt | checking for gmsgfmt... /opt/local/bin/msgfmt checking for xgettext... /opt/local/bin/xgettext | checking for xgettext... /opt/local/bin/xgettext checking for msgmerge... /opt/local/bin/msgmerge | checking for msgmerge... /opt/local/bin/msgmerge checking for CFPreferencesCopyAppValue... (cached) yes | checking for CFPreferencesCopyAppValue... (cached) yes checking for CFLocaleCopyPreferredLanguages... (cached) yes | checking for CFLocaleCopyPreferredLanguages... (cached) yes checking for GNU gettext in libc... no | checking for GNU gettext in libc... no checking for iconv... (cached) yes | checking for iconv... (cached) yes checking for working iconv... (cached) yes | checking for working iconv... (cached) yes checking how to link with libiconv... -liconv | checking how to link with libiconv... -liconv checking for GNU gettext in libintl... yes | checking for GNU gettext in libintl... yes checking whether to use NLS... yes | checking whether to use NLS... yes checking where the gettext function comes from... external libintl | checking where the gettext function comes from... external libintl checking how to link with libintl... -lintl -Wl,-framework -Wl,CoreFoundation | checking how to link with libintl... -lintl -Wl,-framework -Wl,CoreFoundation checking for a traditional french locale... (cached) fr_FR.ISO8859-1 | checking for a traditional french locale... (cached) fr_FR.ISO8859-1 checking that generated files are newer than configure... done | checking that generated files are newer than configure... done }}} Here is a record of changed `gsed` commands to apply the configuration to the software (the bullet in the first column again marks changes from 1 to 0 or 0 to 1): {{{ /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''HAVE_ALLOCA_H''@|1|g' \ ./lib/alloca.in.h > lib/alloca.h-t mv lib/alloca.h-t lib/alloca.h /opt/local/bin/gmkdir -p 'lib/arpa' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''HAVE_FEATURES_H''@|0|g' \ -e 's|@''NEXT_ARPA_INET_H''@||g' \ -e 's|@''HAVE_ARPA_INET_H''@|1|g' \ -e 's/@''GNULIB_INET_NTOP''@/1/g' \ -e 's/@''GNULIB_INET_PTON''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's|@''HAVE_WS2TCPIP_H''@|0|g' \ -e 's|@''HAVE_DECL_INET_NTOP''@|1|g' \ -e 's|@''HAVE_DECL_INET_PTON''@|1|g' \ -e 's|@''REPLACE_INET_NTOP''@|0|g' \ -e 's|@''REPLACE_INET_PTON''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/arpa_inet.in.h > lib/arpa/inet.h-t mv lib/arpa/inet.h-t lib/arpa/inet.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/byteswap.h-t' ./lib/byteswap.in.h mv lib/byteswap.h-t lib/byteswap.h /opt/local/bin/gmkdir -p 'lib' { echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */'; \ echo '#if HAVE_WINSOCK2_H'; \ echo '# include /* avoid mingw pollution on DATADIR */'; \ echo '#endif'; \ echo '#define PREFIX "/opt/local"'; \ echo '#define EXEC_PREFIX "/opt/local"'; \ echo '#define BINDIR "/opt/local/bin"'; \ echo '#define SBINDIR "/opt/local/sbin"'; \ echo '#define LIBEXECDIR "/opt/local/libexec"'; \ echo '#define DATAROOTDIR "/opt/local/share"'; \ echo '#define DATADIR "/opt/local/share"'; \ echo '#define SYSCONFDIR "/opt/local/etc"'; \ echo '#define SHAREDSTATEDIR "/opt/local/com"'; \ echo '#define LOCALSTATEDIR "/opt/local/var"'; \ echo '#define RUNSTATEDIR "/opt/local/var/run"'; \ echo '#define INCLUDEDIR "/opt/local/include"'; \ echo '#define OLDINCLUDEDIR "/usr/include"'; \ echo '#define DOCDIR "/opt/local/share/doc/coreutils"'; \ echo '#define INFODIR "/opt/local/share/info"'; \ echo '#define HTMLDIR "/opt/local/share/doc/coreutils"'; \ echo '#define DVIDIR "/opt/local/share/doc/coreutils"'; \ echo '#define PDFDIR "/opt/local/share/doc/coreutils"'; \ echo '#define PSDIR "/opt/local/share/doc/coreutils"'; \ echo '#define LIBDIR "/opt/local/lib"'; \ echo '#define LISPDIR "/opt/local/share/emacs/site-lisp"'; \ echo '#define LOCALEDIR "/opt/local/share/locale"'; \ echo '#define MANDIR "/opt/local/share/man"'; \ echo '#define MANEXT ""'; \ echo '#define PKGDATADIR "/opt/local/share/coreutils"'; \ echo '#define PKGINCLUDEDIR "/opt/local/include/coreutils"'; \ echo '#define PKGLIBDIR "/opt/local/lib/coreutils"'; \ echo '#define PKGLIBEXECDIR "/opt/local/libexec/coreutils"'; \ } | sed '/""/d' > lib/configmake.h-t mv lib/configmake.h-t lib/configmake.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_CTYPE_H''@||g' \ -e 's/@''GNULIB_ISBLANK''@/1/g' \ -e 's/@''HAVE_ISBLANK''@/1/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/ctype.in.h > lib/ctype.h-t mv lib/ctype.h-t lib/ctype.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_DIRENT_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_DIRENT_H''@||g' \ -e 's/@''GNULIB_OPENDIR''@/1/g' \ -e 's/@''GNULIB_READDIR''@/1/g' \ -e 's/@''GNULIB_REWINDDIR''@/1/g' \ -e 's/@''GNULIB_CLOSEDIR''@/1/g' \ -e 's/@''GNULIB_DIRFD''@/1/g' \ -e 's/@''GNULIB_FDOPENDIR''@/1/g' \ -e 's/@''GNULIB_SCANDIR''@/0/g' \ -e 's/@''GNULIB_ALPHASORT''@/0/g' \ -e 's/@''HAVE_OPENDIR''@/1/g' \ -e 's/@''HAVE_READDIR''@/1/g' \ -e 's/@''HAVE_REWINDDIR''@/1/g' \ -e 's/@''HAVE_CLOSEDIR''@/1/g' \ -e 's|@''HAVE_DECL_DIRFD''@|1|g' \ ? -e 's|@''HAVE_DECL_FDOPENDIR''@|0|g' \ ? -e 's|@''HAVE_FDOPENDIR''@|0|g' \ -e 's|@''HAVE_SCANDIR''@|1|g' \ -e 's|@''HAVE_ALPHASORT''@|1|g' \ -e 's|@''REPLACE_OPENDIR''@|0|g' \ -e 's|@''REPLACE_CLOSEDIR''@|0|g' \ -e 's|@''REPLACE_DIRFD''@|0|g' \ -e 's|@''REPLACE_FDOPENDIR''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/dirent.in.h > lib/dirent.h-t mv lib/dirent.h-t lib/dirent.h /opt/local/bin/gmkdir -p 'lib/malloc' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e '/libc_hidden_proto/d' \ ./lib/malloc/dynarray.h > lib/malloc/dynarray.gl.h-t mv lib/malloc/dynarray.gl.h-t lib/malloc/dynarray.gl.h /opt/local/bin/gmkdir -p 'lib/malloc' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|||g' \ -e 's|__attribute_maybe_unused__|_GL_ATTRIBUTE_MAYBE_UNUSED|g' \ -e 's|__attribute_nonnull__|_GL_ATTRIBUTE_NONNULL|g' \ -e 's|__attribute_warn_unused_result__|_GL_ATTRIBUTE_NODISCARD|g' \ -e 's|__glibc_likely|_GL_LIKELY|g' \ -e 's|__glibc_unlikely|_GL_UNLIKELY|g' \ ./lib/malloc/dynarray-skeleton.c > lib/malloc/dynarray- skeleton.gl.h-t mv lib/malloc/dynarray-skeleton.gl.h-t lib/malloc/dynarray-skeleton.gl.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_ERRNO_H''@||g' \ -e 's|@''EMULTIHOP_HIDDEN''@|0|g' \ -e 's|@''EMULTIHOP_VALUE''@||g' \ -e 's|@''ENOLINK_HIDDEN''@|0|g' \ -e 's|@''ENOLINK_VALUE''@||g' \ -e 's|@''EOVERFLOW_HIDDEN''@|0|g' \ -e 's|@''EOVERFLOW_VALUE''@||g' \ ./lib/errno.in.h > lib/errno.h-t mv lib/errno.h-t lib/errno.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_FCNTL_H''@||g' \ -e 's/@''GNULIB_CREAT''@/0/g' \ -e 's/@''GNULIB_FCNTL''@/1/g' \ -e 's/@''GNULIB_NONBLOCKING''@/0/g' \ -e 's/@''GNULIB_OPEN''@/1/g' \ -e 's/@''GNULIB_OPENAT''@/1/g' \ -e 's/@''GNULIB_MDA_CREAT''@/1/g' \ -e 's/@''GNULIB_MDA_OPEN''@/1/g' \ -e 's|@''HAVE_FCNTL''@|1|g' \ ? -e 's|@''HAVE_OPENAT''@|0|g' \ -e 's|@''REPLACE_CREAT''@|0|g' \ -e 's|@''REPLACE_FCNTL''@|1|g' \ -e 's|@''REPLACE_OPEN''@|1|g' \ ? -e 's|@''REPLACE_OPENAT''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/fcntl.in.h > lib/fcntl.h-t mv lib/fcntl.h-t lib/fcntl.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_FNMATCH_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_FNMATCH_H''@||g' \ -e 's/@''GNULIB_FNMATCH''@/1/g' \ -e 's|@''HAVE_FNMATCH''@|1|g' \ -e 's|@''REPLACE_FNMATCH''@|1|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/fnmatch.in.h > lib/fnmatch.h-t mv lib/fnmatch.h-t lib/fnmatch.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_GETOPT_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_GETOPT_H''@||g' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ ./lib/getopt.in.h > lib/getopt.h-t mv lib/getopt.h-t lib/getopt.h sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''HAVE_SYS_CDEFS_H''@|1|g' \ ./lib/getopt-cdefs.in.h > lib/getopt-cdefs.h-t mv lib/getopt-cdefs.h-t lib/getopt-cdefs.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_ICONV_H''@||g' \ -e 's/@''GNULIB_ICONV''@/1/g' \ -e 's|@''ICONV_CONST''@||g' \ -e 's|@''REPLACE_ICONV''@|0|g' \ -e 's|@''REPLACE_ICONV_OPEN''@|0|g' \ -e 's|@''REPLACE_ICONV_UTF''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/iconv.in.h > lib/iconv.h-t mv lib/iconv.h-t lib/iconv.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's/@''HAVE_INTTYPES_H''@/1/g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_INTTYPES_H''@||g' \ -e 's/@''APPLE_UNIVERSAL_BUILD''@/0/g' \ -e 's/@''PRIPTR_PREFIX''@/"l"/g' \ -e 's/@''GNULIB_IMAXABS''@/0/g' \ -e 's/@''GNULIB_IMAXDIV''@/0/g' \ -e 's/@''GNULIB_STRTOIMAX''@/1/g' \ -e 's/@''GNULIB_STRTOUMAX''@/1/g' \ -e 's/@''HAVE_DECL_IMAXABS''@/1/g' \ -e 's/@''HAVE_DECL_IMAXDIV''@/1/g' \ -e 's/@''HAVE_DECL_STRTOIMAX''@/1/g' \ -e 's/@''HAVE_DECL_STRTOUMAX''@/1/g' \ -e 's/@''HAVE_IMAXDIV_T''@/1/g' \ -e 's/@''REPLACE_STRTOIMAX''@/0/g' \ -e 's/@''REPLACE_STRTOUMAX''@/0/g' \ -e 's/@''INT32_MAX_LT_INTMAX_MAX''@/1/g' \ -e 's/@''INT64_MAX_EQ_LONG_MAX''@/0/g' \ -e 's/@''UINT32_MAX_LT_UINTMAX_MAX''@/1/g' \ -e 's/@''UINT64_MAX_EQ_ULONG_MAX''@/0/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/inttypes.in.h > lib/inttypes.h-t mv lib/inttypes.h-t lib/inttypes.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_LANGINFO_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_LANGINFO_H''@||g' \ -e 's/@''GNULIB_NL_LANGINFO''@/1/g' \ -e 's|@''HAVE_LANGINFO_CODESET''@|1|g' \ -e 's|@''HAVE_LANGINFO_T_FMT_AMPM''@|1|g' \ -e 's|@''HAVE_LANGINFO_ALTMON''@|0|g' \ -e 's|@''HAVE_LANGINFO_ERA''@|1|g' \ -e 's|@''HAVE_LANGINFO_YESEXPR''@|1|g' \ -e 's|@''HAVE_NL_LANGINFO''@|1|g' \ -e 's|@''REPLACE_NL_LANGINFO''@|1|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/langinfo.in.h > lib/langinfo.h-t mv lib/langinfo.h-t lib/langinfo.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_LIMITS_H''@||g' \ ./lib/limits.in.h > lib/limits.h-t mv lib/limits.h-t lib/limits.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_LOCALE_H''@||g' \ -e 's/@''GNULIB_LOCALECONV''@/1/g' \ -e 's/@''GNULIB_SETLOCALE''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_SETLOCALE_NULL''@/1/g' \ -e 's/@''GNULIB_DUPLOCALE''@/0/g' \ -e 's/@''GNULIB_LOCALENAME''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's|@''HAVE_NEWLOCALE''@|1|g' \ -e 's|@''HAVE_DUPLOCALE''@|1|g' \ -e 's|@''HAVE_FREELOCALE''@|1|g' \ -e 's|@''HAVE_XLOCALE_H''@|1|g' \ -e 's|@''REPLACE_LOCALECONV''@|0|g' \ -e 's|@''REPLACE_SETLOCALE''@|1|g' \ -e 's|@''REPLACE_NEWLOCALE''@|0|g' \ -e 's|@''REPLACE_DUPLOCALE''@|0|g' \ -e 's|@''REPLACE_FREELOCALE''@|0|g' \ -e 's|@''REPLACE_STRUCT_LCONV''@|0|g' \ -e 's|@''LOCALENAME_ENHANCE_LOCALE_FUNCS''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/locale.in.h > lib/locale.h-t mv lib/locale.h-t lib/locale.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT_AS_FIRST_DIRECTIVE''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_AS_FIRST_DIRECTIVE_MATH_H''@||g' \ -e 's/@''GNULIB_ACOSF''@/0/g' \ -e 's/@''GNULIB_ACOSL''@/0/g' \ -e 's/@''GNULIB_ASINF''@/0/g' \ -e 's/@''GNULIB_ASINL''@/0/g' \ -e 's/@''GNULIB_ATANF''@/0/g' \ -e 's/@''GNULIB_ATANL''@/0/g' \ -e 's/@''GNULIB_ATAN2F''@/0/g' \ -e 's/@''GNULIB_CBRT''@/0/g' \ -e 's/@''GNULIB_CBRTF''@/0/g' \ -e 's/@''GNULIB_CBRTL''@/0/g' \ -e 's/@''GNULIB_CEIL''@/0/g' \ -e 's/@''GNULIB_CEILF''@/0/g' \ -e 's/@''GNULIB_CEILL''@/0/g' \ -e 's/@''GNULIB_COPYSIGN''@/0/g' \ -e 's/@''GNULIB_COPYSIGNF''@/0/g' \ -e 's/@''GNULIB_COPYSIGNL''@/0/g' \ -e 's/@''GNULIB_COSF''@/0/g' \ -e 's/@''GNULIB_COSL''@/0/g' \ -e 's/@''GNULIB_COSHF''@/0/g' \ -e 's/@''GNULIB_EXPF''@/0/g' \ -e 's/@''GNULIB_EXPL''@/0/g' \ -e 's/@''GNULIB_EXP2''@/0/g' \ -e 's/@''GNULIB_EXP2F''@/0/g' \ -e 's/@''GNULIB_EXP2L''@/0/g' \ -e 's/@''GNULIB_EXPM1''@/0/g' \ -e 's/@''GNULIB_EXPM1F''@/0/g' \ -e 's/@''GNULIB_EXPM1L''@/0/g' \ -e 's/@''GNULIB_FABSF''@/0/g' \ -e 's/@''GNULIB_FABSL''@/0/g' \ -e 's/@''GNULIB_FLOOR''@/0/g' \ -e 's/@''GNULIB_FLOORF''@/0/g' \ -e 's/@''GNULIB_FLOORL''@/0/g' \ -e 's/@''GNULIB_FMA''@/0/g' \ -e 's/@''GNULIB_FMAF''@/0/g' \ -e 's/@''GNULIB_FMAL''@/0/g' \ -e 's/@''GNULIB_FMOD''@/0/g' \ -e 's/@''GNULIB_FMODF''@/0/g' \ -e 's/@''GNULIB_FMODL''@/0/g' \ -e 's/@''GNULIB_FREXPF''@/0/g' \ -e 's/@''GNULIB_FREXP''@/1/g' \ -e 's/@''GNULIB_FREXPL''@/1/g' \ -e 's/@''GNULIB_HYPOT''@/0/g' \ -e 's/@''GNULIB_HYPOTF''@/0/g' \ -e 's/@''GNULIB_HYPOTL''@/0/g' \ < ./lib/math.in.h | \ sed -e 's/@''GNULIB_ILOGB''@/0/g' \ -e 's/@''GNULIB_ILOGBF''@/0/g' \ -e 's/@''GNULIB_ILOGBL''@/0/g' \ -e 's/@''GNULIB_ISFINITE''@/0/g' \ -e 's/@''GNULIB_ISINF''@/0/g' \ -e 's/@''GNULIB_ISNAN''@/0/g' \ -e 's/@''GNULIB_ISNANF''@/0/g' \ -e 's/@''GNULIB_ISNAND''@/0/g' \ -e 's/@''GNULIB_ISNANL''@/0/g' \ -e 's/@''GNULIB_LDEXPF''@/0/g' \ -e 's/@''GNULIB_LDEXPL''@/0/g' \ -e 's/@''GNULIB_LOG''@/0/g' \ -e 's/@''GNULIB_LOGF''@/0/g' \ -e 's/@''GNULIB_LOGL''@/0/g' \ -e 's/@''GNULIB_LOG10''@/0/g' \ -e 's/@''GNULIB_LOG10F''@/0/g' \ -e 's/@''GNULIB_LOG10L''@/0/g' \ -e 's/@''GNULIB_LOG1P''@/0/g' \ -e 's/@''GNULIB_LOG1PF''@/0/g' \ -e 's/@''GNULIB_LOG1PL''@/0/g' \ -e 's/@''GNULIB_LOG2''@/0/g' \ -e 's/@''GNULIB_LOG2F''@/0/g' \ -e 's/@''GNULIB_LOG2L''@/0/g' \ -e 's/@''GNULIB_LOGB''@/0/g' \ -e 's/@''GNULIB_LOGBF''@/0/g' \ -e 's/@''GNULIB_LOGBL''@/0/g' \ -e 's/@''GNULIB_MODF''@/0/g' \ -e 's/@''GNULIB_MODFF''@/0/g' \ -e 's/@''GNULIB_MODFL''@/0/g' \ -e 's/@''GNULIB_POWF''@/0/g' \ -e 's/@''GNULIB_REMAINDER''@/0/g' \ -e 's/@''GNULIB_REMAINDERF''@/0/g' \ -e 's/@''GNULIB_REMAINDERL''@/0/g' \ -e 's/@''GNULIB_RINT''@/0/g' \ -e 's/@''GNULIB_RINTF''@/0/g' \ -e 's/@''GNULIB_RINTL''@/0/g' \ -e 's/@''GNULIB_ROUND''@/0/g' \ -e 's/@''GNULIB_ROUNDF''@/0/g' \ -e 's/@''GNULIB_ROUNDL''@/0/g' \ -e 's/@''GNULIB_SIGNBIT''@/1/g' \ -e 's/@''GNULIB_SINF''@/0/g' \ -e 's/@''GNULIB_SINL''@/0/g' \ -e 's/@''GNULIB_SINHF''@/0/g' \ -e 's/@''GNULIB_SQRTF''@/0/g' \ -e 's/@''GNULIB_SQRTL''@/0/g' \ -e 's/@''GNULIB_TANF''@/0/g' \ -e 's/@''GNULIB_TANL''@/0/g' \ -e 's/@''GNULIB_TANHF''@/0/g' \ -e 's/@''GNULIB_TRUNC''@/0/g' \ -e 's/@''GNULIB_TRUNCF''@/0/g' \ -e 's/@''GNULIB_TRUNCL''@/0/g' \ -e 's/@''GNULIB_MDA_J0''@/1/g' \ -e 's/@''GNULIB_MDA_J1''@/1/g' \ -e 's/@''GNULIB_MDA_JN''@/1/g' \ -e 's/@''GNULIB_MDA_Y0''@/1/g' \ -e 's/@''GNULIB_MDA_Y1''@/1/g' \ -e 's/@''GNULIB_MDA_YN''@/1/g' \ | \ sed -e 's|@''HAVE_ACOSF''@|1|g' \ -e 's|@''HAVE_ACOSL''@|1|g' \ -e 's|@''HAVE_ASINF''@|1|g' \ -e 's|@''HAVE_ASINL''@|1|g' \ -e 's|@''HAVE_ATANF''@|1|g' \ -e 's|@''HAVE_ATANL''@|1|g' \ -e 's|@''HAVE_ATAN2F''@|1|g' \ -e 's|@''HAVE_CBRT''@|1|g' \ -e 's|@''HAVE_CBRTF''@|1|g' \ -e 's|@''HAVE_CBRTL''@|1|g' \ -e 's|@''HAVE_COPYSIGN''@|1|g' \ -e 's|@''HAVE_COPYSIGNL''@|1|g' \ -e 's|@''HAVE_COSF''@|1|g' \ -e 's|@''HAVE_COSL''@|1|g' \ -e 's|@''HAVE_COSHF''@|1|g' \ -e 's|@''HAVE_EXPF''@|1|g' \ -e 's|@''HAVE_EXPL''@|1|g' \ -e 's|@''HAVE_EXPM1''@|1|g' \ -e 's|@''HAVE_EXPM1F''@|1|g' \ -e 's|@''HAVE_FABSF''@|1|g' \ -e 's|@''HAVE_FABSL''@|1|g' \ -e 's|@''HAVE_FMA''@|1|g' \ -e 's|@''HAVE_FMAF''@|1|g' \ -e 's|@''HAVE_FMAL''@|1|g' \ -e 's|@''HAVE_FMODF''@|1|g' \ -e 's|@''HAVE_FMODL''@|1|g' \ -e 's|@''HAVE_FREXPF''@|1|g' \ -e 's|@''HAVE_HYPOTF''@|1|g' \ -e 's|@''HAVE_HYPOTL''@|1|g' \ -e 's|@''HAVE_ILOGB''@|1|g' \ -e 's|@''HAVE_ILOGBF''@|1|g' \ -e 's|@''HAVE_ILOGBL''@|1|g' \ -e 's|@''HAVE_ISNANF''@|1|g' \ -e 's|@''HAVE_ISNAND''@|1|g' \ -e 's|@''HAVE_ISNANL''@|1|g' \ -e 's|@''HAVE_LDEXPF''@|1|g' \ -e 's|@''HAVE_LOGF''@|1|g' \ -e 's|@''HAVE_LOGL''@|1|g' \ -e 's|@''HAVE_LOG10F''@|1|g' \ -e 's|@''HAVE_LOG10L''@|1|g' \ -e 's|@''HAVE_LOG1P''@|1|g' \ -e 's|@''HAVE_LOG1PF''@|1|g' \ -e 's|@''HAVE_LOG1PL''@|1|g' \ -e 's|@''HAVE_LOGBF''@|1|g' \ -e 's|@''HAVE_LOGBL''@|1|g' \ -e 's|@''HAVE_MODFF''@|1|g' \ -e 's|@''HAVE_MODFL''@|1|g' \ -e 's|@''HAVE_POWF''@|1|g' \ -e 's|@''HAVE_REMAINDER''@|1|g' \ -e 's|@''HAVE_REMAINDERF''@|1|g' \ -e 's|@''HAVE_RINT''@|1|g' \ -e 's|@''HAVE_RINTL''@|1|g' \ -e 's|@''HAVE_SINF''@|1|g' \ -e 's|@''HAVE_SINL''@|1|g' \ -e 's|@''HAVE_SINHF''@|1|g' \ -e 's|@''HAVE_SQRTF''@|1|g' \ -e 's|@''HAVE_SQRTL''@|1|g' \ -e 's|@''HAVE_TANF''@|1|g' \ -e 's|@''HAVE_TANL''@|1|g' \ -e 's|@''HAVE_TANHF''@|1|g' \ -e 's|@''HAVE_DECL_ACOSL''@|1|g' \ -e 's|@''HAVE_DECL_ASINL''@|1|g' \ -e 's|@''HAVE_DECL_ATANL''@|1|g' \ -e 's|@''HAVE_DECL_CBRTF''@|1|g' \ -e 's|@''HAVE_DECL_CBRTL''@|1|g' \ -e 's|@''HAVE_DECL_CEILF''@|1|g' \ -e 's|@''HAVE_DECL_CEILL''@|1|g' \ -e 's|@''HAVE_DECL_COPYSIGNF''@|1|g' \ -e 's|@''HAVE_DECL_COSL''@|1|g' \ -e 's|@''HAVE_DECL_EXPL''@|1|g' \ -e 's|@''HAVE_DECL_EXP2''@|1|g' \ -e 's|@''HAVE_DECL_EXP2F''@|1|g' \ -e 's|@''HAVE_DECL_EXP2L''@|1|g' \ -e 's|@''HAVE_DECL_EXPM1L''@|1|g' \ -e 's|@''HAVE_DECL_FLOORF''@|1|g' \ -e 's|@''HAVE_DECL_FLOORL''@|1|g' \ -e 's|@''HAVE_DECL_FREXPL''@|1|g' \ -e 's|@''HAVE_DECL_LDEXPL''@|1|g' \ -e 's|@''HAVE_DECL_LOGL''@|1|g' \ -e 's|@''HAVE_DECL_LOG10L''@|1|g' \ -e 's|@''HAVE_DECL_LOG2''@|1|g' \ -e 's|@''HAVE_DECL_LOG2F''@|1|g' \ -e 's|@''HAVE_DECL_LOG2L''@|1|g' \ -e 's|@''HAVE_DECL_LOGB''@|1|g' \ -e 's|@''HAVE_DECL_REMAINDER''@|1|g' \ -e 's|@''HAVE_DECL_REMAINDERL''@|1|g' \ -e 's|@''HAVE_DECL_RINTF''@|1|g' \ -e 's|@''HAVE_DECL_ROUND''@|1|g' \ -e 's|@''HAVE_DECL_ROUNDF''@|1|g' \ -e 's|@''HAVE_DECL_ROUNDL''@|1|g' \ -e 's|@''HAVE_DECL_SINL''@|1|g' \ -e 's|@''HAVE_DECL_SQRTL''@|1|g' \ -e 's|@''HAVE_DECL_TANL''@|1|g' \ -e 's|@''HAVE_DECL_TRUNC''@|1|g' \ -e 's|@''HAVE_DECL_TRUNCF''@|1|g' \ -e 's|@''HAVE_DECL_TRUNCL''@|1|g' \ | \ sed -e 's|@''REPLACE_ACOSF''@|0|g' \ -e 's|@''REPLACE_ASINF''@|0|g' \ -e 's|@''REPLACE_ATANF''@|0|g' \ -e 's|@''REPLACE_ATAN2F''@|0|g' \ -e 's|@''REPLACE_CBRTF''@|0|g' \ -e 's|@''REPLACE_CBRTL''@|0|g' \ -e 's|@''REPLACE_CEIL''@|0|g' \ -e 's|@''REPLACE_CEILF''@|0|g' \ -e 's|@''REPLACE_CEILL''@|0|g' \ -e 's|@''REPLACE_COSF''@|0|g' \ -e 's|@''REPLACE_COSHF''@|0|g' \ -e 's|@''REPLACE_EXPF''@|0|g' \ -e 's|@''REPLACE_EXPL''@|0|g' \ -e 's|@''REPLACE_EXPM1''@|0|g' \ -e 's|@''REPLACE_EXPM1F''@|0|g' \ -e 's|@''REPLACE_EXPM1L''@|0|g' \ -e 's|@''REPLACE_EXP2''@|0|g' \ -e 's|@''REPLACE_EXP2L''@|0|g' \ -e 's|@''REPLACE_FABSL''@|0|g' \ -e 's|@''REPLACE_FLOOR''@|0|g' \ -e 's|@''REPLACE_FLOORF''@|0|g' \ -e 's|@''REPLACE_FLOORL''@|0|g' \ -e 's|@''REPLACE_FMA''@|0|g' \ -e 's|@''REPLACE_FMAF''@|0|g' \ -e 's|@''REPLACE_FMAL''@|0|g' \ -e 's|@''REPLACE_FMOD''@|0|g' \ -e 's|@''REPLACE_FMODF''@|0|g' \ -e 's|@''REPLACE_FMODL''@|0|g' \ -e 's|@''REPLACE_FREXPF''@|0|g' \ -e 's|@''REPLACE_FREXP''@|0|g' \ -e 's|@''REPLACE_FREXPL''@|1|g' \ -e 's|@''REPLACE_HUGE_VAL''@|0|g' \ -e 's|@''REPLACE_HYPOT''@|0|g' \ -e 's|@''REPLACE_HYPOTF''@|0|g' \ -e 's|@''REPLACE_HYPOTL''@|0|g' \ -e 's|@''REPLACE_ILOGB''@|0|g' \ -e 's|@''REPLACE_ILOGBF''@|0|g' \ -e 's|@''REPLACE_ILOGBL''@|0|g' \ -e 's|@''REPLACE_ISFINITE''@|0|g' \ -e 's|@''REPLACE_ISINF''@|0|g' \ -e 's|@''REPLACE_ISNAN''@|0|g' \ -e 's|@''REPLACE_ITOLD''@|0|g' \ -e 's|@''REPLACE_LDEXPL''@|0|g' \ -e 's|@''REPLACE_LOG''@|0|g' \ -e 's|@''REPLACE_LOGF''@|0|g' \ -e 's|@''REPLACE_LOGL''@|0|g' \ -e 's|@''REPLACE_LOG10''@|0|g' \ -e 's|@''REPLACE_LOG10F''@|0|g' \ -e 's|@''REPLACE_LOG10L''@|0|g' \ -e 's|@''REPLACE_LOG1P''@|0|g' \ -e 's|@''REPLACE_LOG1PF''@|0|g' \ -e 's|@''REPLACE_LOG1PL''@|0|g' \ -e 's|@''REPLACE_LOG2''@|0|g' \ -e 's|@''REPLACE_LOG2F''@|0|g' \ -e 's|@''REPLACE_LOG2L''@|0|g' \ -e 's|@''REPLACE_LOGB''@|0|g' \ -e 's|@''REPLACE_LOGBF''@|0|g' \ -e 's|@''REPLACE_LOGBL''@|0|g' \ -e 's|@''REPLACE_MODF''@|0|g' \ -e 's|@''REPLACE_MODFF''@|0|g' \ -e 's|@''REPLACE_MODFL''@|0|g' \ -e 's|@''REPLACE_NAN''@|0|g' \ -e 's|@''REPLACE_REMAINDER''@|0|g' \ -e 's|@''REPLACE_REMAINDERF''@|0|g' \ -e 's|@''REPLACE_REMAINDERL''@|0|g' \ -e 's|@''REPLACE_RINTL''@|0|g' \ -e 's|@''REPLACE_ROUND''@|0|g' \ -e 's|@''REPLACE_ROUNDF''@|0|g' \ -e 's|@''REPLACE_ROUNDL''@|0|g' \ -e 's|@''REPLACE_SIGNBIT''@|0|g' \ -e 's|@''REPLACE_SIGNBIT_USING_BUILTINS''@|1|g' \ -e 's|@''REPLACE_SINF''@|0|g' \ -e 's|@''REPLACE_SINHF''@|0|g' \ -e 's|@''REPLACE_SQRTF''@|0|g' \ -e 's|@''REPLACE_SQRTL''@|0|g' \ -e 's|@''REPLACE_TANF''@|0|g' \ -e 's|@''REPLACE_TANHF''@|0|g' \ -e 's|@''REPLACE_TRUNC''@|0|g' \ -e 's|@''REPLACE_TRUNCF''@|0|g' \ -e 's|@''REPLACE_TRUNCL''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/math.h-t mv lib/math.h-t lib/math.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_NETDB_H''@||g' \ -e 's|@''HAVE_NETDB_H''@|1|g' \ -e 's/@''GNULIB_GETADDRINFO''@/1/g' \ -e 's|@''HAVE_STRUCT_ADDRINFO''@|1|g' \ -e 's|@''HAVE_DECL_FREEADDRINFO''@|1|g' \ -e 's|@''HAVE_DECL_GAI_STRERROR''@|1|g' \ -e 's|@''HAVE_DECL_GETADDRINFO''@|1|g' \ -e 's|@''HAVE_DECL_GETNAMEINFO''@|1|g' \ -e 's|@''REPLACE_GAI_STRERROR''@|0|g' \ -e 's|@''REPLACE_GETADDRINFO''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/netdb.in.h > lib/netdb.h-t mv lib/netdb.h-t lib/netdb.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_PTHREAD_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_PTHREAD_H''@||g' \ -e 's/@''GNULIB_PTHREAD_THREAD''@/1/g' \ -e 's/@''GNULIB_PTHREAD_ONCE''@/0/g' \ -e 's/@''GNULIB_PTHREAD_MUTEX''@/1/g' \ -e 's/@''GNULIB_PTHREAD_RWLOCK''@/0/g' \ -e 's/@''GNULIB_PTHREAD_COND''@/1/g' \ -e 's/@''GNULIB_PTHREAD_TSS''@/0/g' \ -e 's/@''GNULIB_PTHREAD_SPIN''@/0/g' \ -e 's/@''GNULIB_PTHREAD_MUTEX_TIMEDLOCK''@/1/g' \ -e 's|@''HAVE_PTHREAD_T''@|1|g' \ -e 's|@''HAVE_PTHREAD_SPINLOCK_T''@|0|g' \ -e 's|@''HAVE_PTHREAD_CREATE_DETACHED''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_RECURSIVE''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_ROBUST''@|0|g' \ -e 's|@''HAVE_PTHREAD_PROCESS_SHARED''@|1|g' \ -e 's|@''HAVE_PTHREAD_CREATE''@|1|g' \ -e 's|@''HAVE_PTHREAD_ATTR_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_ATTR_GETDETACHSTATE''@|1|g' \ -e 's|@''HAVE_PTHREAD_ATTR_SETDETACHSTATE''@|1|g' \ -e 's|@''HAVE_PTHREAD_ATTR_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_SELF''@|1|g' \ -e 's|@''HAVE_PTHREAD_EQUAL''@|1|g' \ -e 's|@''HAVE_PTHREAD_DETACH''@|1|g' \ -e 's|@''HAVE_PTHREAD_JOIN''@|1|g' \ -e 's|@''HAVE_PTHREAD_EXIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_ONCE''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEXATTR_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEXATTR_GETTYPE''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEXATTR_SETTYPE''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEXATTR_GETROBUST''@|0|g' \ -e 's|@''HAVE_PTHREAD_MUTEXATTR_SETROBUST''@|0|g' \ -e 's|@''HAVE_PTHREAD_MUTEXATTR_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_LOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_TRYLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_TIMEDLOCK''@|0|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_UNLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_MUTEX_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCKATTR_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCKATTR_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_RDLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_WRLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_TRYRDLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_TRYWRLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_TIMEDRDLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_TIMEDWRLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_UNLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_RWLOCK_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_COND_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_CONDATTR_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_CONDATTR_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_COND_WAIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_COND_TIMEDWAIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_COND_SIGNAL''@|1|g' \ -e 's|@''HAVE_PTHREAD_COND_BROADCAST''@|1|g' \ -e 's|@''HAVE_PTHREAD_COND_DESTROY''@|1|g' \ -e 's|@''HAVE_PTHREAD_KEY_CREATE''@|1|g' \ -e 's|@''HAVE_PTHREAD_SETSPECIFIC''@|1|g' \ -e 's|@''HAVE_PTHREAD_GETSPECIFIC''@|1|g' \ -e 's|@''HAVE_PTHREAD_KEY_DELETE''@|1|g' \ -e 's|@''HAVE_PTHREAD_SPIN_INIT''@|1|g' \ -e 's|@''HAVE_PTHREAD_SPIN_LOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_SPIN_TRYLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_SPIN_UNLOCK''@|1|g' \ -e 's|@''HAVE_PTHREAD_SPIN_DESTROY''@|1|g' \ < ./lib/pthread.in.h | \ sed -e 's|@''REPLACE_PTHREAD_CREATE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_ATTR_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_ATTR_GETDETACHSTATE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_ATTR_SETDETACHSTATE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_ATTR_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SELF''@|0|g' \ -e 's|@''REPLACE_PTHREAD_EQUAL''@|0|g' \ -e 's|@''REPLACE_PTHREAD_DETACH''@|0|g' \ -e 's|@''REPLACE_PTHREAD_JOIN''@|0|g' \ -e 's|@''REPLACE_PTHREAD_EXIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_ONCE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEX_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEXATTR_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEXATTR_GETTYPE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEXATTR_SETTYPE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEXATTR_GETROBUST''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEXATTR_SETROBUST''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEXATTR_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEX_LOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEX_TRYLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEX_TIMEDLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEX_UNLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_MUTEX_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCKATTR_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCKATTR_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_RDLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_WRLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_TRYRDLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_TRYWRLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_TIMEDRDLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_TIMEDWRLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_UNLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_RWLOCK_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_COND_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_CONDATTR_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_CONDATTR_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_COND_WAIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_COND_TIMEDWAIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_COND_SIGNAL''@|0|g' \ -e 's|@''REPLACE_PTHREAD_COND_BROADCAST''@|0|g' \ -e 's|@''REPLACE_PTHREAD_COND_DESTROY''@|0|g' \ -e 's|@''REPLACE_PTHREAD_KEY_CREATE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SETSPECIFIC''@|0|g' \ -e 's|@''REPLACE_PTHREAD_GETSPECIFIC''@|0|g' \ -e 's|@''REPLACE_PTHREAD_KEY_DELETE''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SPIN_INIT''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SPIN_LOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SPIN_TRYLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SPIN_UNLOCK''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SPIN_DESTROY''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _Noreturn/r ./lib/_Noreturn.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/pthread.h-t mv lib/pthread.h-t lib/pthread.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_SCHED_H''@|1|g' \ -e 's|@''HAVE_SYS_CDEFS_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SCHED_H''@||g' \ -e 's|@''HAVE_STRUCT_SCHED_PARAM''@|1|g' \ -e 's/@''GNULIB_SCHED_YIELD''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's|@''HAVE_SCHED_YIELD''@|1|g' \ -e 's|@''REPLACE_SCHED_YIELD''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sched.in.h > lib/sched.h-t mv lib/sched.h-t lib/sched.h /opt/local/bin/gmkdir -p 'lib/malloc' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|__always_inline|inline _GL_ATTRIBUTE_ALWAYS_INLINE|g' \ -e 's|__glibc_likely|_GL_LIKELY|g' \ -e 's|__glibc_unlikely|_GL_UNLIKELY|g' \ -e '/libc_hidden_proto/d' \ ./lib/malloc/scratch_buffer.h > lib/malloc/scratch_buffer.gl.h-t mv lib/malloc/scratch_buffer.gl.h-t lib/malloc/scratch_buffer.gl.h /opt/local/bin/gmkdir -p 'lib/selinux' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SELINUX_SELINUX_H''@||g' \ ./lib/se-selinux.in.h > lib/selinux/selinux.h-t mv lib/selinux/selinux.h-t lib/selinux/selinux.h /opt/local/bin/gmkdir -p 'lib/selinux' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/selinux/context.h-t' ./lib/se-context.in.h mv lib/selinux/context.h-t lib/selinux/context.h /opt/local/bin/gmkdir -p 'lib/selinux' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/selinux/label.h-t' ./lib/se-label.in.h mv lib/selinux/label.h-t lib/selinux/label.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SIGNAL_H''@||g' \ -e 's/@''GNULIB_PTHREAD_SIGMASK''@/1/g' \ -e 's/@''GNULIB_RAISE''@/1/g' \ -e 's/@''GNULIB_SIGNAL_H_SIGPIPE''@/0/g' \ -e 's/@''GNULIB_SIGPROCMASK''@/1/g' \ -e 's/@''GNULIB_SIGACTION''@/1/g' \ -e 's|@''HAVE_POSIX_SIGNALBLOCKING''@|1|g' \ -e 's|@''HAVE_PTHREAD_SIGMASK''@|1|g' \ -e 's|@''HAVE_RAISE''@|1|g' \ -e 's|@''HAVE_SIGSET_T''@|1|g' \ -e 's|@''HAVE_SIGINFO_T''@|1|g' \ -e 's|@''HAVE_SIGACTION''@|1|g' \ -e 's|@''HAVE_STRUCT_SIGACTION_SA_SIGACTION''@|1|g' \ -e 's|@''HAVE_TYPE_VOLATILE_SIG_ATOMIC_T''@|1|g' \ -e 's|@''HAVE_SIGHANDLER_T''@|0|g' \ -e 's|@''REPLACE_PTHREAD_SIGMASK''@|0|g' \ -e 's|@''REPLACE_RAISE''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/signal.in.h > lib/signal.h-t mv lib/signal.h-t lib/signal.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/stdalign.h-t' ./lib/stdalign.in.h mv lib/stdalign.h-t lib/stdalign.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_STDDEF_H''@||g' \ -e 's|@''HAVE_MAX_ALIGN_T''@|0|g' \ -e 's|@''HAVE_WCHAR_T''@|1|g' \ -e 's|@''REPLACE_NULL''@|0|g' \ ./lib/stddef.in.h > lib/stddef.h-t mv lib/stddef.h-t lib/stddef.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's/@''HAVE_STDINT_H''@/1/g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_STDINT_H''@||g' \ -e 's/@''HAVE_C99_STDINT_H''@/0/g' \ -e 's/@''HAVE_SYS_TYPES_H''@/1/g' \ -e 's/@''HAVE_INTTYPES_H''@/1/g' \ -e 's/@''HAVE_SYS_INTTYPES_H''@/0/g' \ -e 's/@''HAVE_SYS_BITYPES_H''@/0/g' \ -e 's/@''HAVE_WCHAR_H''@/1/g' \ -e 's/@''APPLE_UNIVERSAL_BUILD''@/0/g' \ -e 's/@''BITSIZEOF_PTRDIFF_T''@/32/g' \ -e 's/@''PTRDIFF_T_SUFFIX''@//g' \ -e 's/@''BITSIZEOF_SIG_ATOMIC_T''@/32/g' \ -e 's/@''HAVE_SIGNED_SIG_ATOMIC_T''@/1/g' \ -e 's/@''SIG_ATOMIC_T_SUFFIX''@//g' \ -e 's/@''BITSIZEOF_SIZE_T''@/32/g' \ -e 's/@''SIZE_T_SUFFIX''@/ul/g' \ -e 's/@''BITSIZEOF_WCHAR_T''@/32/g' \ -e 's/@''HAVE_SIGNED_WCHAR_T''@/1/g' \ -e 's/@''WCHAR_T_SUFFIX''@//g' \ -e 's/@''BITSIZEOF_WINT_T''@/32/g' \ -e 's/@''HAVE_SIGNED_WINT_T''@/1/g' \ -e 's/@''WINT_T_SUFFIX''@//g' \ -e 's/@''GNULIBHEADERS_OVERRIDE_WINT_T''@/0/g' \ ./lib/stdint.in.h > lib/stdint.h-t mv lib/stdint.h-t lib/stdint.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_STDIO_H''@||g' \ -e 's/@''GNULIB_DPRINTF''@/0/g' \ -e 's/@''GNULIB_FCLOSE''@/1/g' \ -e 's/@''GNULIB_FDOPEN''@/1/g' \ -e 's/@''GNULIB_FFLUSH''@/1/g' \ -e 's/@''GNULIB_FGETC''@/1/g' \ -e 's/@''GNULIB_FGETS''@/1/g' \ -e 's/@''GNULIB_FOPEN''@/1/g' \ -e 's/@''GNULIB_FOPEN_GNU''@/0/g' \ -e 's/@''GNULIB_FPRINTF''@/1/g' \ -e 's/@''GNULIB_FPRINTF_POSIX''@/0/g' \ -e 's/@''GNULIB_FPURGE''@/1/g' \ -e 's/@''GNULIB_FPUTC''@/1/g' \ -e 's/@''GNULIB_FPUTS''@/1/g' \ -e 's/@''GNULIB_FREAD''@/1/g' \ -e 's/@''GNULIB_FREOPEN''@/1/g' \ -e 's/@''GNULIB_FSCANF''@/1/g' \ -e 's/@''GNULIB_FSEEK''@/1/g' \ -e 's/@''GNULIB_FSEEKO''@/1/g' \ -e 's/@''GNULIB_FTELL''@/1/g' \ -e 's/@''GNULIB_FTELLO''@/1/g' \ -e 's/@''GNULIB_FWRITE''@/1/g' \ -e 's/@''GNULIB_GETC''@/1/g' \ -e 's/@''GNULIB_GETCHAR''@/1/g' \ -e 's/@''GNULIB_GETDELIM''@/1/g' \ -e 's/@''GNULIB_GETLINE''@/1/g' \ -e 's/@''GNULIB_OBSTACK_PRINTF''@/0/g' \ -e 's/@''GNULIB_OBSTACK_PRINTF_POSIX''@/0/g' \ -e 's/@''GNULIB_PCLOSE''@/0/g' \ -e 's/@''GNULIB_PERROR''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_POPEN''@/0/g' \ -e 's/@''GNULIB_PRINTF''@/1/g' \ -e 's/@''GNULIB_PRINTF_POSIX''@/0/g' \ -e 's/@''GNULIB_PUTC''@/1/g' \ -e 's/@''GNULIB_PUTCHAR''@/1/g' \ -e 's/@''GNULIB_PUTS''@/1/g' \ -e 's/@''GNULIB_REMOVE''@/1/g' \ -e 's/@''GNULIB_RENAME''@/1/g' \ -e 's/@''GNULIB_RENAMEAT''@/1/g' \ -e 's/@''GNULIB_SCANF''@/1/g' \ -e 's/@''GNULIB_SNPRINTF''@/1/g' \ -e 's/@''GNULIB_SPRINTF_POSIX''@/0/g' \ -e 's/@''GNULIB_STDIO_H_NONBLOCKING''@/0/g' \ -e 's/@''GNULIB_STDIO_H_SIGPIPE''@/0/g' \ -e 's/@''GNULIB_TMPFILE''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_VASPRINTF''@/1/g' \ -e 's/@''GNULIB_VDPRINTF''@/0/g' \ -e 's/@''GNULIB_VFPRINTF''@/1/g' \ -e 's/@''GNULIB_VFPRINTF_POSIX''@/1/g' \ -e 's/@''GNULIB_VFSCANF''@/0/g' \ -e 's/@''GNULIB_VSCANF''@/0/g' \ -e 's/@''GNULIB_VPRINTF''@/1/g' \ -e 's/@''GNULIB_VPRINTF_POSIX''@/1/g' \ -e 's/@''GNULIB_VSNPRINTF''@/0/g' \ -e 's/@''GNULIB_VSPRINTF_POSIX''@/0/g' \ -e 's/@''GNULIB_MDA_FCLOSEALL''@/1/g' \ -e 's/@''GNULIB_MDA_FDOPEN''@/1/g' \ -e 's/@''GNULIB_MDA_FILENO''@/1/g' \ -e 's/@''GNULIB_MDA_GETW''@/1/g' \ -e 's/@''GNULIB_MDA_PUTW''@/1/g' \ -e 's/@''GNULIB_MDA_TEMPNAM''@/1/g' \ < ./lib/stdio.in.h | \ sed -e 's|@''HAVE_DECL_FCLOSEALL''@|0|g' \ -e 's|@''HAVE_DECL_FPURGE''@|1|g' \ -e 's|@''HAVE_DECL_FSEEKO''@|1|g' \ -e 's|@''HAVE_DECL_FTELLO''@|1|g' \ ? -e 's|@''HAVE_DECL_GETDELIM''@|0|g' \ ? -e 's|@''HAVE_DECL_GETLINE''@|0|g' \ -e 's|@''HAVE_DECL_OBSTACK_PRINTF''@|1|g' \ -e 's|@''HAVE_DECL_SNPRINTF''@|1|g' \ -e 's|@''HAVE_DECL_VSNPRINTF''@|1|g' \ -e 's|@''HAVE_DPRINTF''@|1|g' \ -e 's|@''HAVE_FSEEKO''@|1|g' \ -e 's|@''HAVE_FTELLO''@|1|g' \ -e 's|@''HAVE_PCLOSE''@|1|g' \ -e 's|@''HAVE_POPEN''@|1|g' \ ? -e 's|@''HAVE_RENAMEAT''@|0|g' \ -e 's|@''HAVE_VASPRINTF''@|1|g' \ -e 's|@''HAVE_VDPRINTF''@|1|g' \ -e 's|@''REPLACE_DPRINTF''@|0|g' \ -e 's|@''REPLACE_FCLOSE''@|1|g' \ -e 's|@''REPLACE_FDOPEN''@|0|g' \ -e 's|@''REPLACE_FFLUSH''@|1|g' \ -e 's|@''REPLACE_FOPEN''@|0|g' \ -e 's|@''REPLACE_FOPEN_FOR_FOPEN_GNU''@|1|g' \ -e 's|@''REPLACE_FPRINTF''@|0|g' \ -e 's|@''REPLACE_FPURGE''@|1|g' \ -e 's|@''REPLACE_FREOPEN''@|0|g' \ -e 's|@''REPLACE_FSEEK''@|1|g' \ -e 's|@''REPLACE_FSEEKO''@|1|g' \ -e 's|@''REPLACE_FTELL''@|0|g' \ -e 's|@''REPLACE_FTELLO''@|0|g' \ -e 's|@''REPLACE_GETDELIM''@|0|g' \ ? -e 's|@''REPLACE_GETLINE''@|1|g' \ -e 's|@''REPLACE_OBSTACK_PRINTF''@|0|g' \ -e 's|@''REPLACE_PERROR''@|1|g' \ -e 's|@''REPLACE_POPEN''@|0|g' \ -e 's|@''REPLACE_PRINTF''@|0|g' \ -e 's|@''REPLACE_REMOVE''@|1|g' \ -e 's|@''REPLACE_RENAME''@|1|g' \ ? -e 's|@''REPLACE_RENAMEAT''@|0|g' \ -e 's|@''REPLACE_SNPRINTF''@|0|g' \ -e 's|@''REPLACE_SPRINTF''@|0|g' \ -e 's|@''REPLACE_STDIO_READ_FUNCS''@|0|g' \ -e 's|@''REPLACE_STDIO_WRITE_FUNCS''@|0|g' \ -e 's|@''REPLACE_TMPFILE''@|0|g' \ -e 's|@''REPLACE_VASPRINTF''@|1|g' \ -e 's|@''REPLACE_VDPRINTF''@|0|g' \ -e 's|@''REPLACE_VFPRINTF''@|1|g' \ -e 's|@''REPLACE_VPRINTF''@|1|g' \ -e 's|@''REPLACE_VSNPRINTF''@|0|g' \ -e 's|@''REPLACE_VSPRINTF''@|0|g' \ -e 's|@''ASM_SYMBOL_PREFIX''@||g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/stdio.h-t mv lib/stdio.h-t lib/stdio.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_STDLIB_H''@||g' \ -e 's/@''GNULIB__EXIT''@/0/g' \ -e 's/@''GNULIB_ALIGNED_ALLOC''@/0/g' \ -e 's/@''GNULIB_ATOLL''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_CALLOC_GNU''@/1/g' \ -e 's/@''GNULIB_CALLOC_POSIX''@/1/g' \ -e 's/@''GNULIB_CANONICALIZE_FILE_NAME''@/1/g' \ -e 's/@''GNULIB_FREE_POSIX''@/1/g' \ -e 's/@''GNULIB_GETLOADAVG''@/1/g' \ -e 's/@''GNULIB_GETSUBOPT''@/0/g' \ -e 's/@''GNULIB_GRANTPT''@/0/g' \ -e 's/@''GNULIB_MALLOC_GNU''@/1/g' \ -e 's/@''GNULIB_MALLOC_POSIX''@/1/g' \ -e 's/@''GNULIB_MBTOWC''@/1/g' \ -e 's/@''GNULIB_MKDTEMP''@/0/g' \ -e 's/@''GNULIB_MKOSTEMP''@/1/g' \ -e 's/@''GNULIB_MKOSTEMPS''@/0/g' \ -e 's/@''GNULIB_MKSTEMP''@/1/g' \ -e 's/@''GNULIB_MKSTEMPS''@/0/g' \ -e 's/@''GNULIB_POSIX_MEMALIGN''@/1/g' \ -e 's/@''GNULIB_POSIX_OPENPT''@/0/g' \ -e 's/@''GNULIB_PTSNAME''@/0/g' \ -e 's/@''GNULIB_PTSNAME_R''@/0/g' \ -e 's/@''GNULIB_PUTENV''@/1/g' \ -e 's/@''GNULIB_QSORT_R''@/0/g' \ -e 's/@''GNULIB_RANDOM''@/0/g' \ -e 's/@''GNULIB_RANDOM_R''@/0/g' \ -e 's/@''GNULIB_REALLOC_GNU''@/1/g' \ -e 's/@''GNULIB_REALLOC_POSIX''@/1/g' \ -e 's/@''GNULIB_REALLOCARRAY''@/1/g' \ -e 's/@''GNULIB_REALPATH''@/0/g' \ -e 's/@''GNULIB_RPMATCH''@/1/g' \ -e 's/@''GNULIB_SECURE_GETENV''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_SETENV''@/1/g' \ -e 's/@''GNULIB_STRTOD''@/1/g' \ -e 's/@''GNULIB_STRTOL''@/0/g' \ -e 's/@''GNULIB_STRTOLD''@/1/g' \ -e 's/@''GNULIB_STRTOLL''@/1/g' \ -e 's/@''GNULIB_STRTOUL''@/0/g' \ -e 's/@''GNULIB_STRTOULL''@/1/g' \ -e 's/@''GNULIB_SYSTEM_POSIX''@/0/g' \ -e 's/@''GNULIB_UNLOCKPT''@/0/g' \ -e 's/@''GNULIB_UNSETENV''@/1/g' \ -e 's/@''GNULIB_WCTOMB''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_MDA_ECVT''@/1/g' \ -e 's/@''GNULIB_MDA_FCVT''@/1/g' \ -e 's/@''GNULIB_MDA_GCVT''@/1/g' \ -e 's/@''GNULIB_MDA_MKTEMP''@/1/g' \ -e 's/@''GNULIB_MDA_PUTENV''@/1/g' \ < ./lib/stdlib.in.h | \ sed -e 's|@''HAVE__EXIT''@|1|g' \ -e 's|@''HAVE_ALIGNED_ALLOC''@|1|g' \ -e 's|@''HAVE_ATOLL''@|1|g' \ -e 's|@''HAVE_CANONICALIZE_FILE_NAME''@|0|g' \ -e 's|@''HAVE_DECL_ECVT''@|1|g' \ -e 's|@''HAVE_DECL_FCVT''@|1|g' \ -e 's|@''HAVE_DECL_GCVT''@|1|g' \ -e 's|@''HAVE_DECL_GETLOADAVG''@|1|g' \ -e 's|@''HAVE_GETSUBOPT''@|1|g' \ -e 's|@''HAVE_GRANTPT''@|1|g' \ -e 's|@''HAVE_INITSTATE''@|1|g' \ -e 's|@''HAVE_DECL_INITSTATE''@|1|g' \ -e 's|@''HAVE_MBTOWC''@|1|g' \ -e 's|@''HAVE_MKDTEMP''@|1|g' \ -e 's|@''HAVE_MKOSTEMP''@|0|g' \ -e 's|@''HAVE_MKOSTEMPS''@|1|g' \ -e 's|@''HAVE_MKSTEMP''@|1|g' \ -e 's|@''HAVE_MKSTEMPS''@|1|g' \ ? -e 's|@''HAVE_POSIX_MEMALIGN''@|0|g' \ -e 's|@''HAVE_POSIX_OPENPT''@|1|g' \ -e 's|@''HAVE_PTSNAME''@|1|g' \ -e 's|@''HAVE_PTSNAME_R''@|1|g' \ -e 's|@''HAVE_QSORT_R''@|1|g' \ -e 's|@''HAVE_RANDOM''@|1|g' \ -e 's|@''HAVE_RANDOM_H''@|1|g' \ -e 's|@''HAVE_RANDOM_R''@|1|g' \ -e 's|@''HAVE_REALLOCARRAY''@|0|g' \ -e 's|@''HAVE_REALPATH''@|1|g' \ -e 's|@''HAVE_RPMATCH''@|0|g' \ -e 's|@''HAVE_SECURE_GETENV''@|0|g' \ -e 's|@''HAVE_DECL_SETENV''@|1|g' \ -e 's|@''HAVE_SETSTATE''@|1|g' \ -e 's|@''HAVE_DECL_SETSTATE''@|1|g' \ -e 's|@''HAVE_STRTOD''@|1|g' \ -e 's|@''HAVE_STRTOL''@|1|g' \ -e 's|@''HAVE_STRTOLD''@|1|g' \ -e 's|@''HAVE_STRTOLL''@|1|g' \ -e 's|@''HAVE_STRTOUL''@|1|g' \ -e 's|@''HAVE_STRTOULL''@|1|g' \ -e 's|@''HAVE_STRUCT_RANDOM_DATA''@|1|g' \ -e 's|@''HAVE_SYS_LOADAVG_H''@|0|g' \ -e 's|@''HAVE_UNLOCKPT''@|1|g' \ -e 's|@''HAVE_DECL_UNSETENV''@|1|g' \ -e 's|@''REPLACE_ALIGNED_ALLOC''@|0|g' \ -e 's|@''REPLACE_CALLOC_FOR_CALLOC_GNU''@|1|g' \ -e 's|@''REPLACE_CALLOC_FOR_CALLOC_POSIX''@|1|g' \ -e 's|@''REPLACE_CANONICALIZE_FILE_NAME''@|0|g' \ -e 's|@''REPLACE_FREE''@|1|g' \ -e 's|@''REPLACE_INITSTATE''@|0|g' \ -e 's|@''REPLACE_MALLOC_FOR_MALLOC_GNU''@|1|g' \ -e 's|@''REPLACE_MALLOC_FOR_MALLOC_POSIX''@|1|g' \ -e 's|@''REPLACE_MBTOWC''@|0|g' \ -e 's|@''REPLACE_MKSTEMP''@|0|g' \ -e 's|@''REPLACE_POSIX_MEMALIGN''@|0|g' \ -e 's|@''REPLACE_PTSNAME''@|0|g' \ -e 's|@''REPLACE_PTSNAME_R''@|0|g' \ -e 's|@''REPLACE_PUTENV''@|1|g' \ -e 's|@''REPLACE_QSORT_R''@|0|g' \ -e 's|@''REPLACE_RANDOM''@|0|g' \ -e 's|@''REPLACE_RANDOM_R''@|0|g' \ -e 's|@''REPLACE_REALLOC_FOR_REALLOC_GNU''@|0|g' \ -e 's|@''REPLACE_REALLOC_FOR_REALLOC_POSIX''@|1|g' \ -e 's|@''REPLACE_REALLOCARRAY''@|0|g' \ -e 's|@''REPLACE_REALPATH''@|0|g' \ -e 's|@''REPLACE_SETENV''@|1|g' \ -e 's|@''REPLACE_SETSTATE''@|0|g' \ -e 's|@''REPLACE_STRTOD''@|1|g' \ -e 's|@''REPLACE_STRTOL''@|0|g' \ -e 's|@''REPLACE_STRTOLD''@|1|g' \ -e 's|@''REPLACE_STRTOLL''@|1|g' \ -e 's|@''REPLACE_STRTOUL''@|0|g' \ -e 's|@''REPLACE_STRTOULL''@|1|g' \ -e 's|@''REPLACE_UNSETENV''@|0|g' \ -e 's|@''REPLACE_WCTOMB''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _Noreturn/r ./lib/_Noreturn.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/stdlib.h-t mv lib/stdlib.h-t lib/stdlib.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_STRING_H''@||g' \ -e 's/@''GNULIB_EXPLICIT_BZERO''@/1/g' \ -e 's/@''GNULIB_FFSL''@/0/g' \ -e 's/@''GNULIB_FFSLL''@/0/g' \ -e 's/@''GNULIB_MBSLEN''@/1/g' \ -e 's/@''GNULIB_MBSNLEN''@/0/g' \ -e 's/@''GNULIB_MBSCHR''@/1/g' \ -e 's/@''GNULIB_MBSRCHR''@/0/g' \ -e 's/@''GNULIB_MBSSTR''@/1/g' \ -e 's/@''GNULIB_MBSCASECMP''@/1/g' \ -e 's/@''GNULIB_MBSNCASECMP''@/0/g' \ -e 's/@''GNULIB_MBSPCASECMP''@/0/g' \ -e 's/@''GNULIB_MBSCASESTR''@/0/g' \ -e 's/@''GNULIB_MBSCSPN''@/0/g' \ -e 's/@''GNULIB_MBSPBRK''@/0/g' \ -e 's/@''GNULIB_MBSSPN''@/0/g' \ -e 's/@''GNULIB_MBSSEP''@/0/g' \ -e 's/@''GNULIB_MBSTOK_R''@/0/g' \ -e 's/@''GNULIB_MEMCHR''@/1/g' \ -e 's/@''GNULIB_MEMMEM''@/0/g' \ -e 's/@''GNULIB_MEMPCPY''@/1/g' \ -e 's/@''GNULIB_MEMRCHR''@/1/g' \ -e 's/@''GNULIB_RAWMEMCHR''@/1/g' \ -e 's/@''GNULIB_STPCPY''@/1/g' \ -e 's/@''GNULIB_STPNCPY''@/1/g' \ -e 's/@''GNULIB_STRCHRNUL''@/0/g' \ -e 's/@''GNULIB_STRDUP''@/1/g' \ -e 's/@''GNULIB_STRNCAT''@/1/g' \ -e 's/@''GNULIB_STRNDUP''@/0/g' \ -e 's/@''GNULIB_STRNLEN''@/1/g' \ -e 's/@''GNULIB_STRPBRK''@/0/g' \ -e 's/@''GNULIB_STRSEP''@/0/g' \ -e 's/@''GNULIB_STRSTR''@/1/g' \ -e 's/@''GNULIB_STRCASESTR''@/0/g' \ -e 's/@''GNULIB_STRTOK_R''@/0/g' \ -e 's/@''GNULIB_STRERROR''@/1/g' \ -e 's/@''GNULIB_STRERROR_R''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_STRERRORNAME_NP''@/0/g' \ -e 's/@''GNULIB_SIGABBREV_NP''@/0/g' \ -e 's/@''GNULIB_SIGDESCR_NP''@/0/g' \ -e 's/@''GNULIB_STRSIGNAL''@/1/g' \ -e 's/@''GNULIB_STRVERSCMP''@/0/g' \ -e 's/@''GNULIB_MDA_MEMCCPY''@/1/g' \ -e 's/@''GNULIB_MDA_STRDUP''@/1/g' \ -e 's/@''GNULIB_FREE_POSIX''@/1/g' \ < ./lib/string.in.h | \ sed -e 's|@''HAVE_EXPLICIT_BZERO''@|0|g' \ -e 's|@''HAVE_FFSL''@|1|g' \ -e 's|@''HAVE_FFSLL''@|1|g' \ -e 's|@''HAVE_MBSLEN''@|0|g' \ -e 's|@''HAVE_DECL_MEMMEM''@|1|g' \ -e 's|@''HAVE_MEMPCPY''@|0|g' \ -e 's|@''HAVE_DECL_MEMRCHR''@|0|g' \ -e 's|@''HAVE_RAWMEMCHR''@|0|g' \ -e 's|@''HAVE_STPCPY''@|1|g' \ -e 's|@''HAVE_STPNCPY''@|0|g' \ -e 's|@''HAVE_STRCHRNUL''@|1|g' \ -e 's|@''HAVE_DECL_STRDUP''@|1|g' \ -e 's|@''HAVE_DECL_STRNDUP''@|1|g' \ ? -e 's|@''HAVE_DECL_STRNLEN''@|0|g' \ -e 's|@''HAVE_STRPBRK''@|1|g' \ -e 's|@''HAVE_STRSEP''@|1|g' \ -e 's|@''HAVE_STRCASESTR''@|1|g' \ -e 's|@''HAVE_DECL_STRTOK_R''@|1|g' \ -e 's|@''HAVE_DECL_STRERROR_R''@|1|g' \ -e 's|@''HAVE_STRERRORNAME_NP''@|1|g' \ -e 's|@''HAVE_SIGABBREV_NP''@|1|g' \ -e 's|@''HAVE_SIGDESCR_NP''@|1|g' \ -e 's|@''HAVE_DECL_STRSIGNAL''@|1|g' \ -e 's|@''HAVE_STRVERSCMP''@|1|g' \ -e 's|@''REPLACE_FFSLL''@|0|g' \ -e 's|@''REPLACE_MEMCHR''@|0|g' \ -e 's|@''REPLACE_MEMMEM''@|0|g' \ -e 's|@''REPLACE_FREE''@|1|g' \ -e 's|@''REPLACE_STPNCPY''@|0|g' \ -e 's|@''REPLACE_STRCHRNUL''@|0|g' \ -e 's|@''REPLACE_STRDUP''@|0|g' \ -e 's|@''REPLACE_STRNCAT''@|0|g' \ -e 's|@''REPLACE_STRNDUP''@|0|g' \ -e 's|@''REPLACE_STRNLEN''@|0|g' \ -e 's|@''REPLACE_STRSTR''@|0|g' \ -e 's|@''REPLACE_STRCASESTR''@|0|g' \ -e 's|@''REPLACE_STRTOK_R''@|0|g' \ -e 's|@''REPLACE_STRERROR''@|1|g' \ -e 's|@''REPLACE_STRERROR_R''@|1|g' \ -e 's|@''REPLACE_STRERRORNAME_NP''@|0|g' \ -e 's|@''REPLACE_STRSIGNAL''@|0|g' \ -e 's|@''UNDEFINE_STRTOK_R''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/string.h-t mv lib/string.h-t lib/string.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_SYS_IOCTL_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_IOCTL_H''@||g' \ -e 's/@''GNULIB_IOCTL''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's|@''SYS_IOCTL_H_HAVE_WINSOCK2_H''@|0|g' \ -e 's|@''SYS_IOCTL_H_HAVE_WINSOCK2_H_AND_USE_SOCKETS''@|0|g' \ -e 's|@''REPLACE_IOCTL''@|1|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_ioctl.in.h > lib/sys/ioctl.h-t mv lib/sys/ioctl.h-t lib/sys/ioctl.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_RANDOM_H''@||g' \ -e 's|@''HAVE_SYS_RANDOM_H''@|1|g' \ -e 's/@''GNULIB_GETRANDOM''@/1/g' \ -e 's/@''HAVE_GETRANDOM''@/0/g' \ -e 's/@''REPLACE_GETRANDOM''@/0/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_random.in.h > lib/sys/random.h-t mv lib/sys/random.h-t lib/sys/random.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_RESOURCE_H''@||g' \ -e 's|@''HAVE_SYS_RESOURCE_H''@|1|g' \ -e 's/@''GNULIB_GETRUSAGE''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''HAVE_GETRUSAGE''@/1/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_resource.in.h > lib/sys/resource.h-t mv lib/sys/resource.h-t lib/sys/resource.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_SELECT_H''@||g' \ -e 's|@''HAVE_SYS_SELECT_H''@|1|g' \ -e 's/@''GNULIB_PSELECT''@/1/g' \ -e 's/@''GNULIB_SELECT''@/1/g' \ -e 's|@''HAVE_WINSOCK2_H''@|0|g' \ -e 's|@''HAVE_PSELECT''@|1|g' \ -e 's|@''REPLACE_PSELECT''@|0|g' \ -e 's|@''REPLACE_SELECT''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_select.in.h > lib/sys/select.h-t mv lib/sys/select.h-t lib/sys/select.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_SOCKET_H''@||g' \ -e 's|@''HAVE_SYS_SOCKET_H''@|1|g' \ -e 's/@''GNULIB_CLOSE''@/1/g' \ -e 's/@''GNULIB_SOCKET''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_CONNECT''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_ACCEPT''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_BIND''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_GETPEERNAME''@/0/g' \ -e 's/@''GNULIB_GETSOCKNAME''@/0/g' \ -e 's/@''GNULIB_GETSOCKOPT''@/0/g' \ -e 's/@''GNULIB_LISTEN''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_RECV''@/0/g' \ -e 's/@''GNULIB_SEND''@/0/g' \ -e 's/@''GNULIB_RECVFROM''@/0/g' \ -e 's/@''GNULIB_SENDTO''@/0/g' \ -e 's/@''GNULIB_SETSOCKOPT''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_SHUTDOWN''@/0/g' \ -e 's/@''GNULIB_ACCEPT4''@/0/g' \ -e 's|@''HAVE_WINSOCK2_H''@|0|g' \ -e 's|@''HAVE_WS2TCPIP_H''@|0|g' \ -e 's|@''HAVE_STRUCT_SOCKADDR_STORAGE''@|1|g' \ -e 's|@''HAVE_STRUCT_SOCKADDR_STORAGE_SS_FAMILY''@|1|g' \ -e 's|@''HAVE_SA_FAMILY_T''@|1|g' \ -e 's|@''HAVE_ACCEPT4''@|1|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_socket.in.h > lib/sys/socket.h-t mv lib/sys/socket.h-t lib/sys/socket.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_STAT_H''@||g' \ -e 's|@''WINDOWS_64_BIT_ST_SIZE''@|0|g' \ -e 's|@''WINDOWS_STAT_TIMESPEC''@|0|g' \ -e 's/@''GNULIB_FCHMODAT''@/1/g' \ -e 's/@''GNULIB_FSTAT''@/1/g' \ -e 's/@''GNULIB_FSTATAT''@/1/g' \ -e 's/@''GNULIB_FUTIMENS''@/1/g' \ -e 's/@''GNULIB_GETUMASK''@/0/g' \ -e 's/@''GNULIB_LCHMOD''@/1/g' \ -e 's/@''GNULIB_LSTAT''@/1/g' \ -e 's/@''GNULIB_MKDIR''@/1/g' \ -e 's/@''GNULIB_MKDIRAT''@/1/g' \ -e 's/@''GNULIB_MKFIFO''@/1/g' \ -e 's/@''GNULIB_MKFIFOAT''@/1/g' \ -e 's/@''GNULIB_MKNOD''@/1/g' \ -e 's/@''GNULIB_MKNODAT''@/1/g' \ -e 's/@''GNULIB_STAT''@/1/g' \ -e 's/@''GNULIB_UTIMENSAT''@/1/g' \ -e 's/@''GNULIB_OVERRIDES_STRUCT_STAT''@/0/g' \ -e 's/@''GNULIB_MDA_CHMOD''@/1/g' \ -e 's/@''GNULIB_MDA_MKDIR''@/1/g' \ -e 's/@''GNULIB_MDA_UMASK''@/1/g' \ ? -e 's|@''HAVE_FCHMODAT''@|0|g' \ ? -e 's|@''HAVE_FSTATAT''@|0|g' \ ? -e 's|@''HAVE_FUTIMENS''@|0|g' \ -e 's|@''HAVE_GETUMASK''@|1|g' \ -e 's|@''HAVE_LCHMOD''@|1|g' \ -e 's|@''HAVE_LSTAT''@|1|g' \ ? -e 's|@''HAVE_MKDIRAT''@|0|g' \ -e 's|@''HAVE_MKFIFO''@|1|g' \ -e 's|@''HAVE_MKFIFOAT''@|0|g' \ -e 's|@''HAVE_MKNOD''@|1|g' \ -e 's|@''HAVE_MKNODAT''@|0|g' \ ? -e 's|@''HAVE_UTIMENSAT''@|0|g' \ -e 's|@''REPLACE_FCHMODAT''@|0|g' \ -e 's|@''REPLACE_FSTAT''@|0|g' \ ? -e 's|@''REPLACE_FSTATAT''@|0|g' \ ? -e 's|@''REPLACE_FUTIMENS''@|0|g' \ -e 's|@''REPLACE_LSTAT''@|1|g' \ -e 's|@''REPLACE_MKDIR''@|0|g' \ -e 's|@''REPLACE_MKFIFO''@|1|g' \ -e 's|@''REPLACE_MKFIFOAT''@|0|g' \ -e 's|@''REPLACE_MKNOD''@|1|g' \ -e 's|@''REPLACE_MKNODAT''@|0|g' \ -e 's|@''REPLACE_STAT''@|1|g' \ ? -e 's|@''REPLACE_UTIMENSAT''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_stat.in.h > lib/sys/stat.h-t mv lib/sys/stat.h-t lib/sys/stat.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's/@''HAVE_SYS_TIME_H''@/1/g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_TIME_H''@||g' \ -e 's/@''GNULIB_GETTIMEOFDAY''@/1/g' \ -e 's|@''HAVE_WINSOCK2_H''@|0|g' \ -e 's/@''HAVE_GETTIMEOFDAY''@/1/g' \ -e 's/@''HAVE_STRUCT_TIMEVAL''@/1/g' \ -e 's/@''REPLACE_GETTIMEOFDAY''@/0/g' \ -e 's/@''REPLACE_STRUCT_TIMEVAL''@/0/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_time.in.h > lib/sys/time.h-t mv lib/sys/time.h-t lib/sys/time.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_TYPES_H''@||g' \ -e 's|@''WINDOWS_64_BIT_OFF_T''@|0|g' \ -e 's|@''WINDOWS_STAT_INODES''@|0|g' \ ./lib/sys_types.in.h > lib/sys/types.h-t mv lib/sys/types.h-t lib/sys/types.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_UIO_H''@||g' \ -e 's|@''HAVE_SYS_UIO_H''@|1|g' \ ./lib/sys_uio.in.h > lib/sys/uio.h-t mv lib/sys/uio.h-t lib/sys/uio.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's/@''HAVE_SYS_UTSNAME_H''@/1/g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_UTSNAME_H''@||g' \ -e 's/@''GNULIB_UNAME''@/1/g' \ -e 's|@''HAVE_STRUCT_UTSNAME''@|1|g' \ -e 's|@''HAVE_UNAME''@|1|g' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_utsname.in.h > lib/sys/utsname.h-t mv lib/sys/utsname.h-t lib/sys/utsname.h /opt/local/bin/gmkdir -p 'lib/sys' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_SYS_WAIT_H''@||g' \ -e 's/@''GNULIB_WAITPID''@/0/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/sys_wait.in.h > lib/sys/wait.h-t mv lib/sys/wait.h-t lib/sys/wait.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_TERMIOS_H''@||g' \ -e 's/@''GNULIB_TCGETSID''@/0/g' \ -e 's|@''HAVE_DECL_TCGETSID''@|1|g' \ -e 's|@''HAVE_TERMIOS_H''@|1|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/termios.in.h > lib/termios.h-t mv lib/termios.h-t lib/termios.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_TIME_H''@||g' \ -e 's/@''GNULIB_CTIME''@/0/g' \ -e 's/@''GNULIB_LOCALTIME''@/0/g' \ -e 's/@''GNULIB_MKTIME''@/1/g' \ -e 's/@''GNULIB_NANOSLEEP''@/1/g' \ -e 's/@''GNULIB_STRFTIME''@/0/g' \ -e 's/@''GNULIB_STRPTIME''@/0/g' \ -e 's/@''GNULIB_TIMEGM''@/1/g' \ -e 's/@''GNULIB_TIMESPEC_GET''@/0/g' \ -e 's/@''GNULIB_TIMESPEC_GETRES''@/0/g' \ -e 's/@''GNULIB_TIME_R''@/1/g' \ -e 's/@''GNULIB_TIME_RZ''@/1/g' \ -e 's/@''GNULIB_TZSET''@/1/g' \ -e 's/@''GNULIB_MDA_TZSET''@/1/g' \ -e 's|@''HAVE_DECL_LOCALTIME_R''@|1|g' \ -e 's|@''HAVE_NANOSLEEP''@|1|g' \ -e 's|@''HAVE_STRPTIME''@|1|g' \ -e 's|@''HAVE_TIMEGM''@|1|g' \ -e 's|@''HAVE_TIMESPEC_GET''@|1|g' \ -e 's|@''HAVE_TIMESPEC_GETRES''@|1|g' \ -e 's|@''HAVE_TIMEZONE_T''@|0|g' \ -e 's|@''REPLACE_CTIME''@|GNULIB_PORTCHECK|g' \ -e 's|@''REPLACE_GMTIME''@|0|g' \ -e 's|@''REPLACE_LOCALTIME''@|0|g' \ -e 's|@''REPLACE_LOCALTIME_R''@|0|g' \ -e 's|@''REPLACE_MKTIME''@|0|g' \ -e 's|@''REPLACE_NANOSLEEP''@|0|g' \ -e 's|@''REPLACE_STRFTIME''@|GNULIB_PORTCHECK|g' \ -e 's|@''REPLACE_TIMEGM''@|0|g' \ -e 's|@''REPLACE_TZSET''@|0|g' \ -e 's|@''PTHREAD_H_DEFINES_STRUCT_TIMESPEC''@|0|g' \ -e 's|@''SYS_TIME_H_DEFINES_STRUCT_TIMESPEC''@|0|g' \ -e 's|@''TIME_H_DEFINES_STRUCT_TIMESPEC''@|1|g' \ -e 's|@''UNISTD_H_DEFINES_STRUCT_TIMESPEC''@|0|g' \ ? -e 's|@''TIME_H_DEFINES_TIME_UTC''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/time.in.h > lib/time.h-t mv lib/time.h-t lib/time.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''HAVE_UNISTD_H''@|1|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_UNISTD_H''@||g' \ -e 's|@''WINDOWS_64_BIT_OFF_T''@|0|g' \ -e 's/@''GNULIB_ACCESS''@/0/g' \ -e 's/@''GNULIB_CHDIR''@/1/g' \ -e 's/@''GNULIB_CHOWN''@/1/g' \ -e 's/@''GNULIB_CLOSE''@/1/g' \ -e 's/@''GNULIB_COPY_FILE_RANGE''@/1/g' \ -e 's/@''GNULIB_DUP''@/1/g' \ -e 's/@''GNULIB_DUP2''@/1/g' \ -e 's/@''GNULIB_DUP3''@/0/g' \ -e 's/@''GNULIB_ENVIRON''@/1/g' \ -e 's/@''GNULIB_EUIDACCESS''@/1/g' \ -e 's/@''GNULIB_EXECL''@/0/g' \ -e 's/@''GNULIB_EXECLE''@/0/g' \ -e 's/@''GNULIB_EXECLP''@/0/g' \ -e 's/@''GNULIB_EXECV''@/0/g' \ -e 's/@''GNULIB_EXECVE''@/0/g' \ -e 's/@''GNULIB_EXECVP''@/0/g' \ -e 's/@''GNULIB_EXECVPE''@/0/g' \ -e 's/@''GNULIB_FACCESSAT''@/1/g' \ -e 's/@''GNULIB_FCHDIR''@/1/g' \ -e 's/@''GNULIB_FCHOWNAT''@/1/g' \ -e 's/@''GNULIB_FDATASYNC''@/1/g' \ -e 's/@''GNULIB_FSYNC''@/1/g' \ -e 's/@''GNULIB_FTRUNCATE''@/1/g' \ -e 's/@''GNULIB_GETCWD''@/1/g' \ -e 's/@''GNULIB_GETDOMAINNAME''@/0/g' \ -e 's/@''GNULIB_GETDTABLESIZE''@/1/g' \ -e 's/@''GNULIB_GETENTROPY''@/0/g' \ -e 's/@''GNULIB_GETGROUPS''@/1/g' \ -e 's/@''GNULIB_GETHOSTNAME''@/1/g' \ -e 's/@''GNULIB_GETLOGIN''@/1/g' \ -e 's/@''GNULIB_GETLOGIN_R''@/0/g' \ -e 's/@''GNULIB_GETOPT_POSIX''@/1/g' \ -e 's/@''GNULIB_GETPAGESIZE''@/1/g' \ -e 's/@''GNULIB_GETPASS''@/1/g' \ -e 's/@''GNULIB_GETPASS_GNU''@/1/g' \ -e 's/@''GNULIB_GETUSERSHELL''@/1/g' \ -e 's/@''GNULIB_GROUP_MEMBER''@/1/g' \ -e 's/@''GNULIB_ISATTY''@/1/g' \ -e 's/@''GNULIB_LCHOWN''@/1/g' \ -e 's/@''GNULIB_LINK''@/1/g' \ -e 's/@''GNULIB_LINKAT''@/1/g' \ -e 's/@''GNULIB_LSEEK''@/1/g' \ -e 's/@''GNULIB_PIPE''@/1/g' \ -e 's/@''GNULIB_PIPE2''@/1/g' \ -e 's/@''GNULIB_PREAD''@/0/g' \ -e 's/@''GNULIB_PWRITE''@/0/g' \ -e 's/@''GNULIB_READ''@/1/g' \ -e 's/@''GNULIB_READLINK''@/1/g' \ -e 's/@''GNULIB_READLINKAT''@/1/g' \ -e 's/@''GNULIB_RMDIR''@/1/g' \ -e 's/@''GNULIB_SETHOSTNAME''@/0/g' \ -e 's/@''GNULIB_SLEEP''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_SYMLINK''@/1/g' \ -e 's/@''GNULIB_SYMLINKAT''@/1/g' \ -e 's/@''GNULIB_TRUNCATE''@/0/g' \ -e 's/@''GNULIB_TTYNAME_R''@/0/g' \ -e 's/@''GNULIB_UNISTD_H_GETOPT''@/01/g' \ -e 's/@''GNULIB_UNISTD_H_NONBLOCKING''@/0/g' \ -e 's/@''GNULIB_UNISTD_H_SIGPIPE''@/0/g' \ -e 's/@''GNULIB_UNLINK''@/1/g' \ -e 's/@''GNULIB_UNLINKAT''@/1/g' \ -e 's/@''GNULIB_USLEEP''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_WRITE''@/1/g' \ -e 's/@''GNULIB_MDA_ACCESS''@/1/g' \ -e 's/@''GNULIB_MDA_CHDIR''@/1/g' \ -e 's/@''GNULIB_MDA_CLOSE''@/1/g' \ -e 's/@''GNULIB_MDA_DUP''@/1/g' \ -e 's/@''GNULIB_MDA_DUP2''@/1/g' \ -e 's/@''GNULIB_MDA_EXECL''@/1/g' \ -e 's/@''GNULIB_MDA_EXECLE''@/1/g' \ -e 's/@''GNULIB_MDA_EXECLP''@/1/g' \ -e 's/@''GNULIB_MDA_EXECV''@/1/g' \ -e 's/@''GNULIB_MDA_EXECVE''@/1/g' \ -e 's/@''GNULIB_MDA_EXECVP''@/1/g' \ -e 's/@''GNULIB_MDA_EXECVPE''@/1/g' \ -e 's/@''GNULIB_MDA_GETCWD''@/1/g' \ -e 's/@''GNULIB_MDA_GETPID''@/1/g' \ -e 's/@''GNULIB_MDA_ISATTY''@/1/g' \ -e 's/@''GNULIB_MDA_LSEEK''@/1/g' \ -e 's/@''GNULIB_MDA_READ''@/1/g' \ -e 's/@''GNULIB_MDA_RMDIR''@/1/g' \ -e 's/@''GNULIB_MDA_SWAB''@/1/g' \ -e 's/@''GNULIB_MDA_UNLINK''@/1/g' \ -e 's/@''GNULIB_MDA_WRITE''@/1/g' \ < ./lib/unistd.in.h | \ sed -e 's|@''HAVE_CHOWN''@|1|g' \ -e 's|@''HAVE_COPY_FILE_RANGE''@|0|g' \ -e 's|@''HAVE_DUP3''@|1|g' \ -e 's|@''HAVE_EUIDACCESS''@|0|g' \ -e 's|@''HAVE_EXECVPE''@|1|g' \ ? -e 's|@''HAVE_FACCESSAT''@|0|g' \ -e 's|@''HAVE_FCHDIR''@|1|g' \ ? -e 's|@''HAVE_FCHOWNAT''@|0|g' \ -e 's|@''HAVE_FDATASYNC''@|0|g' \ -e 's|@''HAVE_FSYNC''@|1|g' \ -e 's|@''HAVE_FTRUNCATE''@|1|g' \ -e 's|@''HAVE_GETDTABLESIZE''@|1|g' \ -e 's|@''HAVE_GETENTROPY''@|1|g' \ -e 's|@''HAVE_GETGROUPS''@|1|g' \ -e 's|@''HAVE_GETHOSTNAME''@|1|g' \ -e 's|@''HAVE_GETPAGESIZE''@|1|g' \ -e 's|@''HAVE_GETPASS''@|1|g' \ -e 's|@''HAVE_GROUP_MEMBER''@|0|g' \ -e 's|@''HAVE_LCHOWN''@|1|g' \ -e 's|@''HAVE_LINK''@|1|g' \ ? -e 's|@''HAVE_LINKAT''@|0|g' \ -e 's|@''HAVE_PIPE''@|1|g' \ -e 's|@''HAVE_PIPE2''@|0|g' \ -e 's|@''HAVE_PREAD''@|1|g' \ -e 's|@''HAVE_PWRITE''@|1|g' \ -e 's|@''HAVE_READLINK''@|1|g' \ ? -e 's|@''HAVE_READLINKAT''@|0|g' \ -e 's|@''HAVE_SETHOSTNAME''@|1|g' \ -e 's|@''HAVE_SLEEP''@|1|g' \ -e 's|@''HAVE_SYMLINK''@|1|g' \ ? -e 's|@''HAVE_SYMLINKAT''@|0|g' \ ? -e 's|@''HAVE_UNLINKAT''@|0|g' \ -e 's|@''HAVE_USLEEP''@|1|g' \ -e 's|@''HAVE_DECL_ENVIRON''@|0|g' \ -e 's|@''HAVE_DECL_EXECVPE''@|0|g' \ -e 's|@''HAVE_DECL_FCHDIR''@|1|g' \ -e 's|@''HAVE_DECL_FDATASYNC''@|0|g' \ -e 's|@''HAVE_DECL_GETDOMAINNAME''@|1|g' \ -e 's|@''HAVE_DECL_GETLOGIN''@|1|g' \ -e 's|@''HAVE_DECL_GETLOGIN_R''@|1|g' \ -e 's|@''HAVE_DECL_GETPAGESIZE''@|1|g' \ -e 's|@''HAVE_DECL_GETUSERSHELL''@|1|g' \ -e 's|@''HAVE_DECL_SETHOSTNAME''@|1|g' \ -e 's|@''HAVE_DECL_TRUNCATE''@|1|g' \ -e 's|@''HAVE_DECL_TTYNAME_R''@|1|g' \ -e 's|@''HAVE_OS_H''@|0|g' \ -e 's|@''HAVE_SYS_PARAM_H''@|0|g' \ | \ sed -e 's|@''REPLACE_ACCESS''@|0|g' \ -e 's|@''REPLACE_CHOWN''@|1|g' \ -e 's|@''REPLACE_CLOSE''@|0|g' \ -e 's|@''REPLACE_COPY_FILE_RANGE''@|0|g' \ -e 's|@''REPLACE_DUP''@|0|g' \ -e 's|@''REPLACE_DUP2''@|0|g' \ -e 's|@''REPLACE_EXECL''@|0|g' \ -e 's|@''REPLACE_EXECLE''@|0|g' \ -e 's|@''REPLACE_EXECLP''@|0|g' \ -e 's|@''REPLACE_EXECV''@|0|g' \ -e 's|@''REPLACE_EXECVE''@|0|g' \ -e 's|@''REPLACE_EXECVP''@|0|g' \ -e 's|@''REPLACE_EXECVPE''@|0|g' \ ? -e 's|@''REPLACE_FACCESSAT''@|0|g' \ ? -e 's|@''REPLACE_FCHOWNAT''@|0|g' \ -e 's|@''REPLACE_FTRUNCATE''@|0|g' \ -e 's|@''REPLACE_GETCWD''@|0|g' \ -e 's|@''REPLACE_GETDOMAINNAME''@|0|g' \ -e 's|@''REPLACE_GETDTABLESIZE''@|0|g' \ -e 's|@''REPLACE_GETLOGIN_R''@|0|g' \ -e 's|@''REPLACE_GETGROUPS''@|0|g' \ -e 's|@''REPLACE_GETPAGESIZE''@|0|g' \ -e 's|@''REPLACE_GETPASS''@|0|g' \ -e 's|@''REPLACE_GETPASS_FOR_GETPASS_GNU''@|1|g' \ -e 's|@''REPLACE_ISATTY''@|0|g' \ -e 's|@''REPLACE_LCHOWN''@|1|g' \ -e 's|@''REPLACE_LINK''@|1|g' \ ? -e 's|@''REPLACE_LINKAT''@|0|g' \ -e 's|@''REPLACE_LSEEK''@|1|g' \ -e 's|@''REPLACE_PREAD''@|0|g' \ -e 's|@''REPLACE_PWRITE''@|0|g' \ -e 's|@''REPLACE_READ''@|0|g' \ -e 's|@''REPLACE_READLINK''@|1|g' \ ? -e 's|@''REPLACE_READLINKAT''@|0|g' \ -e 's|@''REPLACE_RMDIR''@|0|g' \ -e 's|@''REPLACE_SLEEP''@|0|g' \ -e 's|@''REPLACE_SYMLINK''@|1|g' \ ? -e 's|@''REPLACE_SYMLINKAT''@|0|g' \ -e 's|@''REPLACE_TRUNCATE''@|0|g' \ -e 's|@''REPLACE_TTYNAME_R''@|0|g' \ -e 's|@''REPLACE_UNLINK''@|1|g' \ ? -e 's|@''REPLACE_UNLINKAT''@|0|g' \ -e 's|@''REPLACE_USLEEP''@|0|g' \ -e 's|@''REPLACE_WRITE''@|0|g' \ -e 's|@''UNISTD_H_HAVE_SYS_RANDOM_H''@|1|g' \ -e 's|@''UNISTD_H_HAVE_WINSOCK2_H''@|0|g' \ -e 's|@''UNISTD_H_HAVE_WINSOCK2_H_AND_USE_SOCKETS''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/unistd.h-t mv lib/unistd.h-t lib/unistd.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/unistr.h-t' ./lib/unistr.in.h mv lib/unistr.h-t lib/unistr.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/unitypes.h-t' ./lib/unitypes.in.h mv lib/unitypes.h-t lib/unitypes.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G -n -e 'w lib/uniwidth.h-t' ./lib/uniwidth.in.h mv lib/uniwidth.h-t lib/uniwidth.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's/@''HAVE_UTIME_H''@/1/g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_UTIME_H''@||g' \ -e 's/@''GNULIB_UTIME''@/1/g' \ -e 's/@''GNULIB_MDA_UTIME''@/1/g' \ -e 's|@''HAVE_UTIME''@|1|g' \ -e 's|@''REPLACE_UTIME''@|1|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/utime.in.h > lib/utime.h-t mv lib/utime.h-t lib/utime.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''HAVE_FEATURES_H''@|0|g' \ -e 's|@''NEXT_WCHAR_H''@||g' \ -e 's|@''HAVE_WCHAR_H''@|1|g' \ -e 's/@''HAVE_CRTDEFS_H''@/0/g' \ -e 's/@''GNULIBHEADERS_OVERRIDE_WINT_T''@/0/g' \ -e 's/@''GNULIB_BTOWC''@/1/g' \ -e 's/@''GNULIB_WCTOB''@/IN_COREUTILS_GNULIB_TESTS/g' \ -e 's/@''GNULIB_MBSINIT''@/1/g' \ -e 's/@''GNULIB_MBRTOWC''@/1/g' \ -e 's/@''GNULIB_MBRLEN''@/1/g' \ -e 's/@''GNULIB_MBSRTOWCS''@/1/g' \ -e 's/@''GNULIB_MBSNRTOWCS''@/0/g' \ -e 's/@''GNULIB_WCRTOMB''@/1/g' \ -e 's/@''GNULIB_WCSRTOMBS''@/0/g' \ -e 's/@''GNULIB_WCSNRTOMBS''@/0/g' \ -e 's/@''GNULIB_WCWIDTH''@/1/g' \ -e 's/@''GNULIB_WMEMCHR''@/1/g' \ -e 's/@''GNULIB_WMEMCMP''@/0/g' \ -e 's/@''GNULIB_WMEMCPY''@/0/g' \ -e 's/@''GNULIB_WMEMMOVE''@/0/g' \ -e 's/@''GNULIB_WMEMPCPY''@/1/g' \ -e 's/@''GNULIB_WMEMSET''@/0/g' \ -e 's/@''GNULIB_WCSLEN''@/0/g' \ -e 's/@''GNULIB_WCSNLEN''@/0/g' \ -e 's/@''GNULIB_WCSCPY''@/0/g' \ -e 's/@''GNULIB_WCPCPY''@/0/g' \ -e 's/@''GNULIB_WCSNCPY''@/0/g' \ -e 's/@''GNULIB_WCPNCPY''@/0/g' \ -e 's/@''GNULIB_WCSCAT''@/0/g' \ -e 's/@''GNULIB_WCSNCAT''@/0/g' \ -e 's/@''GNULIB_WCSCMP''@/0/g' \ -e 's/@''GNULIB_WCSNCMP''@/0/g' \ -e 's/@''GNULIB_WCSCASECMP''@/0/g' \ -e 's/@''GNULIB_WCSNCASECMP''@/0/g' \ -e 's/@''GNULIB_WCSCOLL''@/0/g' \ -e 's/@''GNULIB_WCSXFRM''@/0/g' \ -e 's/@''GNULIB_WCSDUP''@/0/g' \ -e 's/@''GNULIB_WCSCHR''@/0/g' \ -e 's/@''GNULIB_WCSRCHR''@/0/g' \ -e 's/@''GNULIB_WCSCSPN''@/0/g' \ -e 's/@''GNULIB_WCSSPN''@/0/g' \ -e 's/@''GNULIB_WCSPBRK''@/0/g' \ -e 's/@''GNULIB_WCSSTR''@/0/g' \ -e 's/@''GNULIB_WCSTOK''@/0/g' \ -e 's/@''GNULIB_WCSWIDTH''@/1/g' \ -e 's/@''GNULIB_WCSFTIME''@/0/g' \ -e 's/@''GNULIB_MDA_WCSDUP''@/1/g' \ -e 's/@''GNULIB_FREE_POSIX''@/1/g' \ < ./lib/wchar.in.h | \ sed -e 's|@''HAVE_WINT_T''@|1|g' \ -e 's|@''HAVE_BTOWC''@|1|g' \ -e 's|@''HAVE_MBSINIT''@|1|g' \ -e 's|@''HAVE_MBRTOWC''@|1|g' \ -e 's|@''HAVE_MBRLEN''@|1|g' \ -e 's|@''HAVE_MBSRTOWCS''@|1|g' \ -e 's|@''HAVE_MBSNRTOWCS''@|1|g' \ -e 's|@''HAVE_WCRTOMB''@|1|g' \ -e 's|@''HAVE_WCSRTOMBS''@|1|g' \ -e 's|@''HAVE_WCSNRTOMBS''@|1|g' \ -e 's|@''HAVE_WMEMCHR''@|1|g' \ -e 's|@''HAVE_WMEMCMP''@|1|g' \ -e 's|@''HAVE_WMEMCPY''@|1|g' \ -e 's|@''HAVE_WMEMMOVE''@|1|g' \ -e 's|@''HAVE_WMEMPCPY''@|0|g' \ -e 's|@''HAVE_WMEMSET''@|1|g' \ -e 's|@''HAVE_WCSLEN''@|1|g' \ -e 's|@''HAVE_WCSNLEN''@|1|g' \ -e 's|@''HAVE_WCSCPY''@|1|g' \ -e 's|@''HAVE_WCPCPY''@|1|g' \ -e 's|@''HAVE_WCSNCPY''@|1|g' \ -e 's|@''HAVE_WCPNCPY''@|1|g' \ -e 's|@''HAVE_WCSCAT''@|1|g' \ -e 's|@''HAVE_WCSNCAT''@|1|g' \ -e 's|@''HAVE_WCSCMP''@|1|g' \ -e 's|@''HAVE_WCSNCMP''@|1|g' \ -e 's|@''HAVE_WCSCASECMP''@|1|g' \ -e 's|@''HAVE_WCSNCASECMP''@|1|g' \ -e 's|@''HAVE_WCSCOLL''@|1|g' \ -e 's|@''HAVE_WCSXFRM''@|1|g' \ -e 's|@''HAVE_WCSDUP''@|1|g' \ -e 's|@''HAVE_WCSCHR''@|1|g' \ -e 's|@''HAVE_WCSRCHR''@|1|g' \ -e 's|@''HAVE_WCSCSPN''@|1|g' \ -e 's|@''HAVE_WCSSPN''@|1|g' \ -e 's|@''HAVE_WCSPBRK''@|1|g' \ -e 's|@''HAVE_WCSSTR''@|1|g' \ -e 's|@''HAVE_WCSTOK''@|1|g' \ -e 's|@''HAVE_WCSWIDTH''@|1|g' \ -e 's|@''HAVE_WCSFTIME''@|1|g' \ -e 's|@''HAVE_DECL_WCTOB''@|1|g' \ ? -e 's|@''HAVE_DECL_WCSDUP''@|0|g' \ -e 's|@''HAVE_DECL_WCWIDTH''@|1|g' \ | \ sed -e 's|@''REPLACE_MBSTATE_T''@|0|g' \ -e 's|@''REPLACE_BTOWC''@|0|g' \ -e 's|@''REPLACE_WCTOB''@|0|g' \ -e 's|@''REPLACE_FREE''@|1|g' \ -e 's|@''REPLACE_MBSINIT''@|0|g' \ -e 's|@''REPLACE_MBRTOWC''@|0|g' \ -e 's|@''REPLACE_MBRLEN''@|0|g' \ -e 's|@''REPLACE_MBSRTOWCS''@|0|g' \ -e 's|@''REPLACE_MBSNRTOWCS''@|0|g' \ -e 's|@''REPLACE_WCRTOMB''@|0|g' \ -e 's|@''REPLACE_WCSRTOMBS''@|0|g' \ -e 's|@''REPLACE_WCSNRTOMBS''@|0|g' \ -e 's|@''REPLACE_WCWIDTH''@|1|g' \ -e 's|@''REPLACE_WCSWIDTH''@|1|g' \ -e 's|@''REPLACE_WCSFTIME''@|0|g' \ -e 's|@''REPLACE_WCSTOK''@|0|g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_ARG_NONNULL/r ./lib/arg-nonnull.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ > lib/wchar.h-t mv lib/wchar.h-t lib/wchar.h /opt/local/bin/gmkdir -p 'lib' sed -e 1h -e '1s,.*,/* DO NOT EDIT! GENERATED AUTOMATICALLY! */,' -e 1G \ -e 's|@''GUARD_PREFIX''@|GL|g' \ -e 's/@''HAVE_WCTYPE_H''@/1/g' \ -e 's|@''INCLUDE_NEXT''@|include_next|g' \ -e 's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' \ -e 's|@''PRAGMA_COLUMNS''@||g' \ -e 's|@''NEXT_WCTYPE_H''@||g' \ -e 's/@''HAVE_CRTDEFS_H''@/0/g' \ -e 's/@''GNULIBHEADERS_OVERRIDE_WINT_T''@/0/g' \ -e 's/@''GNULIB_ISWBLANK''@/1/g' \ -e 's/@''GNULIB_ISWDIGIT''@/1/g' \ -e 's/@''GNULIB_ISWXDIGIT''@/1/g' \ -e 's/@''GNULIB_WCTYPE''@/0/g' \ -e 's/@''GNULIB_ISWCTYPE''@/0/g' \ -e 's/@''GNULIB_WCTRANS''@/0/g' \ -e 's/@''GNULIB_TOWCTRANS''@/0/g' \ -e 's/@''HAVE_ISWBLANK''@/1/g' \ -e 's/@''HAVE_ISWCNTRL''@/1/g' \ -e 's/@''HAVE_WCTYPE_T''@/1/g' \ -e 's/@''HAVE_WCTRANS_T''@/1/g' \ -e 's/@''HAVE_WINT_T''@/1/g' \ -e 's/@''REPLACE_ISWBLANK''@/0/g' \ -e 's/@''REPLACE_ISWDIGIT''@/0/g' \ -e 's/@''REPLACE_ISWXDIGIT''@/0/g' \ -e 's/@''REPLACE_ISWCNTRL''@/0/g' \ -e 's/@''REPLACE_TOWLOWER''@/0/g' \ -e '/definitions of _GL_FUNCDECL_RPL/r ./lib/c++defs.h' \ -e '/definition of _GL_WARN_ON_USE/r ./lib/warn-on-use.h' \ ./lib/wctype.in.h > lib/wctype.h-t mv lib/wctype.h-t lib/wctype.h rm -f src/coreutils.h /opt/local/bin/gmkdir -p src for prog in x ; do \ test $prog = x && continue; \ prog=`basename $prog`; \ main=`echo $prog | tr '[' '_'`; \ echo "SINGLE_BINARY_PROGRAM(\"$prog\", $main)"; \ done | sort > src/coreutils.ht }}} Is it worth to add Legacy Support here? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 16:10:45 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 16:10:45 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.14a19f04d5aa9a737c391bd69d844769@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by mascguy): Replying to [comment:3 artkiver]: > To be honest, I am not entirely sure why there are three separate FFmpeg ports especially since two of them are both an older version? `ffmpeg-upstream` tracks the latest release (currently 5.x). While `ffmpeg-devel` is used to validate pending changes to `ffmpeg`, before rolling out to everyone. So yes, this is intentional. > I suppose a ffmpeg-minimal is another possibility, but creating a 4th Portfile, when it seems as if it might be better to clean up the existing 3 separate, yet very closely related, ports might make more sense? We've considered various options, including adding more variants. But that quickly becomes a testing nightmare, due to the sheer number of combinations. In short, there's simply no way to please everyone. Even today, there are open enhancement requests to add still more functionality. So while you may prefer something simplified, that's at odds with others. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 16:17:59 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 16:17:59 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.f45c6eccedae21d7cdaebbc621e8319d@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by kencu): clearly, I?m with Chris here. Rust is inevitable these days. Most users will just download the prebuilt ffmpeg binary, and never need to install rust anyway. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 16:58:49 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 16:58:49 -0000 Subject: [MacPorts] #66475: Build coreutils with Legacy Support? In-Reply-To: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> References: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> Message-ID: <061.dd5afbc89f8f603f3b961000c838df63@macports.org> #66475: Build coreutils with Legacy Support? --------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard, tiger Port: coreutils | --------------------------+---------------------------- Comment (by kencu): It looks like coreutils uses GNULIB fallbacks very nicely, instead of LegacySupport fallbacks, if LegacySupport is not used. Other than that, I can't see too much difference. Did you spot there anything that you would see as a new functionality in coreutils that LegacySupport would provide that the existing GNULIB fallback does not provide? Otherwise, not much reason to use LegacySupport over GNULIB, I think. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:00:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:00:42 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.e8be74bbcd8c4f43c85b6174e569ec65@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by artkiver): Replying to [comment:6 mascguy]: > Replying to [comment:3 artkiver]: > > To be honest, I am not entirely sure why there are three separate FFmpeg ports especially since two of them are both an older version? > > `ffmpeg-upstream` tracks the latest release (currently 5.x). While `ffmpeg-devel` is used to validate pending changes to `ffmpeg`, before rolling out to everyone. > > So yes, this is intentional. Thank you for that clarification. I guess the delineation still makes zero sense to me, given that ffmpeg-devel is still public; and "rolling out to everyone" seems as if it would be a nomenclature perhaps more suitable for private branches and repositories than something within the MacPorts system? At least in the instance of libressl as contrasted with libressl-devel, that appears to be related to the upstream project tagging some releases as Development and some releases as Stable; so it's a nomenclature from the upstream project, rather than an artifact of MacPorts' maintainer methodologies. Nonetheless, it's your bailiwick. I already offered one possible alternative. I do not think a preference for minimalism and adherence to upstream defaults is an unusual preference, but I am not here to pick a battle. > > I suppose a ffmpeg-minimal is another possibility, but creating a 4th Portfile, when it seems as if it might be better to clean up the existing 3 separate, yet very closely related, ports might make more sense? > > We've considered various options, including adding more variants. But that quickly becomes a testing nightmare, due to the sheer number of combinations. > > In short, there's simply no way to please everyone. Even today, there are open enhancement requests to add still more functionality. > > So while you may prefer something simplified, that's at odds with others. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:01:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:01:09 -0000 Subject: [MacPorts] #63636: new version of auto-multiple-choice-devel fails to run In-Reply-To: <047.751097bcc773bec0f5440891650f7899@macports.org> References: <047.751097bcc773bec0f5440891650f7899@macports.org> Message-ID: <062.7ac38cb42266127a765dde1e3fe5aa05@macports.org> #63636: new version of auto-multiple-choice-devel fails to run -----------------------------------------+---------------------- Reporter: jmgoicolea | Owner: nortcele Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: auto-multiple-choice-devel | -----------------------------------------+---------------------- Changes (by mascguy): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:7 jmgoicolea]: > Many thanks, the workaround you suggest for setting perl5-30 as default seems to work fine! Great, closing as fixed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:05:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:05:27 -0000 Subject: [MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? In-Reply-To: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> References: <045.b507a3dc3e950bd08a0fa5d1ea2e1252@macports.org> Message-ID: <060.94ca5fb9daf5f5b0741af729c0adddf8@macports.org> #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this? --------------------------+-------------------- Reporter: artkiver | Owner: (none) Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ffmpeg | --------------------------+-------------------- Comment (by artkiver): Replying to [comment:7 kencu]: > clearly, I?m with Chris here. > > Rust is inevitable these days. > > Most users will just download the prebuilt binaries, and never need to install rust anyway. > > You got caught up in building rust because the Ventura builder was a bit delayed. So, if I am interpreting this correctly, the implication is I hit an edge case because Apple Silicon binaries had not yet been generated by the buildbots? Out of curiosity: what parameters are the buildbots using to generate such binaries? Is it different than %port install ffmpeg ? It would be nice to know if I can generate similar binaries locally. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:14:12 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:14:12 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave Message-ID: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave ---------------------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: gtk3 NetSurf Mojave | Port: gtk3 ---------------------------------+-------------------- Unsuccessful NetSurf build due to (at least) gtk3 build fail. macOS 10.14.6 w/ Xcode 11.3.1 on Macmini6,2 (NetSurf build on macOS 10.8.5 w/ Xcode 5.1.1 on Macmini5,2 appears successful, I just don't know how to use gtk applications and can't get NetSurf to launch, "can't open display.") {{{ libtool: compile: /usr/bin/clang -arch x86_64 -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DG_LOG_USE_STRUCTURED=1 -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk -fvisibility=hidden -DG_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -DGLIB_MIN_REQUIRED_VERSION=GLIB_VERSION_2_56 -DGLIB_MAX_ALLOWED_VERSION=GLIB_VERSION_2_58 -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/cairo -I/opt/local/include/gio-unix-2.0 -I/opt/local/include/cairo -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include/fribidi -I/opt/local/include -DX_LOCALE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -pipe -Os -fstrict-aliasing -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -arch x86_64 -Wall -MT gdkdevicemanager-xi2.lo -MD -MP -MF .deps /gdkdevicemanager-xi2.Tpo -c gdkdevicemanager-xi2.c -o gdkdevicemanager- xi2.o >/dev/null 2>&1 make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk/x11' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk' make[2]: *** [all] Error 2 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34" && /usr/bin/make -j8 -w all CC="/usr/bin/clang -arch x86_64" CC_FOR_BUILD="/usr/bin/clang -arch x86_64" V=1 CPP_FOR_BUILD="/usr/bin/cpp" Exit code: 2 Error: Failed to build gtk3: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port NetSurf failed }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:14:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:14:42 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.97127e941ad6b6a6faa71e8075fa898c@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Changes (by chillin-): * Attachment "main.log" added. Mojave gtk3 main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:16:14 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:16:14 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.9957493faf3d50b4248c654939140a21@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Description changed by chillin-: Old description: > Unsuccessful NetSurf build due to (at least) gtk3 build fail. > > macOS 10.14.6 w/ Xcode 11.3.1 on Macmini6,2 > > (NetSurf build on macOS 10.8.5 w/ Xcode 5.1.1 on Macmini5,2 appears > successful, I just don't know how to use gtk applications and can't get > NetSurf to launch, "can't open display.") > > {{{ > libtool: compile: /usr/bin/clang -arch x86_64 -DHAVE_CONFIG_H -I. > -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DG_LOG_USE_STRUCTURED=1 -DGDK_COMPILATION > -I../.. -I../../gdk -I../../gdk -fvisibility=hidden -DG_ENABLE_DEBUG > -DG_DISABLE_CAST_CHECKS -DGLIB_MIN_REQUIRED_VERSION=GLIB_VERSION_2_56 > -DGLIB_MAX_ALLOWED_VERSION=GLIB_VERSION_2_58 > -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz > -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz > -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/cairo > -I/opt/local/include/gio-unix-2.0 -I/opt/local/include/cairo > -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include > -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 > -I/opt/local/include/libpng16 -I/opt/local/include/fribidi > -I/opt/local/include -DX_LOCALE > -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -pipe > -Os -fstrict-aliasing > -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -arch > x86_64 -Wall -MT gdkdevicemanager-xi2.lo -MD -MP -MF .deps > /gdkdevicemanager-xi2.Tpo -c gdkdevicemanager-xi2.c -o gdkdevicemanager- > xi2.o >/dev/null 2>&1 > make[4]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk/x11' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk' > make[2]: *** [all] Error 2 > make[2]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34' > make: *** [all] Error 2 > make: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34' > Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34" > && /usr/bin/make -j8 -w all CC="/usr/bin/clang -arch x86_64" > CC_FOR_BUILD="/usr/bin/clang -arch x86_64" V=1 > CPP_FOR_BUILD="/usr/bin/cpp" > Exit code: 2 > Error: Failed to build gtk3: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > Error: Processing of port NetSurf failed > }}} New description: Unsuccessful NetSurf build due to (at least) gtk3 build fail. macOS 10.14.6 w/ Xcode 11.3.1 on Macmini6,2 (NetSurf build on OS X 10.8.5 w/ Xcode 5.1.1 on Macmini5,2 appears successful, I just don't know how to use gtk applications and can't get NetSurf to launch, "can't open display.") {{{ libtool: compile: /usr/bin/clang -arch x86_64 -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DG_LOG_USE_STRUCTURED=1 -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk -fvisibility=hidden -DG_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -DGLIB_MIN_REQUIRED_VERSION=GLIB_VERSION_2_56 -DGLIB_MAX_ALLOWED_VERSION=GLIB_VERSION_2_58 -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz -I/opt/local/include/pango-1.0 -I/opt/local/include/harfbuzz -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/cairo -I/opt/local/include/gio-unix-2.0 -I/opt/local/include/cairo -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include/fribidi -I/opt/local/include -DX_LOCALE -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -pipe -Os -fstrict-aliasing -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -arch x86_64 -Wall -MT gdkdevicemanager-xi2.lo -MD -MP -MF .deps /gdkdevicemanager-xi2.Tpo -c gdkdevicemanager-xi2.c -o gdkdevicemanager- xi2.o >/dev/null 2>&1 make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk/x11' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk' make[2]: *** [all] Error 2 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34/gdk' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/work/gtk+-3.24.34" && /usr/bin/make -j8 -w all CC="/usr/bin/clang -arch x86_64" CC_FOR_BUILD="/usr/bin/clang -arch x86_64" V=1 CPP_FOR_BUILD="/usr/bin/cpp" Exit code: 2 Error: Failed to build gtk3: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gtk3/gtk3/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port NetSurf failed }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:24:35 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:24:35 -0000 Subject: [MacPorts] #66473: plantuml failing to build on Ventura 13.1 In-Reply-To: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> References: <049.10e83d4cc25ff09332b4ce23e0d7d3c6@macports.org> Message-ID: <064.53ac31f8f03743fca528b6ed9b17fab9@macports.org> #66473: plantuml failing to build on Ventura 13.1 ---------------------------+-------------------- Reporter: kickingvegas | Owner: judaew Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: plantuml | ---------------------------+-------------------- Changes (by Vadym-Valdis Yudaiev ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"2935a63e7eca3c593741b090e2d5be5cd78f762a/macports-ports" 2935a63e7eca3c593741b090e2d5be5cd78f762a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2935a63e7eca3c593741b090e2d5be5cd78f762a" plantuml: Update to 1.2022.14 Changes: - use GitHub releases - use latest Java LST as fallback.java - add jlatexmath variant - remove patch Fixed: https://trac.macports.org/ticket/66473 See: https://trac.macports.org/ticket/62933 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:24:35 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:24:35 -0000 Subject: [MacPorts] #62933: plantuml doesn't support latex In-Reply-To: <042.633c1f2eb66e5f6f46c3c5ad1a48f829@macports.org> References: <042.633c1f2eb66e5f6f46c3c5ad1a48f829@macports.org> Message-ID: <057.a51b9750c50c5e5e989b0e0e5b607389@macports.org> #62933: plantuml doesn't support latex -----------------------+-------------------- Reporter: catap | Owner: judaew Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: plantuml | -----------------------+-------------------- Comment (by Vadym-Valdis Yudaiev ): In [changeset:"2935a63e7eca3c593741b090e2d5be5cd78f762a/macports-ports" 2935a63e7eca3c593741b090e2d5be5cd78f762a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2935a63e7eca3c593741b090e2d5be5cd78f762a" plantuml: Update to 1.2022.14 Changes: - use GitHub releases - use latest Java LST as fallback.java - add jlatexmath variant - remove patch Fixed: https://trac.macports.org/ticket/66473 See: https://trac.macports.org/ticket/62933 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 17:38:53 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 17:38:53 -0000 Subject: [MacPorts] #66475: Build coreutils with Legacy Support? In-Reply-To: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> References: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> Message-ID: <061.227ced9d5cac7edeacd5a0e3df27c8bf@macports.org> #66475: Build coreutils with Legacy Support? --------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard, tiger Port: coreutils | --------------------------+---------------------------- Comment (by ballapete): I am not that deep into the library functions used, I cannot tell. OTOH, if the `coreutils` will receive an incompatible update, then LegacySupport could be ready to take over. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:42:08 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 18:42:08 -0000 Subject: [MacPorts] #66475: Build coreutils with Legacy Support? In-Reply-To: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> References: <046.eca8e9fb8e9c5e00ee447de9695eb51f@macports.org> Message-ID: <061.70b7f4ec36190f6ba46435a9ab3c0a3a@macports.org> #66475: Build coreutils with Legacy Support? --------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: leopard, tiger Port: coreutils | --------------------------+---------------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: OK, we'll keep an eye out for that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:44:38 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 18:44:38 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.b3bd472a1befed52414c358268e355c0@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): to fix the "can't open display" issue, either install XQuartz from the XQuartz website, or (probably better) installe xorg-server from macports. After you install it, it will tell you to log out and in again, or restart, and then the "can't open display" should be solved. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 18:56:32 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 18:56:32 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.eef1495b07c6733ecfc85ff5226923ed@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by chillin-): Sorry this is OT to gtk3 issue on Mojave, and I appreciate the suggestion, but I already did that. No joy. On the Mountain Lion mini, I installed XQuartz 2.7.11, but now I get this when I try to start netsurf-gtk3 >> bash-3.2$ netsurf-gtk3 > dbus[2197]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! > Options failed to initialise (BadParameter) Of course, org.freedesktop.dbus-session.plist is neither loaded nor installed. Using Pacifist, I looked in the XQuartz package, and it is not in there, thus it was not installed. This is old software. I'm sure there's instruction by some random college professor out there, but I haven't yet started to wrestle with Google, and I'm really not looking forward to it. (What happened to you, Google?) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 19:03:33 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 19:03:33 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.afcb69deeef61563fc5b36b5360780a1@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): time for an Xquartz upgrade? It's up to 2.8.3 now. https://www.xquartz.org/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 19:04:29 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 19:04:29 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.fcb9ff18c1dc336ffaaf09396053d66e@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): or xorg-desktop from macports instead, after you uninstall all of xquartz's bits. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 19:14:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 19:14:13 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.fa8ea680e665ba7c195ea8bee64a3242@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by chillin-): > time for an Xquartz upgrade? It's up to 2.8.3 now. Not on Mountain Lion. 2.7.11 is the last version that will work on OS X 10.8.5 > or xorg-desktop from macports instead, after you uninstall all of xquartz's bits. Sounds like a really good idea. XQuartz only installed a handful of files. I'm nearly certain the org.freedesktop.dbus-session.plist complaint is a silly bug, as it did install /System/Library/LaunchAgents/org.macosforge.xquartz.startx.plist and /System/Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist I strongly suspect the bit about "org.freedesktop" was probably supposed to be "org.macosforge." Anyway, it sure beats the pants off trying to find a recipe from 2012 on Google. Thanks, I'll give xorg a whirl. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 20:33:39 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 20:33:39 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) Message-ID: <049.286e1e7ace07490cc541f883b3b12770@macports.org> #66477: port install mpich +native: Failed to configure (on M1) --------------------------+--------------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: mpich-default --------------------------+--------------------------- I am trying to install `mpich` with `+native` variant on my MacBook Pro (16-inch, 2021, Apple M1 Max) with macOS Monterey 12.6.2 and Xcode 14.1. The error shows that {{{ :info:configure checking for gcc... /usr/bin/clang :info:configure checking whether the C compiler works... no :info:configure configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich /mpich-default/work/mpich-4.0.3': :info:configure configure: error: C compiler cannot create executables :info:configure See `config.log' for more details :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich /mpich-default/work/mpich-4.0.3" && ./configure --prefix=/opt/local --disable-dependency-tracking --enable-fortran --disable-silent-rules --enable-base-cache --enable-cache --enable-cxx --enable-fast=all --enable-shared --enable-versioning --enable-timer-type=mach_absolute_time --with-pm=hydra --with-thread-package=posix --with-hwloc-prefix=/opt/local --disable-collalgo-tests --disable-f08 F90FLAGS='' F90='' --libdir=/opt/local/lib/mpich-mp --sysconfdir=/opt/local/etc/mpich-mp --program-suffix=-mpich-mp --includedir=/opt/local/include/mpich-mp MPICHLIB_CFLAGS="$CFLAGS" CFLAGS="" MPICHLIB_CPPFLAGS="$CPPFLAGS" CPPFLAGS="" MPICHLIB_CXXFLAGS="$CXXFLAGS" CXXFLAGS="" MPICHLIB_FFLAGS="$FFLAGS" FFLAGS="" MPICHLIB_FCFLAGS="$FCFLAGS" FCFLAGS="" :info:configure Exit code: 77 }}} but I can compile a simple hello world with either Apple Clang or MacPorts gcc12. I attach both `config.log` and `main.log` here. Thanks in advance for taking a look into this issue. /CC -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 20:34:04 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 20:34:04 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.463522f63bb74f2e2cc3ec6270824267@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+-------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+-------------------- Changes (by chaochinyang): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 20:34:16 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 20:34:16 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.4432fd5f282e87d655b8c74ab576037d@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+-------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+-------------------- Changes (by chaochinyang): * Attachment "config.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 20:38:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 20:38:42 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.732c0dba4058172f14182d6edc08f11d@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+-------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+-------------------- Description changed by chaochinyang: Old description: > I am trying to install `mpich` with `+native` variant on my MacBook Pro > (16-inch, 2021, Apple M1 Max) with macOS Monterey 12.6.2 and Xcode 14.1. > > The error shows that > {{{ > :info:configure checking for gcc... /usr/bin/clang > :info:configure checking whether the C compiler works... no > :info:configure configure: error: in > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich > /mpich-default/work/mpich-4.0.3': > :info:configure configure: error: C compiler cannot create executables > :info:configure See `config.log' for more details > :info:configure Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich > /mpich-default/work/mpich-4.0.3" && ./configure --prefix=/opt/local > --disable-dependency-tracking --enable-fortran --disable-silent-rules > --enable-base-cache --enable-cache --enable-cxx --enable-fast=all > --enable-shared --enable-versioning --enable-timer- > type=mach_absolute_time --with-pm=hydra --with-thread-package=posix > --with-hwloc-prefix=/opt/local --disable-collalgo-tests --disable-f08 > F90FLAGS='' F90='' --libdir=/opt/local/lib/mpich-mp > --sysconfdir=/opt/local/etc/mpich-mp --program-suffix=-mpich-mp > --includedir=/opt/local/include/mpich-mp MPICHLIB_CFLAGS="$CFLAGS" > CFLAGS="" MPICHLIB_CPPFLAGS="$CPPFLAGS" CPPFLAGS="" > MPICHLIB_CXXFLAGS="$CXXFLAGS" CXXFLAGS="" MPICHLIB_FFLAGS="$FFLAGS" > FFLAGS="" MPICHLIB_FCFLAGS="$FCFLAGS" FCFLAGS="" > :info:configure Exit code: 77 > }}} > but I can compile a simple hello world with either Apple Clang or > MacPorts gcc12. > > I attach both `config.log` and `main.log` here. > > Thanks in advance for taking a look into this issue. > > /CC New description: I am trying to install `mpich` with `+native` variant on my MacBook Pro (16-inch, 2021, Apple M1 Max) with macOS Monterey 12.6.2 and Xcode 14.1. The error shows that {{{ :info:configure checking for gcc... /usr/bin/clang :info:configure checking whether the C compiler works... no :info:configure configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich /mpich-default/work/mpich-4.0.3': :info:configure configure: error: C compiler cannot create executables :info:configure See `config.log' for more details :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich /mpich-default/work/mpich-4.0.3" && ./configure --prefix=/opt/local --disable-dependency-tracking --enable-fortran --disable-silent-rules --enable-base-cache --enable-cache --enable-cxx --enable-fast=all --enable-shared --enable-versioning --enable-timer-type=mach_absolute_time --with-pm=hydra --with-thread-package=posix --with-hwloc-prefix=/opt/local --disable-collalgo-tests --disable-f08 F90FLAGS='' F90='' --libdir=/opt/local/lib/mpich-mp --sysconfdir=/opt/local/etc/mpich-mp --program-suffix=-mpich-mp --includedir=/opt/local/include/mpich-mp MPICHLIB_CFLAGS="$CFLAGS" CFLAGS="" MPICHLIB_CPPFLAGS="$CPPFLAGS" CPPFLAGS="" MPICHLIB_CXXFLAGS="$CXXFLAGS" CXXFLAGS="" MPICHLIB_FFLAGS="$FFLAGS" FFLAGS="" MPICHLIB_FCFLAGS="$FCFLAGS" FCFLAGS="" :info:configure Exit code: 77 }}} but I can compile a simple hello world with either Apple Clang or MacPorts gcc12. I attach both `config.log` and `main.log` here. BTW, I can install `mpich` ''without'' `+native` variant. Thanks in advance for taking a look into this issue. /CC -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 21:58:41 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 21:58:41 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.a10689d3f78e6543db359b2055d66553@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+-------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+-------------------- Comment (by kencu): {{{ clang: error: the clang compiler does not support '-march=native' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 15 22:11:25 2022 From: noreply at macports.org (MacPorts) Date: Thu, 15 Dec 2022 22:11:25 -0000 Subject: [MacPorts] #65893: fluidsynth @2.2.8 fails to build - Problem with MIDIPacketNext(packet) macro In-Reply-To: <043.f3ffbf17d082c7e3dafc7939d38c887f@macports.org> References: <043.f3ffbf17d082c7e3dafc7939d38c887f@macports.org> Message-ID: <058.2e66f0d60fedd3153bee5fed147bba2f@macports.org> #65893: fluidsynth @2.2.8 fails to build - Problem with MIDIPacketNext(packet) macro -------------------------+-------------------- Reporter: RobK88 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: lion Port: fluidsynth | -------------------------+-------------------- Comment (by RobK88): Ren? -- Sorry for the delay. I just saw your post. I closed all my applications and just ran `sudo port install fluidsynth`. fluidsynth was built and installed without any errors on my old Mac running Lion. {{{ bash-3.2$ port installed fluidsynth The following ports are currently installed: fluidsynth @2.3.0_0 (active) }}} Perhaps, I did not have enough memory to build it in the first place (as you suggested) or perhaps a bug was fixed in version 2.3.0_0 of fluidsynth. In any event, you can close off this ticket now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 00:51:36 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 00:51:36 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.cf8e5adbe7cfcd9a6a005805aec042f9@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+-------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+-------------------- Comment (by chaochinyang): Thanks, Ken, for such a quick response. Indeed I missed that `-march=native` is not supported by Clang. According to [https://www.phoronix.com/news/LLVM-Clang-march-native-M1 this article], this option will be supported by version 15, so until then. /CC -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 01:40:43 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 01:40:43 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.f7874a6541464273954c3a0e1db21571@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+-------------------- Reporter: chaochinyang | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+-------------------- Comment (by kencu): Oh, that is interesting. My spankin' new MacBookPro M1 is sitting in a box, to come under the tree in a few days, so I can't try this out myself just yet, but clang-15 is available in macports now, so it is possible that this might work if that compiler is forced. You would do it like this: {{{ sudo port -v -N install clang-15 sudo port -v install mpich +native configure.compiler=macports-clang-15 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 01:43:02 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 01:43:02 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.60678e2d08cf75685e0ec5062516cb30@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): OK -- when you do get around to xorg-desktop, and you install dbus, don't forget to enable dbus: {{{ % port notes dbus ---> dbus has the following notes: Startup items (named 'dbus-system, dbus-session') have been generated that will aid in starting dbus with launchd. They are disabled by default. Execute the following command to start them, and to cause them to launch at startup: sudo port load dbus }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 02:13:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 02:13:18 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.472c2f6cbe16effea31202fc313fdf46@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by chillin-): Much appreciate your followup, but I actually got that far. Initially starting netsurf-gtk3 gave me the complaint again about org.freedesktop .dbus-session.plist, but after sudo port load dbus, when I try to start netsurf-gtk, I get > Options failed to initialise (BadParameter) Googling this and NetSurf reveals one germane result, a NetSurf incident ticket for an Ubuntu user with the same issue. Resolution was updating NetSurf. I'm boned. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 04:45:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 04:45:20 -0000 Subject: [MacPorts] #66478: upgrade of perl5.26 fails on macos 13.1 (+universal) Message-ID: <051.3908610bac219018b51824fdab00d0e7@macports.org> #66478: upgrade of perl5.26 fails on macos 13.1 (+universal) ----------------------------+---------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: configuration | Port: perl5.26 ----------------------------+---------------------- Error: Failed to configure perl5.26: configure failure: command execution failed main.log is attached -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 04:45:46 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 04:45:46 -0000 Subject: [MacPorts] #66478: upgrade of perl5.26 fails on macos 13.1 (+universal) In-Reply-To: <051.3908610bac219018b51824fdab00d0e7@macports.org> References: <051.3908610bac219018b51824fdab00d0e7@macports.org> Message-ID: <066.a7d4c54e720a2fbff83efbfb2486712a@macports.org> #66478: upgrade of perl5.26 fails on macos 13.1 (+universal) -----------------------------+--------------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: configuration Port: perl5.26 | -----------------------------+--------------------------- Changes (by sudheerhebbale): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 06:12:10 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 06:12:10 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.fbf2eb293f833256217c428ce22ba00f@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): OKee Dokey then. Back to your original ticket, I have both the +x11 and the +quartz version of gtk3 installed on Mojave, no problem: {{{ macOS 10.14.6 18G9323 x86_64 Xcode 11.3.1 11C504 }}} {{{ $ port -v installed gtk3 The following ports are currently installed: gtk3 @3.24.34_2+quartz requested_variants='+quartz' platform='darwin 18' archs='x86_64' date='2022-09-25T12:11:45-0700' gtk3 @3.24.34_2+x11 requested_variants='' platform='darwin 18' archs='x86_64' date='2022-09-25T11:28:05-0700' }}} and the prebuilt binary is available for downloading from the macports packages server: So why can't you install it, I wonder? You should actually be just downloading it from the packages server prebuilt, but you should also be able to install it without trouble. Just to confirm -- you can't, for some reason? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 06:59:32 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 06:59:32 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.9fb7c29bec4ad8919bea095eda367812@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by jmroot): The attached log is from a failed build of libsdl2 @2.26.0, which is not the current version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:02:22 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:02:22 -0000 Subject: [MacPorts] #66477: port install mpich +native: Failed to configure (on M1) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.4a2c81b84224ff524373ebde9c810975@macports.org> #66477: port install mpich +native: Failed to configure (on M1) ----------------------------+---------------------- Reporter: chaochinyang | Owner: eborisch Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: mpich-default | ----------------------------+---------------------- Changes (by jmroot): * cc: mascguy (added) * status: new => assigned * owner: (none) => eborisch -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:06:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:06:55 -0000 Subject: [MacPorts] #66478: upgrade of perl5.26 fails on macos 13.1 (+universal) In-Reply-To: <051.3908610bac219018b51824fdab00d0e7@macports.org> References: <051.3908610bac219018b51824fdab00d0e7@macports.org> Message-ID: <066.7146cc2f0cbdb55edb6f3fbb93338490@macports.org> #66478: upgrade of perl5.26 fails on macos 13.1 (+universal) -----------------------------+---------------------- Reporter: sudheerhebbale | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: perl5.26 | -----------------------------+---------------------- Changes (by jmroot): * keywords: configuration => * status: new => assigned * owner: (none) => mojca Comment: Looks like perl5.26 is just too old to recognise macOS versions 11 and later. Is there a particular reason you need 5.26, or can you uninstall it and switch to perl5.34, which is what most things in MacPorts are using now? Also, presumably you must have migrated from an older OS version in order to have perl5.26 installed in the first place, so make sure to follow wiki:Migration if that's not what you were already doing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:08:03 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:08:03 -0000 Subject: [MacPorts] #66478: perl5.26 +universal: Unexpected product version 13.1 (was: upgrade of perl5.26 fails on macos 13.1 (+universal)) In-Reply-To: <051.3908610bac219018b51824fdab00d0e7@macports.org> References: <051.3908610bac219018b51824fdab00d0e7@macports.org> Message-ID: <066.c88405109e634c3ef728e7f5bc0f20aa@macports.org> #66478: perl5.26 +universal: Unexpected product version 13.1 -----------------------------+---------------------- Reporter: sudheerhebbale | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: perl5.26 | -----------------------------+---------------------- Changes (by ryandesign): * keywords: => ventura Old description: > Error: Failed to configure perl5.26: configure failure: command execution > failed > > main.log is attached New description: {{{ Error: Failed to configure perl5.26: configure failure: command execution failed }}} main.log is attached -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:08:31 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:08:31 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.9bb953c8f20a87fc239e1cffbaf14694@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): NetSurf builds, installs, and works for me on Mojave, although there is a message about not finding dbus, even though I do have it loaded. Screenshot attached. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:09:54 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:09:54 -0000 Subject: [MacPorts] #66477: mpich-default +native: clang: error: the clang compiler does not support '-march=native' (was: port install mpich +native: Failed to configure (on M1)) In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.313977b666d495c4f19f541e384af16d@macports.org> #66477: mpich-default +native: clang: error: the clang compiler does not support '-march=native' ----------------------------+---------------------- Reporter: chaochinyang | Owner: eborisch Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: arm64 Port: mpich-default | ----------------------------+---------------------- Changes (by ryandesign): * keywords: => arm64 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:12:47 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:12:47 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.01d4b40ff3395bedd62f383134cf0ada@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Changes (by kencu): * Attachment "Screen Shot 2022-12-15 at 11.06.52 PM.png" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:13:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:13:12 -0000 Subject: [MacPorts] #66462: port cannot install again graphviz on PPC Leopard, Mac OS X 10.5.6 In-Reply-To: <046.08f27338a5462eb4661ebef7c02215e7@macports.org> References: <046.08f27338a5462eb4661ebef7c02215e7@macports.org> Message-ID: <061.33637ac0f61ceb70bee7fe4c59ecf8f4@macports.org> #66462: port cannot install again graphviz on PPC Leopard, Mac OS X 10.5.6 ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz | ------------------------+------------------------- Comment (by ryandesign): I'm sorry, I don't know why that's happening. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:16:07 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:16:07 -0000 Subject: [MacPorts] #66478: perl5.26 +universal: Unexpected product version 13.1 In-Reply-To: <051.3908610bac219018b51824fdab00d0e7@macports.org> References: <051.3908610bac219018b51824fdab00d0e7@macports.org> Message-ID: <066.2dbf6263fd688a1ef480bbcbac656c1f@macports.org> #66478: perl5.26 +universal: Unexpected product version 13.1 -----------------------------+---------------------- Reporter: sudheerhebbale | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: perl5.26 | -----------------------------+---------------------- Comment (by sudheerhebbale): perl5.34 works It is not necessary to fix 5.26 Thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:20:48 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:20:48 -0000 Subject: [MacPorts] #66464: ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software In-Reply-To: <046.df111525b4170d7d0f210c858917b3db@macports.org> References: <046.df111525b4170d7d0f210c858917b3db@macports.org> Message-ID: <061.4f2f8304c59868d427571606fe0ea95a@macports.org> #66464: ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software --------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: ImageMagick | --------------------------+------------------------- Comment (by ryandesign): `--with-dps` was added in [cea379c3084322297ecad7314f3db9d8ddd99366 /macports-ports] as part of the fix for #847 but the ticket does not explain that change specifically and it was 19 years ago which predates my involvement with MacPorts so who knows why that was done at this point. As to raqm and flif, I suppose I didn't add the configure arguments because I didn't realize they existed. You're right that we should specify any `--without-` or `--disable-` flags that we can when that would prevent the use of a library that we don't want to use, even if that library is not yet in MacPorts. For libraries that are not macOS-compatible, it's less urgent since any check for such a library would fail on macOS. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:23:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:23:42 -0000 Subject: [MacPorts] #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 In-Reply-To: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> References: <046.8ae8b245dec364d6e2c7910cf1fe62ca@macports.org> Message-ID: <061.540784a0a3eefb96d07cadedb3e1d678@macports.org> #66461: port installs graphviz instead of graphviz-devel on PPC Leoprad, Mac OS X 10.5.8 -----------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: graphviz-devel | -----------------------------+------------------------- Comment (by ryandesign): Ok, then I can't explain that, and I can't reproduce it on my system. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:28:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:28:04 -0000 Subject: [MacPorts] #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file In-Reply-To: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> References: <046.529ab1372037ea5b6fdcb962c380c897@macports.org> Message-ID: <061.06cd5f848076f61962aecf7a05052ebe@macports.org> #66459: git @2.39.0 does not build on PPC Leopard, Mac OS X 10.5.8, because of faulty patch file ------------------------+------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: leopard ppc Port: git | ------------------------+------------------------- Changes (by ryandesign): * status: new => closed * resolution: => fixed Comment: [1d3abd838eb4c0af03a80c59fd7e478e89116d1a/macports-ports] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 07:31:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 07:31:53 -0000 Subject: [MacPorts] #65040: octave @6.4.0_2 destroot failure In-Reply-To: <046.eac2bbe2f95cf3755973e1a13772e2c3@macports.org> References: <046.eac2bbe2f95cf3755973e1a13772e2c3@macports.org> Message-ID: <061.13225a66e08778200b8d03862e5d1633@macports.org> #65040: octave @6.4.0_2 destroot failure ------------------------+--------------------------------- Reporter: danielmux | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: octave | ------------------------+--------------------------------- Comment (by ryandesign): The port was updated to 7.1.0, then 7.2.0, then 7.3.0. Does the problem still exist with that version? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 08:03:23 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 08:03:23 -0000 Subject: [MacPorts] #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens In-Reply-To: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> References: <046.860d452c7d36e3aafc6f5a487d37d34b@macports.org> Message-ID: <061.8872c63aab8a458d56b8e940268b9fb0@macports.org> #66425: libdeflate @1.15 does not build on < 10.13, unconditional use of futimens -------------------------+------------------------- Reporter: ballapete | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libdeflate | -------------------------+------------------------- Comment (by ballapete): It also worked to `upgrade on PPC Tiger, Mac OS X 10.4.11`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 08:48:39 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 08:48:39 -0000 Subject: [MacPorts] #66479: pdftk-java @3.3.3: install fails since as bcprov is installed before commons-lang3 on which it depends Message-ID: <049.34b9151c331259b7311408ad8ee77d2a@macports.org> #66479: pdftk-java @3.3.3: install fails since as bcprov is installed before commons-lang3 on which it depends --------------------------+------------------------ Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: pdftk-java --------------------------+------------------------ I tried to install pdftk-java on an Apple M1 (Ventura 13.0.1) and got the following error: {{{ % sudo port install pdftk-java Password: ---> Computing dependencies for pdftk-java The following dependencies will be installed: bcprov commons-lang3 maven3 maven_select openjdk11-zulu openjdk17-zulu Continue? [Y/n]: y ---> Fetching archive for bcprov ---> Attempting to fetch bcprov-1.72_0.darwin_22.noarch.tbz2 from https://packages.macports.org/bcprov ---> Attempting to fetch bcprov-1.72_0.darwin_22.noarch.tbz2 from https://fra.de.packages.macports.org/bcprov ---> Attempting to fetch bcprov-1.72_0.darwin_22.noarch.tbz2 from https://nue.de.packages.macports.org/bcprov ---> Fetching distfiles for bcprov Error: bcprov requires Java 1.8+ but no such installation could be found. Error: Failed to fetch bcprov: missing required Java version Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_bcprov/bcprov/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port pdftk-java failed }}} I solved this by first installing commons-lang3 directly, and then attempting again, which worked. So I suggest either reordering the installation non-alphabetically. Alternatively, this may be an error with bcprov not installing its dependencies properly? I didn't cc anyone in, since there seem no maintainers on either bcprov nor pdtfk-java. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 08:51:05 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 08:51:05 -0000 Subject: [MacPorts] #66299: octave: install infinite loop info:destroot In-Reply-To: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> References: <046.373c2d98b8245ff30f80f7dd01b64f63@macports.org> Message-ID: <061.42bb66eec96da2aa7bcbd502fe226fe9@macports.org> #66299: octave: install infinite loop info:destroot ------------------------+--------------------------------- Reporter: wcvinyard | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: octave | ------------------------+--------------------------------- Changes (by ryandesign): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"1323b4b4b50db914d99dbc35eff7318e55544f56/macports-ports" 1323b4b4b50db914d99dbc35eff7318e55544f56/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1323b4b4b50db914d99dbc35eff7318e55544f56" octave: Fix build with texinfo >= 7 Closes: https://trac.macports.org/ticket/66299 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 09:12:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 09:12:53 -0000 Subject: [MacPorts] #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' Message-ID: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' -----------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: git -----------------------+-------------------- {{{ ---> Building git DEBUG: Executing org.macports.build (git) DEBUG: Environment: CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/.CC_PRINT_OPTIONS' CPATH='/opt/local/include' CPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport' C_INCLUDE_PATH='/opt/local/include/LegacySupport' DEVELOPER_DIR='/Developer' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.4' MACPORTS_LEGACY_SUPPORT_CPPFLAGS='-isystem/opt/local/include/LegacySupport' MACPORTS_LEGACY_SUPPORT_ENABLED='1' MACPORTS_LEGACY_SUPPORT_LDFLAGS='-L/opt/local/lib -lMacportsLegacySupport' OBJCPLUS_INCLUDE_PATH='/opt/local/include/LegacySupport' OBJC_INCLUDE_PATH='/opt/local/include/LegacySupport' Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0" && /usr/bin/make -j1 -w all CFLAGS="-Os -std=gnu99 -arch ppc" LDFLAGS="-Wl,-headerpad_max_install_names -L/opt/local/lib -lMacportsLegacySupport -arch ppc" CC=/opt/local/bin/gcc-apple-4.2 prefix=/opt/local CURLDIR=/opt/local ICONVDIR=/opt/local NO_FINK=1 NO_DARWIN_PORTS=1 NO_R_TO_GCC_LINKER=1 V=1 PERL_PATH="/opt/local/bin/perl5.34" NO_PERL_CPAN_FALLBACK=1 NO_APPLE_COMMON_CRYPTO=1 CC_LD_DYNPATH=-R LIBPCREDIR=/opt/local USE_LIBPCRE2=1 DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0" && /usr/bin/make -j1 -w all CFLAGS="-Os -std=gnu99 -arch ppc" LDFLAGS="-Wl,-headerpad_max_install_names -L/opt/local/lib -lMacportsLegacySupport -arch ppc" CC=/opt/local/bin/gcc-apple-4.2 prefix=/opt/local CURLDIR=/opt/local ICONVDIR=/opt/local NO_FINK=1 NO_DARWIN_PORTS=1 NO_R_TO_GCC_LINKER=1 V=1 PERL_PATH="/opt/local/bin/perl5.34" NO_PERL_CPAN_FALLBACK=1 NO_APPLE_COMMON_CRYPTO=1 CC_LD_DYNPATH=-R LIBPCREDIR=/opt/local USE_LIBPCRE2=1 make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0' Makefile:3323: *** missing `endif'. Stop. make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_devel_git/git/work/git-2.39.0" && /usr/bin/make -j1 -w all CFLAGS="-Os -std=gnu99 -arch ppc" LDFLAGS="-Wl,-headerpad_max_install_names -L/opt/local/lib -lMacportsLegacySupport -arch ppc" CC=/opt/local/bin/gcc-apple-4.2 prefix=/opt/local CURLDIR=/opt/local ICONVDIR=/opt/local NO_FINK=1 NO_DARWIN_PORTS=1 NO_R_TO_GCC_LINKER=1 V=1 PERL_PATH="/opt/local/bin/perl5.34" NO_PERL_CPAN_FALLBACK=1 NO_APPLE_COMMON_CRYPTO=1 CC_LD_DYNPATH=-R LIBPCREDIR=/opt/local USE_LIBPCRE2=1 Exit code: 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 09:13:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 09:13:34 -0000 Subject: [MacPorts] #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' In-Reply-To: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> References: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> Message-ID: <061.8f1e4de7622ee68c3c088bdf1695aef7@macports.org> #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: git | ------------------------+----------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Tiger, Mac OS X 10.4.11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 09:32:45 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 09:32:45 -0000 Subject: [MacPorts] #66481: py311-pylint @2.14.5: installation fails in macOS Mojave Message-ID: <045.1d752d00cf573998a6b3503122b3f088@macports.org> #66481: py311-pylint @2.14.5: installation fails in macOS Mojave ----------------------+-------------------------- Reporter: JD-Veiga | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py311-pylint ----------------------+-------------------------- Hi, The installation of py311-pylint at 2.14.5 fails in my macOS Mojave with the following error: {{{ xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/destroot/opt/local/share/doc/py311-pylint xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/destroot/opt/local/share/doc/py311-pylint/examples Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/pylint-2.14.5" && /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 -m installer /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/pylint-2.14.5-py3-none-any.whl --destdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/destroot xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/destroot/opt/local/etc/select xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/work/destroot/opt/local/etc/select/pylint Error: Failed to destroot py311-pylint: xinstall: Cannot stat: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python /py-pylint/files/pylint311, No such file or directory Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- pylint/py311-pylint/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port py311-pylint failed }}} My system is: * macOS Mojave 10.14.6 * MacPorts 2.8.0 * Python 3.11.1 Thank you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 10:09:08 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 10:09:08 -0000 Subject: [MacPorts] #65742: Gnuradio gui stuck In-Reply-To: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> References: <048.eb9900c44a6999b8bf7886dcb35f4b71@macports.org> Message-ID: <063.6cd5b0bcdd877c1917e7e1fa3d2f25b5@macports.org> #65742: Gnuradio gui stuck --------------------------+----------------------- Reporter: adamgao1996 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: qtgui Port: gnuradio | --------------------------+----------------------- Comment (by ra1nb0w): don't use {{{sync}}}. You need to manually update with {{{pull}}} and {{{rebase}}} the new branch with master's commits. To create the index use {{{portindex}}} command at the root of the repository. Then you can use port as always. see https://guide.macports.org/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 10:19:58 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 10:19:58 -0000 Subject: [MacPorts] #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' Message-ID: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' -----------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: diffutils -----------------------+----------------------- {{{ CC sigsegv.o sigsegv.c: In function 'sigsegv_handler': sigsegv.c:940: error: 'struct mcontext' has no member named '__ss' make[2]: *** [sigsegv.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_diffutils/diffutils/work/diffutils-3.8/lib' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 10:20:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 10:20:42 -0000 Subject: [MacPorts] #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' In-Reply-To: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> References: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> Message-ID: <061.90b3fd78a540d2e317b94171b1ffdfa1@macports.org> #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: diffutils | ------------------------+----------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from PPC Tiger, Mac OS X 10.4.11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 10:49:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 10:49:40 -0000 Subject: [MacPorts] #66478: perl5.26 +universal: Unexpected product version 13.1 In-Reply-To: <051.3908610bac219018b51824fdab00d0e7@macports.org> References: <051.3908610bac219018b51824fdab00d0e7@macports.org> Message-ID: <066.7d314e8c7f5dd0d2fded49f842a7c6b2@macports.org> #66478: perl5.26 +universal: Unexpected product version 13.1 -----------------------------+---------------------- Reporter: sudheerhebbale | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: perl5.26 | -----------------------------+---------------------- Comment (by jmroot): OK, great. I guess the older perl versions should at least be marked as not supported on the newer OS versions. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 10:56:22 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 10:56:22 -0000 Subject: [MacPorts] #66479: bcprov @1.72 should have a java dependency (was: pdftk-java @3.3.3: install fails since as bcprov is installed before commons-lang3 on which it depends) In-Reply-To: <049.34b9151c331259b7311408ad8ee77d2a@macports.org> References: <049.34b9151c331259b7311408ad8ee77d2a@macports.org> Message-ID: <064.80b6d1d301be0f61605ffc213fb5ad4a@macports.org> #66479: bcprov @1.72 should have a java dependency ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bcprov | ---------------------------+-------------------- Changes (by jmroot): * port: pdftk-java => bcprov -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:17:33 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:17:33 -0000 Subject: [MacPorts] #66479: bcprov @1.72 should have a java dependency In-Reply-To: <049.34b9151c331259b7311408ad8ee77d2a@macports.org> References: <049.34b9151c331259b7311408ad8ee77d2a@macports.org> Message-ID: <064.d7ee089c9748bcb57372222604eba840@macports.org> #66479: bcprov @1.72 should have a java dependency ---------------------------+-------------------- Reporter: MarcKaufmann | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: bcprov | ---------------------------+-------------------- Changes (by jmroot): * status: new => closed * owner: (none) => jmroot * resolution: => fixed Comment: In [changeset:"4d60258ebb445998bd18b6d26c096e93a8b1c7a8/macports-ports" 4d60258ebb445998bd18b6d26c096e93a8b1c7a8/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4d60258ebb445998bd18b6d26c096e93a8b1c7a8" bcprov: add java.fallback Also set platforms any. Fixes: https://trac.macports.org/ticket/66479 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:24:01 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:24:01 -0000 Subject: [MacPorts] #66481: py311-pylint @2.14.5: installation fails in macOS Mojave In-Reply-To: <045.1d752d00cf573998a6b3503122b3f088@macports.org> References: <045.1d752d00cf573998a6b3503122b3f088@macports.org> Message-ID: <060.c4ea97bacae23b2df948b03e07d5eef1@macports.org> #66481: py311-pylint @2.14.5: installation fails in macOS Mojave ------------------------+---------------------- Reporter: JD-Veiga | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-pylint | ------------------------+---------------------- Changes (by jmroot): * cc: stromnov@? (removed) * owner: (none) => stromnov * status: new => assigned * port: py311-pylint => py-pylint -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:24:46 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:24:46 -0000 Subject: [MacPorts] #66481: py311-pylint @2.14.5: installation fails in macOS Mojave In-Reply-To: <045.1d752d00cf573998a6b3503122b3f088@macports.org> References: <045.1d752d00cf573998a6b3503122b3f088@macports.org> Message-ID: <060.d4173b14ec53cfdf6465d763b36d9593@macports.org> #66481: py311-pylint @2.14.5: installation fails in macOS Mojave ------------------------+---------------------- Reporter: JD-Veiga | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-pylint | ------------------------+---------------------- Changes (by jmroot): * cc: Schamschula (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:27:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:27:04 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) Message-ID: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) -----------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: python311 -----------------------+----------------------- {{{ /opt/local/bin/gcc-mp-7 -L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc -o _bootstrap_python Modules/getbuildinfo.o Parser/token.o Parser/pegen.o Parser/pegen_errors.o Parser/action_helpers.o Parser/parser.o Parser/string_parser.o Parser/peg_api.o Parser/myreadline.o Parser/tokenizer.o Objects/abstract.o Objects/accu.o Objects/boolobject.o Objects/bytes_methods.o Objects/bytearrayobject.o Objects/bytesobject.o Objects/call.o Objects/capsule.o Objects/cellobject.o Objects/classobject.o Objects/codeobject.o Objects/complexobject.o Objects/descrobject.o Objects/enumobject.o Objects/exceptions.o Objects/genericaliasobject.o Objects/genobject.o Objects/fileobject.o Objects/floatobject.o Objects/frameobject.o Objects/funcobject.o Objects/interpreteridobject.o Objects/iterobject.o Objects/listobject.o Objects/longobject.o Objects/dictobject.o Objects/odictobject.o Objects/memoryobject.o Objects/methodobject.o Objects/moduleobject.o Objects/namespaceobject.o Objects/object.o Objects/obmalloc.o Objects/picklebufobject.o Objects/rangeobject.o Objects/setobject.o Objects/sliceobject.o Objects/structseq.o Objects/tupleobject.o Objects/typeobject.o Objects/unicodeobject.o Objects/unicodectype.o Objects/unionobject.o Objects/weakrefobject.o Python/_warnings.o Python/Python-ast.o Python/Python-tokenize.o Python/asdl.o Python/ast.o Python/ast_opt.o Python/ast_unparse.o Python/bltinmodule.o Python/ceval.o Python/codecs.o Python/compile.o Python/context.o Python/dynamic_annotations.o Python/errors.o Python/frame.o Python/frozenmain.o Python/future.o Python/getargs.o Python/getcompiler.o Python/getcopyright.o Python/getplatform.o Python/getversion.o Python/hamt.o Python/hashtable.o Python/import.o Python/importdl.o Python/initconfig.o Python/marshal.o Python/modsupport.o Python/mysnprintf.o Python/mystrtoul.o Python/pathconfig.o Python/preconfig.o Python/pyarena.o Python/pyctype.o Python/pyfpe.o Python/pyhash.o Python/pylifecycle.o Python/pymath.o Python/pystate.o Python/pythonrun.o Python/pytime.o Python/bootstrap_hash.o Python/specialize.o Python/structmember.o Python/symtable.o Python/sysmodule.o Python/thread.o Python/traceback.o Python/getopt.o Python/pystrcmp.o Python/pystrtod.o Python/pystrhex.o Python/dtoa.o Python/formatter_unicode.o Python/fileutils.o Python/suggestions.o Python/dynload_shlib.o Modules/config.o Modules/main.o Modules/gcmodule.o Modules/atexitmodule.o Modules/faulthandler.o Modules/posixmodule.o Modules/signalmodule.o Modules/_tracemalloc.o Modules/_codecsmodule.o Modules/_collectionsmodule.o Modules/errnomodule.o Modules/_io/_iomodule.o Modules/_io/iobase.o Modules/_io/fileio.o Modules/_io/bytesio.o Modules/_io/bufferedio.o Modules/_io/textio.o Modules/_io/stringio.o Modules/itertoolsmodule.o Modules/_sre/sre.o Modules/_threadmodule.o Modules/timemodule.o Modules/_weakref.o Modules/_abc.o Modules/_functoolsmodule.o Modules/_localemodule.o Modules/_operator.o Modules/_stat.o Modules/symtablemodule.o Modules/pwdmodule.o Modules/xxsubtype.o \ Programs/_bootstrap_python.o Modules/getpath.o -lintl -ldl -framework CoreFoundation ./Programs/_freeze_module zipimport ./Lib/zipimport.py Python/frozen_modules/zipimport.h ./_bootstrap_python ./Programs/_freeze_module.py abc ./Lib/abc.py Python/frozen_modules/abc.h ./_bootstrap_python ./Programs/_freeze_module.py codecs ./Lib/codecs.py Python/frozen_modules/codecs.h ./_bootstrap_python ./Programs/_freeze_module.py io ./Lib/io.py Python/frozen_modules/io.h ./_bootstrap_python ./Programs/_freeze_module.py _collections_abc ./Lib/_collections_abc.py Python/frozen_modules/_collections_abc.h ./_bootstrap_python ./Programs/_freeze_module.py _sitebuiltins ./Lib/_sitebuiltins.py Python/frozen_modules/_sitebuiltins.h ./_bootstrap_python ./Programs/_freeze_module.py genericpath ./Lib/genericpath.py Python/frozen_modules/genericpath.h ./_bootstrap_python ./Programs/_freeze_module.py ntpath ./Lib/ntpath.py Python/frozen_modules/ntpath.h ./_bootstrap_python ./Programs/_freeze_module.py posixpath ./Lib/posixpath.py Python/frozen_modules/posixpath.h ./_bootstrap_python ./Programs/_freeze_module.py os ./Lib/os.py Python/frozen_modules/os.h ./_bootstrap_python ./Programs/_freeze_module.py site ./Lib/site.py Python/frozen_modules/site.h ./_bootstrap_python ./Programs/_freeze_module.py stat ./Lib/stat.py Python/frozen_modules/stat.h ./_bootstrap_python ./Programs/_freeze_module.py importlib.util ./Lib/importlib/util.py Python/frozen_modules/importlib.util.h ./_bootstrap_python ./Programs/_freeze_module.py importlib.machinery ./Lib/importlib/machinery.py Python/frozen_modules/importlib.machinery.h ./_bootstrap_python ./Programs/_freeze_module.py runpy ./Lib/runpy.py Python/frozen_modules/runpy.h ./_bootstrap_python ./Programs/_freeze_module.py __hello__ ./Lib/__hello__.py Python/frozen_modules/__hello__.h ./_bootstrap_python ./Programs/_freeze_module.py __phello__ ./Lib/__phello__/__init__.py Python/frozen_modules/__phello__.h ./_bootstrap_python ./Programs/_freeze_module.py __phello__.ham ./Lib/__phello__/ham/__init__.py Python/frozen_modules/__phello__.ham.h ./_bootstrap_python ./Programs/_freeze_module.py __phello__.ham.eggs ./Lib/__phello__/ham/eggs.py Python/frozen_modules/__phello__.ham.eggs.h ./_bootstrap_python ./Programs/_freeze_module.py __phello__.spam ./Lib/__phello__/spam.py Python/frozen_modules/__phello__.spam.h ./_bootstrap_python ./Programs/_freeze_module.py frozen_only ./Tools/freeze/flag.py Python/frozen_modules/frozen_only.h ./_bootstrap_python ./Tools/scripts/deepfreeze.py \ Python/frozen_modules/importlib._bootstrap.h:importlib._bootstrap \ Python/frozen_modules/importlib._bootstrap_external.h:importlib._bootstrap_external \ Python/frozen_modules/zipimport.h:zipimport \ Python/frozen_modules/abc.h:abc \ Python/frozen_modules/codecs.h:codecs \ Python/frozen_modules/io.h:io \ Python/frozen_modules/_collections_abc.h:_collections_abc \ Python/frozen_modules/_sitebuiltins.h:_sitebuiltins \ Python/frozen_modules/genericpath.h:genericpath \ Python/frozen_modules/ntpath.h:ntpath \ Python/frozen_modules/posixpath.h:posixpath \ Python/frozen_modules/os.h:os \ Python/frozen_modules/site.h:site \ Python/frozen_modules/stat.h:stat \ Python/frozen_modules/importlib.util.h:importlib.util \ Python/frozen_modules/importlib.machinery.h:importlib.machinery \ Python/frozen_modules/runpy.h:runpy \ Python/frozen_modules/__hello__.h:__hello__ \ Python/frozen_modules/__phello__.h:__phello__ \ Python/frozen_modules/__phello__.ham.h:__phello__.ham \ Python/frozen_modules/__phello__.ham.eggs.h:__phello__.ham.eggs \ Python/frozen_modules/__phello__.spam.h:__phello__.spam \ Python/frozen_modules/frozen_only.h:frozen_only \ -o Python/deepfreeze/deepfreeze.c Note: Deepfreeze may have added some global objects, so run 'make regen-global-objects' if necessary. /opt/local/bin/gcc-mp-7 -c -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -arch ppc -std=c11 -Werror=implicit-function-declaration -fvisibility=hidden -I./Include/internal -I. -I./Include -I/opt/local/include -DPy_BUILD_CORE -o Python/deepfreeze/deepfreeze.o Python/deepfreeze/deepfreeze.c /opt/local/bin/gcc-mp-7 -c -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -arch ppc -std=c11 -Werror=implicit-function-declaration -fvisibility=hidden -I./Include/internal -I. -I./Include -I/opt/local/include -DPy_BUILD_CORE -o Python/frozen.o Python/frozen.c rm -f libpython3.11.a ar rcs libpython3.11.a Modules/getbuildinfo.o Parser/token.o Parser/pegen.o Parser/pegen_errors.o Parser/action_helpers.o Parser/parser.o Parser/string_parser.o Parser/peg_api.o Parser/myreadline.o Parser/tokenizer.o Objects/abstract.o Objects/accu.o Objects/boolobject.o Objects/bytes_methods.o Objects/bytearrayobject.o Objects/bytesobject.o Objects/call.o Objects/capsule.o Objects/cellobject.o Objects/classobject.o Objects/codeobject.o Objects/complexobject.o Objects/descrobject.o Objects/enumobject.o Objects/exceptions.o Objects/genericaliasobject.o Objects/genobject.o Objects/fileobject.o Objects/floatobject.o Objects/frameobject.o Objects/funcobject.o Objects/interpreteridobject.o Objects/iterobject.o Objects/listobject.o Objects/longobject.o Objects/dictobject.o Objects/odictobject.o Objects/memoryobject.o Objects/methodobject.o Objects/moduleobject.o Objects/namespaceobject.o Objects/object.o Objects/obmalloc.o Objects/picklebufobject.o Objects/rangeobject.o Objects/setobject.o Objects/sliceobject.o Objects/structseq.o Objects/tupleobject.o Objects/typeobject.o Objects/unicodeobject.o Objects/unicodectype.o Objects/unionobject.o Objects/weakrefobject.o Python/_warnings.o Python/Python-ast.o Python/Python-tokenize.o Python/asdl.o Python/ast.o Python/ast_opt.o Python/ast_unparse.o Python/bltinmodule.o Python/ceval.o Python/codecs.o Python/compile.o Python/context.o Python/dynamic_annotations.o Python/errors.o Python/frame.o Python/frozenmain.o Python/future.o Python/getargs.o Python/getcompiler.o Python/getcopyright.o Python/getplatform.o Python/getversion.o Python/hamt.o Python/hashtable.o Python/import.o Python/importdl.o Python/initconfig.o Python/marshal.o Python/modsupport.o Python/mysnprintf.o Python/mystrtoul.o Python/pathconfig.o Python/preconfig.o Python/pyarena.o Python/pyctype.o Python/pyfpe.o Python/pyhash.o Python/pylifecycle.o Python/pymath.o Python/pystate.o Python/pythonrun.o Python/pytime.o Python/bootstrap_hash.o Python/specialize.o Python/structmember.o Python/symtable.o Python/sysmodule.o Python/thread.o Python/traceback.o Python/getopt.o Python/pystrcmp.o Python/pystrtod.o Python/pystrhex.o Python/dtoa.o Python/formatter_unicode.o Python/fileutils.o Python/suggestions.o Python/dynload_shlib.o Modules/config.o Modules/main.o Modules/gcmodule.o Modules/atexitmodule.o Modules/faulthandler.o Modules/posixmodule.o Modules/signalmodule.o Modules/_tracemalloc.o Modules/_codecsmodule.o Modules/_collectionsmodule.o Modules/errnomodule.o Modules/_io/_iomodule.o Modules/_io/iobase.o Modules/_io/fileio.o Modules/_io/bytesio.o Modules/_io/bufferedio.o Modules/_io/textio.o Modules/_io/stringio.o Modules/itertoolsmodule.o Modules/_sre/sre.o Modules/_threadmodule.o Modules/timemodule.o Modules/_weakref.o Modules/_abc.o Modules/_functoolsmodule.o Modules/_localemodule.o Modules/_operator.o Modules/_stat.o Modules/symtablemodule.o Modules/pwdmodule.o Modules/xxsubtype.o Python/deepfreeze/deepfreeze.o Modules/getpath.o Python/frozen.o /usr/bin/install -c -d -m 755 Python.framework/Versions/3.11 /opt/local/bin/gcc-mp-7 -o Python.framework/Versions/3.11/Python -L/opt/local/lib -Wl,-headerpad_max_install_names -arch ppc -dynamiclib \ -all_load libpython3.11.a -Wl,-single_module \ -install_name /opt/local/Library/Frameworks/Python.framework/Versions/3.11/Python \ -compatibility_version 3.11 \ -current_version 3.11 \ -framework CoreFoundation -lintl -ldl -framework CoreFoundation; ld: absolute addressing (perhaps -mdynamic-no-pic) used in __Py_dg_infinity from libpython3.11.a(dtoa.o) not allowed in slidable image. Use '-read_only_relocs suppress' to enable text relocs collect2: error: ld returned 1 exit status make: *** [Python.framework/Versions/3.11/Python] Error 1 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_lang_python311/python311/work/Python-3.11.1' }}} Main.log already deleted (don't want Python 3.11 this year). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:30:31 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:30:31 -0000 Subject: [MacPorts] #66484: ninja @1.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because Python 3.11 does not build Message-ID: <046.282210bc6dd613dcedf76287638428c4@macports.org> #66484: ninja @1.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because Python 3.11 does not build -----------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: ninja -----------------------+-------------------- {{{ tiger:~ root# port deps ninja Full Name: ninja @1.11.1_1 Build Dependencies: re2c, apple-gcc42 Library Dependencies: python311 }}} See also: #66483. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:39:56 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:39:56 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 Message-ID: <046.e720c8046133de2e1187c40c48c171dd@macports.org> #66485: While I am installing port 1 I cannot build port 2 -------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: -------------------------+-------------------- Modern Macs have more than one CPU core so that it is possible to perform a few things in parallel. But port is very old fashioned and prevents building and installing one software and ''just'' building another one that is not depending on the software that is being built to become installed. Why? What is the sense? I do understand that it can be hard to record in a DB when two installation run at the same time, but here just one build step for a future installation is going on and I want to save some time by performing another build. Nothing to be tracked, or? {{{ tiger:~ root# nice port rdeps diffutils The following ports are dependencies of diffutils @3.8_0: xz lbzip2 apple-gcc42 ld64 ld64-97 libmacho-headers libunwind-headers cctools gcc_select legacy-support gettext libiconv gperf libtextstyle ncurses gettext-runtime gettext-tools-libs }}} Curl is being being built for installation? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:45:59 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:45:59 -0000 Subject: [MacPorts] #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' In-Reply-To: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> References: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> Message-ID: <061.3f4bc255a23fe5b1249696feb84f9edb@macports.org> #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: diffutils | ------------------------+----------------------- Comment (by ballapete): How can I make the compiler invocations visible? If I could see what the compiler is doing I could persuade it to just pre-compile the source file to see what is actually complaining about. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 11:59:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 11:59:04 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.dbd96443b2773589330100d560f2f850@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by jmroot): You should be able to build, what you can't do is any operation that may need to install something else, including things like extract dependencies. Any operation involving the registry would be subject to TOCTOU errors if the lock were not in place. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:13:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 12:13:20 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.e9a112b6502e335c7b30dfca780dc964@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ballapete): But I am not: {{{ sudo port -vds build diffutils Password: DEBUG: Changing to port directory: /opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/sysutils/diffutils DEBUG: OS darwin/8.11.0 (macOS 10.4.11) arch powerpc DEBUG: Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl DEBUG: compiler clang blacklisted because it's not installed or it doesn't work DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Chosen compiler apple-gcc-4.2 is provided by a port, adding dependency DEBUG: Adding depends_build port:apple-gcc42 DEBUG: Adding depends_skip_archcheck apple-gcc42 DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Running callback portstartupitem::add_notes DEBUG: Finished running callback portstartupitem::add_notes DEBUG: Attempting ln -sf /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_diffutils/diffutils/work /opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/sysutils/diffutils/work DEBUG: dropping privileges: euid changed to 502, egid changed to 502. DEBUG: Starting logging for diffutils @3.8_0 DEBUG: Mac OS X 10.4.11 (darwin/8.11.0) arch powerpc DEBUG: MacPorts 2.8.0 DEBUG: Xcode 2.5, CLT none DEBUG: SDK 10.4 DEBUG: MACOSX_DEPLOYMENT_TARGET: 10.4 Waiting for lock on /opt/local/var/macports/registry/.registry.lock }}} In one instance of GNU Emacs `pango` is being built in `some variant for installation`, in another instance of GNU Emacs I wanted to build again `diffutils`. There are no obvious remote dependencies, because then second `port` would try to build `pango` which is not installed right now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:32:27 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 12:32:27 -0000 Subject: [MacPorts] #66486: sendfile build fails Message-ID: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> #66486: sendfile build fails -----------------------+---------------------- Reporter: MStraeten | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: sendfile | Port: sendfile -----------------------+---------------------- sudo port install sendfile ---> Fetching distfiles for sendfile ---> Verifying checksums for sendfile ---> Extracting sendfile ---> Applying patches to sendfile ---> Configuring sendfile ---> Building sendfile Error: Failed to build sendfile: command execution failed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:34:10 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 12:34:10 -0000 Subject: [MacPorts] #66486: sendfile build fails In-Reply-To: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> References: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> Message-ID: <061.ce5815f10736d3b73c56c998c51aaef8@macports.org> #66486: sendfile build fails ------------------------+---------------------- Reporter: MStraeten | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: sendfile Port: sendfile | ------------------------+---------------------- Changes (by MStraeten): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:44:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 12:44:50 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.21b943fdcecc1f9e2066a87070583b66@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by jmroot): The diffutils port has a number of dependencies. Checking whether they are installed, installing them, and doing the build that uses them have to be done with the lock held, otherwise another port process could install or uninstall any of those dependencies after they are checked for, resulting in incorrect behaviour. If you want to be responsible for making sure this doesn't happen, you could edit `${prefix}/libexec/macports/lib/registry2.0/registry.tcl` and edit the `exclusive_lock` and `exclusive_unlock` procs to do nothing. But if it breaks, you get to keep the pieces. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:51:51 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 12:51:51 -0000 Subject: [MacPorts] #66486: sendfile @2.1b-20110604 build fails (was: sendfile build fails) In-Reply-To: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> References: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> Message-ID: <061.7ef4ead40af78c6ab696a2a17309fb76@macports.org> #66486: sendfile @2.1b-20110604 build fails ------------------------+-------------------- Reporter: MStraeten | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: sendfile | ------------------------+-------------------- Changes (by jmroot): * keywords: sendfile => Old description: > sudo port install sendfile > ---> Fetching distfiles for sendfile > ---> Verifying checksums for sendfile > ---> Extracting sendfile > ---> Applying patches to sendfile > ---> Configuring sendfile > ---> Building sendfile > Error: Failed to build sendfile: command execution failed New description: {{{ sudo port install sendfile ---> Fetching distfiles for sendfile ---> Verifying checksums for sendfile ---> Extracting sendfile ---> Applying patches to sendfile ---> Configuring sendfile ---> Building sendfile Error: Failed to build sendfile: command execution failed }}} -- Comment: {{{ :info:build sendfiled.c:2597:26: error: no member named 'ut_user' in 'struct utmp' :info:build strncpy(user,uinfo.ut_user,8); :info:build ~~~~~ ^ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 12:53:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 12:53:18 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.882e0bfe639f1b9d7120c1e0be491e4b@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ballapete): `port` lists a handful of dependencies that are all met. Otherwise it would try to install a missing dependency and would have to wait until it has the right to perform so. `port` lists 17 rdeps, all of them are them are met. Cairo is none of them, and so it Panga. So why does port fail? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 13:25:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 13:25:20 -0000 Subject: [MacPorts] #66481: py311-pylint @2.14.5: installation fails in macOS Mojave In-Reply-To: <045.1d752d00cf573998a6b3503122b3f088@macports.org> References: <045.1d752d00cf573998a6b3503122b3f088@macports.org> Message-ID: <060.f1ec42ae924229d665342951c15fbff5@macports.org> #66481: py311-pylint @2.14.5: installation fails in macOS Mojave ------------------------+---------------------- Reporter: JD-Veiga | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-pylint | ------------------------+---------------------- Changes (by Marius Schamschula ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"d0500fd94998471aad954cbd12fe6cf62a02b406/macports-ports" d0500fd94998471aad954cbd12fe6cf62a02b406/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="d0500fd94998471aad954cbd12fe6cf62a02b406" py-pylint: add missing pylint311 file Closes: https://trac.macports.org/ticket/66481 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:49:47 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 14:49:47 -0000 Subject: [MacPorts] #66487: gtk3 menues broken with macos ventura - update needed Message-ID: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> #66487: gtk3 menues broken with macos ventura - update needed -----------------------+-------------------- Reporter: MStraeten | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: gtk3 -----------------------+-------------------- gtk3 menues doesn't react on mouse hover on macos ventura reproducible with darktable but also with gtk3-demo (reported at gtk: https://gitlab.gnome.org/GNOME/gtk/-/issues/5305) There seems to be a fix for that see https://gitlab.gnome.org/Infrastructure/gimp-macos- build/-/commit/d965dc994b8a770a592a1b47436ef6a70e010056 needs to be integrated in macports -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:56:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 14:56:53 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Changes (by chillin-): * Attachment "main.log" removed. Mojave gtk3 main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:56:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 14:56:53 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.56c2412da8ecbf5db76fbc23f8de166c@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Changes (by chillin-): * Attachment "main.log" added. this is the real Mojave sdk3 build log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:57:15 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 14:57:15 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.6f819d168fe46e529804e80ce455a755@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by chillin-): > The attached log is from a failed build of libsdl2 @2.26.0, which is not the current version. oops. >< -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:57:37 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 14:57:37 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion Message-ID: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------------+-------------------- Reporter: RobK88 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: mountain-lion | Port: lerc ---------------------------+-------------------- I am unable to upgrade lerc from v 3.0 to v4.0 on my Mac running Mountain Lion. The port fails to build. {{{ bash-3.2$ port outdated The following installed ports are outdated: lerc 3.0_0 < 4.0.0_0 bash-3.2$ sudo port clean lerc ---> Cleaning lerc bash-3.2$ sudo port -v upgrade lerc ---> Computing dependencies for lerc. ---> Fetching archive for lerc ---> lerc-4.0.0_0.darwin_12.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified ---> Attempting to fetch lerc-4.0.0_0.darwin_12.x86_64.tbz2 from http://packages.macports.org/lerc % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 ---> Attempting to fetch lerc-4.0.0_0.darwin_12.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/lerc % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 ---> Attempting to fetch lerc-4.0.0_0.darwin_12.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/lerc % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 ---> Fetching distfiles for lerc ---> Verifying checksums for lerc ---> Checksumming lerc-4.0.0.tar.gz ---> Extracting lerc ---> Extracting lerc-4.0.0.tar.gz Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/lerc/lerc-4.0.0.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - ---> Configuring lerc Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.8" -DCMAKE_OSX_SYSROOT="/" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0 -- The C compiler identification is AppleClang 5.1.0.5030040 -- The CXX compiler identification is AppleClang 5.1.0.5030040 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/clang - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/clang++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_OBJCXX_COMPILER CMAKE_OBJC_COMPILER CMAKE_POLICY_DEFAULT_CMP0025 CMAKE_POLICY_DEFAULT_CMP0060 -- Build files have been written to: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build ---> Building lerc Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build" && /usr/bin/make -j2 -w all VERBOSE=ON make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' /opt/local/bin/cmake -S/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0 -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build --check-build-system CMakeFiles/Makefile.cmake 0 /opt/local/bin/cmake -E cmake_progress_start /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build/CMakeFiles /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build//CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' /usr/bin/make -f CMakeFiles/Lerc.dir/build.make CMakeFiles/Lerc.dir/depend make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build/CMakeFiles/Lerc.dir/DependInfo.cmake --color= make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' /usr/bin/make -f CMakeFiles/Lerc.dir/build.make CMakeFiles/Lerc.dir/build make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' [ 6%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/BitStuffer2.cpp.o /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.8 -fPIC -std=gnu++1y -MD -MT CMakeFiles/Lerc.dir/src/LercLib/BitStuffer2.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/BitStuffer2.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/BitStuffer2.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/BitStuffer2.cpp [ 13%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/BitMask.cpp.o /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.8 -fPIC -std=gnu++1y -MD -MT CMakeFiles/Lerc.dir/src/LercLib/BitMask.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/BitMask.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/BitMask.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/BitMask.cpp [ 20%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/Huffman.cpp.o /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.8 -fPIC -std=gnu++1y -MD -MT CMakeFiles/Lerc.dir/src/LercLib/Huffman.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/Huffman.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/Huffman.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Huffman.cpp [ 26%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/Lerc.cpp.o /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.8 -fPIC -std=gnu++1y -MD -MT CMakeFiles/Lerc.dir/src/LercLib/Lerc.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/Lerc.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/Lerc.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp [ 33%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/BitStuffer.cpp.o /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.8 -fPIC -std=gnu++1y -MD -MT CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/BitStuffer.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/BitStuffer.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/BitStuffer.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc1Decode/BitStuffer.cpp /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1541:64: error: no template named 'greater' in namespace 'std'; did you mean 'isgreater'? std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); ~~~~~^~~~~~~ isgreater /usr/bin/../lib/c++/v1/cmath:478:1: note: 'isgreater' declared here isgreater(_A1 __x, _A2 __y) _NOEXCEPT ^ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1541:59: error: no matching function for call to 'isgreater' std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); ^~~~~~~~~~~~~~~~~~~~ /usr/bin/../lib/c++/v1/cmath:478:1: note: candidate function template not viable: requires 2 arguments, but 0 were provided isgreater(_A1 __x, _A2 __y) _NOEXCEPT ^ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1568:64: error: no template named 'greater' in namespace 'std'; did you mean 'isgreater'? std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); ~~~~~^~~~~~~ isgreater /usr/bin/../lib/c++/v1/cmath:478:1: note: 'isgreater' declared here isgreater(_A1 __x, _A2 __y) _NOEXCEPT ^ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1568:59: error: no matching function for call to 'isgreater' std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); ^~~~~~~~~~~~~~~~~~~~ /usr/bin/../lib/c++/v1/cmath:478:1: note: candidate function template not viable: requires 2 arguments, but 0 were provided isgreater(_A1 __x, _A2 __y) _NOEXCEPT ^ [ 40%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/CntZImage.cpp.o /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.8 -fPIC -std=gnu++1y -MD -MT CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/CntZImage.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/CntZImage.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/Lerc1Decode/CntZImage.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc1Decode/CntZImage.cpp 4 errors generated. make[2]: *** [CMakeFiles/Lerc.dir/src/LercLib/Lerc.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' make[1]: *** [CMakeFiles/Lerc.dir/all] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/work/build" && /usr/bin/make -j2 -w all VERBOSE=ON Exit code: 2 Error: Failed to build lerc: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. bash-3.2$ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 14:58:03 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 14:58:03 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.28aa105106639a7531c8f56da34ee779@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+--------------------------- Reporter: RobK88 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: mountain-lion Port: lerc | ---------------------+--------------------------- Changes (by RobK88): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:10:46 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 15:10:46 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.42cd76c75594e97a9436881615b2190d@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+--------------------------- Reporter: RobK88 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: mountain-lion Port: lerc | ---------------------+--------------------------- Comment (by RobK88): FYI -- Until the port is fixed, the workaround is simple -- specify a newer compiler when installing or upgrading lerc. {{{ bash-3.2$ sudo port clean lerc Password: ---> Cleaning lerc bash-3.2$ sudo port upgrade lerc configure.compiler=macports-clang-7.0 ---> Computing dependencies for lerc ---> Fetching archive for lerc ---> Attempting to fetch lerc-4.0.0_0.darwin_12.x86_64.tbz2 from http://packages.macports.org/lerc ---> Attempting to fetch lerc-4.0.0_0.darwin_12.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/lerc ---> Attempting to fetch lerc-4.0.0_0.darwin_12.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/lerc ---> Fetching distfiles for lerc ---> Verifying checksums for lerc ---> Extracting lerc ---> Configuring lerc ---> Building lerc ---> Staging lerc into destroot ---> Installing lerc @4.0.0_0 ---> Cleaning lerc ---> Deactivating lerc @3.0_0 ---> Cleaning lerc ---> Activating lerc @4.0.0_0 ---> Cleaning lerc ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. bash-3.2$ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:17:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 15:17:13 -0000 Subject: [MacPorts] #66477: mpich-default +native: clang: error: the clang compiler does not support '-march=native' In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.805a0b306eda487a9d134c2ea103e93b@macports.org> #66477: mpich-default +native: clang: error: the clang compiler does not support '-march=native' ----------------------------+---------------------- Reporter: chaochinyang | Owner: eborisch Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: arm64 Port: mpich-default | ----------------------------+---------------------- Comment (by eborisch): Since it works without +native, just install that? Adding -march=native is almost all +native does. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:28:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 15:28:42 -0000 Subject: [MacPorts] #66489: Help required updating the port for TortoiseHG to 6.3.1 Message-ID: <055.5991b60ee65c3804191b4adc30c41b12@macports.org> #66489: Help required updating the port for TortoiseHG to 6.3.1 --------------------------------+------------------------------ Reporter: Themanwithoutaplan | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: devel/tortoisehg --------------------------------+------------------------------ I've started work updating the portfile. Unfortunately, it looks like changes upstream in Python mean a simple update of version and hashes are not sufficient. When running port -v build against the local repository I get the following error: {{{ Executing: cd "/opt/local/var/macports/build /_Users_charlieclark_temp_macports- ports_devel_tortoisehg/tortoisehg/work/thg-6.3.1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 setup.py --no-user-cfg build -j1 /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn() }}} I'm trying to work out how the build is initiated so that changes can be made but it's not clear to me how the build is initiated by MacPorts. There is a makefile with an "app" target but I can't get that to work either because `HGPATH` is missing or wrong. FWIW in the thg repos there is another approach to building the app in contrib/packaging/macos but it looks to me like this is not being called. Apart from updating the port, I'm hoping improve the build process and docs upstream. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:51:52 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 15:51:52 -0000 Subject: [MacPorts] #66436: cctools @949.0.1_2 checksum mismatch In-Reply-To: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> References: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> Message-ID: <058.7a0625f8795dc8e1ed16a734acb3bc90@macports.org> #66436: cctools @949.0.1_2 checksum mismatch ----------------------+---------------------- Reporter: gplunk | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+---------------------- Comment (by michaelld): Yes the extracted files are the same ... checksums & size are different. Once I verify build, I'll put in a PR for the move to Github -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:52:45 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 15:52:45 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.238ab9591e3e97907589f333acf924ff@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by jmroot): You can deduce that it is safe to run these particular commands at the same time because you have the benefit of knowing what actions you are performing, the ports they are operating on, what their dependencies are, and the current state of those dependencies. Each `port` process on the other hand has no way of knowing what the others are going to do. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 15:55:28 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 15:55:28 -0000 Subject: [MacPorts] #66487: gtk3 menues broken with macos ventura - update needed In-Reply-To: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> References: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> Message-ID: <061.d0a5f978cbe00bccb66779cc5a244d8a@macports.org> #66487: gtk3 menues broken with macos ventura - update needed ------------------------+---------------------- Reporter: MStraeten | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gtk3 | ------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => mascguy -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:03:35 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:03:35 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.dbd5ed76937294b30153c5921d70fd23@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Changes (by jmroot): * cc: vince@? (removed) * cc: dgilman, reneeotten (added) * keywords: mountain-lion => * status: new => assigned * owner: (none) => Veence Comment: Fails to build on everything < 10.14, in fact. `std::greater` is very old so the compiler is unlikely to be the problem. A missing `#include ` perhaps? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:07:26 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:07:26 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.e510693e233354fdfaedab28538f2b40@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Comment (by jmroot): Yep. https://github.com/Esri/lerc/commit/6292d634f4d138696305e1025325e2f4be2c2f92 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:09:26 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:09:26 -0000 Subject: [MacPorts] #66489: Help required updating the port for TortoiseHG to 6.3.1 In-Reply-To: <055.5991b60ee65c3804191b4adc30c41b12@macports.org> References: <055.5991b60ee65c3804191b4adc30c41b12@macports.org> Message-ID: <070.8658601440f324cdd11fc3942045d46e@macports.org> #66489: Help required updating the port for TortoiseHG to 6.3.1 ---------------------------------+-------------------- Reporter: Themanwithoutaplan | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: tortoisehg | ---------------------------------+-------------------- Changes (by jmroot): * port: devel/tortoisehg => tortoisehg -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:21:29 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:21:29 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.747e2e675ecdf892d40058cff2a8fa82@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Comment (by RobK88): @jmroot - Joshua, Thanks for the fix by adding the missing `#include` statements. I am curious. Why do you think, the code compiled without these `#include` statements using a newer compiler such as clang-7.0? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:21:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:21:55 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.f97dfa2d64ca014b71878f9836365fe6@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): well, we?re getting closer to sorting you out. Now we know it builds fine, and the error is somewhere on your system. {{{ gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found }}} what version of glib2 have you got installed, x11 or quartz? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:24:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:24:40 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.bb4ba122907ed5bd236b30d21c63627e@macports.org> #66476: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave -----------------------+--------------------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: gtk3 NetSurf Mojave Port: gtk3 | -----------------------+--------------------------------- Comment (by kencu): by the way, if you are looking for a browser for old macos versions 10.7 to 10.12, use this, it?s the best there is and usually works well: https://github.com/blueboxd/chromium-legacy -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:26:38 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:26:38 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found (was: gtk3 @3.24.34_2 (NetSurf dependency) build fail on Mojave) In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.432352a1cc404f55215f9f639357d791@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+-------------------- Changes (by kencu): * keywords: gtk3 NetSurf Mojave => Mojave -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:30:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:30:12 -0000 Subject: [MacPorts] #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' In-Reply-To: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> References: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> Message-ID: <061.3419e18ea40e150bc011ea53d70ec17f@macports.org> #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: diffutils | ------------------------+----------------------- Comment (by kencu): it?s a common Tiger error? the register names are slightly different in the 10.4 sdk. I?ll fix it a bit later on for you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:44:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:44:19 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.0da8e067ec7dba156a269d560e7f937d@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Comment (by jmroot): Standard library headers can include other headers internally, so it's possible to get a header included without explicitly asking for it. But you can't rely on this happening since it's an implementation detail that can easily change between stdlib implementations and different versions of the same stdlib. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 16:54:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 16:54:42 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.6954733a7bc4569305f4190b13320de2@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+-------------------- Comment (by chillin-): Replying to [comment:13 kencu]: > what version of glib2 have you got installed, x11 or quartz? glib2 @2.70.5_0+quartz Replying to [comment:14 kencu]: > by the way, if you are looking for a browser for old macos versions 10.7 to 10.12, use this, it?s the best there is and usually works well: > > https://github.com/blueboxd/chromium-legacy Thanks, I'll check it out. Chrome horrified me, though I have heard Chromium is different -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:21:56 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:21:56 -0000 Subject: [MacPorts] #66490: (cmus, 10.13.6) failed to build lerc Message-ID: <044.77063dc9a918c6fc99a1907dd1257121@macports.org> #66490: (cmus, 10.13.6) failed to build lerc -----------------------------------+-------------------- Reporter: mrkapqa | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: cmus lerc high sierra | Port: cmus -----------------------------------+-------------------- Hello , on a fresh installation of 10.13.6 getting the following error {{{ ---> Building lerc Error: Failed to build lerc: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gis_lerc/lerc/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port cmus failed }}} Thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:22:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:22:12 -0000 Subject: [MacPorts] #66490: (cmus, 10.13.6) failed to build lerc In-Reply-To: <044.77063dc9a918c6fc99a1907dd1257121@macports.org> References: <044.77063dc9a918c6fc99a1907dd1257121@macports.org> Message-ID: <059.1cb1775814f392fda5d4fe7bd5b99cbe@macports.org> #66490: (cmus, 10.13.6) failed to build lerc ----------------------+----------------------------------- Reporter: mrkapqa | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: cmus lerc high sierra Port: cmus | ----------------------+----------------------------------- Changes (by mrkapqa): * Attachment "lerq.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:24:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:24:50 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.bcd3276e20044517edbc574e2dd96f8a@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+-------------------- Comment (by chillin-): Sorry OT again. Unfortunately, Chromium legacy is giving me the same business as Firefox legacy. https://youtu.be/6OZXWboon6Y These two minis, 2011 ML & 2012 Mojave, are headless, so interface is through ssh and vnc. Safari doesn't do that on ML, nor does that happen with Firefox or anything else on Mojave. Currently, curl -Ok and wget are my best web performers on the ML mini. That's why I installed NetSurf, because it appears to still be under development and has a version number above 0.x. I don't really need a browser on ML very often, and, technically, I don't need one at all so long as Firefox is still updated and working on Mojave. It would just be more convenient, cut out the Mojave middleman. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:29:32 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:29:32 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.df7776f4421bc7121b6c0f331362a854@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+-------------------- Comment (by mascguy): Replying to [comment:13 kencu]: > well, we?re getting closer to sorting you out. Now we know it builds fine, and the error is somewhere on your system. > > {{{ > gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found > }}} > > what version of glib2 have you got installed, x11 or quartz? Ken's spot-on with respect to the underlying cause: You have glib2 installed for quartz, but other dependencies are being built for x11. So you need to be consistent, and install everything with +quartz. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:33:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:33:25 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.ac7dd94317d1f05c79a0b8b1544bea49@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by vallon): The bsdmake.diff file is reversed, but I would not just accept the new file. The portfile has been working for 10 years. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:36:49 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:36:49 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.a75712b11b1cfdb48219f8722c343066@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+-------------------- Comment (by chillin-): Replying to [comment:18 mascguy]: > Ken's spot-on with respect to the underlying cause: You have glib2 installed for quartz, but other dependencies are being built for x11. So you need to be consistent, and install everything with +quartz. Like what, for instance? {{{ $ port installed |grep +x11 cairo @1.17.4_0+quartz+x11 (active) gd2 @2.3.3_1+x11 (active) ghostscript @9.56.1_0+x11 (active) graphviz @7.0.1_0+pangocairo+x11 (active) ImageMagick @6.9.11-60_3+x11 (active) pango @1.50.7_0+quartz+x11 (active) py27-cairo @1.18.2_0+quartz+x11 (active) $ port installed |grep +quartz cairo @1.17.4_0+quartz+x11 (active) gegl @0.4.38_2+quartz (active) gimp @2.10.32_1+quartz (active) gimp-lqr-plugin @0.7.2_3+quartz (active) gimp2 @2.10.32_2+python27+quartz (active) glib2 @2.70.5_0+quartz (active) gtk2 @2.24.33_3+quartz (active) gutenprint @5.3.3_0+quartz (active) libglade2 @2.6.4_8+quartz (active) pango @1.50.7_0+quartz+x11 (active) py27-cairo @1.18.2_0+quartz+x11 (active) py27-gobject @2.28.7_2+quartz (active) py27-pygtk @2.24.0_6+quartz (active) py39-cairo @1.21.0_0+quartz (active) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:37:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:37:25 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.3f7ab8c60667c993541b1db284c8c442@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ballapete): Hoe can software components vanish by installation? The act removing is called de- or uninstallation. Even when I change software +variant_a to software minus or plus any other variant nothing will vanish, because each variant is equivalent (otherwise it would be a different port). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:37:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:37:55 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.fb26dfb6d791ffdb22760b14b64c1658@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by rieder): Shouldn't the solution be to add a file `bsdmake- 24_1.darwin_22.arm64.tbz2` to the package servers? for x86_64 it exists, but for arm64 (my architecture), it is missing. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:42:06 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:42:06 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.128a54a8c99167e63167f477a7f8a016@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by vallon): The original problem seems to be installing binaries. The source checksums fail (as well): Portfile lists master_sites http://opensource.apple.com/tarballs/${name} port log shows :notice:fetch ---> Attempting to fetch bsdmake-24.tar.gz from http://opensource.apple.com/tarballs/bsdmake wget of that does some redirects: original http://opensource.apple.com/tarballs/bsdmake/bsdmake-24.tar.gz to https https://opensource.apple.com/tarballs/bsdmake/bsdmake-24.tar.gz to github https://github.com/apple-oss- distributions/bsdmake/archive/refs/tags/bsdmake-24.tar.gz to codeload.github https://codeload.github.com/apple-oss- distributions/bsdmake/tar.gz/refs/tags/bsdmake-24 $ sha256sum bsdmake-24.tar.gz 096f333f94193215931a9fab86b9bca0713fbd22ec465bf55510067b53940e62 bsdmake-24.tar.gz $ port cat bsdmake | grep sha256 sha256 82a948b80c2abfc61c4aa5c1da775986418a8e8eb3dd896288cfadf2e19c4985 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 17:58:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 17:58:25 -0000 Subject: [MacPorts] #66491: py-spyder: The 'astroid<=2.12.0-dev0, >=2.11.6' distribution was not found and is required by pylint Message-ID: <041.3aee0b1f38554f7761985667fc3d8519@macports.org> #66491: py-spyder: The 'astroid<=2.12.0-dev0,>=2.11.6' distribution was not found and is required by pylint --------------------+------------------------ Reporter: mf2k | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: py-spyder --------------------+------------------------ I am not able to launch spyder-3.10. {{{ $ spyder Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 581, in _build_master ws.require(__requires__) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 909, in require needed = self.resolve(parse_requirements(requirements)) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 800, in resolve raise VersionConflict(dist, req).with_context(dependent_req) pkg_resources.ContextualVersionConflict: (astroid 2.12.13 (/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages), Requirement.parse('astroid<=2.12.0-dev0,>=2.11.6'), {'pylint'}) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/local/bin/spyder", line 33, in sys.exit(load_entry_point('spyder==5.4.0', 'gui_scripts', 'spyder')()) File "/opt/local/bin/spyder", line 25, in importlib_load_entry_point return next(matches).load() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/metadata/__init__.py", line 171, in load module = import_module(match.group('module')) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 1006, in _find_and_load_unlocked File "", line 688, in _load_unlocked File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/spyder/app/start.py", line 58, in from spyder.utils.external import lockfile File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/spyder/utils/external/lockfile.py", line 31, in from spyder.utils.programs import is_spyder_process File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/spyder/utils/programs.py", line 28, in import pkg_resources File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 3260, in def _initialize_master_working_set(): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 3234, in _call_aside f(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 3272, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 583, in _build_master return cls._build_from_requirements(__requires__) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 596, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 795, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'astroid<=2.12.0-dev0,>=2.11.6' distribution was not found and is required by pylint }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 18:19:47 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 18:19:47 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.3e6aeb6bc308655c3911b57a586bec40@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+-------------------- Reporter: chillin- | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+-------------------- Comment (by mascguy): Replying to [comment:19 chillin-]: > Like what, for instance? Based on your list of installed ports, everything else looks great. So you're close! The one item you now need to install with `+quartz`, is gtk3. But you can simplify the process, by specifying `+quartz` when installing NetSurf. (Even though the latter doesn't have a quartz variant, it will cascase to all deps... including gtk3.) {{{ $ sudo port clean gtk3 netsurf $ sudo port install netsurf +quartz }}} Give that a try, and let us know how it goes! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 18:21:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 18:21:40 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.add272278a8d6f3f05b93b95aad3f222@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Changes (by mascguy): * owner: (none) => mascguy * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 18:32:00 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 18:32:00 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.04d1d428c53efd03b2fa477cea8edde5@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by vallon): Internet archive to the rescue: http://web.archive.org/web/20210124223828/http://opensource.apple.com/tarballs/bsdmake/bsdmake-24.tar.gz {{{ $ wget http://web.archive.org/web/20210124223828/http://opensource.apple.com/tarballs/bsdmake/bsdmake-24.tar.gz ... $ sha256sum bsdmake-24.tar.gz 82a948b80c2abfc61c4aa5c1da775986418a8e8eb3dd896288cfadf2e19c4985 bsdmake-24.tar.gz }}} That matches the Portfile. The contents are identical, but the top-level directory name is different (old bsdmake-24 new bsdmake-bsdmake-24). The github format is $reponame-$tagname, and the tag in the git repo is "bsdmake-24": {{{ $ sha256sum archive/bsdmake-24.tar.gz github/bsdmake-24.tar.gz 82a948b80c2abfc61c4aa5c1da775986418a8e8eb3dd896288cfadf2e19c4985 archive/bsdmake-24.tar.gz 096f333f94193215931a9fab86b9bca0713fbd22ec465bf55510067b53940e62 github/bsdmake-24.tar.gz $ tar -C archive -xzf archive/bsdmake-24.tar.gz $ tar -C github -xzf github/bsdmake-24.tar.gz $ ls archive github archive: bsdmake-24 bsdmake-24.tar.gz github: bsdmake-24.tar.gz bsdmake-bsdmake-24 $ diff -Nur archive/bsdmake-24 github/bsdmake-bsdmake-24 }}} Created https://github.com/macports/macports-ports/pull/16992 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 18:41:56 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 18:41:56 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.44284beb8ccda63b109f70b493629691@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by vallon): PR failed. It fetched https://distfiles.macports.org/bsdmake/bsdmake-24.tar.gz. That file matches the internet archive, but does not match the master-site. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 20:12:43 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 20:12:43 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.4485f63cd2eec0c120b148e03286c77a@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by jmroot): Again, you know that nothing is being uninstalled by the particular commands you run, but port does not. You could just as easily run `port install pango` and then `port uninstall ninja` while the first command is still running. Of course these problems are not impossible to solve, but I hope you understand that the lock is not there just to get in your way, and that implementing a finer-grained locking scheme would be a significant amount of work. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 20:43:54 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 20:43:54 -0000 Subject: [MacPorts] #66490: (cmus, 10.13.6) failed to build lerc In-Reply-To: <044.77063dc9a918c6fc99a1907dd1257121@macports.org> References: <044.77063dc9a918c6fc99a1907dd1257121@macports.org> Message-ID: <059.67b3bcdaf908eda224f64756c8513933@macports.org> #66490: (cmus, 10.13.6) failed to build lerc ------------------------+-------------------- Reporter: mrkapqa | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: lerc | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * keywords: cmus lerc high sierra => * resolution: => duplicate * port: cmus => lerc Comment: #66488 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:00:34 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 21:00:34 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.0beb2a32d00e75414bdcfbfa5ac86665@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by kencu): Replying to [comment:17 chillin-]: > Sorry OT again. > Unfortunately, Chromium legacy is giving me the same business as Firefox legacy. The author of chromium legacy builds a new version every 12 hours or so :> Sometimes, one build can be a bit flaky, depending the latest commits. I just try another version. I found a good one a few months ago, and have been using it ever since on 10.7 with great success. There is -- currently -- no better browser to be found anywhere for these systems though, so you won't do any better looking elsewhere. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:01:23 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 21:01:23 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz (was: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found) In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.3d887c37c397cc71e7f8a539a04f6829@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:03:57 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 21:03:57 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) In-Reply-To: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> References: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> Message-ID: <061.33e68b799c026227a62cecd19ad0bd65@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: python311 | ------------------------+----------------------- Comment (by kencu): python311 installed on Tiger Intel as is, but the installation on Tiger PPC required a trivial tweak to the ldflags. I'll PR that in a bit. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:29:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 21:29:12 -0000 Subject: [MacPorts] #66154: py-pyobjc: Update to 8.6 In-Reply-To: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> References: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> Message-ID: <056.6fdb8c073f54ffa7db78d9755f2e88ad@macports.org> #66154: py-pyobjc: Update to 8.6 ------------------------+---------------------- Reporter: mf2k | Owner: danchr Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyobjc | ------------------------+---------------------- Comment (by Schamschula): It looks like version 9.0 is also need to py311 (and py312). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:33:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 21:33:12 -0000 Subject: [MacPorts] #66154: py-pyobjc: Update to 8.6 In-Reply-To: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> References: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> Message-ID: <056.878b36d64c4aacc0a4984e8e66098e76@macports.org> #66154: py-pyobjc: Update to 8.6 ------------------------+---------------------- Reporter: mf2k | Owner: danchr Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyobjc | ------------------------+---------------------- Comment (by Schamschula): See: https://github.com/macports/macports- ports/commit/09d2d77fa4aa0d74ee3ba6052e86512c02c2d174 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 21:45:07 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 21:45:07 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.d7bd4f42edff085b81a4d0d5a73b7199@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Comment (by RobK88): Thanks for the info. I learnt something new today. I always thought stdlib was governed by a standard and was not implementation dependent. Now I know better. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:00:23 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 22:00:23 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.77c3495c37de9d111831912ddffbfe77@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Comment (by jmroot): It is governed by a standard, but the standard doesn't specify every implementation detail. The standard requires that if you `#include ` then `std::greater` is defined. It doesn't require it to be undefined otherwise. In fact if it required that no header pull in definitions from any other header, that would be pretty much impossible to comply with. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:06:00 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 22:06:00 -0000 Subject: [MacPorts] #66492: mpir requires texinfo but is not a requirement.... Message-ID: <046.fd4a020c28b22c6c7c4b3f404668ac03@macports.org> #66492: mpir requires texinfo but is not a requirement.... -----------------------+-------------------- Reporter: sck-nogas | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: mpir -----------------------+-------------------- While building gnuradio, I got a failure in mpir... Digging in deeper, I discovered that it was failing due to a missing makeinfo. {{{ ---> Fetching archive for mpir ---> Attempting to fetch mpir-3.0.0_2.darwin_22.x86_64.tbz2 from https://packages.macports.org/mpir ---> Attempting to fetch mpir-3.0.0_2.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/mpir ---> Attempting to fetch mpir-3.0.0_2.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/mpir ---> Building mpir Error: Failed to build mpir: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port gr-osmosdr failed :info:build /bin/sh ../libtool --tag=CXX --mode=link /usr/bin/clang++ -pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64 -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch x86_64 -o libcxx.la isfuns.lo ismpf.lo ismpq.lo ismpz.lo ismpznw.lo osdoprnti.lo osfuns.lo osmpf.lo osmpq.lo osmpz.lo :info:build libtool: link: ar cq .libs/libcxx.a .libs/isfuns.o .libs/ismpf.o .libs/ismpq.o .libs/ismpz.o .libs/ismpznw.o .libs/osdoprnti.o .libs/osfuns.o .libs/osmpf.o .libs/osmpq.o .libs/osmpz.o :info:build libtool: link: ranlib .libs/libcxx.a :info:build libtool: link: ( cd ".libs" && rm -f "libcxx.la" && ln -s "../libcxx.la" "libcxx.la" ) :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a/cxx' :info:build Making all in tune :info:build make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a/tune' :info:build make[2]: Nothing to be done for `all'. :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a/tune' :info:build Making all in doc :info:build make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a/doc' :info:build restore=: && backupdir=".am$$" && \ :info:build am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \ :info:build rm -rf $backupdir && mkdir $backupdir && \ :info:build if (/bin/sh '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work/mpir-3.0.0/missing' makeinfo --version) >/dev/null 2>&1; then \ :info:build for f in mpir.info mpir.info-[0-9] mpir.info-[0-9][0-9] mpir.i[0-9] mpir.i[0-9][0-9]; do \ :info:build if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ :info:build done; \ :info:build else :; fi && \ :info:build cd "$am__cwd"; \ :info:build if /bin/sh '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work/mpir-3.0.0/missing' makeinfo -I . \ :info:build -o mpir.info mpir.texi; \ :info:build then \ :info:build rc=0; \ :info:build CDPATH="${ZSH_VERSION+.}:" && cd .; \ :info:build else \ :info:build rc=$?; \ :info:build CDPATH="${ZSH_VERSION+.}:" && cd . && \ :info:build $restore $backupdir/* `echo "./mpir.info" | sed 's|[^/]*$||'`; \ :info:build fi; \ :info:build rm -rf $backupdir; exit $rc :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work/mpir-3.0.0/missing: line 81: makeinfo: command not found :info:build WARNING: 'makeinfo' is missing on your system. :info:build You should only need it if you modified a '.texi' file, or :info:build any other file indirectly affecting the aspect of the manual. :info:build You might want to install the Texinfo package: :info:build :info:build The spurious makeinfo call might also be the consequence of :info:build using a buggy 'make' (AIX, DU, IRIX), in which case you might :info:build want to install GNU make: :info:build :info:build make[2]: *** [mpir.info] Error 127 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a/doc' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work /wbhart-mpir-cdd444a' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mpir/mpir/work/mpir-3.0.0" && /usr/bin/make -j8 -w all :info:build Exit code: 2 :error:build Failed to build mpir: command execution failed :debug:build Error code: CHILDSTATUS 52173 2 }}} Once I installed texinfo, the compile worked. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:13:41 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 22:13:41 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.df0a5ecf16f38d96143dbc6da253d4d0@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Replying to [comment:20 mascguy]: > Based on your list of installed ports, everything else looks great. So you're close! > > The one item you now need to install with `+quartz`, is gtk3. But you can simplify the process, by specifying `+quartz` when installing NetSurf. (Even though the latter doesn't have a quartz variant, it will cascade to all deps... including gtk3.) > > > {{{ > $ sudo port clean gtk3 netsurf > $ sudo port install netsurf +quartz > }}} > > Give that a try, and let us know how it goes! Just finished building xorg. Trying this now (w/ -vsN) Replying to [comment:22 kencu]: > Replying to [comment:17 chillin-]: > > Sorry OT again. > > Unfortunately, Chromium legacy is giving me the same business as Firefox legacy. > > The author of chromium legacy builds a new version every 12 hours or so :> > > Sometimes, one build can be a bit flaky, depending the latest commits. I just try another version. I found a good one a few months ago, and have been using it ever since on 10.7 with great success. I installed the stable version, 108.0.5359.98.2. Maybe when I have time to test out older versions, but since both the last ML supported version of Firefox and Firefox legacy gave me the same behavior, I'm not optimistic. I also tried out Ungoogled Chromium, but it gave me the same problem as before over VNC. Replying to [comment:22 kencu]: > There is -- currently -- no better browser to be found anywhere for these systems though, so you won't do any better looking elsewhere. That is highly subjective. IMO Safari is superior to Chromium, at least what I have just seen of it, with its residual "log in" crap, and Google failing to respect boundaries. They're both WebKit, anyway, but Safari's dress is better all around. I don't really like either Firefox's or Chrome's or Chromium's method of putting settings in the browser and all that crap on the Tool Bar and popups and nags. If you're going to make a native application, then make it native, use the native UI. Apple is annoying too, and getting more and more annoying, but I still think Safari has a better and simpler UI with easy to find defaults to change to "do nothing, show nothing automatically, don't suggest anything & don't track." I'm not a developer, but I actually did write one single application for my late sister years ago. She had bad surfing habits, and I was concerned for her getting robbed or getting her identity stolen. It was called, "Safari Reset," and it worked on Snow Leopard and Lion (maybe ML, too, haven't tried it). All it did was delete every Safari setting, all bookmarks, cookies, caches, everything that can change from a default fresh install it just removed. Took about half a second and relaunched Safari. Track that, Google. I really miss my sister... and Snow Leopard. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:19:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 22:19:18 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.ddbf918a70609bf9e85ad67bfea5b8e0@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Changes (by chillin-): * Attachment "Safari Reset.app.zip" added. c. 2014. Try ir out -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 22:41:19 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 22:41:19 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.6f060d87deb40f781954fd647b640871@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Build succeeded on Mojave, but I'm getting the same problem at launch as on Mountain Lion {{{ bash-3.2$ sudo port load dbus Password: ---> Loading startupitem 'dbus-system' for dbus ---> Loading startupitem 'dbus-session' for dbus bash-3.2$ netsurf-gtk3 Options failed to initialise (BadParameter) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 23:43:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 23:43:18 -0000 Subject: [MacPorts] #66493: Libarchive 3.6.2 breaks all builds that depends on it. Message-ID: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> #66493: Libarchive 3.6.2 breaks all builds that depends on it. --------------------+------------------------ Reporter: lukaso | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: Keywords: | Port: libarchive --------------------+------------------------ Here is the upstream issue: https://github.com/libarchive/libarchive/issues/1819 Any build that depends on libarchive is now breaking. Best solution I believe, is to revert to 3.6.1 until this is fixed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 23:46:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 23:46:20 -0000 Subject: [MacPorts] #66493: Libarchive 3.6.2 breaks all builds that depends on it. In-Reply-To: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> References: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> Message-ID: <058.1992df4c6212e0015a5e7a7f88f4a7f1@macports.org> #66493: Libarchive 3.6.2 breaks all builds that depends on it. -------------------------+-------------------- Reporter: lukaso | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | -------------------------+-------------------- Comment (by lukaso): I've created a PR: https://github.com/macports/macports-ports/pull/16993 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 23:47:32 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 23:47:32 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.d08e9d972305e88a193c17e1bdf63b88@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): {{{ bash-3.2$ netsurf-gtk3 -v (0.000001) [INFO netsurf] frontends/gtk/gui.c:1003 nserror create_config_home(char **): Attempting to create configuration directory (0.000060) [INFO netsurf] frontends/gtk/gui.c:1243 int main(int, char **): Unable to locate a configuration directory. (0.000070) [INFO netsurf] utils/log.c:268 nserror nslog_init(nslog_ensure_t *, int *, char **): NetSurf version '3.10 (24th May 2020)' (0.000107) [INFO netsurf] utils/log.c:279 nserror nslog_init(nslog_ensure_t *, int *, char **): NetSurf on , node , release <18.7.0>, version , machine (0.000511) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/netsurf.gtk3.ui (0.000594) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/tabcontents.gtk3.ui (0.000670) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/password.gtk3.ui (0.000740) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/toolbar.gtk3.ui (0.000810) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/downloads.gtk3.ui (0.000877) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/globalhistory.gtk3.ui (0.000945) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/localhistory.gtk3.ui (0.001012) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/options.gtk3.ui (0.001078) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/hotlist.gtk3.ui (0.001144) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/cookies.gtk3.ui (0.001211) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/viewdata.gtk3.ui (0.001271) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/warning.gtk3.ui (0.001336) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/pageinfo.gtk3.ui (0.001401) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/favicon.png (0.001464) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/netsurf.xpm (0.001524) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/menu_cursor.png (0.001590) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/local-history.png (0.001651) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/show-cookie.png (0.001717) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/24x24/actions/page-info-insecure.png (0.001776) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/24x24/actions/page-info-internal.png (0.001839) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/24x24/actions/page-info-local.png (0.001906) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/24x24/actions/page-info-secure.png (0.001969) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/24x24/actions/page-info-warning.png (0.002032) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/48x48/actions/page-info-insecure.png (0.002094) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/48x48/actions/page-info-internal.png (0.002157) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/48x48/actions/page-info-local.png (0.002220) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/48x48/actions/page-info-secure.png (0.002283) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/48x48/actions/page-info-warning.png (0.002346) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber0.png (0.002408) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber1.png (0.002474) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber2.png (0.002533) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber3.png (0.002593) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber4.png (0.002653) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber5.png (0.002712) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber6.png (0.002775) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber7.png (0.002839) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/throbber/throbber8.png (0.002913) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/welcome.html (0.002992) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/credits.html (0.003064) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/licence.html (0.003138) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/default.css (0.003211) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/adblock.css (0.003291) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/internal.css (0.003362) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/quirks.css (0.003435) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/netsurf.png (0.003510) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/default.ico (0.003585) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/arrow-l.png (0.003659) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/content.png (0.003734) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/directory2.png (0.003808) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/directory.png (0.003884) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/hotlist-add.png (0.003958) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/hotlist-rmv.png (0.004032) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/icons/search.png (0.004107) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/languages (0.004183) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/accelerators (0.004259) [INFO netsurf] frontends/gtk/resources.c:240 nserror init_resource(char **, struct nsgtk_resource_s *): Found gresource path /org/netsurf/Messages (0.004293) [INFO netsurf] frontends/gtk/gui.c:211 nserror set_defaults(struct nsoption_s *): Failed initialising default resource paths Options failed to initialise (BadParameter) bash-3.2$ }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 16 23:51:15 2022 From: noreply at macports.org (MacPorts) Date: Fri, 16 Dec 2022 23:51:15 -0000 Subject: [MacPorts] #66491: py-pylint: The 'astroid<=2.12.0-dev0, >=2.11.6' distribution was not found and is required by pylint (was: py-spyder: The 'astroid<=2.12.0-dev0, >=2.11.6' distribution was not found and is required by pylint) In-Reply-To: <041.3aee0b1f38554f7761985667fc3d8519@macports.org> References: <041.3aee0b1f38554f7761985667fc3d8519@macports.org> Message-ID: <056.ef89539cf6ddacd7ea4c47d36a70392c@macports.org> #66491: py-pylint: The 'astroid<=2.12.0-dev0,>=2.11.6' distribution was not found and is required by pylint ------------------------------------+---------------------- Reporter: mf2k | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: py-pylint, py-astroid | ------------------------------------+---------------------- Changes (by reneeotten): * cc: stromnov (removed) * cc: reneeotten (added) * owner: reneeotten => stromnov * port: py-spyder => py-pylint, py-astroid Comment: this is caused by an [https://github.com/macports/macports- ports/commit/0b458fed3045d2a5c08994009dabd97206b14835#commitcomment-93363742 update] of py-astroid that broke py-pylint - nothing specific related to py-spyder. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:17:00 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 00:17:00 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.41adbdfe684a4f01c2bd02dba5384892@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: Port: libmsn | --------------------------+-------------------- Comment (by mpbb77): I've just tried to install the full kde4 package on Monterey and it stopped at this issue. So, what can I deduce from the fact that this ticket is 20 months old ? That nobody installs any more kde at all even for fun or that it is actually deprecated by this very transition to openssl 1.1 (maybe there is already a way to force the port to use 1.0 as noted above) ? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:21:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 00:21:56 -0000 Subject: [MacPorts] #66492: mpir requires texinfo but is not a requirement.... In-Reply-To: <046.fd4a020c28b22c6c7c4b3f404668ac03@macports.org> References: <046.fd4a020c28b22c6c7c4b3f404668ac03@macports.org> Message-ID: <061.dfd405bc1a6a0ad1b0208e970931d368@macports.org> #66492: mpir requires texinfo but is not a requirement.... ------------------------+----------------------- Reporter: sck-nogas | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: mpir | ------------------------+----------------------- Changes (by jmroot): * status: new => assigned * keywords: => ventura * owner: (none) => michaelld -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:23:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 00:23:56 -0000 Subject: [MacPorts] #66493: Libarchive 3.6.2 breaks all builds that depends on it. In-Reply-To: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> References: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> Message-ID: <058.01a0cdff9279f89c29590b7a517c2672@macports.org> #66493: Libarchive 3.6.2 breaks all builds that depends on it. -------------------------+-------------------------- Reporter: lukaso | Owner: tobypeterson Type: defect | Status: assigned Priority: High | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | -------------------------+-------------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => tobypeterson -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 00:35:23 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 00:35:23 -0000 Subject: [MacPorts] #66493: Libarchive 3.6.2 breaks all builds that depends on it. In-Reply-To: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> References: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> Message-ID: <058.cbf360bbd0bdc45596b2b9b84ee03b37@macports.org> #66493: Libarchive 3.6.2 breaks all builds that depends on it. -------------------------+-------------------------- Reporter: lukaso | Owner: tobypeterson Type: defect | Status: closed Priority: High | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libarchive | -------------------------+-------------------------- Changes (by jmroot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"055995c0ffa708c42df16b4784a839dae3b3619e/macports-ports" 055995c0ffa708c42df16b4784a839dae3b3619e/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="055995c0ffa708c42df16b4784a839dae3b3619e" libarchive: fix .pc file Closes: https://trac.macports.org/ticket/66493 Closes: https://github.com/macports/macports-ports/pull/16993 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:08:07 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 01:08:07 -0000 Subject: [MacPorts] #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' In-Reply-To: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> References: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> Message-ID: <061.f6b3730fe978982dc94232abdd4ff74e@macports.org> #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: git | ------------------------+----------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"7b66c3889ccad99237601a021fac753e26f2c904/macports-ports" 7b66c3889ccad99237601a021fac753e26f2c904/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7b66c3889ccad99237601a021fac753e26f2c904" git: use newer gmake on Tiger closes: https://trac.macports.org/ticket/66480 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 01:19:00 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 01:19:00 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) In-Reply-To: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> References: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> Message-ID: <061.ac9edc956192caf086d8fecbb29e40dd@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) ------------------------+----------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger ppc Port: python311 | ------------------------+----------------------- Comment (by kencu): the fix needed on Tiger PPC was this: {{{ configure.ldflags-append -Wl,-read_only_relocs,suppress }}} but we have to see if that is just for TigerPPC, or also for Leopard PPC. It is related to gcc7 being the compiler? Or the system. And then not sure about +universal yet. Because of the need for gcc7, the only universal that is now possible is either "i386/x86_64" or "ppc/ppc64" and not many people are actually trying to build those archs on these old systems. So a bit of work to do to get it exactly right, but it does work: {{{ $ port -v installed python311 The following ports are currently installed: python311 @3.11.1_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2022-12-16T12:59:57-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 02:37:14 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 02:37:14 -0000 Subject: [MacPorts] #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' In-Reply-To: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> References: <046.a01cbd3d91b075e596cbc74ee352f057@macports.org> Message-ID: <061.5c8fe6fcf32361942d2f7fc6f9b9130f@macports.org> #66482: diffutils @3.8 do not build on PPC Tiger, Mac OS X 10.4.11, because 'struct mcontext' has no member named '__ss' ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: diffutils | ------------------------+----------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"686366972aed5fc7aa12c70345e5526a657f80bb/macports-ports" 686366972aed5fc7aa12c70345e5526a657f80bb/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="686366972aed5fc7aa12c70345e5526a657f80bb" diffutils: use older register names on Tiger the register names in the 10.4 SDK were changed in the 10.5+ SDK closes: https://trac.macports.org/ticket/66482 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 06:00:15 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 06:00:15 -0000 Subject: [MacPorts] #66494: py311-dnspython @2.2.1: ModuleNotFoundError: No module named 'poetry' Message-ID: <047.c0371176d5ad45e694a0b7679416a48d@macports.org> #66494: py311-dnspython @2.2.1: ModuleNotFoundError: No module named 'poetry' ------------------------+-------------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-dnspython ------------------------+-------------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/2934/steps/install-port/logs/stdio {{{ * Getting dependencies for wheel... Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11 /site-packages/pep517/wrappers.py", line 319, in _call_hook raise BackendUnavailable(data.get('traceback', '')) pep517.wrappers.BackendUnavailable: Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11 /site-packages/pep517/in_process/_in_process.py", line 77, in _build_backend obj = import_module(mod_path) ^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1128, in _find_and_load_unlocked File "", line 241, in _call_with_frames_removed File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1128, in _find_and_load_unlocked File "", line 241, in _call_with_frames_removed File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1128, in _find_and_load_unlocked File "", line 241, in _call_with_frames_removed File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'poetry' ERROR Backend 'poetry.core. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 06:34:43 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 06:34:43 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) In-Reply-To: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> References: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> Message-ID: <061.d305ff8654b25d2ecc09ff887daba9aa@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) ------------------------+------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger leopard ppc Port: python311 | ------------------------+------------------------------- Changes (by kencu): * keywords: tiger ppc => tiger leopard ppc Comment: same error happens on Leopard PPC building python311. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 10:02:42 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 10:02:42 -0000 Subject: [MacPorts] #66495: ocaml: update to 5.0.0 Message-ID: <047.10356d53e3ea348091a7ab1e3224ad4d@macports.org> #66495: ocaml: update to 5.0.0 ------------------------+-------------------- Reporter: mohd-akram | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ocaml ------------------------+-------------------- https://ocaml.org/news/ocaml-5.0 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 10:40:45 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 10:40:45 -0000 Subject: [MacPorts] #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' In-Reply-To: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> References: <046.576b5f3dfc59711651fde7c582ca397e@macports.org> Message-ID: <061.aa47b9cc00b1defd5ad312538f4c9c02@macports.org> #66480: git @2.39.0 does not build on PPC Tiger, Mac OS X 10.4.11, because of Makefile:3323: *** missing `endif' ------------------------+----------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger ppc Port: git | ------------------------+----------------------- Comment (by ballapete): There is still a flaw ? twelve times this complaint: `ld: warning: duplicate dylib /opt/local/lib/libz.1.dylib`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 11:04:42 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 11:04:42 -0000 Subject: [MacPorts] #51310: ImageMagick: update to 7.x In-Reply-To: <045.2ea0f4361ffed471a247ab0c24423535@macports.org> References: <045.2ea0f4361ffed471a247ab0c24423535@macports.org> Message-ID: <060.bbf6d7d99692f0cf340bd30fac148150@macports.org> #51310: ImageMagick: update to 7.x --------------------------+------------------------ Reporter: mopihopi | Owner: ryandesign Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ImageMagick | --------------------------+------------------------ Comment (by essandess): The ImageMagick binaries distributed by MacPorts have several critical CVEs. This port must be updated to latest ASAP. I?ve posted PR https://github.com/macports/macports-ports/pull/16945 that does this and builds the latest without the deprecated OpenCL stuff, with OpenMP, and other minor changes. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 11:14:42 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 11:14:42 -0000 Subject: [MacPorts] #66494: py311-dnspython @2.2.1: ModuleNotFoundError: No module named 'poetry' In-Reply-To: <047.c0371176d5ad45e694a0b7679416a48d@macports.org> References: <047.c0371176d5ad45e694a0b7679416a48d@macports.org> Message-ID: <062.bd13a3425b8d1ac1f24444141c05d2e8@macports.org> #66494: py311-dnspython @2.2.1: ModuleNotFoundError: No module named 'poetry' ---------------------------+-------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-dnspython | ---------------------------+-------------------- Comment (by Schamschula): One to the annoying aspects of python build under MacPorts: they seem to ignore trace mode. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 11:18:11 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 11:18:11 -0000 Subject: [MacPorts] #66493: Libarchive 3.6.2 breaks all builds that depends on it. In-Reply-To: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> References: <043.d3f542b24ee9b7d2bf43ead82d2a90b2@macports.org> Message-ID: <058.dbf545ecd866051bd9929b716896faad@macports.org> #66493: Libarchive 3.6.2 breaks all builds that depends on it. -------------------------+-------------------------- Reporter: lukaso | Owner: tobypeterson Type: defect | Status: closed Priority: High | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libarchive | -------------------------+-------------------------- Comment (by lukaso): Thanks! That was fast! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 11:22:43 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 11:22:43 -0000 Subject: [MacPorts] #66494: py311-dnspython @2.2.1: ModuleNotFoundError: No module named 'poetry' In-Reply-To: <047.c0371176d5ad45e694a0b7679416a48d@macports.org> References: <047.c0371176d5ad45e694a0b7679416a48d@macports.org> Message-ID: <062.f85b964f5683f33b97f46086f12572fc@macports.org> #66494: py311-dnspython @2.2.1: ModuleNotFoundError: No module named 'poetry' -------------------------+------------------------------------------------- Reporter: ryandesign | Owner: Marius Schamschula Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py- | dnspython | -------------------------+------------------------------------------------- Changes (by Marius Schamschula ): * owner: (none) => Marius Schamschula * status: new => closed * resolution: => fixed Comment: In [changeset:"0011506f55f9d1015562c4da8694d7b444b6e50c/macports-ports" 0011506f55f9d1015562c4da8694d7b444b6e50c/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="0011506f55f9d1015562c4da8694d7b444b6e50c" py-dnspython: use poetry pep517_backend Closes: https://trac.macports.org/ticket/66494 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 15:14:38 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 15:14:38 -0000 Subject: [MacPorts] #63806: sbcl @2.1.10 +fancy: Cannot build on macOS 12.0.1 with Xcode 13.1 In-Reply-To: <052.81de0bf7e6aa3f2fd3e51d956254dfba@macports.org> References: <052.81de0bf7e6aa3f2fd3e51d956254dfba@macports.org> Message-ID: <067.e65243b951445a7f1e372473d4841b81@macports.org> #63806: sbcl @2.1.10 +fancy: Cannot build on macOS 12.0.1 with Xcode 13.1 ------------------------------+---------------------- Reporter: foretspaisibles | Owner: easye Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: monterey Port: sbcl | ------------------------------+---------------------- Comment (by foretspaisibles): @easye, this ticket seems to be history now. I performed several upgrades of SBCL without any issue? I can also build SBCL on a fresh 12.X install (GitHub Actions) using MacPorts, so we could probably close that! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 15:19:51 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 15:19:51 -0000 Subject: [MacPorts] #66477: mpich-default +native: clang: error: the clang compiler does not support '-march=native' In-Reply-To: <049.286e1e7ace07490cc541f883b3b12770@macports.org> References: <049.286e1e7ace07490cc541f883b3b12770@macports.org> Message-ID: <064.9dcb8d8a556fbee9b748e71cceeedb3b@macports.org> #66477: mpich-default +native: clang: error: the clang compiler does not support '-march=native' ----------------------------+---------------------- Reporter: chaochinyang | Owner: eborisch Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: arm64 Port: mpich-default | ----------------------------+---------------------- Comment (by chaochinyang): @eborisch: I feel if a variant is not intended for certain use, a stoppage and info message should be in place for the benefits of regular users (with the expiration when Apple upgrades their clang to 15). Of course I will not use the variant because it doesn't work, but I would want to know why it didn't. @kencu: After testing your suggestion, I can confirm that `clang-15` accepts `-march=native` option, and `mpich` with `mpich-default` can be installed with variant `+native`. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 17:42:01 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 17:42:01 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.33561dc1d47f80bb2977af536817795d@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Replying to [comment:7 kencu]: > OK -- when you do get around to xorg-server, and you install dbus, don't forget to enable dbus: Going over this again... On the Mountain Lion system I tried to build xorg-server as soon as xorg finished building, but it complained, {{{ Error: xorg-server is known to fail (use --allow-failing to try to install anyway) }}} but I did it anyway with -y and got a message that led me to believe everything was fine, that xorg and xorg-server were mutually exclusive: {{{ $ port -vsNy install --allow-failing xorg-server ---> Computing dependencies for xorg-server. Error: Can't install xorg-server because conflicting ports are active: xorg-server-legacy Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port xorg-server failed }}} And I forgot all about this when I tried again on Mojave. IOW I never got around to xorg-server, and I never installed dbus, but dbus @1.14.4_0 just happened to be installed on Mountain Lion, and both dbus @1.14.4_0 and dbus-glib @0.112_0 happened to be installed on Mojave. So now I want to ask, 1) when you suggested I install "xorg-desktop," just what did you mean, exactly? and 2) I didn't install xorg-server due what may be my mistaken beliefs due to the message about xorg-server-legacy that I got on Mountain Lion (but checking now I don't get that complaint on Mojave)... ''you want I should install xorg-server?!'' -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 18:35:02 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 18:35:02 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.874af47591b13338edbecaa479d11b3b@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by kencu): MacPorts is powerful, and the admins and devs have chosen to keep more options available at the expense of it being slightly more complicated for users, especially initially. Homebrew has taken the opposite approach, no variants, usually one option for things, and they don't support users building their own software, even. MacPorts has four xorg-server ports: {{{ % port search xorg-server xorg-server @1.20.11_1 (x11, devel) The X.org / Xquartz X server. xorg-server-1.18 @1.18.4 (x11, devel) The X.org / Xquartz X server. xorg-server-devel @1.20.99.1_1 (x11, devel) The X.org / Xquartz X server. xorg-server-legacy @1.20.10_2 (x11, devel) The X.org / Xquartz X server. }}} The primary xorg-server port works for almost all users on newer systems. The xorg-server-legacy port works on the older systems where the primary port no longer usually will build or work properly. The other two xorg- server ports have uses, the 1.18 version on Tiger, and the devel version for devs to use to move the envelope down the path for the next update. Now ideally when you tried to install xorg-server on a system that is too old to support it, it would not tell you it won't build, but try anyway -- that is kinda confusing -- what it would do is say that that xorg-server doesn't work on your system, so MacPorts will be installing xorg-server- legacy for you instead. Wouldn't that be great? It's not overly hard to write that code into the Portfiles, but nobody who is capable of doing that (like me) has bothered to do it, because there are just too many other things to do. It would be really great if users like you might get to the point where you could add that to MacPorts for us.... we'd really appreciate it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 18:37:37 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 18:37:37 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.c32913da37b2bb63e5dfeccc9601a819@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+---------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: lerc | ---------------------+---------------------- Comment (by chillin-): Replying to [comment:1 RobK88]: > FYI -- Until the port is fixed, the workaround is simple -- specify a newer compiler when installing or upgrading lerc. {{{ $ sudo port -vsN upgrade lerc configure.compiler=macports-clang-7.0 ---> Computing dependencies for cmake-bootstrap.... ---> Dependencies to be installed: clang-7.0 cmake-bootstrap llvm-7.0 Error: The following dependencies were not installed because all of them have unmet dependencies (likely due to a dependency cycle): clang-7.0 cmake-bootstrap llvm-7.0 Error: Problem while installing cmake-bootstrap Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. }}} That's ok. I'll just wait. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 18:49:11 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 18:49:11 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.50a5bbba59a7467b8138857d74fb09b9@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Replying to [comment:28 kencu]: > MacPorts is powerful, and the admins and devs have chosen to ... ... for you instead. Wouldn't that be great? > > It's not overly hard to write that code into the Portfiles, but nobody who is capable of doing that (like me) has bothered to do it, because there are just too many other things to do. It would be really great if users like you might get to the point where you could add that to MacPorts for us.... we'd really appreciate it. Really appreciate the explanation and history. I love that stuff. When CS kicked my ass, I studied a lot of history of technology instead, just because I really like it, but it's not like anything sticks (I remember the name Ken Thompson). I learned BASIC and LOGO before HS, then never saw another computer in HS, and all that being a CS major gave me was a pedestrian introduction Pascal and UNIX. I can't remember Pascal, but I've been painfully, painfully slowly learning Bash since 2014. If I could write code into the Portfiles, you really wouldn't want ''me'' doing that. Just sayin, if you're busy now, it'd only make more work for everyone. The best I can do is report a bug. But maybe someday I'll get smarter. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 19:45:02 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 19:45:02 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) In-Reply-To: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> References: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> Message-ID: <061.e46b4eb1420e785e055a4d4ab997c21b@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) ------------------------+------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger leopard ppc Port: python311 | ------------------------+------------------------------- Comment (by kencu): Also happens on Leopard Intel when building as PPC, but not when building as PPC. Which might be the different linker (ld64-97 vs ld64-127) or maybe something to do with building for PPC... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 20:41:53 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 20:41:53 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) In-Reply-To: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> References: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> Message-ID: <061.083df51a3342290787dc987e23a1133b@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) ------------------------+------------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: tiger leopard ppc Port: python311 | ------------------------+------------------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/16998 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 21:37:24 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 21:37:24 -0000 Subject: [MacPorts] #66496: lerc @4.0.0_0: lerc fails to build on 10.10 Message-ID: <046.19c2c9f03b7e33c3528505251f94873a@macports.org> #66496: lerc @4.0.0_0: lerc fails to build on 10.10 -----------------------+-------------------- Reporter: macdeport | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: yosemite | Port: -----------------------+-------------------- I am unable to upgrade lerc from v 3.0 to v4.0 on my Mac running Yosemite. The port fails to build. {{{ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1541:64: error: no template named 'greater' in namespace 'std'; did you mean 'isgreater'? :info:build std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); :info:build ~~~~~^~~~~~~ :info:build isgreater :info:build /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/cmath:478:1: note: 'isgreater' declared here :info:build isgreater(_A1 __lcpp_x, _A2 __lcpp_y) _NOEXCEPT :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1541:59: error: no matching function for call to 'isgreater' :info:build std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); :info:build ^~~~~~~~~~~~~~~~~~~~ :info:build /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/cmath:478:1: note: candidate function template not viable: requires 2 arguments, but 0 were provided :info:build isgreater(_A1 __lcpp_x, _A2 __lcpp_y) _NOEXCEPT :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1568:64: error: no template named 'greater' in namespace 'std'; did you mean 'isgreater'? :info:build std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); :info:build ~~~~~^~~~~~~ :info:build isgreater :info:build /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/cmath:478:1: note: 'isgreater' declared here :info:build isgreater(_A1 __lcpp_x, _A2 __lcpp_y) _NOEXCEPT :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/Lerc.cpp:1568:59: error: no matching function for call to 'isgreater' :info:build std::sort(noDataCandVec.begin(), noDataCandVec.end(), std::greater()); :info:build ^~~~~~~~~~~~~~~~~~~~ :info:build /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/cmath:478:1: note: candidate function template not viable: requires 2 arguments, but 0 were provided :info:build isgreater(_A1 __lcpp_x, _A2 __lcpp_y) _NOEXCEPT :info:build ^ :info:build [ 86%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/fpl_Predictor.cpp.o :info:build /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version- min=10.10 -fPIC -std=gnu++1z -MD -MT CMakeFiles/Lerc.dir/src/LercLib/fpl_Predictor.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/fpl_Predictor.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/fpl_Predictor.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/fpl_Predictor.cpp :info:build [ 93%] Building CXX object CMakeFiles/Lerc.dir/src/LercLib/fpl_UnitTypes.cpp.o :info:build /usr/bin/clang++ -DLERC_EXPORTS -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version- min=10.10 -fPIC -std=gnu++1z -MD -MT CMakeFiles/Lerc.dir/src/LercLib/fpl_UnitTypes.cpp.o -MF CMakeFiles/Lerc.dir/src/LercLib/fpl_UnitTypes.cpp.o.d -o CMakeFiles/Lerc.dir/src/LercLib/fpl_UnitTypes.cpp.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/lerc-4.0.0/src/LercLib/fpl_UnitTypes.cpp :info:build 4 errors generated. :info:build make[2]: *** [CMakeFiles/Lerc.dir/src/LercLib/Lerc.cpp.o] Error 1 :info:build make[2]: *** Waiting for unfinished jobs.... :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/build' :info:build make[1]: *** [CMakeFiles/Lerc.dir/all] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/build' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/work/build" && /usr/bin/make -j8 -w all VERBOSE=ON :info:build Exit code: 2 :error:build Failed to build lerc: command execution failed :debug:build Error code: CHILDSTATUS 18489 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_lerc/lerc/main.log for details. version:1 :debug:clean Starting logging for lerc @4.0.0_0 :debug:sysinfo OS X 10.10.5 (darwin/14.5.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode none, CLT 7.2.0.0.1.1447826929 :debug:sysinfo SDK 10.10 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.10 :msg:clean ---> Computing dependencies for lerc:info:clean .:debug:clean lerc has no conflicts }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 21:37:54 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 21:37:54 -0000 Subject: [MacPorts] #66496: lerc @4.0.0_0: lerc fails to build on 10.10 In-Reply-To: <046.19c2c9f03b7e33c3528505251f94873a@macports.org> References: <046.19c2c9f03b7e33c3528505251f94873a@macports.org> Message-ID: <061.23303257f448c00b7cb8655db10a3327@macports.org> #66496: lerc @4.0.0_0: lerc fails to build on 10.10 ------------------------+---------------------- Reporter: macdeport | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: yosemite Port: | ------------------------+---------------------- Changes (by macdeport): * Attachment "main.log.zip" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 21:40:46 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 21:40:46 -0000 Subject: [MacPorts] #66497: gnupg2 @2.2.40 has no configure option --disable-openldap Message-ID: <046.f7a4e56cf27b305979f62bb7629b875d@macports.org> #66497: gnupg2 @2.2.40 has no configure option --disable-openldap -----------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: gnupg2 -----------------------+-------------------- {{{ Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_mail_gnupg2/gnupg2/work/gnupg-2.2.40" && ./configure --prefix=/opt/local --disable-openldap --with-ldap=no --with-pinentry-pgm=/opt/local/bin/pinentry DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_mail_gnupg2/gnupg2/work/gnupg-2.2.40" && ./configure --prefix=/opt/local --disable-openldap --with-ldap=no --with-pinentry-pgm=/opt/local/bin/pinentry configure: WARNING: unrecognized options: --disable-openldap }}} The correct option is {{{ --disable-ldap disable LDAP support }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 23:28:28 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 23:28:28 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.fa038f822eb4777b3e40541abb6316c3@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by kencu): > IMO Safari is superior to Chromium? Yeah, but as of about 10.13 and older it?s hopelessly outdated and never will be updated. So not an option then, is it? Older systems have been also dropped by Firefox, Chrome, and Safari. Chromium-legacy it all you got, baby. Lucky to have that! Or Netsurf-gtk etc which are **really** useless. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 17 23:53:35 2022 From: noreply at macports.org (MacPorts) Date: Sat, 17 Dec 2022 23:53:35 -0000 Subject: [MacPorts] #66496: lerc @4.0.0_0: lerc fails to build on 10.10 In-Reply-To: <046.19c2c9f03b7e33c3528505251f94873a@macports.org> References: <046.19c2c9f03b7e33c3528505251f94873a@macports.org> Message-ID: <061.2cdbd30f748e6acf112c930cc9e4d789@macports.org> #66496: lerc @4.0.0_0: lerc fails to build on 10.10 ------------------------+-------------------- Reporter: macdeport | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: lerc | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * keywords: yosemite => * resolution: => duplicate * port: => lerc Comment: #66488 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:43:20 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 00:43:20 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.9c86e9246327a2b705868d48208a970c@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Replying to [comment:30 kencu]: > > IMO Safari is superior to Chromium? > > Yeah, but as of about 10.13 and older it?s hopelessly outdated and never will be updated. So not an option then, is it? No. Replying to [comment:30 kencu]: > Older systems have been also dropped by Firefox, Chrome, and Safari. > > Chromium-legacy is all you got, baby. Lucky to have that! > > Or Netsurf-gtk etc which are **really** useless. You have a fair point, but unless I get NetSurf running on ML and it doesn't have the VNC problems Chromium-legacy and Firefox-legacy have, I'll stick with Lynx+ssl, cURL and Wget. I really don't use that machine to surf, but sometimes stuff is only available for download through a browser, has a bazillion redirects or requires a login. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:43:49 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 00:43:49 -0000 Subject: [MacPorts] #66498: octave python27 dependency Message-ID: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> #66498: octave python27 dependency -------------------------+-------------------- Reporter: Schamschula | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: octave -------------------------+-------------------- When I saw https://trac.macports.org/ticket/66299 I was reminded of the {{{python27}}} dependency in the octave Portfile. The upstream documentation does not mention Python: https://docs.octave.org/latest/External-Packages.html So I rebuilt octave from source and kept the logfile to see if Python actually gets used. Indeed a file is generated: {{{/opt/local/share/octave/7.3.0/m/miscellaneous/python.m}}} This file calls {{{system (["python ", script file,...}}} In other words, {{{octave}}} doesn't care about the Python version. Indeed, I have locally built octave against {{{python3x}}} several times in the past. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:44:13 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 00:44:13 -0000 Subject: [MacPorts] #66498: octave python27 dependency In-Reply-To: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> References: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> Message-ID: <063.fe713bf9fc954db05882c1f0dbde2fb8@macports.org> #66498: octave python27 dependency --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | --------------------------+--------------------------------- Changes (by Schamschula): * cc: MarcusCalhoun-Lopez (removed) * status: new => assigned * owner: (none) => MarcusCalhoun-Lopez -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 00:45:18 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 00:45:18 -0000 Subject: [MacPorts] #66498: octave python27 dependency In-Reply-To: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> References: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> Message-ID: <063.2a9fde6ac7004ad9f1200e81531c81d9@macports.org> #66498: octave python27 dependency --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | --------------------------+--------------------------------- Description changed by Schamschula: Old description: > When I saw https://trac.macports.org/ticket/66299 I was reminded of the > {{{python27}}} dependency in the octave Portfile. > > The upstream documentation does not mention Python: > > https://docs.octave.org/latest/External-Packages.html > > So I rebuilt octave from source and kept the logfile to see if Python > actually gets used. Indeed a file is generated: > > {{{/opt/local/share/octave/7.3.0/m/miscellaneous/python.m}}} > > This file calls {{{system (["python ", script file,...}}} > > In other words, {{{octave}}} doesn't care about the Python version. > > Indeed, I have locally built octave against {{{python3x}}} several times > in the past. New description: When I saw https://trac.macports.org/ticket/66299 I was reminded of the {{{python27}}} dependency in the octave Portfile. The upstream documentation does not mention Python: https://docs.octave.org/latest/External-Packages.html So I rebuilt octave from source and kept the logfile to see if Python actually gets used. A file is generated: {{{/opt/local/share/octave/7.3.0/m/miscellaneous/python.m}}} This file calls {{{system (["python ", script file,...}}} In other words, {{{octave}}} doesn't care about the Python version. Indeed, I have locally built octave against {{{python3x}}} several times in the past. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 03:39:29 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 03:39:29 -0000 Subject: [MacPorts] #66238: iTerm2 quit unexpectedly In-Reply-To: <041.e646815e7baa4b39290e1b1215470036@macports.org> References: <041.e646815e7baa4b39290e1b1215470036@macports.org> Message-ID: <056.9bacd456eaa0404520857ae030d9bacd@macports.org> #66238: iTerm2 quit unexpectedly ---------------------+---------------------- Reporter: jmgc | Owner: markemer Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: iTerm2 | ---------------------+---------------------- Comment (by alfredrajo): I'm experiencing the same problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 10:09:38 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 10:09:38 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install space by removing base.tar and compressing ports.tar Message-ID: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> #66499: Significantly reduce MacPorts base install space by removing base.tar and compressing ports.tar -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: -------------------------+-------------------- While comparing MacPorts to Homebrew I've noticed that in some respect it's even worse in its installation size despite having an architectural advantage of not relying on a repo with a history (though Homebrew is currently even better in allowing skipping the repos altogether with ''HOMEBREW_INSTALL_FROM_API'') The **base.tar** and **ports.tar** files are - ~215m uncompressed (~113m base and 101m ports) and only - ~35m compressed (~15 and ~21 respectively), which is a 80% savings!!! So here is an easy win ??just compress the files instead of downloading the uncompressed versions! But then what's even worse is that these files remain even after being unpacked, which is another source of wasted space 1. **Base.tar** should just be removed after being unpacked. And the unpacked version has way too many large ''tests'' and ''idoc'' folders to be pushed to every single MacPorts install 2. And the better way to deal with **ports.tar** is: instead of having a gazillion of unpacked text files (with some taking as much as 1m per port!) that you'll mostly never need (because you'd install only a handful of ports) occupying ~170m to use a few compressed database files of ~21m or at least a single compressed file per port (just like Yarn package manager does with its modern PnP ZIP APIs) and then read those compressed files having them unpacked on a hard drive Or maybe there is a way to just go the ''HOMEBREW_INSTALL_FROM_API'' way and read the port manifests the same way you install the apps by downloading the file from https://packages.macports.org/app_name Then ideally the whole MacPorts install could be a couple of dozen Mbs instead of taking half a Gigabyte! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 10:32:42 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 10:32:42 -0000 Subject: [MacPorts] #66488: lerc fails to build on Mountain Lion In-Reply-To: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> References: <043.3722c81e1a2c3c9b26802d5bc0854a09@macports.org> Message-ID: <058.ddef6c762701e13b94c7888a3ebabca9@macports.org> #66488: lerc fails to build on Mountain Lion ---------------------+-------------------- Reporter: RobK88 | Owner: Veence Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: lerc | ---------------------+-------------------- Changes (by dgilman): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"943f85650255e79d5da4c03864b000e29f6c2653/macports-ports" 943f85650255e79d5da4c03864b000e29f6c2653/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="943f85650255e79d5da4c03864b000e29f6c2653" lerc: fix includes Closes: https://trac.macports.org/ticket/66488 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 10:49:08 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 10:49:08 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) Message-ID: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.8.0 Keywords: | Port: -------------------------+-------------------- Terminal commands that a user is supposed to type are formatted with ''$'' dollar sign {{{ $ Commands to be typed into a terminal window. }}} However, this makes it very inconvenient to copy&paste the easiest selection item ??the whole line ? since the ''$'' dollar sign will corrupt the command. The better way is to either: - enhance the guide's terminal command field to show the $ without it being selectable on triple click (as some other websites do) or - change the syntax to exclude the $ altogether (a much more disruptive move as it's a common convention to denote user terminal input with $) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 10:58:23 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 10:58:23 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) In-Reply-To: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> References: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> Message-ID: <058.e8c1d5f282bea46cb4af62a9bca5b296@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: Port: | --------------------------+-------------------- Changes (by ryandesign): * version: 2.8.0 => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:03:04 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:03:04 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install space by removing base.tar and compressing ports.tar In-Reply-To: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> References: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> Message-ID: <058.95907f579b2d4abff7c1a3ca048c5d66@macports.org> #66499: Significantly reduce MacPorts base install space by removing base.tar and compressing ports.tar --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): The base.tar and ports.tar files are kept on disk, and are downloaded as uncompressed files instead of compressed ones, so that rsync can produce a small diff of them so that only a small amount of network traffic is needed during updates. Admittedly, this design decision was made decades ago when base and ports were both much smaller. I understand where your suggestions are coming from but they represent several significant changes to how MacPorts base works. If you would like to work on one or more of these changes, I suggest you discuss them in detail on the macports-dev mailing list and gain consensus on the method of doing so before beginning to write any code. That way you can avoid unnecessary work. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:07:12 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:07:12 -0000 Subject: [MacPorts] #66485: While I am installing port 1 I cannot build port 2 In-Reply-To: <046.e720c8046133de2e1187c40c48c171dd@macports.org> References: <046.e720c8046133de2e1187c40c48c171dd@macports.org> Message-ID: <061.6c2c7d373d5a15caa58be5a5a47f63a1@macports.org> #66485: While I am installing port 1 I cannot build port 2 --------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): On macOS 10.15, I very often have multiple terminal windows open performing separate sets of builds at the same time, so it is already possible to do so, in some circumstances. (I'm not sure what the conditions are that lead to the "Waiting for lock" message you encountered.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:07:50 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:07:50 -0000 Subject: [MacPorts] #66486: sendfile @2.1b-20110604: error: no member named 'ut_user' in 'struct utmp' (was: sendfile @2.1b-20110604 build fails) In-Reply-To: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> References: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> Message-ID: <061.a66a00053ea8330a6ff44d0f10402497@macports.org> #66486: sendfile @2.1b-20110604: error: no member named 'ut_user' in 'struct utmp' ------------------------+--------------------- Reporter: MStraeten | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: sendfile | ------------------------+--------------------- Changes (by ryandesign): * keywords: => ventura -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:13:52 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:13:52 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar (was: Significantly reduce MacPorts base install space by removing base.tar and compressing ports.tar) In-Reply-To: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> References: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> Message-ID: <058.0912915e26bb891b6c184067f9d57e9f@macports.org> #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:23:04 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:23:04 -0000 Subject: [MacPorts] #66361: ps2eps: Checksum mismatch (was: ps2eps: Building Fails For Darwin 22) In-Reply-To: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> References: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> Message-ID: <059.2382f01932b2159409802e6a4e115b75@macports.org> #66361: ps2eps: Checksum mismatch ----------------------+-------------------- Reporter: maierh7 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ps2eps | ----------------------+-------------------- Changes (by ryandesign): * cc: Schamschula, hmeine, easye (added) Comment: According to your log the distfile checksums do not match. This is not surprising since the [PortfileRecipes#unversioned-distfiles distfile is unversioned] and it has been changed by its developer since the last time this port was updated. The port should be switched to use a versioned distfile, if available. If not available, this update should be handled as a [PortfileRecipes#stealth-updates stealth update]. In May, ps2eps was [changeset:5583a3ec4a54be5e50ba54d66e98ebb2de206d21 /macports-ports allegedly updated from 1.68 to 1.70] but was in fact not updated at all. The port still installs 1.68 despite claiming to have installed 1.70: {{{ % sudo port install ps2eps ---> Computing dependencies for ps2eps ---> Fetching archive for ps2eps ---> Attempting to fetch ps2eps-1.70_0.darwin_21.x86_64.tbz2 from https://packages.macports.org/ps2eps ---> Attempting to fetch ps2eps-1.70_0.darwin_21.x86_64.tbz2.rmd160 from https://packages.macports.org/ps2eps ---> Installing ps2eps @1.70_0 ---> Activating ps2eps @1.70_0 ---> Cleaning ps2eps ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. % ps2eps --version ps2eps - convert PostScript to EPS (Encapsulated PostScript) files (C)opyright 1998-2009 Roland Bless Version: 1.68 }}} Has duplicate #66410. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:23:10 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:23:10 -0000 Subject: [MacPorts] #66410: ps2eps @1.70_0 stealth update In-Reply-To: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> References: <043.7c6de14e8e363f0aec38acb6256bc129@macports.org> Message-ID: <058.e56bf391701210a47d375f0bda4c44f0@macports.org> #66410: ps2eps @1.70_0 stealth update ------------------------+-------------------- Reporter: hmeine | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: ps2eps | ------------------------+-------------------- Changes (by ryandesign): * status: new => closed * resolution: => duplicate Comment: Duplicate of #66361. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:25:24 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:25:24 -0000 Subject: [MacPorts] #66501: rrdtool: configure: error: I need a copy of *nroff to format the documentation Message-ID: <047.8bca49f39d5e1f458f4392f1deea7dbd@macports.org> #66501: rrdtool: configure: error: I need a copy of *nroff to format the documentation ------------------------+--------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: rrdtool ------------------------+--------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/2051/steps/install-port/logs/stdio {{{ checking for gnroff... no checking for nroff... no configure: error: I need a copy of *nroff to format the documentation }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:27:02 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:27:02 -0000 Subject: [MacPorts] #66502: geneweb @5.02: Error: This expression has type string but an expression was expected of type bytes Message-ID: <047.cb9c9d85a2ae946ded8f3ec825b04365@macports.org> #66502: geneweb @5.02: Error: This expression has type string but an expression was expected of type bytes ------------------------+--------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: geneweb ------------------------+--------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/3356/steps/install-port/logs/stdio {{{ camlp5r pa_extend.cmo q_MLast.cmo -o pa_macro5.ppo pa_macro5.ml ocamlc -c -I `camlp5 -where` -impl pa_macro5.ppo File "pa_macro5.ml", line 103, characters 10-21: 103 | let v = String.copy Sys.ocaml_version in ^^^^^^^^^^^ Alert deprecated: Stdlib.String.copy Strings now immutable: no need to copy File "pa_macro5.ml", line 107, characters 11-12: 107 | | _ -> v.[i] := '_' ]; ^ Error: This expression has type string but an expression was expected of type bytes }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:31:37 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:31:37 -0000 Subject: [MacPorts] #66503: py27-radical-utils: Error: No such port: py27-pymongo Message-ID: <047.5c91b86d47088d4b0f81b91b0d26bcaa@macports.org> #66503: py27-radical-utils: Error: No such port: py27-pymongo ------------------------+------------------------------ Reporter: ryandesign | Owner: petrrr Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-radical-utils ------------------------+------------------------------ https://build.macports.org/builders/ports- 13_x86_64-builder/builds/2502/steps/install-dependencies/logs/stdio {{{ Error: No such port: py27-pymongo Processing dependencies for 'py27-radical-utils' failed, aborting. }}} Caused by stromnov in [ddc8d9926f799c93f38e232de46ee519ae26d9c9/macports- ports]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:54:09 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:54:09 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar In-Reply-To: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> References: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> Message-ID: <058.497ae2cd6f5683b345e81c1ee9510add@macports.org> #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by jmroot): Overlaps with #38265. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:56:34 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:56:34 -0000 Subject: [MacPorts] #38265: selfupdate should fetch tarball over HTTP In-Reply-To: <043.323fba2d96d2b058598aa05a5843f06d@macports.org> References: <043.323fba2d96d2b058598aa05a5843f06d@macports.org> Message-ID: <058.781ba8c0393d51df52aabe58b1a01f6c@macports.org> #38265: selfupdate should fetch tarball over HTTP --------------------------+-------------------------------- Reporter: raimue | Owner: macports-tickets@? Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jmroot): WIP PR that was linked from duplicate ticket https://github.com/macports /macports-base/pull/184 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 11:56:49 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 11:56:49 -0000 Subject: [MacPorts] #44402: jpilot has missing dependencies In-Reply-To: <041.857c1094c82c3cb734d07e229122b4ef@macports.org> References: <041.857c1094c82c3cb734d07e229122b4ef@macports.org> Message-ID: <056.0061b04ecb6c33e04c69d56f437a2d23@macports.org> #44402: jpilot has missing dependencies ---------------------+---------------------- Reporter: mf2k | Owner: (none) Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: jpilot | ---------------------+---------------------- Comment (by ryandesign): https://build.macports.org/builders/ports- 13_x86_64-builder/builds/3374/steps/install-port/logs/stdio {{{ checking for xgettext... no checking for msgmerge... no checking for msgfmt... no checking for gmsgfmt... no configure: error: GNU gettext tools not found; required for intltool }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 12:03:10 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 12:03:10 -0000 Subject: [MacPorts] #66503: py27-radical-utils: Error: No such port: py27-pymongo In-Reply-To: <047.5c91b86d47088d4b0f81b91b0d26bcaa@macports.org> References: <047.5c91b86d47088d4b0f81b91b0d26bcaa@macports.org> Message-ID: <062.2b4644df29bb3b1e3b19d7c3eb6e53c1@macports.org> #66503: py27-radical-utils: Error: No such port: py27-pymongo -------------------------------+---------------------- Reporter: ryandesign | Owner: petrrr Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-radical-utils | -------------------------------+---------------------- Comment (by jmroot): Not the only port broken by that removal, BTW: {{{ % port echo depends:py27-pymongo gr37-lora-rpp0 py27-flask-mongoalchemy py27-harstorage py27-mongoalchemy py27-radical-utils }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 12:03:48 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 12:03:48 -0000 Subject: [MacPorts] #66503: py27-radical-utils: Error: No such port: py27-pymongo In-Reply-To: <047.5c91b86d47088d4b0f81b91b0d26bcaa@macports.org> References: <047.5c91b86d47088d4b0f81b91b0d26bcaa@macports.org> Message-ID: <062.40eb341ea4ba4df72df2f72a9453f9f0@macports.org> #66503: py27-radical-utils: Error: No such port: py27-pymongo -------------------------------+---------------------- Reporter: ryandesign | Owner: petrrr Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-radical-utils | -------------------------------+---------------------- Changes (by jmroot): * cc: michaelld (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 12:17:37 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 12:17:37 -0000 Subject: [MacPorts] #66504: geda-gaf @1.10.2: /bin/sh: no: command not found Message-ID: <047.96a7e22c955739d344853ca74de452cd@macports.org> #66504: geda-gaf @1.10.2: /bin/sh: no: command not found ------------------------+---------------------- Reporter: ryandesign | Owner: markemer Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: ventura | Port: geda-gaf ------------------------+---------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/3384/steps/install-port/logs/stdio {{{ /bin/sh: no: command not found }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 12:20:59 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 12:20:59 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar In-Reply-To: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> References: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> Message-ID: <058.c34e875e25563349359a4b83c05acacc@macports.org> #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:1 ryandesign]: > The base.tar and ports.tar files are kept on disk, and are downloaded as uncompressed files instead of compressed ones, so that rsync can produce a small diff of them so that only a small amount of network traffic is needed during updates. Sure, but there are much better ways of achieving this while also not requiring the full duplicate file to be present, you could get just the currently installed base version from the user and then send him the compressed diffs, which will be removed after having been applied to the installed base to update it to the latest version Or for ports you might only need a small index with the latest versions > Admittedly, this design decision was made decades ago when base and ports were both much smaller. Yeah, unfortunately, the duplicately :) unsound decision persisted for way too long :( > I understand where your suggestions are coming from but they represent several significant changes to how MacPorts base works. Sure, while also representing a significant improvement in how it works :) > If you would like to work on one or more of these changes, I suggest you discuss them in detail on the macports-dev mailing list and gain consensus on the method of doing so before beginning to write any code. That way you can avoid unnecessary work. Sorry wouldn't be of much help here, don't know any Tcl or much of C... Meanwhile, at least pairing down the vendored Tcl version to the bare minimum required to run MacPorts shouldn't need any major changes, right? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 14:39:13 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 14:39:13 -0000 Subject: [MacPorts] #66505: texlive-basic @62858_2 misses to install files Message-ID: <046.d7b17e61d8176cd24566d04c19276656@macports.org> #66505: texlive-basic @62858_2 misses to install files -----------------------+--------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: tiger ppc | Port: texlive-basic -----------------------+--------------------------- {{{ xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-basic/texlive- basic/work/destroot/opt/local/share/texmf-texlive/fonts/map/dvipdfmx DEBUG: warning: unknown file destination: tlpkg/tlpostcode/dvipdfmx.pl xinstall: mkdir /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports .org_macports_release_tarballs_ports_tex_texlive-basic/texlive- basic/work/destroottlpkg }}} `tlpkg/tlpostcode` should be `/opt/local/share/tlpkg//tlpostcode`, but this subdiretory does not exist. A regular `TeX Live installation` contains in `/usr/local/texlive//tlpkg/tlpostcode` a few `PL` files with `Perl code`. They are obviously meant for some `post installation`. Other warnings are: {{{ DEBUG: warning: unknown file destination: install-tl DEBUG: warning: unknown file destination: tlpkg/installer/ctan-mirrors.pl DEBUG: warning: unknown file destination: tlpkg/installer/install-menu- extl.pl DEBUG: warning: unknown file destination: tlpkg/installer/install-menu- text.pl DEBUG: warning: unknown file destination: tlpkg/installer/install-tl- gui.tcl DEBUG: warning: unknown file destination: tlpkg/tltcl/tlmgr.gif DEBUG: warning: unknown file destination: tlpkg/tltcl/tltcl.tcl DEBUG: warning: unknown file destination: doc.html DEBUG: warning: unknown file destination: tlpkg/tltcl/README.TEXLIVE }}} These seem to be connected to `tlmgr`, the `TeX Live Manager` to manage the installed packages and update them manually. Are they all harmless? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 15:30:21 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 15:30:21 -0000 Subject: [MacPorts] #66361: ps2eps: Checksum mismatch In-Reply-To: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> References: <044.e59f8c0dfe2343185a4edd47e5e55660@macports.org> Message-ID: <059.ff8f67271abed0f62d0a4ba6b3a444f5@macports.org> #66361: ps2eps: Checksum mismatch ----------------------+------------------------------------------------- Reporter: maierh7 | Owner: Marius Schamschula Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ps2eps | ----------------------+------------------------------------------------- Changes (by Marius Schamschula ): * owner: (none) => Marius Schamschula * status: new => closed * resolution: => fixed Comment: In [changeset:"ce4fcdd6438b74504f994457097ad51818f3e521/macports-ports" ce4fcdd6438b74504f994457097ad51818f3e521/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ce4fcdd6438b74504f994457097ad51818f3e521" ps2eps: use github Closes: https://trac.macports.org/ticket/66361 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:02:19 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 16:02:19 -0000 Subject: [MacPorts] #66506: lerc 4.0.0 build failure on 10.13.6 Message-ID: <042.f2b0bf8643b9e858a139a7e1769848f1@macports.org> #66506: lerc 4.0.0 build failure on 10.13.6 -------------------------------+------------------------ Reporter: rufty | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: lerc std::greater | Port: lerc 4.0.0 -------------------------------+------------------------ On OSX 10.13.6, MacPorts 2.8.0 trying to upgrade: lerc 3.0_0 < 4.0.0_0 Getting an error: Lerc.cpp:1568:64: error: no template named 'greater' in namespace 'std' -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 16:02:55 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 16:02:55 -0000 Subject: [MacPorts] #66506: lerc 4.0.0 build failure on 10.13.6 In-Reply-To: <042.f2b0bf8643b9e858a139a7e1769848f1@macports.org> References: <042.f2b0bf8643b9e858a139a7e1769848f1@macports.org> Message-ID: <057.47e14238d8cecdb81b4884a924648fdf@macports.org> #66506: lerc 4.0.0 build failure on 10.13.6 -------------------------+------------------------------- Reporter: rufty | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: lerc std::greater Port: lerc 4.0.0 | -------------------------+------------------------------- Changes (by rufty): * Attachment "lerc.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 17:22:11 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 17:22:11 -0000 Subject: [MacPorts] #66506: lerc 4.0.0 build failure on 10.13.6 In-Reply-To: <042.f2b0bf8643b9e858a139a7e1769848f1@macports.org> References: <042.f2b0bf8643b9e858a139a7e1769848f1@macports.org> Message-ID: <057.cd358084b4799950cda601d32692293f@macports.org> #66506: lerc 4.0.0 build failure on 10.13.6 ------------------------+-------------------- Reporter: rufty | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: lerc | ------------------------+-------------------- Changes (by jmroot): * status: new => closed * keywords: lerc std::greater => * resolution: => duplicate * port: lerc 4.0.0 => lerc Comment: #66488 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 18 19:05:38 2022 From: noreply at macports.org (MacPorts) Date: Sun, 18 Dec 2022 19:05:38 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.8d4cfd1762f245561693c9f6e247c478@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/17012 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 00:27:54 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 00:27:54 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.4ab0e38bab4611a7b27afbfb38c4af1f@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Replying to [comment:20 mascguy]: > The one item you now need to install with `+quartz`, is gtk3. But you can simplify the process, by specifying `+quartz` when installing NetSurf. (Even though the latter doesn't have a quartz variant, it will cascade to all deps... including gtk3.) > > > {{{ > $ sudo port clean gtk3 netsurf > $ sudo port install netsurf +quartz > }}} > > Give that a try, and let us know how it goes! Replying to [comment:25 chillin-]: > Build succeeded on Mojave, but I'm getting the same problem at launch as on Mountain Lion Your suggestion worked, Chris, now have gtk3 @3.24.34_2+quartz and NetSurf @3.10_1 installed. The problems I'm having with NetSurf have nothing to do with gtk3 anymore, so we can probably call this one resolved. Thanks much. I'll keep banging away at {{{ bash-3.2$ netsurf-gtk3 Options failed to initialise (BadParameter) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 04:22:38 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 04:22:38 -0000 Subject: [MacPorts] #66498: octave python27 dependency In-Reply-To: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> References: <048.1e11afd703e52d97ebe6f36a73eacc86@macports.org> Message-ID: <063.c007d5cea6585569bb9c48c9b7e7028c@macports.org> #66498: octave python27 dependency --------------------------+--------------------------------- Reporter: Schamschula | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: octave | --------------------------+--------------------------------- Description changed by ryandesign: Old description: > When I saw https://trac.macports.org/ticket/66299 I was reminded of the > {{{python27}}} dependency in the octave Portfile. > > The upstream documentation does not mention Python: > > https://docs.octave.org/latest/External-Packages.html > > So I rebuilt octave from source and kept the logfile to see if Python > actually gets used. A file is generated: > > {{{/opt/local/share/octave/7.3.0/m/miscellaneous/python.m}}} > > This file calls {{{system (["python ", script file,...}}} > > In other words, {{{octave}}} doesn't care about the Python version. > > Indeed, I have locally built octave against {{{python3x}}} several times > in the past. New description: When I saw #66299 I was reminded of the {{{python27}}} dependency in the octave Portfile. The upstream documentation does not mention Python: https://docs.octave.org/latest/External-Packages.html So I rebuilt octave from source and kept the logfile to see if Python actually gets used. A file is generated: {{{/opt/local/share/octave/7.3.0/m/miscellaneous/python.m}}} This file calls {{{system (["python ", script file,...}}} In other words, {{{octave}}} doesn't care about the Python version. Indeed, I have locally built octave against {{{python3x}}} several times in the past. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 06:30:37 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 06:30:37 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) In-Reply-To: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> References: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> Message-ID: <058.76abde12f9dac8208a6f4b21dcc44b30@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: Port: | --------------------------+-------------------- Description changed by esbugz: Old description: > Terminal commands that a user is supposed to type are formatted with > ''$'' dollar sign > {{{ > $ Commands to be typed into a terminal window. > }}} > > However, this makes it very inconvenient to copy&paste the easiest > selection item ??the whole line ? since the ''$'' dollar sign will > corrupt the command. > > The better way is to either: > - enhance the guide's terminal command field to show the $ without it > being selectable on triple click (as some other websites do) or > - change the syntax to exclude the $ altogether (a much more disruptive > move as it's a common convention to denote user terminal input with $) New description: Terminal commands that a user is supposed to type are formatted with ''$'' dollar sign {{{ $ Commands to be typed into a terminal window. }}} However, this makes it very inconvenient to copy&paste the easiest selection item ??the whole line ? since the ''$'' dollar sign will corrupt the command. The better way is to either: - enhance the guide's terminal command field to show the $ without it being selectable on triple click as some other websites do, for example, check this one [https://scoop.sh/#/apps?q=regfileexport&s=0&d=1&o=true] ? you don't even need to triple click to select a line, just clicking on the line can select the command you can paste to the terminal, and there is also a very helpful clipboard icon indicator that you've copied - or change the syntax to exclude the $ altogether (a much more disruptive move as it's a common convention to denote user terminal input with $) -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 09:25:06 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 09:25:06 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis Message-ID: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> #66507: Allow customizing applications_dir on a per-port basis -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: -------------------------+-------------------- I don't like to have a single folder dump and usually sort my apps in categories (e.g., video, office, etc.) Homebrew allows you to pass a custom path argument for each cask (binary app) so that the native Mac app can be placed in an arbitrary folder within /Applications However, as far as I understand, MacPorts only allows a global **applications_dir** configuration variable, not a per-port installation flag It would be great if MacPorts also allowed a per-port target folder for native Mac app bundles -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 12:57:34 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 12:57:34 -0000 Subject: [MacPorts] #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz In-Reply-To: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> References: <045.27588462cad1d8424d04fc8b28d7207f@macports.org> Message-ID: <060.7497cd43a20f7221260c5b00c6439963@macports.org> #66476: gtk3 @3.24.34_2 build fail on Mojave gdkapplaunchcontext-x11.c:30:10: fatal error: 'gio/gdesktopappinfo.h' file not found when glib2 is installed for +quartz -----------------------+---------------------- Reporter: chillin- | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Mojave Port: gtk3 | -----------------------+---------------------- Comment (by chillin-): Since this is still open... might as well continue with my OT: The versions installed don't seem right to me: Mountain Lion xorg-server-legacy @1.20.10_2 xorg @20090316_0 X11.app @1.20.10 Mojave xorg-server @1.20.11_1 xorg @20090316_0 X11.app @1.20.11 when XQuartz.app (which I thought was the same as this MacPorts xorg X11.app) is up to 2.8.3, and the last version supported on Mountain Lion (which I installed, didn't think it worked, and uninstalled) is 2.7.11 [https://www.xquartz.org/releases/archive.html] Maybe these aren't the same? But XQuartz Releases page literally instructs the alternative method of XQuartz install with MacPorts [https://www.xquartz.org/releases/index.html] Just what is going on here? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:32:09 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 15:32:09 -0000 Subject: [MacPorts] #66508: qore-jni-module+openjdk16: Error: No such port: openjdk16 Message-ID: <047.8ae4864ceb1b14f0b44ba85c5a75b7e6@macports.org> #66508: qore-jni-module+openjdk16: Error: No such port: openjdk16 ------------------------+----------------------------- Reporter: ryandesign | Owner: davidnich Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: qore-jni-module ------------------------+----------------------------- The qore-jni-module port's +openjdk16 variant should be deleted because the openjdk16 port has already been deleted: https://build.macports.org/builders/jobs- mirror/builds/501338/steps/mirror/logs/stdio {{{ Error: No such port: openjdk16 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:44:55 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 15:44:55 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.0ea7454c154d01f7c3432eac71f62add@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): It's a nice idea, but I don't see how it would be possible in the general case. The paths where a port installs its files are baked into the pre- compiled archives we distribute. If you change the `prefix` or `applications_dir` or certain other variables in macports.conf (which applies to all ports), then you are no longer able to receive our pre- compiled archives, which is a significant drawback of deviating from our defaults. The same would apply to any hypothetical ability to customize it on a per-port basis, unless MacPorts were rearchitected. At minimum, it would require some ability of MacPorts to move selected items from wherever they are in the pre-compiled archive to wherever you wanted them to be, however paths to those items might be embedded in other files installed by the port, so those references would need to be found and updated as well, which may not be possible if the reference is within a binary file. References to the items you wanted to move might even be contained within other ports; how could we deal with that situation? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 15:57:19 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 15:57:19 -0000 Subject: [MacPorts] #66508: qore-jni-module+openjdk16: Error: No such port: openjdk16 In-Reply-To: <047.8ae4864ceb1b14f0b44ba85c5a75b7e6@macports.org> References: <047.8ae4864ceb1b14f0b44ba85c5a75b7e6@macports.org> Message-ID: <062.add7e832f16166c07d549a6b3b704b2b@macports.org> #66508: qore-jni-module+openjdk16: Error: No such port: openjdk16 ------------------------------+----------------------- Reporter: ryandesign | Owner: davidnich Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: qore-jni-module | ------------------------------+----------------------- Changes (by davidnich): * status: assigned => closed * resolution: => fixed Comment: done - referenes to the openjdk16 port removed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:03:51 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:03:51 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.4133c5612da361d3c3d8819f638d3066@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): You can alias the apps whever you want. I use homebrew?s casks sometimes, but find it very confusing to not know which apps are bring managed by brew and which I installed, without checking every time. I label them, but the labels disappear on updates. So I find having all the MacPorts apps in one folder is much much easier to keep that straight. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:11:37 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:11:37 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.fe9c80462f8b3ac44f0166abd878d1b3@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:2 kencu]: > You can alias the apps whever you want. That's what I did before I learned about this command > I use homebrew?s casks sometimes, but find it very confusing to not know which apps are bring managed by brew and which I installed, without checking every time. > So I find having all the MacPorts apps in one folder is much much easier to keep that straight. That's fine, I find the opposite to be the case. I don't really need that information all that often, and if you do, > I label them, but the labels disappear on updates. that's exactly what aliases are for ? they convey that labeling information and only that. But you can't **alias your way out of lacking app size** and not knowing that your picture viewers apps occupy 2G because you've installed a bunch of them from various sources to compare and forgot to delete -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:19:53 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:19:53 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.e56f467be65567fe4ff1166caf565e74@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): no, aliases don't "convey that labelling information and only that." That would be pretty useless. They function as movable references to an application that you can put anywhere you want. **Which is exactly what you are asking for.** But they don't require re-engineering MacPorts in a basically impossible and (IMHO) inferior way. **Lacking app size** in an alias is a pretty trivial complaint, wouldn't you agree? :> -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:21:38 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:21:38 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.606d59e12212d027a056b73ee7893ea7@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:1 ryandesign]: > It's a nice idea, but I don't see how it would be possible in the general case. The paths where a port installs its files are baked into the pre-compiled archives we distribute. If you change the `prefix` or `applications_dir` or certain other variables in macports.conf (which applies to all ports), I'm not talking about a general case and `prefix`, but mostly about GUI apps that should work from any folder (e.g., https://ports.macports.org/port/alacritty/) (though I'm in general curious why the build have evolved in such a way as to be so sensitive to absolute paths instead of relying on some env var or other method of relative system overrides, it's not something I plan to as MacPorts to solve) > then you are no longer able to receive our pre-compiled archives which is a significant drawback of deviating from our defaults. Absolutely, breaking this would be a disaster, it's too much of a waste having to rebuild the world instead of downloading a prebuilt binary that was grown in an organic app farm ;). >may not be possible if the reference is within a binary file. References to the items you wanted to move might even be contained within other ports; how could we deal with that situation? a) Would a symlink to the new app's location help? b) if not, then these apps would simply not be good candidates for relocation -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:36:41 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:36:41 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar In-Reply-To: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> References: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> Message-ID: <058.06fb89edd72caef680056a57b873c5cc@macports.org> #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): I think the entire base TCL installation is something like 14MB {{{ % du -sh tcl* 292K tcl8 2.5M tcl8.6 8.0K tclConfig.sh 11M tcllib1.21 4.0K tclooConfig.sh 276K tclx8.6 }}} so not much of a burden (size of three photos), although the source code for it is about 50MB, if you have to download that for a new release. Figuring out how to scrape that source code down by modifying the upstream build is not something I could see being maintainable over the long term. Might even break the license, have to check... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:39:26 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:39:26 -0000 Subject: [MacPorts] #66509: Please upgrade ksh93-devel to current release version Message-ID: <045.8f93dcb34244ec2acd1cd608d23d6f81@macports.org> #66509: Please upgrade ksh93-devel to current release version ----------------------+------------------------- Reporter: posguy99 | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ksh93-devel ----------------------+------------------------- The current version of ksh93u+m is v1.0.4 (https://github.com/ksh93/ksh/releases/tag/v1.0.4), released on 10/21. Please upgrade the MacPorts version to the current release. Thank you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:46:47 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:46:47 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.afd24a5ba5e1234af049de6d7b839ddd@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:4 kencu]: > no, aliases don't "convey that labelling information and only that." That would be pretty useless. Why would they be useless if you complained that your labels were lost on app updates??? Links persist on app updates, that's useful. I used them exactly for this + for the labeling info itself: e.g., I'd change the app names from various `Kitty` and `Puppy` to `File Manager Kitty` and `File Manager Puppy` (and you could add `(Macports)` at the end if you need that label), and then the apps were easier to find in Alfred (especially for rarely used apps the names of which you could forget). That's the second use of the useless labels > They function as movable references to an application that you can put anywhere you want. **Which is exactly what you are asking for.** Nope, not sure why you'd insist in your misinterpretation of what I'm asking for when I've explicitly explained that the alias is not it. > But they don't require re-engineering MacPorts in a basically impossible and (IMHO) inferior way. Why is that impossible??? > **Lacking app size** in an alias is a pretty trivial complaint, wouldn't you agree? :> Compared to the made up impossibility, yep; otherwise, not really, why would I agree with trivializing one of the main driving factors behind the request a copy of this Homebrew's flag? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:50:43 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:50:43 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) In-Reply-To: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> References: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> Message-ID: <058.ef0c7bb2e144a0b9903634a462c8fe63@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: Port: | --------------------------+-------------------- Description changed by esbugz: Old description: > Terminal commands that a user is supposed to type are formatted with > ''$'' dollar sign > {{{ > $ Commands to be typed into a terminal window. > }}} > > However, this makes it very inconvenient to copy&paste the easiest > selection item ??the whole line ? since the ''$'' dollar sign will > corrupt the command. > > The better way is to either: > - enhance the guide's terminal command field to show the $ without it > being selectable on triple click as some other websites do, for example, > check this one [https://scoop.sh/#/apps?q=regfileexport&s=0&d=1&o=true] ? > you don't even need to triple click to select a line, just clicking on > the line can select the command you can paste to the terminal, and there > is also a very helpful clipboard icon indicator that you've copied > - or change the syntax to exclude the $ altogether (a much more > disruptive move as it's a common convention to denote user terminal input > with $) New description: Terminal commands that a user is supposed to type are formatted with ''$'' dollar sign {{{ $ Commands to be typed into a terminal window. }}} However, this makes it very inconvenient to copy&paste the easiest selection item ??the whole line ? since the ''$'' dollar sign will corrupt the command. The better way is to either: - enhance the guide's terminal command field to show the $ without it being selectable on triple click as some other websites do, or do what you do on [https://ports.macports.org/] ? you don't even need to triple click to select a line, just click the copy button - or change the syntax to exclude the $ altogether (a much more disruptive move as it's a common convention to denote user terminal input with $) -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 16:59:44 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 16:59:44 -0000 Subject: [MacPorts] #66510: Uninstall warning: 'continue' ignores 'N' Message-ID: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> #66510: Uninstall warning: 'continue' ignores 'N' --------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: --------------------+-------------------- I'd assume that passing `N` or `n` or hitting enter (since 'N' implies it's the default) would abort uninstallation, but instead all of these result in the warning being ignored {{{ $sudo port uninstall libunistring brotli Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break: libidn2 @2.3.4_0 libpsl @0.21.1-20220513_1 Continue? [y/N]: N ---> Cleaning libunistring ---> Deactivating brotli @1.0.9_2 ---> Cleaning brotli ---> Uninstalling brotli @1.0.9_2 ---> Cleaning brotli }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 18:24:14 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 18:24:14 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.e3a05d48b8017662602c8ebf6333cf68@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+---------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: bsdmake | ---------------------------+---------------------- Comment (by vallon): Added dist_subdir hack for stealth update. PR is green. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 20:09:53 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 20:09:53 -0000 Subject: [MacPorts] #66511: Issue installing or upgrading ghostscript port Message-ID: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> #66511: Issue installing or upgrading ghostscript port ----------------------+-------------------- Reporter: Hardies1 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: ----------------------+-------------------- When I try to install or update ghostscript, my computer (macbook pro running os 10.15.7)completely loses internet connection when the process gets to ?Fetching distfiles for ghostscript?. I have to reboot the computer to get the internet connection running again. I have tried cleaning the port and then reinstalling and the install still fails at the same point. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 20:12:12 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 20:12:12 -0000 Subject: [MacPorts] #66511: Issue installing or upgrading ghostscript port In-Reply-To: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> References: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> Message-ID: <060.5240ca1a944bc937bac872ef351f7b7b@macports.org> #66511: Issue installing or upgrading ghostscript port -----------------------+-------------------- Reporter: Hardies1 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | -----------------------+-------------------- Changes (by Hardies1): * Attachment "0BEE708E-6E1A-470F-94E9-6F9A7280971E.jpeg" added. Screenshot of the Terminal app window when the error occurs. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 20:39:54 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 20:39:54 -0000 Subject: [MacPorts] #66509: Please upgrade ksh93-devel to current release version In-Reply-To: <045.8f93dcb34244ec2acd1cd608d23d6f81@macports.org> References: <045.8f93dcb34244ec2acd1cd608d23d6f81@macports.org> Message-ID: <060.a398f9cc21d50631b2cba5b90c8cc6fb@macports.org> #66509: Please upgrade ksh93-devel to current release version --------------------------+------------------------ Reporter: posguy99 | Owner: ryandesign Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ksh93-devel | --------------------------+------------------------ Changes (by jmroot): * owner: (none) => ryandesign * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 23:19:07 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 23:19:07 -0000 Subject: [MacPorts] #66463: Failed to configure openvdb: boost176 must be installed with +python39. In-Reply-To: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> References: <049.dc12053a8c7ac29f2c6dd419ee22fb47@macports.org> Message-ID: <064.d5ee34959a61776e63aa8982d64646aa@macports.org> #66463: Failed to configure openvdb: boost176 must be installed with +python39. ---------------------------+--------------------------------- Reporter: Davidpmorrow | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: openvdb | ---------------------------+--------------------------------- Comment (by sbgraphic): Hello, same issue here on iMac Pro 10.6.2. I tried the suggestion above but I get the following new error. {{{ Processing of port openvdb failed }}} {{{ [ 72%] Built target doc make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_openvdb/openvdb/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_openvdb/openvdb/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_openvdb/openvdb/work/build" && /usr/bin/make -j20 -w all VERBOSE=ON Exit code: 2 Error: Failed to build openvdb: command execution failed }}} latest from log {{{ latest from openvdb log: :info:build Exit code: 2 :error:build Failed to build openvdb: command execution failed :debug:build Error code: CHILDSTATUS 8720 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/ }}} Thanks for any update? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 23:24:36 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 23:24:36 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.f3f3093882c002d0cb8500dbc4d1da6a@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+-------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: bsdmake | ---------------------------+-------------------- Changes (by System Administrator ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"89d92116dff67a155a57729fa8f0cc7d723805d9/macports-ports" 89d92116dff67a155a57729fa8f0cc7d723805d9/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="89d92116dff67a155a57729fa8f0cc7d723805d9" bsdmake: Update checksums after Apple redirect to github Apple's redirect to github gives a different top-level dir in tar; no diffs. stealth upgrade. Fixes: https://trac.macports.org/ticket/66404 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 19 23:52:22 2022 From: noreply at macports.org (MacPorts) Date: Mon, 19 Dec 2022 23:52:22 -0000 Subject: [MacPorts] #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) In-Reply-To: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> References: <046.0070e45d02a1337abd29ca528c68cb91@macports.org> Message-ID: <061.ea78a5a888d37dce0f889961e98fc1dd@macports.org> #66483: python311 @3.11.1 does not build on PPC Tiger, Mac OS X 10.4.11, because 'ld returned 1 exit status' (absolute addressing not allowed in slidable image) ------------------------+------------------------------- Reporter: ballapete | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: tiger leopard ppc Port: python311 | ------------------------+------------------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"e2d0e39b88abbffda2a88004d1665577911b3143/macports-ports" e2d0e39b88abbffda2a88004d1665577911b3143/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e2d0e39b88abbffda2a88004d1665577911b3143" python311: fix linker error on PPC with PPC builds only, it seems, there is a linker error involving relocs. This is not happening with 32bit builds on Intel however. closes: https://trac.macports.org/ticket/66483 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 00:55:57 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 00:55:57 -0000 Subject: [MacPorts] #66512: rb-eventmachine @0.12.10_1: still broken (cxx_stdlib mismatch) after rebuilding more than 3 times. Message-ID: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> #66512: rb-eventmachine @0.12.10_1: still broken (cxx_stdlib mismatch) after rebuilding more than 3 times. -------------------------+----------------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: rb-eventmachine -------------------------+----------------------------- {{{ ---> No broken files found. rb-eventmachine is using libstdc++ (this installation is configured to use libc++) Error: Port rb-eventmachine is still broken (cxx_stdlib mismatch) after rebuilding it more than 3 times. DEBUG: rev-upgrade failed: Port rb-eventmachine still broken after rebuilding 3 times while executing "error "Port $portname still broken after rebuilding $rebuild_tries time${s}"" (procedure "revupgrade_scanandrebuild" line 315) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" Error: rev-upgrade failed: Port rb-eventmachine still broken after rebuilding 3 times Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. }}} I'm on Big Sur (x86_64) with Xcode 13.2.1. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 01:22:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 01:22:41 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.d470205468aed7f991754ca6f7eab80e@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: Port: libmsn | --------------------------+-------------------- Comment (by mpbb77): ok, I guess that the lack of any feedback speaks for itself. I've searched for any hint like "kde port on macports deprecated" or the like but even that seems silentful. Then the kde package is listed as not ported since years so I should have known better. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 04:58:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 04:58:23 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.5b75f13c4b7866244652b6e4d832d85d@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: Port: libmsn | --------------------------+-------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"3f362e8cfd94e0918f74f800bdfeadbd614928be/macports-ports" 3f362e8cfd94e0918f74f800bdfeadbd614928be/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3f362e8cfd94e0918f74f800bdfeadbd614928be" libmsn: update to 4.2.1 use openssl 1.0 (newer versions didn't build). closes: https://trac.macports.org/ticket/62833 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:09:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 05:09:49 -0000 Subject: [MacPorts] #66510: Uninstall warning: 'continue' ignores 'N' In-Reply-To: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> References: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> Message-ID: <058.2f8fa9094f866c92ab40f328fc930e15@macports.org> #66510: Uninstall warning: 'continue' ignores 'N' ---------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------+-------------------- Comment (by kencu): libunistring was not uninstalled, as you commanded when you responded "N". librotli was uninstalled, as you asked, as there were no issues with uninstalling it. So the warning was not ignored, it was obeyed. however, when you put multiple port uninstalls on one line like that, it would be more clear perhaps if there was a port named that was the responsible port at each prompt, eg: {{{ $sudo port uninstall libunistring brotli Note: when uninstalling libunistring, dependent ports will break. Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break: libidn2 @2.3.4_0 libpsl @0.21.1-20220513_1 Continue? [y/N]: N ---> Cleaning libunistring ---> Deactivating brotli @1.0.9_2 ---> Cleaning brotli ---> Uninstalling brotli @1.0.9_2 ---> Cleaning brotli }}} That is a pretty niche request, but it can be left as a request for someone to look at someday. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:11:05 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 05:11:05 -0000 Subject: [MacPorts] #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. (was: Uninstall warning: 'continue' ignores 'N') In-Reply-To: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> References: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> Message-ID: <058.ed2cc9a9256cd84ad40309555964996c@macports.org> #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. ---------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:12:56 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 05:12:56 -0000 Subject: [MacPorts] #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. In-Reply-To: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> References: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> Message-ID: <058.c0a2e3c0ce7ad2ddf4b0b934c275a7c3@macports.org> #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. ---------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------+-------------------- Comment (by kencu): This looks like it would be a pretty simple 5-minute project to add that line to base, if the admins feel it would make things less confusing for users. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:15:46 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 05:15:46 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.991ce8a302052009b37b11feaf3a807e@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: Port: libmsn | --------------------------+-------------------- Comment (by kencu): I don't use this port, but it seemed like you were really hoping it would be fixed, so I took 5 minutes to update and fix it for you. It looks like it is building successfully on most systems; I'll check back later to see if any of them failed and take care of that if so. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:43:12 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 05:43:12 -0000 Subject: [MacPorts] #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. In-Reply-To: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> References: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> Message-ID: <058.caf24b80e2878472ff7472b8a41f03ed@macports.org> #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. ---------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------+-------------------- Comment (by esbugz): Oh, I see, thanks for clarification. Another source of confusion is `Cleaning libunistring`, can this operation be removed as well? And I'd suggest a shorter message and a more explicit 'Continue uninstalling': {{{ Note: uninstalling 'libunistring' will break the following dependent ports: libidn2 @2.3.4_0 libpsl @0.21.1-20220513_1 Continue uninstalling? [y/N]: N }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 05:54:35 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 05:54:35 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.7756bcec6a3bdd8d93c40d3fa17e19eb@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Changes (by larryv): * cc: larryv (added) Comment: And 10.14. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:25:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 07:25:31 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.f78aabc144866a3e3069e4cbd34d1774@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: Port: libmsn | --------------------------+-------------------- Comment (by cooljeanius): Thanks for the fix! I can confirm that libmsn installs for me now. mpbb77, if you are trying to install the kde ports, the next bug you'll probably run into would be #62880, for reference. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:34:17 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 07:34:17 -0000 Subject: [MacPorts] #66513: podman @4.3.1: env: python3: No such file or directory Message-ID: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> #66513: podman @4.3.1: env: python3: No such file or directory ------------------------+---------------------- Reporter: ryandesign | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: podman ------------------------+---------------------- Build failure on Mojave and earlier: https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/174710/steps /install-port/logs/stdio {{{ Makefile:134: invalid `override' directive mkdir -p bin/darwin CGO_ENABLED=0 \ GOOS=darwin \ GOARCH=amd64 \ go build \ \ -o bin/darwin/podman-mac-helper \ ./cmd/podman-mac-helper hack/markdown-preprocess docs/source/markdown/podman-attach.1.md.in env: python3: No such file or directory make: *** [docs/source/markdown/podman-attach.1.md] Error 127 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:37:40 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 07:37:40 -0000 Subject: [MacPorts] #62880: smokekde @4.14.3_5 +debug+docs: Undefined symbols for architecture x86_64 with kdelibs4+osxkeychain In-Reply-To: <048.59a43cb7a1d9bc745d7e21013a351f3f@macports.org> References: <048.59a43cb7a1d9bc745d7e21013a351f3f@macports.org> Message-ID: <063.b6f3c64edbd96bda21d446a43575bdd9@macports.org> #62880: smokekde @4.14.3_5 +debug+docs: Undefined symbols for architecture x86_64 with kdelibs4+osxkeychain --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: | Keywords: Port: smokekde | --------------------------+-------------------- Comment (by kencu): Perhaps at the moment we might focus on getting the kde stuff built once with all default variants at least, and then move on to the non-default variants? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:40:22 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 07:40:22 -0000 Subject: [MacPorts] #66512: rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++) (was: rb-eventmachine @0.12.10_1: still broken (cxx_stdlib mismatch) after rebuilding more than 3 times.) In-Reply-To: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> References: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> Message-ID: <063.68a81f2f01ec8db53f266ad6032bf5b1@macports.org> #66512: rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++) ------------------------------+---------------------- Reporter: cooljeanius | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: rb-eventmachine | ------------------------------+---------------------- Changes (by ryandesign): * owner: (none) => kimuraw * status: new => assigned * cc: kimuraw (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:48:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 07:48:41 -0000 Subject: [MacPorts] #66511: Issue installing or upgrading ghostscript port In-Reply-To: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> References: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> Message-ID: <060.593866a2747844a878e1da996ce27c15@macports.org> #66511: Issue installing or upgrading ghostscript port -----------------------+-------------------- Reporter: Hardies1 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | -----------------------+-------------------- Comment (by ryandesign): In future please paste the text of error messages, not photos of them. Photos take up tons of space and are not searchable. The photo says: {{{ $ sudo port install ghostscript Password: ---> Computing dependencies for ghostscript ---> Fetching archive for ghostscript ---> Attempting to fetch ghostscript-9.56.1_0+x11.darwin_19.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/ghostscript ---> Attempting to fetch ghostscript-9.56.1_0+x11.darwin_19.x86_64.tbz2 from https://packages.macports.org/ghostscript ---> Attempting to fetch ghostscript-9.56.1_0+x11.darwin_19.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/ghostscript ---> Fetching distfiles for ghostscript }}} This problem sounds like #60509 (which was experienced by me on 32-bit Mac OS X 10.6 and by another user on Mac OS X 10.7, and which we attempted to work around in MacPorts 2.7.0 by reducing the number of processes that get spawned simultaneously when determining which servers are closest to you) and #61683 (which was experienced by many users of macOS 11.0, 11.1, and 11.2, and which was fixed by Apple in macOS 11.3). There are some details in those tickets about steps you can take to limit the number of processes even further, to see if that helps, and also mentions of some third-party software that may exacerbate the problem (which you could try disabling). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 07:54:06 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 07:54:06 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) In-Reply-To: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> References: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> Message-ID: <058.16761cf14380bb85d84bb91a994db576@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): It's a good idea. I've certainly appreciated it when other web sites do that, but I've never attempted to figure out how they do that. If you or anyone can figure out what we need to change in the guide to cause that to happen, please send a pull request. As of macOS Catalina the default shell changed from bash (whose default prompt ends with `$`) to zsh (where the default prompt ends with `%`) so we might want to switch to `%` at this point. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 08:39:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 08:39:09 -0000 Subject: [MacPorts] #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max Message-ID: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max -------------------------------------------------+------------------------- Reporter: amadeus24 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: chromaprint-1.5.1 failed to build | Port: Ventura arm | chromaprint-1.5.1 -------------------------------------------------+------------------------- main.lo attached -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 08:40:03 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 08:40:03 -0000 Subject: [MacPorts] #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max In-Reply-To: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> References: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> Message-ID: <061.16bfaf8f600b08f0ebfd5f7a62c00000@macports.org> #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max -------------------------+------------------------------------------------- Reporter: amadeus24 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: chromaprint-1.5.1 failed to build Port: | Ventura arm chromaprint-1.5.1 | -------------------------+------------------------------------------------- Changes (by amadeus24): * Attachment "main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 09:24:11 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 09:24:11 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) In-Reply-To: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> References: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> Message-ID: <058.8d6e04c9ab36e1099c87baf4486e0922@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): One good example seems to simply put the `$` (`>` in their case) in a separate `span` from the text command [https://scoop.sh/#/apps?q=wget&s=0&d=1&o=true] {{{#!html
>
}}} {{{
>
}}} Meanwhile there is one simple fix :) based on the existing functionality of [https://ports.macports.org/port/wget/] {{{#!html
$
}}} {{{
>
}}} Then the only missing piece will be making a hover on the input field select the copy button and a single click on the input field the whole text, but at least here a triple click does NOT select `$`, so that's already an improvement (and in the guide there is no copy button, so that's not a regression :)) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 10:22:46 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 10:22:46 -0000 Subject: [MacPorts] #66515: cctools @949.0.1_2 does not support llvm-15 Message-ID: <046.20125798cf456e1004d4a36bdc581381@macports.org> #66515: cctools @949.0.1_2 does not support llvm-15 --------------------------------+--------------------- Reporter: ballapete | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: bigsur, highsierra | Port: cctools --------------------------------+--------------------- Only the `variants llvm10, llvm11, llvm12, llvm13, llvm14, llvmdev, [+]xcode, and xtools` are supported while `clang15/llvm15` are already out since a few months. No need to update `cctools`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 12:09:46 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 12:09:46 -0000 Subject: [MacPorts] #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max In-Reply-To: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> References: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> Message-ID: <061.f21ed81be7c908020184f519b3706c79@macports.org> #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max -------------------------+------------------------------------------------- Reporter: amadeus24 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: chromaprint-1.5.1 failed to build Port: | Ventura arm chromaprint-1.5.1 | -------------------------+------------------------------------------------- Comment (by amadeus24): Solved. The problem was, I had a conflicting and old library in /usr/local -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 13:01:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 13:01:09 -0000 Subject: [MacPorts] #66404: bsdmake @24_1 checksum mismatch In-Reply-To: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> References: <049.fd99252a0270e9bdece20bf421e5b504@macports.org> Message-ID: <064.89b9786df1d39e36330283e1f07436ba@macports.org> #66404: bsdmake @24_1 checksum mismatch ---------------------------+-------------------- Reporter: feinbein1968 | Owner: raimue Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: bsdmake | ---------------------------+-------------------- Comment (by feinbein1968): Thanks a lot for helping me out. This fixed my problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 14:39:37 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 14:39:37 -0000 Subject: [MacPorts] #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max In-Reply-To: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> References: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> Message-ID: <061.a1d17989c5f61e265a14fe9b236165f1@macports.org> #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max -------------------------+------------------------------------------------- Reporter: amadeus24 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: chromaprint-1.5.1 failed to build Port: | Ventura arm chromaprint-1.5.1 | -------------------------+------------------------------------------------- Changes (by kencu): * status: new => closed * resolution: => invalid -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 15:37:38 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 15:37:38 -0000 Subject: [MacPorts] #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max In-Reply-To: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> References: <046.bf0d9ea6fc785eb8a8c7812f66e988f1@macports.org> Message-ID: <061.a23c02e9ded6e8ba2d80a7b6f5bb74ff@macports.org> #66514: chromaprint-1.5.1_0 failed to build on macOS 13.1 (Ventura) with M1 Max --------------------------+-------------------- Reporter: amadeus24 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: Port: chromaprint | --------------------------+-------------------- Changes (by jmroot): * keywords: chromaprint-1.5.1 failed to build Ventura arm => * port: chromaprint-1.5.1 => chromaprint -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 16:49:20 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 16:49:20 -0000 Subject: [MacPorts] #65110: texlive-lang-italian was stealth-updated In-Reply-To: <047.a06f1860349c55562b4aab88cc4e5efb@macports.org> References: <047.a06f1860349c55562b4aab88cc4e5efb@macports.org> Message-ID: <062.2aba6af5c263b29399ce6001183ca8c1@macports.org> #65110: texlive-lang-italian was stealth-updated -----------------------------------+---------------------- Reporter: Lev-GitHub | Owner: drkp Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: texlive-lang-italian | -----------------------------------+---------------------- Comment (by Lev-GitHub): Replying to [comment:11 Lev-GitHub]: > Same problem appeared recently. The problem persists to the date. I'm thinking that there needs to be a better fix than fixing this every time an update comes up. And, this port seems to be the only one that's having such a problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 17:24:28 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 17:24:28 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.36fbd8a6007ddd4ae4ca2e377dbb341c@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: Port: libmsn | --------------------------+-------------------- Comment (by kencu): OK, fixed a half-dozen more little issues like this, and all of the kde ports specified by: {{{ sudo port -v -N install kde }}} now install without any trouble for me on Ventura at least, using all and only the default variants. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 17:28:37 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 17:28:37 -0000 Subject: [MacPorts] #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? In-Reply-To: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> References: <048.d9428f8f5236cd0be7ec95d56bdd628e@macports.org> Message-ID: <063.f70d128a3a0f29b95e2cdf7a25411b6f@macports.org> #62833: libmsn @4.1_2 +debug: error: unknown type name 'des_key_schedule'; did you mean 'DES_key_schedule'? --------------------------+-------------------- Reporter: cooljeanius | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: Port: libmsn | --------------------------+-------------------- Comment (by kencu): however, you may find a lack of happiness with these kde ports once they are installed, at least on newer systems: {{{ % /Applications/MacPorts/KDE4/ark.app/Contents/MacOS/ark 2022-12-20 09:26:23.888 ark[94871:1644786] *** Assertion failure in -[NSNib initWithContentsOfURL:], NSNib.m:65 2022-12-20 09:26:23.890 ark[94871:1644786] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Deprecated in 10.8.' *** First throw call stack: ( 0 CoreFoundation 0x00007ff800e8acc3 __exceptionPreprocess + 242 1 libobjc.A.dylib 0x00007ff8009d910a objc_exception_throw + 48 2 Foundation 0x00007ff801c69fb0 -[NSCalendarDate initWithCoder:] + 0 3 AppKit 0x00007ff804535613 -[NSNib initWithContentsOfURL:] + 105 4 QtGui 0x0000000111ad23cf _Z18qt_mac_loadMenuNibP16QCocoaMenuLoader + 751 5 QtGui 0x0000000111ad5955 _Z7qt_initP19QApplicationPrivatei + 2117 6 QtGui 0x0000000111b42f48 _ZN19QApplicationPrivate9constructEv + 568 7 QtGui 0x0000000111b4333e _ZN12QApplicationC2ERiPPcbi + 94 8 libkdeui.5.14.3.dylib 0x0000000110c64ce6 _ZN12KApplicationC2Eb + 62 9 ark 0x000000010fb3e41d main + 5245 10 dyld 0x00007ff800a05310 start + 2432 ) libc++abi: terminating with uncaught exception of type NSException zsh: abort /Applications/MacPorts/KDE4/ark.app/Contents/MacOS/ark }}} I am not going to be digging in on this kind of issue for you. What may or may not be fixable in there is a good question. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 23:47:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 23:47:09 -0000 Subject: [MacPorts] #66516: cantor @4.14.3_5 +debug+docs: error: unknown type name 'string'; did you mean 'std::string'? Message-ID: <048.9979c211aaf62ee806c7efa1e9b92358@macports.org> #66516: cantor @4.14.3_5 +debug+docs: error: unknown type name 'string'; did you mean 'std::string'? -------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: cantor -------------------------+-------------------- {{{ make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_cantor/cantor/work/build' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_cantor/cantor/work/cantor-4.14.3/src/backends/qalculate/qalculateexpression.cpp:104:9: error: unknown type name 'string'; did you mean 'std::string'? string expression = unlocalizeExpression(command); ^~~~~~ std::string /Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk/usr/include/c++/v1/iosfwd:210:65: note: 'std::string' declared here typedef basic_string, allocator > string; ^ [ 94%] Built target cantor_kalgebrabackend [ 94%] Linking CXX shared module ../../../../lib/cantor_qalculateplotassistant.so cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_cantor/cantor/work/build/src/backends/qalculate/plotassistant && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/cantor_qalculateplotassistant.dir/link.txt --verbose=ON /usr/bin/clang++ -pipe -Os -g -fno-limit-debug-info -DDEBUG -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -fno-common -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -mmacosx-version- min=11.0 -bundle -Wl,-headerpad_max_install_names -multiply_defined suppress -Wl,-headerpad_max_install_names -g -fno-limit-debug-info -DDEBUG -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -o ../../../../lib/cantor_qalculateplotassistant.so CMakeFiles/cantor_qalculateplotassistant.dir/cantor_qalculateplotassistant_automoc.o CMakeFiles/cantor_qalculateplotassistant.dir/qalculateplotassistant.o CMakeFiles/cantor_qalculateplotassistant.dir/settings.o -Wl,-rpath,/opt/local/lib ../../../../lib/libcantorlibs.0.0.4.dylib /opt/local/lib/libkdeui.5.14.3.dylib /opt/local/libexec/qt4/lib/libQtGui.dylib /opt/local/libexec/qt4/lib/libQtSvg.dylib /opt/local/lib/libkdecore.5.14.3.dylib /opt/local/libexec/qt4/lib/libQtDBus.dylib /opt/local/libexec/qt4/lib/libQtCore.dylib -framework Carbon 1 error generated. make[2]: *** [src/backends/qalculate/CMakeFiles/cantor_qalculatebackend.dir/qalculateexpression.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_cantor/cantor/work/build' [ 95%] Built target cantor_qalculateplotassistant make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_cantor/cantor/work/build' make[1]: *** [src/backends/qalculate/CMakeFiles/cantor_qalculatebackend.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 20 23:51:53 2022 From: noreply at macports.org (MacPorts) Date: Tue, 20 Dec 2022 23:51:53 -0000 Subject: [MacPorts] #66516: cantor @4.14.3_5 +debug+docs: error: unknown type name 'string'; did you mean 'std::string'? In-Reply-To: <048.9979c211aaf62ee806c7efa1e9b92358@macports.org> References: <048.9979c211aaf62ee806c7efa1e9b92358@macports.org> Message-ID: <063.52eb7e2f7b4eef9f1626ed3169dbaa03@macports.org> #66516: cantor @4.14.3_5 +debug+docs: error: unknown type name 'string'; did you mean 'std::string'? --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: cantor | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "cantor_main.log" added. main.log for cantor -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:33:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:33:51 -0000 Subject: [MacPorts] #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero Message-ID: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero -------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: kiten -------------------------+-------------------- {{{ [ 4%] Building CXX object lib/CMakeFiles/kiten.dir/dictquery.o cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build/lib && /usr/bin/clang++ -DMAKE_KITEN_LIB -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build/lib -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/kiten-4.14.3/lib -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build -I/opt/local/include/KDE4 -I/opt/local/include/KDE4/KDE -I/opt/local/include/KDE -I/opt/local/include -I/opt/local/libexec/qt4/include/QtXmlPatterns -I/opt/local/libexec/qt4/include/QtXml -I/opt/local/libexec/qt4/include/QtWebKit -I/opt/local/libexec/qt4/include/QtUiTools -I/opt/local/libexec/qt4/include/QtTest -I/opt/local/libexec/qt4/include/QtSvg -I/opt/local/libexec/qt4/include/QtSql -I/opt/local/libexec/qt4/include/QtScriptTools -I/opt/local/libexec/qt4/include/QtScript -I/opt/local/libexec/qt4/include/QtOpenGL -I/opt/local/libexec/qt4/include/QtNetwork -I/opt/local/libexec/qt4/include/QtMultimedia -I/opt/local/libexec/qt4/include/QtHelp -I/opt/local/libexec/qt4/include/QtDesigner -I/opt/local/libexec/qt4/include/QtDeclarative -I/opt/local/libexec/qt4/include/QtDBus -I/opt/local/libexec/qt4/include/Qt3Support -I/opt/local/libexec/qt4/include/QtGui -I/opt/local/libexec/qt4/include/QtCore -I/opt/local/libexec/qt4/include -I/opt/local/libexec/qt4/share/mkspecs/default -pipe -Os -g -fno-limit- debug-info -DDEBUG -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -fno-common -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -Woverloaded-virtual -fno- common -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -Wno-return-type-c-linkage -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -mmacosx-version- min=11.0 -fPIC -MD -MT lib/CMakeFiles/kiten.dir/dictquery.o -MF CMakeFiles/kiten.dir/dictquery.o.d -o CMakeFiles/kiten.dir/dictquery.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/kiten-4.14.3/lib/dictquery.cpp /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/kiten-4.14.3/lib/dictquery.cpp:462:40: error: ordered comparison between pointer and zero ('const void *' and 'int') return d->entryOrder.contains( key ) > 0; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~ 1 error generated. make[2]: *** [lib/CMakeFiles/kiten.dir/dictquery.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build' make[1]: *** [lib/CMakeFiles/kiten.dir/all] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_kiten/kiten/work/build" && /usr/bin/make -j16 -w all VERBOSE=ON Exit code: 2 Error: Failed to build kiten: command execution failed DEBUG: Error code: CHILDSTATUS 51317 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:36:07 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:36:07 -0000 Subject: [MacPorts] #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero In-Reply-To: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> References: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> Message-ID: <063.5adbaffc6a1effe123224673c987dde2@macports.org> #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: kiten | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "kiten_main.log" added. main.log for kiten -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:42:33 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:42:33 -0000 Subject: [MacPorts] #66518: qtruby @4.14.3_2 +debug+docs+ruby18: error: ordered comparison between pointer and zero Message-ID: <048.7633909e0588fd8cd89370abffc3ef46@macports.org> #66518: qtruby @4.14.3_2 +debug+docs+ruby18: error: ordered comparison between pointer and zero -------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: qtruby -------------------------+-------------------- {{{ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_qtruby/qtruby/work/qtruby-4.14.3/src/qtruby.cpp:2097:17: error: ordered comparison between pointer and zero ('void *' and 'int') return (ptr > 0 ? Qtrue : Qfalse); ~~~ ^ ~ 1 error generated. make[2]: *** [src/CMakeFiles/qtruby4.dir/qtruby.cpp.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_qtruby/qtruby/work/build' make[1]: *** [src/CMakeFiles/qtruby4.dir/all] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_qtruby/qtruby/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_qtruby/qtruby/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_kde_qtruby/qtruby/work/build" && /usr/bin/make -j16 -w all VERBOSE=ON Exit code: 2 Error: Failed to build qtruby: command execution failed DEBUG: Error code: CHILDSTATUS 52296 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:44:33 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:44:33 -0000 Subject: [MacPorts] #66518: qtruby @4.14.3_2 +debug+docs+ruby18: error: ordered comparison between pointer and zero In-Reply-To: <048.7633909e0588fd8cd89370abffc3ef46@macports.org> References: <048.7633909e0588fd8cd89370abffc3ef46@macports.org> Message-ID: <063.9cfc3511eb823c7c9c508e1ada98c29c@macports.org> #66518: qtruby @4.14.3_2 +debug+docs+ruby18: error: ordered comparison between pointer and zero --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: qtruby | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "qtruby_main.log" added. main.log for qtruby -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:54:04 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:54:04 -0000 Subject: [MacPorts] #66519: rocs @4.14.3_6 +debug+docs: fatal error: too many errors emitted, stopping now [-ferror-limit=] (c++11-related?) Message-ID: <048.ac7f933cb716956ffe49f4dac557dd01@macports.org> #66519: rocs @4.14.3_6 +debug+docs: fatal error: too many errors emitted, stopping now [-ferror-limit=] (c++11-related?) -------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: rocs -------------------------+-------------------- I'm not going to paste the full output here, just the last portion of it that will fit in a single screen's worth of space: {{{ /opt/local/include/boost/math/tools/mp.hpp:403:12: error: unknown type name 'constexpr' static constexpr T M = N / 2; ^ /opt/local/include/boost/math/tools/mp.hpp:403:23: error: expected ';' at end of declaration list static constexpr T M = N / 2; ^ ; /opt/local/include/boost/math/tools/mp.hpp:404:12: error: unknown type name 'constexpr' static constexpr T R = N % 2; ^ /opt/local/include/boost/math/tools/mp.hpp:404:23: error: expected ';' at end of declaration list static constexpr T R = N % 2; ^ ; /opt/local/include/boost/math/tools/mp.hpp:406:18: warning: alias declarations are a C++11 extension [-Wc++11-extensions] using seq1 = typename make_integer_sequence_impl::type; ^ /opt/local/include/boost/math/tools/mp.hpp:407:18: warning: alias declarations are a C++11 extension [-Wc++11-extensions] using seq2 = typename append_integer_sequence::type; ^ /opt/local/include/boost/math/tools/mp.hpp:407:51: error: use of undeclared identifier 'seq1' using seq2 = typename append_integer_sequence::type; ^ /opt/local/include/boost/math/tools/mp.hpp:408:18: warning: alias declarations are a C++11 extension [-Wc++11-extensions] using seq3 = typename make_integer_sequence_impl::type; ^ /opt/local/include/boost/math/tools/mp.hpp:409:18: warning: alias declarations are a C++11 extension [-Wc++11-extensions] using seq4 = typename append_integer_sequence::type; ^ /opt/local/include/boost/math/tools/mp.hpp:409:51: error: use of undeclared identifier 'seq2' using seq4 = typename append_integer_sequence::type; ^ /opt/local/include/boost/math/tools/mp.hpp:412:18: warning: alias declarations are a C++11 extension [-Wc++11-extensions] using type = seq4; ^ /opt/local/include/boost/math/tools/mp.hpp:412:18: error: unknown type name 'seq4' /opt/local/include/boost/math/tools/mp.hpp:418:18: warning: alias declarations are a C++11 extension [-Wc++11-extensions] using type = typename iseq_if_c MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:55:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:55:37 -0000 Subject: [MacPorts] #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero In-Reply-To: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> References: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> Message-ID: <063.2f0098a26ac104ab36a8ef06598bbed7@macports.org> #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: kiten | --------------------------+-------------------- Comment (by kencu): Eric, see this one https://github.com/macports/macports- ports/commit/7dc53b88eaee0048613854b1676a66925917a825 the maintainer hasn?t been seen for some time. Want to fix and PR this? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 02:59:40 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 02:59:40 -0000 Subject: [MacPorts] #66519: rocs @4.14.3_6 +debug+docs: fatal error: too many errors emitted, stopping now [-ferror-limit=] (c++11-related?) In-Reply-To: <048.ac7f933cb716956ffe49f4dac557dd01@macports.org> References: <048.ac7f933cb716956ffe49f4dac557dd01@macports.org> Message-ID: <063.736ed3e1fba22e665d7a109c26bc512d@macports.org> #66519: rocs @4.14.3_6 +debug+docs: fatal error: too many errors emitted, stopping now [-ferror-limit=] (c++11-related?) --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: rocs | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "rocs_main.log" added. main.log for rocs -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 07:24:05 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 07:24:05 -0000 Subject: [MacPorts] #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero In-Reply-To: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> References: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> Message-ID: <063.340cbc01537ed1de0c7dbe4fe0451d4e@macports.org> #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: kiten | --------------------------+-------------------- Comment (by cooljeanius): Replying to [comment:1 kencu]: > Eric, see this one > > https://github.com/macports/macports- ports/commit/7dc53b88eaee0048613854b1676a66925917a825 > > the maintainer hasn?t been seen for some time. Want to fix and PR this? ok, feel free to assign me -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 07:41:34 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 07:41:34 -0000 Subject: [MacPorts] #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero In-Reply-To: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> References: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> Message-ID: <063.541ce58ac91eaaa41ac3837a32e192b3@macports.org> #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: kiten | --------------------------+-------------------- Comment (by cooljeanius): ok so I got past the initial error, but now am running into a bunch of linking ones: {{{ [ 97%] Linking CXX executable kiten.app/Contents/MacOS/kiten cd /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build/app && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/kiten_bin.dir/link.txt --verbose=ON /usr/bin/clang++ -pipe -Os -DNDEBUG -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -fno-common -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -Woverloaded-virtual -fno- common -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -Wno-return-type-c-linkage -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -mmacosx-version- min=11.0 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk CMakeFiles/kiten_bin.dir/kiten_bin_automoc.o CMakeFiles/kiten_bin.dir/configdictionaryselector.o CMakeFiles/kiten_bin.dir/configsortingpage.o CMakeFiles/kiten_bin.dir/configuredialog.o CMakeFiles/kiten_bin.dir/entrylistmodel.o CMakeFiles/kiten_bin.dir/entrylistview.o CMakeFiles/kiten_bin.dir/kiten.o CMakeFiles/kiten_bin.dir/main.o CMakeFiles/kiten_bin.dir/resultsview.o CMakeFiles/kiten_bin.dir/searchstringinput.o CMakeFiles/kiten_bin.dir/dictionaryupdatemanager.o CMakeFiles/kiten_bin.dir/wordtype.o CMakeFiles/kiten_bin.dir/kitenconfig.o -o kiten.app/Contents/MacOS/kiten -Wl,-rpath,/opt/local/lib /opt/local/lib/libkhtml.5.14.3.dylib ../lib/libkiten.4.14.3.dylib /opt/local/lib/libphonon.dylib /opt/local/lib/libkjs.4.14.3.dylib /opt/local/lib/libkparts.4.14.3.dylib /opt/local/lib/libkio.5.14.3.dylib /opt/local/libexec/qt4/lib/libQtNetwork.dylib /opt/local/libexec/qt4/lib/libQtXml.dylib /opt/local/lib/libnepomukutils.4.14.3.dylib /opt/local/lib/libnepomuk.4.14.3.dylib /opt/local/lib/libsoprano.dylib /opt/local/lib/libkdeui.5.14.3.dylib /opt/local/lib/libkdecore.5.14.3.dylib /opt/local/libexec/qt4/lib/libQtCore.dylib /opt/local/libexec/qt4/lib/libQtDBus.dylib -framework Carbon /opt/local/libexec/qt4/lib/libQtGui.dylib /opt/local/libexec/qt4/lib/libQtSvg.dylib 1 warning generated. Undefined symbols for architecture x86_64: "HistoryPtrList::setCurrent(int)", referenced from: Kiten::goInHistory(int) in kiten.o Kiten::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in kiten.o "HistoryPtrList::next(int)", referenced from: Kiten::forward() in kiten.o Kiten::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in kiten.o "HistoryPtrList::prev(int)", referenced from: Kiten::back() in kiten.o Kiten::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in kiten.o "HistoryPtrList::count()", referenced from: Kiten::enableHistoryButtons() in kiten.o "HistoryPtrList::index()", referenced from: Kiten::enableHistoryButtons() in kiten.o "HistoryPtrList::addItem(EntryList*)", referenced from: Kiten::searchAndDisplay(DictQuery const&) in kiten.o Kiten::addHistory(EntryList*) in kiten.o Kiten::searchInResults() in kiten.o Kiten::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) in kiten.o "HistoryPtrList::current()", referenced from: Kiten::addExportListEntry(int) in kiten.o Kiten::searchInResults() in kiten.o Kiten::displayHistoryItem() in kiten.o Kiten::setCurrentScrollValue(int) in kiten.o "HistoryPtrList::HistoryPtrList()", referenced from: Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::Kiten(QWidget*, char const*) in kiten.o "HistoryPtrList::~HistoryPtrList()", referenced from: Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::~Kiten() in kiten.o "DictionaryManager::loadSettings(KConfig const&)", referenced from: Kiten::loadDictionaries() in kiten.o "DictionaryManager::addDictionary(QString const&, QString const&, QString const&)", referenced from: Kiten::loadDictConfig(QString const&) in kiten.o "DictionaryManager::loadDictSettings(QString const&, KConfigSkeleton*)", referenced from: Kiten::loadDictionaries() in kiten.o "DictionaryManager::removeDictionary(QString const&)", referenced from: Kiten::loadDictConfig(QString const&) in kiten.o "DictionaryManager::listDictFileTypes()", referenced from: ConfigSortingPage::ConfigSortingPage(QWidget*, KitenConfigSkeleton*, QFlags) in configsortingpage.o ConfigureDialog::makeDictionaryPreferencesPage(QWidget*, KitenConfigSkeleton*) in configuredialog.o Kiten::loadDictionaries() in kiten.o "DictionaryManager::removeAllDictionaries()", referenced from: Kiten::loadDictionaries() in kiten.o "DictionaryManager::generatePreferenceDialogs(KConfigSkeleton*, QWidget*)", referenced from: ConfigureDialog::makeDictionaryPreferencesPage(QWidget*, KitenConfigSkeleton*) in configuredialog.o "DictionaryManager::generateExtendedFieldsList()", referenced from: ConfigSortingPage::ConfigSortingPage(QWidget*, KitenConfigSkeleton*, QFlags) in configsortingpage.o "DictionaryManager::DictionaryManager()", referenced from: Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::Kiten(QWidget*, char const*) in kiten.o "DictionaryManager::~DictionaryManager()", referenced from: Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::~Kiten() in kiten.o "DictQuery::setProperty(QString const&, QString const&)", referenced from: SearchStringInput::getSearchQuery() const in searchstringinput.o "DictQuery::setMatchType(DictQuery::MatchType)", referenced from: Kiten::searchAndDisplay(DictQuery const&) in kiten.o SearchStringInput::getSearchQuery() const in searchstringinput.o "DictQuery::setFilterType(DictQuery::FilterType)", referenced from: SearchStringInput::getSearchQuery() const in searchstringinput.o "DictQuery::removeProperty(QString const&)", referenced from: SearchStringInput::setSearchQuery(DictQuery const&) in searchstringinput.o "DictQuery::setMatchWordType(DictQuery::MatchWordType)", referenced from: SearchStringInput::getSearchQuery() const in searchstringinput.o "DictQuery::DictQuery(QString const&)", referenced from: Kiten::searchText(QString const&) in kiten.o Kiten::searchClipboard() in kiten.o SearchStringInput::getSearchQuery() const in searchstringinput.o "DictQuery::DictQuery(DictQuery const&)", referenced from: Kiten::searchAndDisplay(DictQuery const&) in kiten.o SearchStringInput::setSearchQuery(DictQuery const&) in searchstringinput.o "DictQuery::DictQuery()", referenced from: Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::updateConfiguration() in kiten.o Kiten::Kiten(QWidget*, char const*) in kiten.o "DictQuery::~DictQuery()", referenced from: Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::updateConfiguration() in kiten.o Kiten::Kiten(QWidget*, char const*) in kiten.o Kiten::~Kiten() in kiten.o Kiten::searchFromEdit() in kiten.o Kiten::searchAndDisplay(DictQuery const&) in kiten.o Kiten::searchText(QString const&) in kiten.o ... "DictQuery::operator=(DictQuery const&)", referenced from: Kiten::updateConfiguration() in kiten.o Kiten::searchFromEdit() in kiten.o "EntryList::setScrollValue(int)", referenced from: Kiten::setCurrentScrollValue(int) in kiten.o "EntryList::sort(QStringList&, QStringList&)", referenced from: Kiten::displayResults(EntryList*) in kiten.o "EntryList::EntryList(EntryList const&)", referenced from: EntryListModel::EntryListModel(EntryList const&) in entrylistmodel.o EntryListModel::entryList() const in entrylistmodel.o "EntryList::EntryList()", referenced from: Kiten::setupExportListDock() in kiten.o "EntryList::~EntryList()", referenced from: EntryListModel::~EntryListModel() in entrylistmodel.o EntryListModel::~EntryListModel() in entrylistmodel.o Kiten::setupExportListDock() in kiten.o Kiten::addExportListEntry(int) in kiten.o "EntryList::operator=(EntryList const&)", referenced from: EntryListModel::setEntryList(EntryList const&) in entrylistmodel.o "DictionaryManager::doSearchInList(DictQuery const&, EntryList const*) const", referenced from: Kiten::searchInResults() in kiten.o "DictionaryManager::listDictionariesOfType(QString const&) const", referenced from: Kiten::loadDictConfig(QString const&) in kiten.o "DictionaryManager::doSearch(DictQuery const&) const", referenced from: Kiten::searchAndDisplay(DictQuery const&) in kiten.o "DictionaryPreferenceDialog::name() const", referenced from: ConfigureDialog::makeDictionaryPreferencesPage(QWidget*, KitenConfigSkeleton*) in configuredialog.o "Entry::getMeanings() const", referenced from: EntryListModel::data(QModelIndex const&, int) const in entrylistmodel.o "Entry::getReadings() const", referenced from: EntryListModel::data(QModelIndex const&, int) const in entrylistmodel.o "Entry::getWord() const", referenced from: EntryListModel::data(QModelIndex const&, int) const in entrylistmodel.o "DictQuery::getMatchType() const", referenced from: Kiten::searchAndDisplay(DictQuery const&) in kiten.o SearchStringInput::setSearchQuery(DictQuery const&) in searchstringinput.o "DictQuery::getFilterType() const", referenced from: SearchStringInput::setSearchQuery(DictQuery const&) in searchstringinput.o "DictQuery::getMatchWordType() const", referenced from: SearchStringInput::setSearchQuery(DictQuery const&) in searchstringinput.o "DictQuery::toString() const", referenced from: SearchStringInput::setSearchQuery(DictQuery const&) in searchstringinput.o "EntryList::scrollValue() const", referenced from: Kiten::displayResults(EntryList*) in kiten.o "EntryList::toHTML() const", referenced from: Kiten::displayResults(EntryList*) in kiten.o "EntryList::getQuery() const", referenced from: Kiten::searchAndDisplay(DictQuery const&) in kiten.o Kiten::displayHistoryItem() in kiten.o "operator<(DictQuery const&, DictQuery const&)", referenced from: Kiten::searchClipboard() in kiten.o "operator!=(DictQuery const&, DictQuery const&)", referenced from: Kiten::searchFromEdit() in kiten.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [app/kiten.app/Contents/MacOS/kiten] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build' make[1]: *** [app/CMakeFiles/kiten_bin.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:169:34: warning: comparison of integers of different signs: 'unsigned int' and 'int' [-Wsign-compare] || list.last().strokes() + 5 < high ) ~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:168:30: warning: comparison of integers of different signs: 'unsigned int' and 'int' [-Wsign-compare] || list.last().strokes() < low ~~~~~~~~~~~~~~~~~~~~~ ^ ~~~ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:188:45: warning: comparison of integers of different signs: 'unsigned int' and 'int' [-Wsign-compare] if( low <= it.strokes() && it.strokes() <= high ) ~~~~~~~~~~~~ ^ ~~~~ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:188:13: warning: comparison of integers of different signs: 'int' and 'unsigned int' [-Wsign-compare] if( low <= it.strokes() && it.strokes() <= high ) ~~~ ^ ~~~~~~~~~~~~ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:199:41: warning: unused parameter 'kanji' [-Wunused-parameter] void RadSelectView::loadKanji( QString &kanji ) ^ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:204:51: warning: unused parameter 'radicals' [-Wunused-parameter] void RadSelectView::loadRadicals( const QString &radicals ^ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:205:40: warning: unused parameter 'strokeMin' [-Wunused-parameter] , int strokeMin ^ /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/kiten-4.14.3/radselect/radselectview.cpp:206:40: warning: unused parameter 'strokeMax' [-Wunused-parameter] , int strokeMax ) ^ [ 98%] Linking CXX executable kitenkanjibrowser.app/Contents/MacOS/kitenkanjibrowser cd /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build/kanjibrowser && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/kanjibrowser_bin.dir/link.txt --verbose=ON /usr/bin/clang++ -pipe -Os -DNDEBUG -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -fno-common -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -Woverloaded-virtual -fno- common -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -Wno-return-type-c-linkage -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -mmacosx-version- min=11.0 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk CMakeFiles/kanjibrowser_bin.dir/kanjibrowser_bin_automoc.o CMakeFiles/kanjibrowser_bin.dir/kanjibrowser.o CMakeFiles/kanjibrowser_bin.dir/kanjibrowserview.o CMakeFiles/kanjibrowser_bin.dir/main.o CMakeFiles/kanjibrowser_bin.dir/kanjibrowserconfig.o -o kitenkanjibrowser.app/Contents/MacOS/kitenkanjibrowser -Wl,-rpath,/opt/local/lib ../lib/libkiten.4.14.3.dylib /opt/local/lib/libkdeui.5.14.3.dylib /opt/local/lib/libkdecore.5.14.3.dylib /opt/local/libexec/qt4/lib/libQtDBus.dylib /opt/local/libexec/qt4/lib/libQtCore.dylib -framework Carbon /opt/local/libexec/qt4/lib/libQtGui.dylib /opt/local/libexec/qt4/lib/libQtSvg.dylib Undefined symbols for architecture x86_64: "DictFileKanjidic::loadSettings()", referenced from: KanjiBrowser::loadKanji() in kanjibrowser.o "DictFileKanjidic::dumpDictionary()", referenced from: KanjiBrowser::loadKanji() in kanjibrowser.o "DictFileKanjidic::DictFileKanjidic()", referenced from: KanjiBrowser::loadKanji() in kanjibrowser.o "DictQuery::DictQuery(QString const&)", referenced from: KanjiBrowserView::searchKanji(QListWidgetItem*) in kanjibrowserview.o "DictQuery::~DictQuery()", referenced from: KanjiBrowserView::searchKanji(QListWidgetItem*) in kanjibrowserview.o "EntryKanjidic::getKanjiGrade() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getStrokesCount() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getOnyomiReadings() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getInNamesReadings() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getKunyomiReadings() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getAsRadicalReadings() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getOnyomiReadingsList() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getInNamesReadingsList() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getKunyomiReadingsList() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "EntryKanjidic::getAsRadicalReadingsList() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "Entry::getMeanings() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "Entry::getMeaningsList() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o "Entry::getWord() const", referenced from: KanjiBrowserView::showKanjiInformation(EntryKanjidic const*) in kanjibrowserview.o KanjiBrowserView::searchKanji(QListWidgetItem*) in kanjibrowserview.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [kanjibrowser/kitenkanjibrowser.app/Contents/MacOS/kitenkanjibrowser] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build' make[1]: *** [kanjibrowser/CMakeFiles/kanjibrowser_bin.dir/all] Error 2 8 warnings generated. [100%] Linking CXX executable kitenradselect.app/Contents/MacOS/kitenradselect cd /opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build/radselect && /opt/local/bin/cmake -E cmake_link_script CMakeFiles/radselect_bin.dir/link.txt --verbose=ON /usr/bin/clang++ -pipe -Os -DNDEBUG -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -fno-common -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -Woverloaded-virtual -fno- common -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -Wno-return-type-c-linkage -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -mmacosx-version- min=11.0 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk CMakeFiles/radselect_bin.dir/radselect_bin_automoc.o CMakeFiles/radselect_bin.dir/buttongrid.o CMakeFiles/radselect_bin.dir/kanji.o CMakeFiles/radselect_bin.dir/main.o CMakeFiles/radselect_bin.dir/radical.o CMakeFiles/radselect_bin.dir/radicalbutton.o CMakeFiles/radselect_bin.dir/radicalfile.o CMakeFiles/radselect_bin.dir/radselect.o CMakeFiles/radselect_bin.dir/radselectview.o CMakeFiles/radselect_bin.dir/radselectconfig.o -o kitenradselect.app/Contents/MacOS/kitenradselect -Wl,-rpath,/opt/local/lib ../lib/libkiten.4.14.3.dylib /opt/local/lib/libkdeui.5.14.3.dylib /opt/local/lib/libkdecore.5.14.3.dylib /opt/local/libexec/qt4/lib/libQtDBus.dylib /opt/local/libexec/qt4/lib/libQtCore.dylib -framework Carbon /opt/local/libexec/qt4/lib/libQtGui.dylib /opt/local/libexec/qt4/lib/libQtSvg.dylib Undefined symbols for architecture x86_64: "DictQuery::DictQuery()", referenced from: RadSelect::RadSelect() in radselect.o RadSelect::RadSelect() in radselect.o "DictQuery::~DictQuery()", referenced from: RadSelect::RadSelect() in radselect.o RadSelect::RadSelect() in radselect.o RadSelect::~RadSelect() in radselect.o "DictQuery::operator=(QString const&)", referenced from: RadSelect::loadSearchString(QString const&) in radselect.o RadSelect::sendSearch(QStringList const&) in radselect.o "DictQuery::getProperty(QString const&) const", referenced from: RadSelect::loadSearchString(QString const&) in radselect.o "DictQuery::isEmpty() const", referenced from: RadSelect::saveProperties(KConfigGroup&) in radselect.o "DictQuery::toString() const", referenced from: RadSelect::sendSearch(QStringList const&) in radselect.o "DictQuery::operator QString() const", referenced from: RadSelect::saveProperties(KConfigGroup&) in radselect.o RadSelect::sendSearch(QStringList const&) in radselect.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [radselect/kitenradselect.app/Contents/MacOS/kitenradselect] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build' make[1]: *** [radselect/CMakeFiles/radselect_bin.dir/all] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build' Command failed: cd "/opt/local/var/macports/build /_Users_ericgallager_Documents_GitHub_macports- ports_kde_kiten/kiten/work/build" && /usr/bin/make -j16 -w all VERBOSE=ON Exit code: 2 Error: Failed to build kiten: command execution failed DEBUG: Error code: CHILDSTATUS 68700 2 }}} Attaching a new logfile next. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 07:43:01 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 07:43:01 -0000 Subject: [MacPorts] #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero In-Reply-To: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> References: <048.4fb35e45aade1a7eedf9f73b51b53f56@macports.org> Message-ID: <063.9cef7dceb5f2836198af8863053e971d@macports.org> #66517: kiten @4.14.3_3 +debug+docs: error: ordered comparison between pointer and zero --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: kiten | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "kiten_main1.log" added. main.log for kiten, after the initial error is worked past -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:00:53 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 08:00:53 -0000 Subject: [MacPorts] #63761: gdb: Failed to destroot gdb: no files matched glob pattern "g*" In-Reply-To: <047.c36231f044feff685fe8287450e2a8b7@macports.org> References: <047.c36231f044feff685fe8287450e2a8b7@macports.org> Message-ID: <062.6f74579d400eb9bb2d927a994619521e@macports.org> #63761: gdb: Failed to destroot gdb: no files matched glob pattern "g*" -------------------------+---------------------- Reporter: joelburton | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: monterey Port: gdb | -------------------------+---------------------- Comment (by diekhans): I am now getting this problem on M1/13.0.1.. any idea how to fix? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:17:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 08:17:51 -0000 Subject: [MacPorts] #64411: gdal-grass: --with-grass=/opt/local/share/grass-7.4.0 requested, but libraries not found! In-Reply-To: <047.4cf657f6cbfccd453e0632cca2926c73@macports.org> References: <047.4cf657f6cbfccd453e0632cca2926c73@macports.org> Message-ID: <062.305db6efd530f066ee7af5c6545e4547@macports.org> #64411: gdal-grass: --with-grass=/opt/local/share/grass-7.4.0 requested, but libraries not found! -------------------------------+---------------------- Reporter: ryandesign | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gdal-grass, qgis | -------------------------------+---------------------- Comment (by ryandesign): Nearly a year later, the problem still exists. https://build.macports.org/builders/ports- 13_x86_64-builder/builds/4935/steps/install-port/logs/stdio -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 08:20:18 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 08:20:18 -0000 Subject: [MacPorts] #66520: py311-psygnal @0.7.0: ERROR Missing dependencies: hatch-vcs Message-ID: <047.ff5f56cb45b2a345854b3b75f8d1082a@macports.org> #66520: py311-psygnal @0.7.0: ERROR Missing dependencies: hatch-vcs ------------------------+------------------------- Reporter: ryandesign | Owner: Schamschula Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-psygnal ------------------------+------------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/4928/steps/install-port/logs/stdio {{{ * Getting dependencies for wheel... ERROR Missing dependencies: hatch-vcs }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 11:08:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 11:08:58 -0000 Subject: [MacPorts] #66520: py311-psygnal @0.7.0: ERROR Missing dependencies: hatch-vcs In-Reply-To: <047.ff5f56cb45b2a345854b3b75f8d1082a@macports.org> References: <047.ff5f56cb45b2a345854b3b75f8d1082a@macports.org> Message-ID: <062.5fde523f8d3f2a886d47e1470f60a8ac@macports.org> #66520: py311-psygnal @0.7.0: ERROR Missing dependencies: hatch-vcs -------------------------+------------------------- Reporter: ryandesign | Owner: Schamschula Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-psygnal | -------------------------+------------------------- Comment (by Schamschula): That dependency isn't declared upstream. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 11:59:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 11:59:58 -0000 Subject: [MacPorts] #66520: py311-psygnal @0.7.0: ERROR Missing dependencies: hatch-vcs In-Reply-To: <047.ff5f56cb45b2a345854b3b75f8d1082a@macports.org> References: <047.ff5f56cb45b2a345854b3b75f8d1082a@macports.org> Message-ID: <062.c31827ae820a8ebedd1f4d1e23d2e5d6@macports.org> #66520: py311-psygnal @0.7.0: ERROR Missing dependencies: hatch-vcs -------------------------+------------------------- Reporter: ryandesign | Owner: Schamschula Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-psygnal | -------------------------+------------------------- Changes (by Marius Schamschula ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"1bc0839603adaf1be34872cc1c49a31e270c868f/macports-ports" 1bc0839603adaf1be34872cc1c49a31e270c868f/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1bc0839603adaf1be34872cc1c49a31e270c868f" py-psygnal: add py-hatch-vcs as depends_build Closes: https://trac.macports.org/ticket/66520 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 14:08:53 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 14:08:53 -0000 Subject: [MacPorts] #66521: qbs-docs @1.23.0: destroot failure Message-ID: <047.d82f72f07e9df81f88703831eec1d18c@macports.org> #66521: qbs-docs @1.23.0: destroot failure ------------------------+---------------------- Reporter: ryandesign | Owner: jobor Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: qbs-docs ------------------------+---------------------- qbs-docs fails to destroot: https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5022/steps/install-port/logs/stdio {{{ -- Found Python3: /opt/local/bin/python3.11 (found version "3.11.1") found components: Interpreter -- Could NOT find PY_lxml (missing: PY_LXML) -- Could NOT find PY_bs4 (missing: PY_BS4) CMake Warning at cmake/QbsDocumentation.cmake:166 (message): Cannot import lxml and bs4 python modules. Qbs documentation will not be built. }}} {{{ Error: No files have been installed in the destroot directory! }}} The port declares dependencies on python 3.10 and modules but cmake has found and tried to use python 3.11, for which the modules were not installed. Modify the configuration process so that python 3.10 is always used, even if python 3.11 is installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:06:10 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 15:06:10 -0000 Subject: [MacPorts] #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt Message-ID: <043.f37ee7fc32e607c67802430979985441@macports.org> #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt --------------------+----------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: python310 --------------------+----------------------- I've tried to install neovim, which has a dependency on python310, which for some reason didn't install cleanly and required to be rebuilt (a big waste of time), although [https://ports.macports.org/port/python310/details/] says that it should work fine on Catalina Neovim launches fine even without rebuilding the port, but then I get a constant nag that this ports needs to be rebuilt every time I install something. Is there a way to avoid that? (also, where are the logs that describe why the installation didn't succeed and the rebuilt is required, couldn't find anyting in `/opt/local/var/macports/logs`) Below are the neovim installation logs {{{ ---> Computing dependencies for neovim The following dependencies will be installed: boost176 bzip2 expat gettext gettext-tools-libs icu libedit libffi libtermkey libtextstyle libuv libvterm lua51-lpeg lua51-mpack luajit luv-luajit lz4 lzma msgpack msgpack-c msgpack-cpp ncurses python310 python3_select python_select sqlite3 tree-sitter unibilium xz zstd Continue? [Y/n]: y ---> Fetching archive for ncurses ---> Attempting to fetch ncurses-6.3_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/ncurses ---> Attempting to fetch ncurses-6.3_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/ncurses ---> Installing ncurses @6.3_0 ---> Activating ncurses @6.3_0 ---> Cleaning ncurses ---> Fetching archive for libtextstyle ---> Attempting to fetch libtextstyle-0.21_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/libtextstyle ---> Attempting to fetch libtextstyle-0.21_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/libtextstyle ---> Installing libtextstyle @0.21_0 ---> Activating libtextstyle @0.21_0 ---> Cleaning libtextstyle ---> Fetching archive for gettext-tools-libs ---> Attempting to fetch gettext-tools-libs-0.21_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/gettext-tools-libs ---> Attempting to fetch gettext-tools- libs-0.21_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/gettext-tools-libs ---> Installing gettext-tools-libs @0.21_0 ---> Activating gettext-tools-libs @0.21_0 ---> Cleaning gettext-tools-libs ---> Fetching archive for gettext ---> Attempting to fetch gettext-0.21_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/gettext ---> Attempting to fetch gettext-0.21_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/gettext ---> Installing gettext @0.21_0 ---> Activating gettext @0.21_0 ---> Cleaning gettext ---> Fetching archive for unibilium ---> Attempting to fetch unibilium-2.0.0_1.darwin_19.x86_64.tbz2 from https://packages.macports.org/unibilium ---> Attempting to fetch unibilium-2.0.0_1.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/unibilium ---> Installing unibilium @2.0.0_1 ---> Activating unibilium @2.0.0_1 ---> Cleaning unibilium ---> Fetching archive for libtermkey ---> Attempting to fetch libtermkey-0.22_1.darwin_19.x86_64.tbz2 from https://packages.macports.org/libtermkey ---> Attempting to fetch libtermkey-0.22_1.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/libtermkey ---> Installing libtermkey @0.22_1 ---> Activating libtermkey @0.22_1 ---> Cleaning libtermkey ---> Fetching archive for libuv ---> Attempting to fetch libuv-1.44.2_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/libuv ---> Attempting to fetch libuv-1.44.2_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/libuv ---> Installing libuv @1.44.2_0 ---> Activating libuv @1.44.2_0 ---> Cleaning libuv ---> Fetching archive for libvterm ---> Attempting to fetch libvterm-0.3_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/libvterm ---> Attempting to fetch libvterm-0.3_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/libvterm ---> Installing libvterm @0.3_0 ---> Activating libvterm @0.3_0 ---> Cleaning libvterm ---> Fetching archive for luajit ---> Attempting to fetch luajit-2.1.0-beta3_6.darwin_19.x86_64.tbz2 from https://packages.macports.org/luajit ---> Attempting to fetch luajit-2.1.0-beta3_6.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/luajit ---> Installing luajit @2.1.0-beta3_6 ---> Activating luajit @2.1.0-beta3_6 ---> Cleaning luajit ---> Fetching archive for lua51-lpeg ---> Attempting to fetch lua51-lpeg-1.0.2-1_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/lua51-lpeg ---> Attempting to fetch lua51-lpeg-1.0.2-1_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/lua51-lpeg ---> Installing lua51-lpeg @1.0.2-1_0 ---> Activating lua51-lpeg @1.0.2-1_0 ---> Cleaning lua51-lpeg ---> Fetching archive for lua51-mpack ---> Attempting to fetch lua51-mpack-1.0.8-0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/lua51-mpack ---> Attempting to fetch lua51-mpack-1.0.8-0_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/lua51-mpack ---> Installing lua51-mpack @1.0.8-0_0 ---> Activating lua51-mpack @1.0.8-0_0 ---> Cleaning lua51-mpack ---> Fetching archive for luv-luajit ---> Attempting to fetch luv-luajit-1.43.0-0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/luv-luajit ---> Attempting to fetch luv- luajit-1.43.0-0_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/luv-luajit ---> Installing luv-luajit @1.43.0-0_0 ---> Activating luv-luajit @1.43.0-0_0 ---> Cleaning luv-luajit ---> Fetching archive for msgpack-c ---> Attempting to fetch msgpack-c-4.0.0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/msgpack-c ---> Attempting to fetch msgpack-c-4.0.0_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/msgpack-c ---> Installing msgpack-c @4.0.0_0 ---> Activating msgpack-c @4.0.0_0 ---> Cleaning msgpack-c ---> Fetching archive for bzip2 ---> Attempting to fetch bzip2-1.0.8_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/bzip2 ---> Attempting to fetch bzip2-1.0.8_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/bzip2 ---> Installing bzip2 @1.0.8_0 ---> Activating bzip2 @1.0.8_0 ---> Cleaning bzip2 ---> Fetching archive for expat ---> Attempting to fetch expat-2.5.0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/expat ---> Attempting to fetch expat-2.5.0_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/expat ---> Installing expat @2.5.0_0 ---> Activating expat @2.5.0_0 ---> Cleaning expat ---> Fetching archive for icu ---> Attempting to fetch icu-72.1_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/icu ---> Attempting to fetch icu-72.1_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/icu ---> Installing icu @72.1_0 ---> Activating icu @72.1_0 ---> Cleaning icu ---> Fetching archive for lzma ---> Attempting to fetch lzma-22.01_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/lzma ---> Attempting to fetch lzma-22.01_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/lzma ---> Installing lzma @22.01_0 ---> Activating lzma @22.01_0 ---> Cleaning lzma ---> Fetching archive for libedit ---> Attempting to fetch libedit-20221030-3.1_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/libedit ---> Attempting to fetch libedit-20221030-3.1_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/libedit ---> Installing libedit @20221030-3.1_0 ---> Activating libedit @20221030-3.1_0 ---> Cleaning libedit ---> Fetching archive for libffi ---> Attempting to fetch libffi-3.4.4_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/libffi ---> Attempting to fetch libffi-3.4.4_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/libffi ---> Installing libffi @3.4.4_0 ---> Activating libffi @3.4.4_0 ---> Cleaning libffi ---> Fetching archive for python3_select ---> Attempting to fetch python3_select-0.0_3.darwin_19.noarch.tbz2 from https://packages.macports.org/python3_select ---> Attempting to fetch python3_select-0.0_3.darwin_19.noarch.tbz2.rmd160 from https://packages.macports.org/python3_select ---> Installing python3_select @0.0_3 ---> Activating python3_select @0.0_3 ---> Cleaning python3_select ---> Fetching archive for python_select ---> Attempting to fetch python_select-0.3_10.darwin_19.noarch.tbz2 from https://packages.macports.org/python_select ---> Attempting to fetch python_select-0.3_10.darwin_19.noarch.tbz2.rmd160 from https://packages.macports.org/python_select ---> Installing python_select @0.3_10 ---> Activating python_select @0.3_10 ---> Cleaning python_select ---> Fetching archive for sqlite3 ---> Attempting to fetch sqlite3-3.40.0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/sqlite3 ---> Attempting to fetch sqlite3-3.40.0_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/sqlite3 ---> Installing sqlite3 @3.40.0_0 ---> Activating sqlite3 @3.40.0_0 ---> Cleaning sqlite3 ---> Fetching archive for xz ---> Attempting to fetch xz-5.2.9_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/xz ---> Attempting to fetch xz-5.2.9_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/xz ---> Installing xz @5.2.9_0 ---> Activating xz @5.2.9_0 ---> Cleaning xz ---> Fetching archive for python310 ---> Attempting to fetch python310-3.10.9_0+lto+optimizations.darwin_19.x86_64.tbz2 from https://packages.macports.org/python310 ---> Attempting to fetch python310-3.10.9_0+lto+optimizations.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/python310 ---> Installing python310 @3.10.9_0+lto+optimizations ---> Activating python310 @3.10.9_0+lto+optimizations ---> Cleaning python310 ---> Fetching archive for lz4 ---> Attempting to fetch lz4-1.9.4_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/lz4 ---> Attempting to fetch lz4-1.9.4_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/lz4 ---> Installing lz4 @1.9.4_0 ---> Activating lz4 @1.9.4_0 ---> Cleaning lz4 ---> Fetching archive for zstd ---> Attempting to fetch zstd-1.5.2_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/zstd ---> Attempting to fetch zstd-1.5.2_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/zstd ---> Installing zstd @1.5.2_0 ---> Activating zstd @1.5.2_0 ---> Cleaning zstd ---> Fetching archive for boost176 ---> Attempting to fetch boost176-1.76.0_6+no_single+no_static+python310.darwin_19.x86_64.tbz2 from https://packages.macports.org/boost176 ---> Attempting to fetch boost176-1.76.0_6+no_single+no_static+python310.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/boost176 ---> Installing boost176 @1.76.0_6+no_single+no_static+python310 ---> Activating boost176 @1.76.0_6+no_single+no_static+python310 ---> Cleaning boost176 ---> Fetching archive for msgpack-cpp ---> Attempting to fetch msgpack-cpp-4.1.1_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/msgpack-cpp ---> Attempting to fetch msgpack-cpp-4.1.1_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/msgpack-cpp ---> Installing msgpack-cpp @4.1.1_0 ---> Activating msgpack-cpp @4.1.1_0 ---> Cleaning msgpack-cpp ---> Fetching archive for msgpack ---> Attempting to fetch msgpack-4_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/msgpack ---> Attempting to fetch msgpack-4_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/msgpack ---> Installing msgpack @4_0 ---> Activating msgpack @4_0 ---> Cleaning msgpack ---> Fetching archive for tree-sitter ---> Attempting to fetch tree-sitter-0.20.7_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/tree-sitter ---> Attempting to fetch tree- sitter-0.20.7_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/tree-sitter ---> Installing tree-sitter @0.20.7_0 ---> Activating tree-sitter @0.20.7_0 ---> Cleaning tree-sitter ---> Fetching archive for neovim ---> Attempting to fetch neovim-0.8.0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/neovim ---> Attempting to fetch neovim-0.8.0_0.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/neovim ---> Installing neovim @0.8.0_0 ---> Activating neovim @0.8.0_0 ---> Cleaning neovim ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 4 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: python310 @3.10.9+lto+optimizations Continue? [Y/n]: n }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 15:50:03 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 15:50:03 -0000 Subject: [MacPorts] #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt In-Reply-To: <043.f37ee7fc32e607c67802430979985441@macports.org> References: <043.f37ee7fc32e607c67802430979985441@macports.org> Message-ID: <058.1447db982ab4969c9483c912bb1b2b3d@macports.org> #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt ------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: python310 | ------------------------+-------------------- Description changed by esbugz: Old description: > I've tried to install neovim, which has a dependency on python310, which > for some reason didn't install cleanly and required to be rebuilt (a big > waste of time), although > [https://ports.macports.org/port/python310/details/] says that it should > work fine on Catalina > > Neovim launches fine even without rebuilding the port, but then I get a > constant nag that this ports needs to be rebuilt every time I install > something. Is there a way to avoid that? > > (also, where are the logs that describe why the installation didn't > succeed and the rebuilt is required, couldn't find anyting in > `/opt/local/var/macports/logs`) > > Below are the neovim installation logs > {{{ > > ---> Computing dependencies for neovim > The following dependencies will be installed: > boost176 > bzip2 > expat > gettext > gettext-tools-libs > icu > libedit > libffi > libtermkey > libtextstyle > libuv > libvterm > lua51-lpeg > lua51-mpack > luajit > luv-luajit > lz4 > lzma > msgpack > msgpack-c > msgpack-cpp > ncurses > python310 > python3_select > python_select > sqlite3 > tree-sitter > unibilium > xz > zstd > Continue? [Y/n]: y > ---> Fetching archive for ncurses > ---> Attempting to fetch ncurses-6.3_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/ncurses > ---> Attempting to fetch ncurses-6.3_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/ncurses > ---> Installing ncurses @6.3_0 > ---> Activating ncurses @6.3_0 > ---> Cleaning ncurses > ---> Fetching archive for libtextstyle > ---> Attempting to fetch libtextstyle-0.21_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/libtextstyle > ---> Attempting to fetch > libtextstyle-0.21_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/libtextstyle > ---> Installing libtextstyle @0.21_0 > ---> Activating libtextstyle @0.21_0 > ---> Cleaning libtextstyle > ---> Fetching archive for gettext-tools-libs > ---> Attempting to fetch gettext-tools-libs-0.21_0.darwin_19.x86_64.tbz2 > from https://packages.macports.org/gettext-tools-libs > ---> Attempting to fetch gettext-tools- > libs-0.21_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/gettext-tools-libs > ---> Installing gettext-tools-libs @0.21_0 > ---> Activating gettext-tools-libs @0.21_0 > ---> Cleaning gettext-tools-libs > ---> Fetching archive for gettext > ---> Attempting to fetch gettext-0.21_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/gettext > ---> Attempting to fetch gettext-0.21_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/gettext > ---> Installing gettext @0.21_0 > ---> Activating gettext @0.21_0 > ---> Cleaning gettext > ---> Fetching archive for unibilium > ---> Attempting to fetch unibilium-2.0.0_1.darwin_19.x86_64.tbz2 from > https://packages.macports.org/unibilium > ---> Attempting to fetch unibilium-2.0.0_1.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/unibilium > ---> Installing unibilium @2.0.0_1 > ---> Activating unibilium @2.0.0_1 > ---> Cleaning unibilium > ---> Fetching archive for libtermkey > ---> Attempting to fetch libtermkey-0.22_1.darwin_19.x86_64.tbz2 from > https://packages.macports.org/libtermkey > ---> Attempting to fetch libtermkey-0.22_1.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/libtermkey > ---> Installing libtermkey @0.22_1 > ---> Activating libtermkey @0.22_1 > ---> Cleaning libtermkey > ---> Fetching archive for libuv > ---> Attempting to fetch libuv-1.44.2_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/libuv > ---> Attempting to fetch libuv-1.44.2_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/libuv > ---> Installing libuv @1.44.2_0 > ---> Activating libuv @1.44.2_0 > ---> Cleaning libuv > ---> Fetching archive for libvterm > ---> Attempting to fetch libvterm-0.3_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/libvterm > ---> Attempting to fetch libvterm-0.3_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/libvterm > ---> Installing libvterm @0.3_0 > ---> Activating libvterm @0.3_0 > ---> Cleaning libvterm > ---> Fetching archive for luajit > ---> Attempting to fetch luajit-2.1.0-beta3_6.darwin_19.x86_64.tbz2 from > https://packages.macports.org/luajit > ---> Attempting to fetch > luajit-2.1.0-beta3_6.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/luajit > ---> Installing luajit @2.1.0-beta3_6 > ---> Activating luajit @2.1.0-beta3_6 > ---> Cleaning luajit > ---> Fetching archive for lua51-lpeg > ---> Attempting to fetch lua51-lpeg-1.0.2-1_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/lua51-lpeg > ---> Attempting to fetch > lua51-lpeg-1.0.2-1_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/lua51-lpeg > ---> Installing lua51-lpeg @1.0.2-1_0 > ---> Activating lua51-lpeg @1.0.2-1_0 > ---> Cleaning lua51-lpeg > ---> Fetching archive for lua51-mpack > ---> Attempting to fetch lua51-mpack-1.0.8-0_0.darwin_19.x86_64.tbz2 > from https://packages.macports.org/lua51-mpack > ---> Attempting to fetch > lua51-mpack-1.0.8-0_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/lua51-mpack > ---> Installing lua51-mpack @1.0.8-0_0 > ---> Activating lua51-mpack @1.0.8-0_0 > ---> Cleaning lua51-mpack > ---> Fetching archive for luv-luajit > ---> Attempting to fetch luv-luajit-1.43.0-0_0.darwin_19.x86_64.tbz2 > from https://packages.macports.org/luv-luajit > ---> Attempting to fetch luv- > luajit-1.43.0-0_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/luv-luajit > ---> Installing luv-luajit @1.43.0-0_0 > ---> Activating luv-luajit @1.43.0-0_0 > ---> Cleaning luv-luajit > ---> Fetching archive for msgpack-c > ---> Attempting to fetch msgpack-c-4.0.0_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/msgpack-c > ---> Attempting to fetch msgpack-c-4.0.0_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/msgpack-c > ---> Installing msgpack-c @4.0.0_0 > ---> Activating msgpack-c @4.0.0_0 > ---> Cleaning msgpack-c > ---> Fetching archive for bzip2 > ---> Attempting to fetch bzip2-1.0.8_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/bzip2 > ---> Attempting to fetch bzip2-1.0.8_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/bzip2 > ---> Installing bzip2 @1.0.8_0 > ---> Activating bzip2 @1.0.8_0 > ---> Cleaning bzip2 > ---> Fetching archive for expat > ---> Attempting to fetch expat-2.5.0_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/expat > ---> Attempting to fetch expat-2.5.0_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/expat > ---> Installing expat @2.5.0_0 > ---> Activating expat @2.5.0_0 > ---> Cleaning expat > ---> Fetching archive for icu > ---> Attempting to fetch icu-72.1_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/icu > ---> Attempting to fetch icu-72.1_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/icu > ---> Installing icu @72.1_0 > ---> Activating icu @72.1_0 > ---> Cleaning icu > ---> Fetching archive for lzma > ---> Attempting to fetch lzma-22.01_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/lzma > ---> Attempting to fetch lzma-22.01_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/lzma > ---> Installing lzma @22.01_0 > ---> Activating lzma @22.01_0 > ---> Cleaning lzma > ---> Fetching archive for libedit > ---> Attempting to fetch libedit-20221030-3.1_0.darwin_19.x86_64.tbz2 > from https://packages.macports.org/libedit > ---> Attempting to fetch > libedit-20221030-3.1_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/libedit > ---> Installing libedit @20221030-3.1_0 > ---> Activating libedit @20221030-3.1_0 > ---> Cleaning libedit > ---> Fetching archive for libffi > ---> Attempting to fetch libffi-3.4.4_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/libffi > ---> Attempting to fetch libffi-3.4.4_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/libffi > ---> Installing libffi @3.4.4_0 > ---> Activating libffi @3.4.4_0 > ---> Cleaning libffi > ---> Fetching archive for python3_select > ---> Attempting to fetch python3_select-0.0_3.darwin_19.noarch.tbz2 from > https://packages.macports.org/python3_select > ---> Attempting to fetch > python3_select-0.0_3.darwin_19.noarch.tbz2.rmd160 from > https://packages.macports.org/python3_select > ---> Installing python3_select @0.0_3 > ---> Activating python3_select @0.0_3 > ---> Cleaning python3_select > ---> Fetching archive for python_select > ---> Attempting to fetch python_select-0.3_10.darwin_19.noarch.tbz2 from > https://packages.macports.org/python_select > ---> Attempting to fetch > python_select-0.3_10.darwin_19.noarch.tbz2.rmd160 from > https://packages.macports.org/python_select > ---> Installing python_select @0.3_10 > ---> Activating python_select @0.3_10 > ---> Cleaning python_select > ---> Fetching archive for sqlite3 > ---> Attempting to fetch sqlite3-3.40.0_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/sqlite3 > ---> Attempting to fetch sqlite3-3.40.0_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/sqlite3 > ---> Installing sqlite3 @3.40.0_0 > ---> Activating sqlite3 @3.40.0_0 > ---> Cleaning sqlite3 > ---> Fetching archive for xz > ---> Attempting to fetch xz-5.2.9_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/xz > ---> Attempting to fetch xz-5.2.9_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/xz > ---> Installing xz @5.2.9_0 > ---> Activating xz @5.2.9_0 > ---> Cleaning xz > ---> Fetching archive for python310 > ---> Attempting to fetch > python310-3.10.9_0+lto+optimizations.darwin_19.x86_64.tbz2 from > https://packages.macports.org/python310 > ---> Attempting to fetch > python310-3.10.9_0+lto+optimizations.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/python310 > ---> Installing python310 @3.10.9_0+lto+optimizations > ---> Activating python310 @3.10.9_0+lto+optimizations > ---> Cleaning python310 > ---> Fetching archive for lz4 > ---> Attempting to fetch lz4-1.9.4_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/lz4 > ---> Attempting to fetch lz4-1.9.4_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/lz4 > ---> Installing lz4 @1.9.4_0 > ---> Activating lz4 @1.9.4_0 > ---> Cleaning lz4 > ---> Fetching archive for zstd > ---> Attempting to fetch zstd-1.5.2_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/zstd > ---> Attempting to fetch zstd-1.5.2_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/zstd > ---> Installing zstd @1.5.2_0 > ---> Activating zstd @1.5.2_0 > ---> Cleaning zstd > ---> Fetching archive for boost176 > ---> Attempting to fetch > boost176-1.76.0_6+no_single+no_static+python310.darwin_19.x86_64.tbz2 > from https://packages.macports.org/boost176 > ---> Attempting to fetch > boost176-1.76.0_6+no_single+no_static+python310.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/boost176 > ---> Installing boost176 @1.76.0_6+no_single+no_static+python310 > ---> Activating boost176 @1.76.0_6+no_single+no_static+python310 > ---> Cleaning boost176 > ---> Fetching archive for msgpack-cpp > ---> Attempting to fetch msgpack-cpp-4.1.1_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/msgpack-cpp > ---> Attempting to fetch msgpack- > cpp-4.1.1_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/msgpack-cpp > ---> Installing msgpack-cpp @4.1.1_0 > ---> Activating msgpack-cpp @4.1.1_0 > ---> Cleaning msgpack-cpp > ---> Fetching archive for msgpack > ---> Attempting to fetch msgpack-4_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/msgpack > ---> Attempting to fetch msgpack-4_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/msgpack > ---> Installing msgpack @4_0 > ---> Activating msgpack @4_0 > ---> Cleaning msgpack > ---> Fetching archive for tree-sitter > ---> Attempting to fetch tree-sitter-0.20.7_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/tree-sitter > ---> Attempting to fetch tree- > sitter-0.20.7_0.darwin_19.x86_64.tbz2.rmd160 from > https://packages.macports.org/tree-sitter > ---> Installing tree-sitter @0.20.7_0 > ---> Activating tree-sitter @0.20.7_0 > ---> Cleaning tree-sitter > ---> Fetching archive for neovim > ---> Attempting to fetch neovim-0.8.0_0.darwin_19.x86_64.tbz2 from > https://packages.macports.org/neovim > ---> Attempting to fetch neovim-0.8.0_0.darwin_19.x86_64.tbz2.rmd160 > from https://packages.macports.org/neovim > ---> Installing neovim @0.8.0_0 > ---> Activating neovim @0.8.0_0 > ---> Cleaning neovim > ---> Updating database of binaries > ---> Scanning binaries for linking errors > ---> Found 4 broken files, matching files to ports > ---> Found 1 broken port, determining rebuild order > You can always run 'port rev-upgrade' again to fix errors. > The following ports will be rebuilt: python310 @3.10.9+lto+optimizations > Continue? [Y/n]: n > }}} New description: I've tried to install python310 and for some reason instead of just installing the prebuilt option it asks to waste time rebuilding python, although [https://ports.macports.org/port/python310/details/] says that it should work fine on Catalina (I've tried on 10.15.7) {{{ sudo port install python310 ---> Computing dependencies for python310 ---> Fetching archive for python310 ---> Attempting to fetch python310-3.10.9_0+lto+optimizations.darwin_19.x86_64.tbz2 from https://packages.macports.org/python310 ---> Attempting to fetch python310-3.10.9_0+lto+optimizations.darwin_19.x86_64.tbz2.rmd160 from https://packages.macports.org/python310 ---> Installing python310 @3.10.9_0+lto+optimizations ---> Activating python310 @3.10.9_0+lto+optimizations ---> Cleaning python310 ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 4 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: python310 @3.10.9+lto+optimizations Continue? [Y/n]: }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:15:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 16:15:58 -0000 Subject: [MacPorts] #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) Message-ID: <043.dc96f0184a0798ad208d10790ded6433@macports.org> #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) ---------------------------+-------------------------- Reporter: tjhart | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura arm64 | Port: libgcc-devel ---------------------------+-------------------------- Happens with update/upgrade and also reinstall after uninstall (uninstalling @12-20220828_2+stdlib_flag) {{{ ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from http://mirror.fcix.net/macports/packages/libgcc-devel ---> Fetching distfiles for libgcc-devel ---> Attempting to fetch gcc-darwin- arm64-7bb7023a9c79bd4e035cdf29a6b650069471467c.tar.gz from https://distfiles.macports.org/gcc-devel ---> Verifying checksums for libgcc-devel ---> Extracting libgcc-devel ---> Configuring libgcc-devel ---> Building libgcc-devel Error: Failed to build libgcc-devel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. }}} I manually executed the failed command {{{cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc- devel/work/build" && /usr/bin/make -j8 -w bootstrap-lean }}} and included that log also ({{{manually-executed-command.log.zip}}}). I'm unsure if it's useful, because I don't know if there were environmental differences. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:16:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 16:16:37 -0000 Subject: [MacPorts] #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) In-Reply-To: <043.dc96f0184a0798ad208d10790ded6433@macports.org> References: <043.dc96f0184a0798ad208d10790ded6433@macports.org> Message-ID: <058.2cb71fc8a63e7dbd7b4ce9a9dd48201a@macports.org> #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) ---------------------------+--------------------------- Reporter: tjhart | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Changes (by tjhart): * Attachment "main.log.zip" added. /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:17:26 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 16:17:26 -0000 Subject: [MacPorts] #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) In-Reply-To: <043.dc96f0184a0798ad208d10790ded6433@macports.org> References: <043.dc96f0184a0798ad208d10790ded6433@macports.org> Message-ID: <058.db89d9e77757e2986b55bf566417ed25@macports.org> #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) ---------------------------+--------------------------- Reporter: tjhart | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Changes (by tjhart): * Attachment "manually-executed-command.log.zip" added. cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc- devel/work/build" && /usr/bin/make -j8 -w bootstrap-lean -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:42:09 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 16:42:09 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates Message-ID: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: -------------------------+-------------------- After installing some ports I realized there is this huge duplicate folder containing `.tbz2` archives, which from the Guide: software Contains the compressed archives of installed software. If a port is activated its files are extracted to the ${prefix} folders from the compressed files here. port uninstall + would remove it from here, but then this port can not be used anymore. So this offers no rationale why this duplication exists, nor a practical convenient solution for cleaning it. I'd like to delete all of them, but still use the ports This old SO post [https://apple.stackexchange.com/questions/64074 /macports-software-clean-up-opt-local-var-macports-software] is similar: no rationale, no practical convenient solution Homebrew has a command that allows you to delete the zips and it also runs the command automatically I'd like to have something similar in MacPorts: - ideally a config that would delete all the duplicates right away after a successful install - a command to delete all the archives in the `software` folder manually - maybe a default of running such a command every X days or something? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:54:21 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 16:54:21 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.14c0da3fdfa82dec0153c2664c2eadf9@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Description changed by esbugz: Old description: > After installing some ports I realized there is this huge duplicate > folder containing `.tbz2` archives, which from the Guide: > software > Contains the compressed archives of installed software. If a port is > activated its files are extracted to the ${prefix} folders from the > compressed files here. port uninstall + would > remove it from here, but then this port can not be used anymore. > > So this offers no rationale why this duplication exists, nor a practical > convenient solution for cleaning it. I'd like to delete all of them, but > still use the ports > > This old SO post [https://apple.stackexchange.com/questions/64074 > /macports-software-clean-up-opt-local-var-macports-software] is similar: > no rationale, no practical convenient solution > > Homebrew has a command that allows you to delete the zips and it also > runs the command automatically > > I'd like to have something similar in MacPorts: > - ideally a config that would delete all the duplicates right away > after a successful install > - a command to delete all the archives in the `software` folder > manually > - maybe a default of running such a command every X days or something? New description: After installing some ports I realized there is this huge duplicate folder containing `.tbz2` archives, which from the Guide: software Contains the compressed archives of installed software. If a port is activated its files are extracted to the ${prefix} folders from the compressed files here. port uninstall + would remove it from here, but then this port can not be used anymore. So this offers no rationale why this duplication exists, nor a practical convenient solution for cleaning it. I'd like to delete all of them, but still use the ports This old SO post [https://apple.stackexchange.com/questions/64074 /macports-software-clean-up-opt-local-var-macports-software] is similar: no rationale, no practical convenient solution Homebrew has a command that allows you to delete the zips and it also runs the command automatically I'd like to have something similar in MacPorts: - ideally a config that would delete all the duplicates right away after a successful install - a command to delete all the archives in the `software` folder manually - maybe a default of running such a command every X days or something? P.S. same thing should be done to distfiles -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 16:59:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 16:59:49 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.4e12feab96a9a96a0d8c86e1b74d4030@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): I presume you know about: {{{ sudo port -v reclaim }}} that cleans up your system of expired software you have upgraded, partial builds, and other cruft. It will automatically run every two weeks if you agree to that. But it won't remove all the archives from software you have installed, stored in the software folder. To be honest, I thought this was a requirement of how macports worked -- it is used to reinstall software you already have installed, as lots of folks have had to build those and wouldn't be happy to go through the whole rebuild process. It would be easy enough to test that. If MacPorts can work properly with the contents of that folder moved or deleted, and it will just rebuild or redownload what is needed, then emptying that software folder might something that could be added to the port reclaim mechanism. But I am not certain MacPorts will work right if that folder is deleted -- I can see how it might malfunction -- so it would need some testing to see. Homebrew in some ways has it much easier, a consequence of restricting your options and flexibility - it does not support you building your own software, for example - so it can make some assumptions that MacPorts cannot make. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:04:52 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:04:52 -0000 Subject: [MacPorts] #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt In-Reply-To: <043.f37ee7fc32e607c67802430979985441@macports.org> References: <043.f37ee7fc32e607c67802430979985441@macports.org> Message-ID: <058.fa6600935be525dc64cb0f37f88c2656@macports.org> #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt ------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: python310 | ------------------------+-------------------- Comment (by kencu): if you run this: {{{ sudo port -v rev-upgrade }}} the added "-v" flag will tell you what port is seeing, and why python310 is / is thought to be broken. This information can be helpful most times to understand what is exactly wrong. Often it might be caused by forcing the uninstall of a dependent port, for example, but there are other reasons it could occur. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:06:23 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:06:23 -0000 Subject: [MacPorts] #66525: helix runtime should exclude SOURCES for grammars and debugging symbols to save 90+% Message-ID: <043.948d21a8b146efe0b608ead394d6cd91@macports.org> #66525: helix runtime should exclude SOURCES for grammars and debugging symbols to save 90+% -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: helix -------------------------+-------------------- The compiled grammar are enough and are already large enough since they include all the syntaxes, no need to also include debugging symbols (`*.so.dSYM`) and the `sources` (the sources are actually 90% of the 170m folder size) Maybe move all of that in a `+dev` version if someone ever needs it? Thanks -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:07:45 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:07:45 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.f1a15326f0d1ecd8622471872698b472@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): By the way, almost everything I have seen on stack overflow about MacPorts is ancient, out-of-date, and mostly useless information that is more misleading than helpful. I would take anything you see there with a big lump (not grain) of NaCl. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:41:22 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:41:22 -0000 Subject: [MacPorts] #66378: llvm-13 +universal build fails due to architecture of /opt/local/lib/libstdc++.6.dylib In-Reply-To: <049.6a42cabbf1eefa4a22af86d4c699c3e0@macports.org> References: <049.6a42cabbf1eefa4a22af86d4c699c3e0@macports.org> Message-ID: <064.dbae5b48ad72c5bccfe07cd7fdbb10e8@macports.org> #66378: llvm-13 +universal build fails due to architecture of /opt/local/lib/libstdc++.6.dylib ---------------------------+-------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: mountainlion Port: llvm-13 | ---------------------------+-------------------------- Comment (by kencu): Replying to [comment:6 barracuda156]: > Not today though. It is another multi-hour endeavor. actually, 10 seconds is all it takes, no multi-hour endeavours needed: {{{ sudo port -v deactivate libgcc12 }}} see if any toolchain parts are listed as going to be broken by this. Then after you see that, say "N" and everything stays like it was. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:42:18 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:42:18 -0000 Subject: [MacPorts] #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt In-Reply-To: <043.f37ee7fc32e607c67802430979985441@macports.org> References: <043.f37ee7fc32e607c67802430979985441@macports.org> Message-ID: <058.56da7ee5a40a00233cbce869e4cb52cc@macports.org> #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt ------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: python310 | ------------------------+-------------------- Comment (by esbugz): Nice, thanks! Fixed via `sudo port install openssl3` {{{ Could not open /opt/local/libexec/openssl3/lib/libcrypto.3.dylib: Error opening or reading file (referenced from /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /lib-dynload/_hashlib.cpython-310-darwin.so) Could not open /opt/local/libexec/openssl3/lib/libssl.3.dylib: Error opening or reading file (referenced from /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /lib-dynload/_hashlib.cpython-310-darwin.so) ---> Found 4 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: python310 @3.10.9+lto+optimizations }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:45:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:45:48 -0000 Subject: [MacPorts] #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt In-Reply-To: <043.f37ee7fc32e607c67802430979985441@macports.org> References: <043.f37ee7fc32e607c67802430979985441@macports.org> Message-ID: <058.705a7cdd2f9a0424f834243cfd7c8d98@macports.org> #66522: python310 @3.10.9+lto+optimizations requires to be rebuilt -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: Port: python310 | -------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => worksforme -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 17:48:25 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 17:48:25 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.8386dda6e4e192473e8feb1ff71b93ed@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): What's the up-to-date source? The official Guide [https://guide.macports.org/#project.tickets] provides me with this very useful information on how to pick one of the many outdated archive formats {{{ Binary archive files are placed in ${prefix}/var/macports/software/. The archive file type is set in macports.conf using the portarchivetype key. The default format is tbz2; other options are: tar, tbz, tbz2, tgz, tlz, txz, xar, zip, cpgz, and cpio. }}} but not how to clean the backups for the mostly unneeded functionality of multiple port versions (which I think is anyway better solved via symlinks that would link to either version1 or version2 of the port instead of having each port have a mandatory backup) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:03:06 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 18:03:06 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.d2a9d8c6d64e486f1b8869a731e026db@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:2 kencu]: > I presume you know about: > {{{ > sudo port -v reclaim > }}} Yes, though I'd prefer this to also autorun on a schedule rather than having to run it myself. Basically, I don't see much value in these backups, I almost never need them and when I do, a redownload is much easier since it's ore likely the package has been updated by then anyway, so the backup is stale > But it won't remove all the archives from software you have installed, stored in the software folder. Yeah, that's the biggest one ? I need to clean the versions that I actually use, not just the unused ones > To be honest, I thought this was a requirement of how macports worked -- it is used to reinstall software you already have installed, as lots of folks have had to build those and wouldn't be happy to go through the whole rebuild process. Sure, but now the main use case is just download prebuilt stuff, and even for the build artifacts that should be optional as in my experience this is also very rarely needed to justify having it by default (but if someone wants to keep them, that's also fine) > It would be easy enough to test that. If MacPorts can work properly with the contents of that folder moved or deleted, and it will just rebuild or redownload what is needed, then emptying that software folder might something that could be added to the port reclaim mechanism. I've already deleted the folder so already testing it, seems fine :) And the SO implied it's fine, so it should be fine ;) (but you're right, they are pretty old, so shouldn't rely on it much) > But I am not certain MacPorts will work right if that folder is deleted -- I can see how it might malfunction -- so it would need some testing to see. Why would it? Anyway, the proper way would be to fix the cause of the malfunctioning, the whole design of mandatory backup isn't great > Homebrew in some ways has it much easier, a consequence of restricting your options and flexibility - it does not support you building your own software, for example But it does, I've built a few formulas myself from the git HEAD versions when I needed a quick fix before it lands in the main formula. Yes, Homebrew removed the many options previously available in their main repository (very bad decision), but not the ability to build > - so it can make some assumptions that MacPorts cannot make. Which ones? Even when I was building the latest HEAD versions, I never needed a backup since I'd just never uninstall it to require a full rebuild (and hence needing a backup). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:33:28 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 18:33:28 -0000 Subject: [MacPorts] #66526: Port space command ignores hardlinks in it's total size calculations Message-ID: <043.2b415ec8080221b4f81910a8e9d1ecd2@macports.org> #66526: Port space command ignores hardlinks in it's total size calculations --------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: --------------------+-------------------- I'm using `port space --units MB installed | sort -n # MacPorts: list ports by size` I get `523.30 MB git @2.39.0_0` This is incorrect since git has ~140 files 3.2m each (or physical 1.6m, not sure why there is such a big discrepancy here for a single file) that are actually hardlinks to a single file The `port space` command should calculate the size of a file as `file size/count of hardlinks` and then sum this up to get the size of a port instead of summing up `file size`'s as is -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:42:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 18:42:49 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.0a0ad3a1fdd9425181f201141398ab54@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): The official policy of homebrew is that they will not support users building their own software. This has been stated hundreds of times when people post up issues. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 18:46:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 18:46:54 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.d70cf553208c85c495632422092bb343@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): To really test what happens when you delete the "software" folder, you'd need to do some digging... like try to deactivate and reactivate a port, and try to rebuild something with dependencies, especially toolchain components, and try it in a non-default prefix where the prebuilt binaries can't be used, and try to rebuild something where the default stdlib has been changed to "libstdc++" from "libc++" for example. These are all the kinds of assumptions that homebrew never has to make, because they don't really support any of this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:01:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 19:01:58 -0000 Subject: [MacPorts] #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. In-Reply-To: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> References: <043.c28480d69d4e495597f7b5b2374cb135@macports.org> Message-ID: <058.c6a4190ec1ce6531a3e0a04da8c3fc88@macports.org> #66510: Uninstall warning: add portname to warning prompt. Makes it more clear which port is triggering the warning if multiple ports are specified on the uninstall line. ---------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------+-------------------- Comment (by kencu): I agree, I don't know why the "cleaning" message is there exactly, and it is somewhat confusing as it it not clear what it is cleaning. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:12:02 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 19:12:02 -0000 Subject: [MacPorts] #66238: iTerm2 quit unexpectedly In-Reply-To: <041.e646815e7baa4b39290e1b1215470036@macports.org> References: <041.e646815e7baa4b39290e1b1215470036@macports.org> Message-ID: <056.1406945672e912b4f84ac1db39db99c1@macports.org> #66238: iTerm2 quit unexpectedly ---------------------+---------------------- Reporter: jmgc | Owner: markemer Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: iTerm2 | ---------------------+---------------------- Comment (by esafak): [https://gitlab.com/gnachman/iterm2/-/issues/10728 As I reported on gitlab], the `TeamIdentifier` is missing from `/Applications/MacPorts/iTerm2.app/Contents/Frameworks/BetterFontPicker.framework/Versions/A/BetterFontPicker`, and the iterm2 executable from iterm2.com works, so this is probably a problem at macports' end. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 19:18:46 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 19:18:46 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.0516acfec390e9b4e4601fc045c54185@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): You're new here?you filed your first MacPorts ticket (and joined GitHub) 3 days ago. MacPorts has existed for 20 years and so there is a long history to explain why MacPorts works the way it does, in many cases with good reason, and for many of the suggestions you've casually made in this and other tickets, there would be substantial effort to make the changes you suggest, with significant consequences. I recommend instead of filing more tickets for further substantial changes, you write to the macports-dev mailing list to discuss your suggestions. Perhaps there you will get a bigger audience that can explain, for each of your suggestions, why things are the way they are. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 20:35:39 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 20:35:39 -0000 Subject: [MacPorts] #66288: Discussion re pre-build ports for PPC In-Reply-To: <049.ee3d1614ff9978b2c1df6e1ff447e1d2@macports.org> References: <049.ee3d1614ff9978b2c1df6e1ff447e1d2@macports.org> Message-ID: <064.2fe032482de8a5c2ae97b151c45d22cb@macports.org> #66288: Discussion re pre-build ports for PPC ----------------------------+------------------------------------------- Reporter: barracuda156 | Owner: kencu Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: buildbot/mpbb | Version: 2.8.0 Resolution: | Keywords: powerpc, leopard, snowleopard Port: | ----------------------------+------------------------------------------- Comment (by barracuda156): Replying to [comment:1 ryandesign]: > Replying to [ticket:66288 barracuda156]: > > ''If you or someone can allocate one PowerMac to this end, it would be a superior solution to what I am suggesting''. > > I have recently acquired another broken Power Mac G5. I should be able to swap parts with the other one I have to get a working machine that can then build for Leopard PPC. Please update us if any progress happens in this regard. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 22:11:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 22:11:37 -0000 Subject: [MacPorts] #66527: ffmpeg @4.4.2_3 +gpl3 +nonfree +x11 does not build on macOS Monterey, Version 12.6, because of an "unknown load command 5"? Message-ID: <046.54c59ba7da0bfaa8901ae2b2c16acaab@macports.org> #66527: ffmpeg @4.4.2_3 +gpl3 +nonfree +x11 does not build on macOS Monterey, Version 12.6, because of an "unknown load command 5"? ----------------------------+-------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: monterey intel | Port: ffmpeg ----------------------------+-------------------- `ffmpeg @4.4.2_3+gpl2+nonfree+x11 (active) requested_variants='+gpl2+nonfree+x11' platform='darwin 21' archs='x86_64'`built in summer: `date='2022-08-27T22:23:28+0200'`, but since a few minutes it is winter? Quite early first failures happen: `/usr/bin/clang` (or `/Library/Developer/CommandLineTools/usr/bin/clang`) and `ar` (or `/opt/local/libexec/*/ar`) crash and generate reports for Apple. Build ends here: {{{ ---> Staging ffmpeg into destroot ... Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-4.4.2" && /opt/local/bin/gmake -w install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-4.4.2" && /opt/local/bin/gmake -w install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot gmake: Entering directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-4.4.2' mkdir -p "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib" install -m 644 libavdevice/libavdevice.a "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib" ranlib "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib/libavdevice.a" mkdir -p "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib" install -m 755 libavdevice/libavdevice.dylib "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib/libavdevice.58.13.100.dylib" strip -x "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib/libavdevice.58.13.100.dylib" strip: object: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot/opt/local/lib/libavdevice.58.13.100.dylib malformed object (unknown load command 5) gmake: *** [ffbuild/library.mak:104: install-libavdevice-shared] Error 1 gmake: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-4.4.2' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-4.4.2" && /opt/local/bin/gmake -w install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/destroot Exit code: 2 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 22:12:30 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 22:12:30 -0000 Subject: [MacPorts] #66527: ffmpeg @4.4.2_3 +gpl3 +nonfree +x11 does not build on macOS Monterey, Version 12.6, because of an "unknown load command 5"? In-Reply-To: <046.54c59ba7da0bfaa8901ae2b2c16acaab@macports.org> References: <046.54c59ba7da0bfaa8901ae2b2c16acaab@macports.org> Message-ID: <061.bbcaa58aaac2ece8d7bca8b721be6406@macports.org> #66527: ffmpeg @4.4.2_3 +gpl3 +nonfree +x11 does not build on macOS Monterey, Version 12.6, because of an "unknown load command 5"? ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: monterey intel Port: ffmpeg | ------------------------+---------------------------- Changes (by ballapete): * Attachment "main.log" added. Main.log from x86_64 macOS Monterey, Version 12.6 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 22:30:05 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 22:30:05 -0000 Subject: [MacPorts] #66527: ffmpeg @4.4.2_3 +gpl3 +nonfree +x11 does not build on macOS Monterey, Version 12.6, because of an "unknown load command 5"? In-Reply-To: <046.54c59ba7da0bfaa8901ae2b2c16acaab@macports.org> References: <046.54c59ba7da0bfaa8901ae2b2c16acaab@macports.org> Message-ID: <061.6a1bf7d5cd0898061f4a9a94a71ab753@macports.org> #66527: ffmpeg @4.4.2_3 +gpl3 +nonfree +x11 does not build on macOS Monterey, Version 12.6, because of an "unknown load command 5"? ------------------------+---------------------------- Reporter: ballapete | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: monterey intel Port: ffmpeg | ------------------------+---------------------------- Comment (by ballapete): It builds when I leave `variant +gpl3` away. When I leave `variant +nonfree` away, then `ar` crashes again during the `configure phase`. The build does not finish, it fails as reported before. So `+gpl3` could be the culprit? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 21 22:47:03 2022 From: noreply at macports.org (MacPorts) Date: Wed, 21 Dec 2022 22:47:03 -0000 Subject: [MacPorts] #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat In-Reply-To: <049.e272b09c50fa936576291104f672d5f6@macports.org> References: <049.e272b09c50fa936576291104f672d5f6@macports.org> Message-ID: <064.fc385403a8c080bb7679cbfa7f01c89b@macports.org> #65177: python27-bootstrap fails to build: ImportError: No module named pyexpat ---------------------------------+-------------------------------- Reporter: barracuda156 | Owner: jmroot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: tiger, snowleopard Port: python27-bootstrap | ---------------------------------+-------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"7da4ca386628281ce33938b322ba3f2d61f35fc0/macports-ports" 7da4ca386628281ce33938b322ba3f2d61f35fc0/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7da4ca386628281ce33938b322ba3f2d61f35fc0" python27-bootstrap: fix missing expat/libffi on Tiger Can't use system expat and libffi as they don't exist on Tiger. Closes: https://trac.macports.org/ticket/65177 Add notes about Tiger modules--because it builds from system roots, the python27-bootstrap port cannot build as many modules as the full python27 port. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 00:02:17 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 00:02:17 -0000 Subject: [MacPorts] #66528: py311-pyqt5 missing dependency bus-python311 Message-ID: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> #66528: py311-pyqt5 missing dependency bus-python311 --------------------+-------------------- Reporter: Fut1l3 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------+-------------------- Following upgrade to python 311 attempted to install py311-pyqt5. py311-pyqt5 fails with dbus-python311 not found. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 00:03:00 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 00:03:00 -0000 Subject: [MacPorts] #66528: py311-pyqt5 missing dependency dbus-python311 (was: py311-pyqt5 missing dependency bus-python311) In-Reply-To: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> References: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> Message-ID: <058.a99de3b43ad4e72699905a5c9bd277bc@macports.org> #66528: py311-pyqt5 missing dependency dbus-python311 ---------------------+-------------------- Reporter: Fut1l3 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ---------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 02:20:39 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 02:20:39 -0000 Subject: [MacPorts] #66529: postgresql15 +universal: darwin/x86_64 cross-compile to arm64 results in broken build Message-ID: <048.ae45039ca5c8c34edcb7680f58cb76f9@macports.org> #66529: postgresql15 +universal: darwin/x86_64 cross-compile to arm64 results in broken build -------------------------+-------------------- Reporter: FabianPonce | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -------------------------+-------------------- I ran two different installations of postgresql15, one on my M1 MacBook Pro, and another on an EC2 instance running x86_64. Both machines are running the latest release of Ventura. In both builds, I request a universal build, so the intended output should be a fat binary containing both x86_64 and arm64 architecture executables. On my M1, this succeeds without issue. On my x86_64 EC2 instance, the build fails with the following error: {{{ "./data/tzdata.zi", line 4194: input line of unknown type "./data/tzdata.zi", line 4195: input line of unknown type "./data/tzdata.zi", line 4196: input line of unknown type gnumake[2]: *** [install] Error 1 gnumake[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql15/postgresql15/work/postgresql-15.1-arm64/src/timezone' gnumake[1]: *** [install-timezone-recurse] Error 2 gnumake[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql15/postgresql15/work/postgresql-15.1-arm64/src' gnumake: *** [install-world-src-recurse] Error 2 gnumake: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql15/postgresql15/work/postgresql-15.1-arm64' }}} It took me a fair bit to figure out what was happening. The native Mac `zic` compiler does not support the format that postgresql ships with it's src. This is the _same_ compiler on both M1 and Intel machines, so why does one succeed and the other doesn't? Postgres attempts to build zic.c as part of its build process and output a binary file. It then attempts to _use_ that binary to generate the compiled tzdata. In the case of the M1 machine, this succeeds because of Rosetta 2. In the case of the Intel machine, this fails and the system falls back to the /usr/sbin/zic which was shipped with macOS, and the build process fails. I hacked my build together by doing: {{{ cp /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql15/postgresql15/work/postgresql-15.1-x86_64/src/timezone/zic /opt/local/bin/ export ZIC=/opt/local/bin/zic }}} I then re-ran the normal port install postgresql15 +universal, and this succeeded. I believe this issue affects all recent versions of the postgresql port as well, though I only attempted postgresql14. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 09:08:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 09:08:09 -0000 Subject: [MacPorts] #66513: podman @4.3.1: env: python3: No such file or directory In-Reply-To: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> References: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> Message-ID: <062.bcecd76b5c7261ca89d362aae26f2fb2@macports.org> #66513: podman @4.3.1: env: python3: No such file or directory -------------------------+---------------------- Reporter: ryandesign | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: podman | -------------------------+---------------------- Comment (by Vadym-Valdis Yudaiev ): In [changeset:"21cbcb16539b8281147d11377f3ab758ef14f600/macports-ports" 21cbcb16539b8281147d11377f3ab758ef14f600/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="21cbcb16539b8281147d11377f3ab758ef14f600" podman: fix: python3: No such file or directory See https://trac.macports.org/ticket/66513 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 10:36:33 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 10:36:33 -0000 Subject: [MacPorts] #66528: py311-pyqt5 missing dependency dbus-python311 In-Reply-To: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> References: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> Message-ID: <058.1c17c8de3f82d07fba26d583a5eb536d@macports.org> #66528: py311-pyqt5 missing dependency dbus-python311 -----------------------------------+------------------------ Reporter: Fut1l3 | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyqt5 dbus-python | -----------------------------------+------------------------ Changes (by jmroot): * status: new => assigned * owner: (none) => reneeotten * port: => py-pyqt5 dbus-python -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 10:37:53 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 10:37:53 -0000 Subject: [MacPorts] #66529: postgresql15 +universal: darwin/x86_64 cross-compile to arm64 results in broken build In-Reply-To: <048.ae45039ca5c8c34edcb7680f58cb76f9@macports.org> References: <048.ae45039ca5c8c34edcb7680f58cb76f9@macports.org> Message-ID: <063.c7d9a2613e68865b750588298e448419@macports.org> #66529: postgresql15 +universal: darwin/x86_64 cross-compile to arm64 results in broken build ---------------------------+-------------------- Reporter: FabianPonce | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: postgresql15 | ---------------------------+-------------------- Changes (by jmroot): * port: => postgresql15 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 11:37:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 11:37:42 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.8d0c8c8eaf2e75e7152792bc62ec676c@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:6 kencu]: > The official policy of homebrew is that they will not support users building their own software. This has been stated hundreds of times when people post up issues. Regardless of the "official policy", Homebrew does allow building from source, so this in itself is not a reason for the difference in behavior Replying to [comment:7 kencu]: > To really test what happens when you delete the "software" folder, you'd need to do some digging... like try to deactivate and reactivate a port Currently deactivating deletes the port, though the guide is a bit confusing as to what's supposed to happen > it deactivates it, i.e., it stashes the files belonging to the older version away in a tarball. This suggests that the files are not deleted, but move to an archive > Deactivating a port only removes the files from their activated locations (usually under ${prefix})?the deactivated port's image is not disturbed. This says they're removed So you could fix this by zipping the port on deactivation and putting it back to `/software` if it's empty, or you could skip autodelete to flagged ports (or automatically to ports with multiple versions), but the cleaner solution would be similar to what Homebrew does, so activating/deactivating would mean symlinking to the port's install folder rather than moving the files while leaving a backed up duplicate version behind > try it in a non-default prefix where the prebuilt packages can't be used > and try to rebuild something where the default stdlib has been changed to "libstdc++" from "libc++" for example. That defeats the core benefit of MacPorts, but then it's also fine just disabling autoremove functionality in such cases and let the user opt in > These are all the kinds of assumptions that homebrew never has to make, because they don't really support any of this. Sure, they strongly advise against it and will close your issues, but them some people still installed to their home folder, for example, with the same huge downside - you'd have to rebuild everything from source instead of using the prebuilt packages from their cache. But even then, none of this assumptions affect the most convenient use case of installing with the default prefix and relying on prebuilt packages, so none of them block removing the waste -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:23:11 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 12:23:11 -0000 Subject: =?utf-8?q?=5BMacPorts=5D_=2366530=3A_py310-spyder_=405=2E4=2E0?= =?utf-8?q?=5F1_+pil_=E2=80=93_Spyder_won=27t_start_on_M1_pro_mac?= =?utf-8?q?hine_=28Potentially_an_issue_with_the_version_of_port_?= =?utf-8?q?py310-codestyle_=402=2E9=2E1=5F0_being_=22too_old=22_r?= =?utf-8?q?ather_than_spyder=29?= Message-ID: <044.55db2b732ff6862bccb8754439625e94@macports.org> #66530: py310-spyder @5.4.0_1 +pil ? Spyder won't start on M1 pro machine (Potentially an issue with the version of port py310-codestyle @2.9.1_0 being "too old" rather than spyder) ---------------------+----------------------- Reporter: Gandoon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-spyder ---------------------+----------------------- Spyder won't start on a MacBook Pro. The latest version of all dependencies, built from source, are available. There seems to be a complaint about `pycodestyle`, available as port `py310-codestyle @2.9.1_0`. If I understand the complaint correctly Spyder seems to want an even later version of the package. Weirdly enough, on another Intel machine there are no problems whatsoever to start Spyder, and that machine was updated within the last week, so something seems off. I realise this may be an issue with `py-codestyle` rather than `py- spyder`, but as it manifests in relation to the latter, it gets the ticket. Feel fre to re-route it if relevant. {{{ > spyder Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 581, in _build_master ws.require(__requires__) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 909, in require needed = self.resolve(parse_requirements(requirements)) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 800, in resolve raise VersionConflict(dist, req).with_context(dependent_req) pkg_resources.ContextualVersionConflict: (pycodestyle 2.9.1 (/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages), Requirement.parse('pycodestyle>=2.10.0'), {'autopep8'}) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/local/bin/spyder", line 33, in sys.exit(load_entry_point('spyder==5.4.0', 'gui_scripts', 'spyder')()) File "/opt/local/bin/spyder", line 25, in importlib_load_entry_point return next(matches).load() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/metadata/__init__.py", line 171, in load module = import_module(match.group('module')) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 1006, in _find_and_load_unlocked File "", line 688, in _load_unlocked File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/spyder/app/start.py", line 58, in from spyder.utils.external import lockfile File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/spyder/utils/external/lockfile.py", line 31, in from spyder.utils.programs import is_spyder_process File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/spyder/utils/programs.py", line 28, in import pkg_resources File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 3260, in def _initialize_master_working_set(): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 3234, in _call_aside f(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 3272, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 583, in _build_master return cls._build_from_requirements(__requires__) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 596, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pkg_resources/__init__.py", line 800, in resolve raise VersionConflict(dist, req).with_context(dependent_req) pkg_resources.ContextualVersionConflict: (pycodestyle 2.9.1 (/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages), Requirement.parse('pycodestyle>=2.10.0'), {'autopep8'}) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:45:25 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 12:45:25 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.fd378f5755b37ef3784d89b86c12fd0d@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: worksforme | Keywords: Port: | --------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: ok, your understanding of what happens is pretty incomplete. I?m going to close this ticket as this is not the forum for a multiple- point running debate, and you can take this to macports-dev as the admin suggested. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:48:18 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 12:48:18 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.ac2b39ab2a7c11cbb425206256f3bc09@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: worksforme | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:8 ryandesign]: > MacPorts has existed for 20 years and so there is a long history to explain why MacPorts works the way it does, in many cases with good reason And in many cases without a good reason; or with reasons that were only good 20 years ago. So, how is this of any help in discussing specific issues? > instead of filing more tickets for further substantial changes, you write to the macports-dev mailing list to discuss your suggestions. But the mailing is a much worse substitute even to this outdated forum since: - you have a per-issue-page anyone can track (once they find the tiny cc button ;)) - you see the whole discussion thread instead of having to click "next/previous" message to follow - you have access to the WikiFormatting markup > Perhaps there you will get a bigger audience that can explain, for each of your suggestions, why things are the way they are. And how would that help solve the issue? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:58:16 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 12:58:16 -0000 Subject: [MacPorts] #66524: Autoremove macports/software not to waste space with archived duplicates In-Reply-To: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> References: <043.25383935af31cf83bd36ae66c05e8ca6@macports.org> Message-ID: <058.9c72f2d7c429f54aa7417e6540d366e0@macports.org> #66524: Autoremove macports/software not to waste space with archived duplicates --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: worksforme | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:10 kencu]: > ok, your understanding of what happens is pretty incomplete. Ha-ha. > I?m going to close this ticket as this is not the forum for a multiple- point running debate Then don't debate? How is it relevant to whether the feature request is valid? > , and you can take this to macports-dev as the admin suggested. No, thanks, I've wasted enough time as it is, if you're so unresponsive to such obvious issues, why would I engage in an even less convenient avenue that a dedicated forum? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 12:58:56 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 12:58:56 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.c704fddbb3343eb29247600f8ca74f28@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by kencu): you?re arguing hard against a perfectly-reasonable alias, yet just above you suggest a symlink as a solution? the problem with forum posts is I can never tell if I?m debating a 10 year old? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 13:07:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 13:07:27 -0000 Subject: [MacPorts] #66507: Allow customizing applications_dir on a per-port basis In-Reply-To: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> References: <043.2d314294218ff841d4022e10a4f3ecca@macports.org> Message-ID: <058.c870ba057008e0aff835add39c41ad4d@macports.org> #66507: Allow customizing applications_dir on a per-port basis --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:7 kencu]: > you?re arguing hard against a perfectly-reasonable alias, yet just above you suggest a symlink as a solution? a) it's not perfectly reasonable b) the symlinks is a proposed solution to a completely different issue > the problem with forum posts is I can never tell if I?m debating a 10 year old? No, the problem is with your inability to understand and debate on the merits and resorting to these childish insults -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 14:41:46 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 14:41:46 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366530=3A_py310-spyder_=405=2E4?= =?utf-8?q?=2E0=5F1_+pil_=E2=80=93_Spyder_won=27t_start_on_M1_pro?= =?utf-8?q?_machine_=28Potentially_an_issue_with_the_version_of_p?= =?utf-8?q?ort_py310-codestyle_=402=2E9=2E1=5F0_being_=22too_old?= =?utf-8?q?=22_rather_than_spyder=29?= In-Reply-To: <044.55db2b732ff6862bccb8754439625e94@macports.org> References: <044.55db2b732ff6862bccb8754439625e94@macports.org> Message-ID: <059.0926b22d1c5a56a7b3cc60c55214adfc@macports.org> #66530: py310-spyder @5.4.0_1 +pil ? Spyder won't start on M1 pro machine (Potentially an issue with the version of port py310-codestyle @2.9.1_0 being "too old" rather than spyder) ------------------------+-------------------- Reporter: Gandoon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-spyder | ------------------------+-------------------- Comment (by Gandoon): In case anyone wonders: No, the vanilla flavour spyder without `+pil` does not work either. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 14:48:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 14:48:09 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366530=3A_py310-spyder_=405=2E4?= =?utf-8?q?=2E0=5F1_+pil_=E2=80=93_Spyder_won=27t_start_on_M1_pro?= =?utf-8?q?_machine_=28Potentially_an_issue_with_the_version_of_p?= =?utf-8?q?ort_py310-codestyle_=402=2E9=2E1=5F0_being_=22too_old?= =?utf-8?q?=22_rather_than_spyder=29?= In-Reply-To: <044.55db2b732ff6862bccb8754439625e94@macports.org> References: <044.55db2b732ff6862bccb8754439625e94@macports.org> Message-ID: <059.8fe252bdbdb6f01a91e87337c4fcd7c5@macports.org> #66530: py310-spyder @5.4.0_1 +pil ? Spyder won't start on M1 pro machine (Potentially an issue with the version of port py310-codestyle @2.9.1_0 being "too old" rather than spyder) ------------------------+------------------------ Reporter: Gandoon | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-spyder | ------------------------+------------------------ Changes (by mf2k): * status: new => assigned * owner: (none) => reneeotten -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 14:53:25 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 14:53:25 -0000 Subject: [MacPorts] #66154: py-pyobjc: Update to 8.6 In-Reply-To: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> References: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> Message-ID: <056.4089c68246795e36f2ce804396831ad9@macports.org> #66154: py-pyobjc: Update to 8.6 ------------------------+---------------------- Reporter: mf2k | Owner: danchr Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyobjc | ------------------------+---------------------- Description changed by mf2k: Old description: > Can py-pyobjc be at least updated to version 8.6? See #66052. It appears > that > [https://pyobjc.readthedocs.io/en/latest/changelog.html#version-9-0a1 > version 9] may be required for Ventura. Since that is only at a1, maybe a > -devel sub-port can be added for it? New description: Can py-pyobjc be at least updated to version 8.6? See #66052. It appears that [https://pyobjc.readthedocs.io/en/latest/changelog.html#version-9-0a1 version 9] may be required for Ventura. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 17:00:21 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 17:00:21 -0000 Subject: [MacPorts] #65109: py-build, py-bootstrap-modules: breaks use of trace-mode In-Reply-To: <047.279369fbd2573110778929557d20408b@macports.org> References: <047.279369fbd2573110778929557d20408b@macports.org> Message-ID: <062.cca8c55797184f936980253b8ad5e47c@macports.org> #65109: py-build,py-bootstrap-modules: breaks use of trace-mode --------------------------------------------+---------------------- Reporter: reneeotten | Owner: jmroot Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: py-build py-bootstrap-modules | --------------------------------------------+---------------------- Comment (by danchr): In [changeset:"e2b5f57f25f0f2934ceb78b4558411ca200c9d87/macports-ports" e2b5f57f25f0f2934ceb78b4558411ca200c9d87/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e2b5f57f25f0f2934ceb78b4558411ca200c9d87" py-build: update to 0.9.0 The upgrade addresses the issues with Colorama & trace mode. The issues with `importlib_metadata` seem to persist, but only for certain older versions of Python as far as I can tell. To work around this, we simply add it as (sort of) redundant dependency. See https://trac.macports.org/ticket/65109 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 17:03:37 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 17:03:37 -0000 Subject: [MacPorts] #66154: py-pyobjc: Update to 8.6 In-Reply-To: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> References: <041.f98e587ad3e7beabef4a6e8b9b43d4ad@macports.org> Message-ID: <056.9f24451618a256a66589c92547def8d5@macports.org> #66154: py-pyobjc: Update to 8.6 ------------------------+-------------------- Reporter: mf2k | Owner: danchr Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-pyobjc | ------------------------+-------------------- Changes (by danchr): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"89756876d36a5e58e4e41b87e3aab1176813c44c/macports-ports" 89756876d36a5e58e4e41b87e3aab1176813c44c/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="89756876d36a5e58e4e41b87e3aab1176813c44c" py-pyobjc: update to 9.0 Generally speaking, upgrading pyobjc involves: 1. Applying the current patches to the corresponding version. 2. Rebasing the commits onto the desired version, resolving any conflicts. 3. Remove any spurious Werror introductions using a command such as: find . -name pyobjc_setup.py \ | xargs sed -i '' '/if "-Werror" not in cflags:/{N; N; d; }' 4. Amend the final commit to reflect any new changes picked up. 5. Export the resulting commits as patches. The reason for this rather involved process is the build system, which isn't quite normal Python, and which introduces -Werror all over the place, frequently breaking older systems. Closes: https://trac.macports.org/ticket/66154 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 17:13:54 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 17:13:54 -0000 Subject: [MacPorts] #66531: I am not beeing successful on installing MARS through macports Message-ID: <050.9d2f7351757ad59c908903a2cc50634a@macports.org> #66531: I am not beeing successful on installing MARS through macports ---------------------------+-------------------- Reporter: PhilippeMenge | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: mars | Port: mars ---------------------------+-------------------- "Error: Failed to build mars: command execution failed" this error is being reported at the terminal. how can I install it? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 18:17:33 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 18:17:33 -0000 Subject: [MacPorts] #66532: moltenvk should be labeled as a universal variant Message-ID: <050.478450c82a0eb5cbbc05f9bee8e79303@macports.org> #66532: moltenvk should be labeled as a universal variant ------------------------------------------+-------------------------------- Reporter: MichaelGDev48 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: vk, vulkan, loader, moltenvk | Port: moltenvk, vulkan- | loader ------------------------------------------+-------------------------------- When compiling and installing moltenvk it provides a universal variant but isn't labeled as such which causes issues for packages you try to build with universal label , that depend on it like vulkan-loader Error: Cannot install vulkan-loader for the archs 'arm64 x86_64' because Error: its dependency MoltenVK is only installed for the arch 'arm64' Error: and does not have a universal variant. file /opt/local/lib/libMoltenVK.dylib /opt/local/lib/libMoltenVK.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64] /opt/local/lib/libMoltenVK.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/libMoltenVK.dylib (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 21:02:05 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 21:02:05 -0000 Subject: [MacPorts] #66177: qt5-qtwebkit @5.9.2_4 fails to build In-Reply-To: <044.0893fa41b204973d4be592538766859d@macports.org> References: <044.0893fa41b204973d4be592538766859d@macports.org> Message-ID: <059.0ea2becfe5ad65125049ff3f0b02fbb6@macports.org> #66177: qt5-qtwebkit @5.9.2_4 fails to build ---------------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by ostefano): Is there any workaround for this? Unfortunately qt5-qtwebkit is a dependency for wkhtmltopdf :/ -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 21:28:48 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 21:28:48 -0000 Subject: [MacPorts] #66513: podman @4.3.1: env: python3: No such file or directory In-Reply-To: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> References: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> Message-ID: <062.4eac3cea8ab7857ee9b952e621fe3e08@macports.org> #66513: podman @4.3.1: env: python3: No such file or directory -------------------------+---------------------- Reporter: ryandesign | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: podman | -------------------------+---------------------- Comment (by Vadym-Valdis Yudaiev ): In [changeset:"cd520c57a6b0ecfa6fa432426afec267fed470cd/macports-ports" cd520c57a6b0ecfa6fa432426afec267fed470cd/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="cd520c57a6b0ecfa6fa432426afec267fed470cd" podman: add pre-commit for fix build on <=10.14 As far as I understand, if there is no pre-commit, then Makefile tries to install it by itself using `python3`: {{{ @echo "FATAL: pre-commit was not found, make .install.pre-commit to installing it." >&2 }}} Increase the revision to make sure that builds for >10.14 will not differ from lower ones. See https://trac.macports.org/ticket/66513 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 21:46:38 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 21:46:38 -0000 Subject: [MacPorts] #66177: qt5-qtwebkit @5.9.2_4 fails to build In-Reply-To: <044.0893fa41b204973d4be592538766859d@macports.org> References: <044.0893fa41b204973d4be592538766859d@macports.org> Message-ID: <059.87ef8fff20eae81a5141ad774e3da877@macports.org> #66177: qt5-qtwebkit @5.9.2_4 fails to build ---------------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by dershow): Yes, but I'm not sure what. It did ultimately build for me more recently. But, I'm not sure what changed and fixed it. So, I don't think that the ticket should be closed unless there was a fix introduced. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 22:22:30 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 22:22:30 -0000 Subject: [MacPorts] #66531: I am not beeing successful on installing MARS through macports In-Reply-To: <050.9d2f7351757ad59c908903a2cc50634a@macports.org> References: <050.9d2f7351757ad59c908903a2cc50634a@macports.org> Message-ID: <065.950b4f95d39fa2f1b22b4e8b1aecabec@macports.org> #66531: I am not beeing successful on installing MARS through macports ----------------------------+-------------------- Reporter: PhilippeMenge | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mars | ----------------------------+-------------------- Changes (by ryandesign): * keywords: mars => Old description: > "Error: Failed to build mars: command execution failed" > > this error is being reported at the terminal. how can I install it? New description: {{{ Error: Failed to build mars: command execution failed }}} this error is being reported at the terminal. how can I install it? -- Comment: Please attach the main.log. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 22:25:38 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 22:25:38 -0000 Subject: [MacPorts] #66532: MoltenVK: Add universal variant; don't install universal unless universal variant is selected (was: moltenvk should be labeled as a universal variant) In-Reply-To: <050.478450c82a0eb5cbbc05f9bee8e79303@macports.org> References: <050.478450c82a0eb5cbbc05f9bee8e79303@macports.org> Message-ID: <065.da96e51ca67783f7eedec435e0972703@macports.org> #66532: MoltenVK: Add universal variant; don't install universal unless universal variant is selected ----------------------------+------------------------ Reporter: MichaelGDev48 | Owner: ryandesign Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: MoltenVK | ----------------------------+------------------------ Changes (by ryandesign): * status: new => assigned * cc: Gcenx (added) * keywords: vk, vulkan, loader, moltenvk => * owner: (none) => ryandesign * port: moltenvk, vulkan-loader => MoltenVK Old description: > When compiling and installing moltenvk it provides a universal variant > but isn't labeled as such which causes issues for packages you try to > build with universal label , that depend on it like vulkan-loader > Error: Cannot install vulkan-loader for the archs 'arm64 x86_64' because > Error: its dependency MoltenVK is only installed for the arch 'arm64' > Error: and does not have a universal variant. > > file /opt/local/lib/libMoltenVK.dylib > /opt/local/lib/libMoltenVK.dylib: Mach-O universal binary with 2 > architectures: [x86_64:Mach-O 64-bit dynamically linked shared library > x86_64] [arm64] > /opt/local/lib/libMoltenVK.dylib (for architecture x86_64): Mach-O > 64-bit dynamically linked shared library x86_64 > /opt/local/lib/libMoltenVK.dylib (for architecture arm64): Mach-O > 64-bit dynamically linked shared library arm64 New description: When compiling and installing moltenvk it provides a universal variant but isn't labeled as such which causes issues for packages you try to build with universal label , that depend on it like vulkan-loader {{{ Error: Cannot install vulkan-loader for the archs 'arm64 x86_64' because Error: its dependency MoltenVK is only installed for the arch 'arm64' Error: and does not have a universal variant. }}} {{{ file /opt/local/lib/libMoltenVK.dylib /opt/local/lib/libMoltenVK.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64] /opt/local/lib/libMoltenVK.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/libMoltenVK.dylib (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64 }}} -- Comment: So, 1. MoltenVK should have a universal variant, and 2. MoltenVK should not install universal files when the universal variant has not been requested I'm assigning the ticket to myself since I'm the maintainer but I'm not working on this issue; others are welcome to. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 23:38:25 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 23:38:25 -0000 Subject: [MacPorts] #66533: mars: Update to 4.5 Message-ID: <047.9f56931c263a58f3f1f14e48fd769fce@macports.org> #66533: mars: Update to 4.5 ------------------------+---------------------- Reporter: ryandesign | Owner: maehne Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: mars ------------------------+---------------------- The mars port is at version 4.4 but version 4.5 was released in 2014. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 22 23:45:15 2022 From: noreply at macports.org (MacPorts) Date: Thu, 22 Dec 2022 23:45:15 -0000 Subject: [MacPorts] #66531: I am not beeing successful on installing MARS through macports In-Reply-To: <050.9d2f7351757ad59c908903a2cc50634a@macports.org> References: <050.9d2f7351757ad59c908903a2cc50634a@macports.org> Message-ID: <065.3f6bcf98f17342db5254b8bdae7aecfe@macports.org> #66531: I am not beeing successful on installing MARS through macports ----------------------------+---------------------- Reporter: PhilippeMenge | Owner: maehne Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mars | ----------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: (none) => maehne Comment: We won't know until we see your main.log, but perhaps the problem you see is the same that we see on some of our build servers: https://build.macports.org/builders/ports- 11_x86_64-builder/builds/96683/steps/install-port/logs/stdio {{{ Error: Failed to destroot mars: xinstall: Cannot stat: /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/MacOS/JavaApplicationStub, No such file or directory }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 03:51:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 03:51:50 -0000 Subject: [MacPorts] #66534: LibreOffice fails to configure on install because it can't find the correct macOS SDK. Message-ID: <050.67493431e544c05c6109577d7bd5f08b@macports.org> #66534: LibreOffice fails to configure on install because it can't find the correct macOS SDK. ---------------------------+------------------------- Reporter: LinuxRocks101 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: libreoffice ---------------------------+------------------------- Fails to configure because of: "error: Could not find an appropriate macOS SDK." "checking what macOS SDK to use... configure: error: Could not find an appropriate macOS SDK Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.3.2" && ./configure --prefix=/opt/local --disable-breakpad --disable-bundle- mariadb --disable-ccache --disable-coinmp --disable-epm --disable-ext- numbertext --disable-fetch-external --disable-firebird-sdbc --disable-ldap --disable-lotuswordpro --disable-lpsolve --disable-odk --disable-online- update --disable-openssl --disable-pdfimport --disable-pdfium --disable- postgresql-sdbc --disable-report-builder --disable-zxing --enable-bogus- pkg-config --enable-cups --enable-extension-integration --enable-mpl- subset --enable-python=system --enable-readonly-installset --enable- release-build --enable-symbols --with-boost=/opt/local/libexec/boost/1.76 --with-external-tar=/opt/local/var/macports/distfiles/libreoffice --with- gnu-patch=/opt/local/bin/gpatch --with-myspell-dicts --with-package- version=7.4.3.2 --with-parallelism=4 --with-product-name=LibreOffice --with-system-clucene --with-system-cuckoo --with-system-dragonbox --with- system-epoxy --with-system-gpgmepp --with-system-headers --with-system- hunspell --with-system-jars --with-system-libabw --with-system-libebook --with-system-libepubgen --with-system-libexttextcat --with-system-libmwaw --with-system-libnumbertext --with-system-libqxp --with-system-libs --with-system-libstaroffice --with-system-libzmf --with-system-mdds --with-system-mythes --with-system-orcus --with-system-ucpp --with-system- xmlsec --with-theme=colibre --with-tls=nss --with-vendor=MacPorts --without-doxygen --without-fonts --without-java --without-package-format --without-system-dicts --without-system-libcmis --without-system- libfixmath --without-system-sane --without-webdav "--with-lang=bg br ca ca-valencia cy cs da de el en-US en-GB es et eu fi fr ga gd gl hr hu id is it ja km lt lv nb nl nn pl pt pt-BR ro ru sk sl sv ta tr uk zh-CN zh-TW" Exit code: 1" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 03:53:01 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 03:53:01 -0000 Subject: [MacPorts] #66534: LibreOffice fails to configure on install in macOS Ventura (13.1) because it can't find the correct macOS SDK. (was: LibreOffice fails to configure on install because it can't find the correct macOS SDK.) In-Reply-To: <050.67493431e544c05c6109577d7bd5f08b@macports.org> References: <050.67493431e544c05c6109577d7bd5f08b@macports.org> Message-ID: <065.d901d9e79618322d1079bf1c816d13c1@macports.org> #66534: LibreOffice fails to configure on install in macOS Ventura (13.1) because it can't find the correct macOS SDK. ----------------------------+-------------------- Reporter: LinuxRocks101 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libreoffice | ----------------------------+-------------------- Comment (by LinuxRocks101): Forgot to specify macOS version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 06:10:06 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 06:10:06 -0000 Subject: [MacPorts] #66534: LibreOffice fails to configure on install in macOS Ventura (13.1) because it can't find the correct macOS SDK. In-Reply-To: <050.67493431e544c05c6109577d7bd5f08b@macports.org> References: <050.67493431e544c05c6109577d7bd5f08b@macports.org> Message-ID: <065.0af8a508b7752118a2979064db0b2915@macports.org> #66534: LibreOffice fails to configure on install in macOS Ventura (13.1) because it can't find the correct macOS SDK. ----------------------------+---------------------- Reporter: LinuxRocks101 | Owner: Tatsh Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libreoffice | ----------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => Tatsh Old description: > Fails to configure because of: "error: Could not find an appropriate > macOS SDK." > > "checking what macOS SDK to use... configure: error: Could not find an > appropriate macOS SDK > Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.3.2" > && ./configure --prefix=/opt/local --disable-breakpad --disable-bundle- > mariadb --disable-ccache --disable-coinmp --disable-epm --disable-ext- > numbertext --disable-fetch-external --disable-firebird-sdbc --disable- > ldap --disable-lotuswordpro --disable-lpsolve --disable-odk --disable- > online-update --disable-openssl --disable-pdfimport --disable-pdfium > --disable-postgresql-sdbc --disable-report-builder --disable-zxing > --enable-bogus-pkg-config --enable-cups --enable-extension-integration > --enable-mpl-subset --enable-python=system --enable-readonly-installset > --enable-release-build --enable-symbols --with- > boost=/opt/local/libexec/boost/1.76 --with-external- > tar=/opt/local/var/macports/distfiles/libreoffice --with-gnu- > patch=/opt/local/bin/gpatch --with-myspell-dicts --with-package- > version=7.4.3.2 --with-parallelism=4 --with-product-name=LibreOffice > --with-system-clucene --with-system-cuckoo --with-system-dragonbox > --with-system-epoxy --with-system-gpgmepp --with-system-headers --with- > system-hunspell --with-system-jars --with-system-libabw --with-system- > libebook --with-system-libepubgen --with-system-libexttextcat --with- > system-libmwaw --with-system-libnumbertext --with-system-libqxp --with- > system-libs --with-system-libstaroffice --with-system-libzmf --with- > system-mdds --with-system-mythes --with-system-orcus --with-system-ucpp > --with-system-xmlsec --with-theme=colibre --with-tls=nss --with- > vendor=MacPorts --without-doxygen --without-fonts --without-java > --without-package-format --without-system-dicts --without-system-libcmis > --without-system-libfixmath --without-system-sane --without-webdav > "--with-lang=bg br ca ca-valencia cy cs da de el en-US en-GB es et eu fi > fr ga gd gl hr hu id is it ja km lt lv nb nl nn pl pt pt-BR ro ru sk sl > sv ta tr uk zh-CN zh-TW" > Exit code: 1" New description: Fails to configure because of: "error: Could not find an appropriate macOS SDK." {{{ checking what macOS SDK to use... configure: error: Could not find an appropriate macOS SDK Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.3.2" && ./configure --prefix=/opt/local --disable-breakpad --disable-bundle- mariadb --disable-ccache --disable-coinmp --disable-epm --disable-ext- numbertext --disable-fetch-external --disable-firebird-sdbc --disable-ldap --disable-lotuswordpro --disable-lpsolve --disable-odk --disable-online- update --disable-openssl --disable-pdfimport --disable-pdfium --disable- postgresql-sdbc --disable-report-builder --disable-zxing --enable-bogus- pkg-config --enable-cups --enable-extension-integration --enable-mpl- subset --enable-python=system --enable-readonly-installset --enable- release-build --enable-symbols --with-boost=/opt/local/libexec/boost/1.76 --with-external-tar=/opt/local/var/macports/distfiles/libreoffice --with- gnu-patch=/opt/local/bin/gpatch --with-myspell-dicts --with-package- version=7.4.3.2 --with-parallelism=4 --with-product-name=LibreOffice --with-system-clucene --with-system-cuckoo --with-system-dragonbox --with- system-epoxy --with-system-gpgmepp --with-system-headers --with-system- hunspell --with-system-jars --with-system-libabw --with-system-libebook --with-system-libepubgen --with-system-libexttextcat --with-system-libmwaw --with-system-libnumbertext --with-system-libqxp --with-system-libs --with-system-libstaroffice --with-system-libzmf --with-system-mdds --with-system-mythes --with-system-orcus --with-system-ucpp --with-system- xmlsec --with-theme=colibre --with-tls=nss --with-vendor=MacPorts --without-doxygen --without-fonts --without-java --without-package-format --without-system-dicts --without-system-libcmis --without-system- libfixmath --without-system-sane --without-webdav "--with-lang=bg br ca ca-valencia cy cs da de el en-US en-GB es et eu fi fr ga gd gl hr hu id is it ja km lt lv nb nl nn pl pt pt-BR ro ru sk sl sv ta tr uk zh-CN zh-TW" Exit code: 1 }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 06:11:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 06:11:25 -0000 Subject: [MacPorts] #64410: LibreOffice @7.3.0.1 may contain malware... In-Reply-To: <048.c4a709d2bb8aaf570b5bb75f5364da30@macports.org> References: <048.c4a709d2bb8aaf570b5bb75f5364da30@macports.org> Message-ID: <063.d3b22a1cb1d8ff407fd16c7c98532c91@macports.org> #64410: LibreOffice @7.3.0.1 may contain malware... --------------------------+---------------------- Reporter: josephsacco | Owner: Tatsh Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: wontfix | Keywords: upstream Port: libreoffice | --------------------------+---------------------- Changes (by jmroot): * status: assigned => closed * keywords: => upstream * resolution: => wontfix -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 06:12:15 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 06:12:15 -0000 Subject: [MacPorts] #62496: libreoffice @7.1.1.2: configure: error: Package requirements (epoxy >= 1.2) were not met In-Reply-To: <047.17ffac315bac040da1e6fb4c2b31d8ca@macports.org> References: <047.17ffac315bac040da1e6fb4c2b31d8ca@macports.org> Message-ID: <062.8a00c959531c63b045e6f0f90dfde5c0@macports.org> #62496: libreoffice @7.1.1.2: configure: error: Package requirements (epoxy >= 1.2) were not met --------------------------+-------------------- Reporter: ryandesign | Owner: Tatsh Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: Port: libreoffice | --------------------------+-------------------- Changes (by jmroot): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:27:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 08:27:42 -0000 Subject: [MacPorts] #66177: qt5-qtwebkit @5.9.2_4 fails to build In-Reply-To: <044.0893fa41b204973d4be592538766859d@macports.org> References: <044.0893fa41b204973d4be592538766859d@macports.org> Message-ID: <059.73bf50c31e089e6d0ef31c5587ff8f2d@macports.org> #66177: qt5-qtwebkit @5.9.2_4 fails to build ---------------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by kencu): there is a thought that certain headers, which ones not yet sorted out, in the macports prefix might cause the failure. an arm-only fix is pr?d here https://github.com/macports/macports- ports/pull/16890 but thst might need to be used on all systems? It hasn?t bern commited yet as it?s still not fully sorted out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:28:21 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 08:28:21 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' Message-ID: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> #66535: spice-server: configure: no module named 'six' --------------------+-------------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: spice-server --------------------+-------------------------- spice-server fails to configure: {{{ Program python3 found: YES (/opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11) Message: Checking for python module six WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Running command: /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 -c import six --- stdout --- --- stderr --- Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'six' subprojects/spice-common/meson.build:141:6: ERROR: Problem encountered: Python module six not found }}} The Portfile has py_ver_nodot=310, and has a depends_build on py310-six, but it is actually running Python 3.11 during the configure. I don't know why it chose Python 3.11. My port select for python3 is "none". If I switch py_ver_nodot=311, it configures after it installs py311-six. (But, it fails later with ":info:build asciidoc: ERROR: manual.txt: line 9: only book doctypes can contain level 0 sections", but might be the subject of another ticket) So, the Portfile tries to depend on py${py_ver_nodot}-six, but the configure appears to be picking some version besides python${py_ver_nodot} for its execution. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:33:43 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 08:33:43 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.9e0a4af425f985fcde17a25102de1dd0@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by kencu): have you ?sudo port selected? python311 as your python3? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 08:35:43 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 08:35:43 -0000 Subject: [MacPorts] #66536: warzone2100: set `platforms any` for music and videos Message-ID: <043.de97dab41595d8bd6b390f5141b14b64@macports.org> #66536: warzone2100: set `platforms any` for music and videos -------------------------+------------------------- Reporter: jmroot | Owner: jasonliu-- Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: warzone2100 -------------------------+------------------------- The `warzone2100-music` and `warzone2100-videos` subports pretty clearly install the same files everywhere, so they should set `platforms any` to avoid building a separate archive per macOS version. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 09:00:18 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 09:00:18 -0000 Subject: [MacPorts] #66500: Remove $ dollar sign from line copy&paste (user terminal commands) In-Reply-To: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> References: <043.d6566ee797626a273afaf3efe8867ed4@macports.org> Message-ID: <058.f5a3a01955171982875996bb606aca16@macports.org> #66500: Remove $ dollar sign from line copy&paste (user terminal commands) --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Oh, there seems to be a much easier option: just apply this (from [docs.python.org]) to the span containing the prompt marker and it won't be selected on triple click `>>> ` {{{ span.gp { user-select: none; -webkit-user-select: text; -webkit-user-select: none; -moz-user-select: none; -ms-user-select: none; } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 10:30:35 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 10:30:35 -0000 Subject: [MacPorts] #66537: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina Message-ID: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> #66537: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina --------------------+----------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: gocryptfs --------------------+----------------------- [https://ports.macports.org/port/gocryptfs/details/] state that there is a prebuilt package for Catalina, and that only `macfuse` is a dependency, but trying to install gocryptfs triggers a complete build from source with the installation of all 4 build dependencies macOS Catalina 10.15.7 {{{ $ sudo port install gocryptfs ---> Computing dependencies for gocryptfs The following dependencies will be installed: go pandoc pkgconfig Continue? [Y/n]: y }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 10:38:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 10:38:50 -0000 Subject: [MacPorts] #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 In-Reply-To: <041.64f540df932b21a27a6730e7853db9e4@macports.org> References: <041.64f540df932b21a27a6730e7853db9e4@macports.org> Message-ID: <056.cac36b5facc9388a6100d81aef8c3a6a@macports.org> #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 ---------------------------+--------------------------------- Reporter: 6aKa | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by ostefano): Confirming that is still an issue since qt5-qtwebkit is not prebuilt on Ventura. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 10:41:25 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 10:41:25 -0000 Subject: [MacPorts] #66538: Allow suppressing 'Warning: couldn't find file' Message-ID: <043.c11081b39d5e3b1911d4567d618536bb@macports.org> #66538: Allow suppressing 'Warning: couldn't find file' -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Keywords: | Port: -------------------------+-------------------- I've deleted some mistakenly installed port files [https://trac.macports.org/ticket/66525] and now during the `Scanning binaries for linking errors` installation step I get warnings for missing files. Is it possible to either limit the scanning step to the port being installed, not to all ports, or at least allow to suppress the warnings and leave them only for `port diagnose` command? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 11:02:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 11:02:20 -0000 Subject: [MacPorts] #66539: tcp_wrappers: master_sites has moved Message-ID: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> #66539: tcp_wrappers: master_sites has moved ---------------------+-------------------------- Reporter: 4d724ce | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: tcp_wrappers ---------------------+-------------------------- The source tarball URL has moved from https://opensource.apple.com/tarballs to https://github.com/apple-oss- distributions/tcp_wrappers, which causes builds to fail. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 11:35:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 11:35:20 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.6b152fee33eb3c465a69dce07f02ef99@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by jmroot): The port doesn't actually tell the build system which python to use, so I guess it just picks the latest. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 11:37:05 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 11:37:05 -0000 Subject: [MacPorts] #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 In-Reply-To: <041.64f540df932b21a27a6730e7853db9e4@macports.org> References: <041.64f540df932b21a27a6730e7853db9e4@macports.org> Message-ID: <056.24321ae81aa2691792eededcfb3ed05e@macports.org> #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 ---------------------------+--------------------------------- Reporter: 6aKa | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by jhoyt4): @ostefano - I've issued a new PR that applies @i0ntempest's suggested fix [https://github.com/macports/macports-ports/pull/16890]. I've tested it on both intel and arm without issues and am able to use webkit. I'd suggest giving that PR a try and let me know if it doesn't work for you as it can be updated. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:03:49 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:03:49 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.9c4ca489083e0fc9bf328410751994e5@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by jmroot): So meson apparently has no built-in support for choosing which python to use via an environment variable or command line option. Does this work for you? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:04:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:04:04 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.f7e6d76d88e84e01e7f86bd936c73f5c@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Changes (by jmroot): * Attachment "Portfile.diff" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:04:48 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:04:48 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.34a117e27b760951e7413a3e3f198529@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Changes (by jmroot): * Attachment "configurable-python.patch" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:05:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:05:53 -0000 Subject: [MacPorts] #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded Message-ID: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded ------------------------+-------------------- Reporter: Imzxhir | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: highsierra | Port: iTerm2 ------------------------+-------------------- Basically the title, where I can't install iTerm2 bacause it says I need Xcode even though I already have it installed. I'm on macOS 10.13.6 and I have Xcode version 10.1, here are some images: https://imgur.com/a/Ctfgmyd -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:10:23 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:10:23 -0000 Subject: [MacPorts] #66539: tcp_wrappers: master_sites has moved In-Reply-To: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> References: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> Message-ID: <059.1b66c7da1f162864743724294f0d6587@macports.org> #66539: tcp_wrappers: master_sites has moved ---------------------------+---------------------- Reporter: 4d724ce | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: tcp_wrappers | ---------------------------+---------------------- Changes (by jmroot): * cc: jeremyhu (added) * owner: (none) => mascguy * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:18:11 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:18:11 -0000 Subject: [MacPorts] #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded In-Reply-To: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> References: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> Message-ID: <059.20a4f7b8bdf8ec5561340885f19f5f3e@macports.org> #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded ----------------------+------------------------ Reporter: Imzxhir | Owner: markemer Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: highsierra Port: iTerm2 | ----------------------+------------------------ Changes (by jmroot): * owner: (none) => markemer * status: new => assigned * cc: mark@?, markemer, openmaintainer (removed) Comment: What does `xcodebuild -version` output? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:20:31 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:20:31 -0000 Subject: [MacPorts] #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded In-Reply-To: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> References: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> Message-ID: <059.98c58c063e9cbf62e8d6512d6081cbad@macports.org> #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded ----------------------+------------------------ Reporter: Imzxhir | Owner: markemer Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: highsierra Port: iTerm2 | ----------------------+------------------------ Comment (by Imzxhir): Here is what it outputs: https://imgur.com/a/y3GIi7x -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 12:27:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 12:27:53 -0000 Subject: [MacPorts] #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded In-Reply-To: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> References: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> Message-ID: <059.d2facd4dd9eae474b9c63ddd6a3ff56f@macports.org> #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded ----------------------+------------------------ Reporter: Imzxhir | Owner: markemer Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: highsierra Port: iTerm2 | ----------------------+------------------------ Comment (by Imzxhir): This problem is now fixed, I just had to switch the path for Xcode to where my Xcode.app is and it worked. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 14:26:05 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 14:26:05 -0000 Subject: [MacPorts] #66436: cctools @949.0.1_2 checksum mismatch In-Reply-To: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> References: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> Message-ID: <058.8665ce18a0374825e9a7d4fd6f6658e5@macports.org> #66436: cctools @949.0.1_2 checksum mismatch ----------------------+---------------------- Reporter: gplunk | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+---------------------- Comment (by esbugz): To fix the issue I not only had to change the port hashes @ `/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/cctools/Portfile` to {{{ checksums ld64-530.tar.gz \ rmd160 57d6629f31180b53f6f6a324a28e723611bd3cfb \ sha256 a21de4c2d4cd3ebf13c887eebbafc4b58ff0ee5bb07e592ba12690fb28a9cb17 \ size 729897 \ cctools-949.0.1.tar.gz \ rmd160 54a8e318087547b827eee4e5dbb21a8f3956402f \ sha256 8b2d8dc371a57e42852fa6102efaf324ef004adf86072bf9957e2ac9005326c1 \ size 1967695 }}} But also the folder names changed to some buggy duplicates, so had to rename these two folders, replacing the duplicate `cctools-cctools-` and `ld64-ld64-` with a single `cctools-` and `ld64-` `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work /cctools-cctools-949.0.1` `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cctools/cctools/work/ld64-ld64-530` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 15:49:21 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 15:49:21 -0000 Subject: [MacPorts] #66436: cctools @949.0.1_2 checksum mismatch In-Reply-To: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> References: <043.ba63a8eeb49aaed763be1a676ff0811b@macports.org> Message-ID: <058.3d6d608ecf01867a1d245e05c4d58a91@macports.org> #66436: cctools @949.0.1_2 checksum mismatch ----------------------+---------------------- Reporter: gplunk | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: cctools | ----------------------+---------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/17006 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 16:10:52 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 16:10:52 -0000 Subject: [MacPorts] #66538: Allow suppressing 'Warning: couldn't find file' In-Reply-To: <043.c11081b39d5e3b1911d4567d618536bb@macports.org> References: <043.c11081b39d5e3b1911d4567d618536bb@macports.org> Message-ID: <058.a4b75eebcf06366dc02d9b2e213252f5@macports.org> #66538: Allow suppressing 'Warning: couldn't find file' --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Old description: > I've deleted some mistakenly installed port files > [https://trac.macports.org/ticket/66525] and now during the `Scanning > binaries for linking errors` installation step I get warnings for missing > files. > Is it possible to either limit the scanning step to the port being > installed, not to all ports, or at least allow to suppress the warnings > and leave them only for `port diagnose` command? New description: I've deleted some mistakenly installed port files #66525 and now during the `Scanning binaries for linking errors` installation step I get warnings for missing files. Is it possible to either limit the scanning step to the port being installed, not to all ports, or at least allow to suppress the warnings and leave them only for `port diagnose` command? -- Comment (by ryandesign): Neither of those is currently possible. You are expected not to delete any files that ports install. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 16:21:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 16:21:40 -0000 Subject: [MacPorts] #66537: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.e48d851c50c48bb66d3636092e23a3eb@macports.org> #66537: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina ------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gocryptfs | ------------------------+-------------------- Comment (by ryandesign): ports.macports.org tells you whether a build of a port has been attempted, and if so what the result of that build was, but it does not tell you whether the package that resulted from a successful build was uploaded to the public server. In the case of gocryptfs, we do not distribute a prebuilt package because we believe we are not legally permitted to do so due to the combination of its license and the licenses of its dependencies. {{{ % ./port_binary_distributable.tcl -v gocryptfs "gocryptfs" is not distributable because its dependency "macfuse" has license "restrictive" which is not known to be distributable }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 16:28:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 16:28:20 -0000 Subject: [MacPorts] #66537: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.a857e5292696c517431b2f834b2dab40@macports.org> #66537: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina ------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gocryptfs | ------------------------+-------------------- Comment (by esbugz): Ok, thanks for the clarification! Is there a more accessible place to get this basic port info? At least the `details` page could maybe include it, though would also be nice to know from the `info` command? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 16:32:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 16:32:13 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild (was: gocryptfs always builds instead of just downloading the prebuilt binary on macOS Catalina) In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.73a2240185caf268201b2c2b5252c194@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Changes (by esbugz): * component: ports => base * type: defect => enhancement * port: gocryptfs => Old description: > [https://ports.macports.org/port/gocryptfs/details/] state that there is > a prebuilt package for Catalina, and that only `macfuse` is a dependency, > but trying to install gocryptfs triggers a complete build from source > with the installation of all 4 build dependencies > > macOS Catalina 10.15.7 > {{{ > $ sudo port install gocryptfs > ---> Computing dependencies for gocryptfs > The following dependencies will be installed: > go > pandoc > pkgconfig > Continue? [Y/n]: y > }}} New description: I thought that port details with various OS versions, for example, [https://ports.macports.org/port/gocryptfs/details/], imply that there is a prebuilt package for a green-check-marked system But it's not the case, so I'd like to suggest adding such information to the details page and the `info` commands as it makes a big difference in installation time & space requirements -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:14:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:14:20 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.9aacd6d50bfa80854988bcb9e848ef91@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Changes (by ryandesign): * cc: MarcelBochtler (removed) Comment: Determining whether a port ''can be'' distributed as a binary could be determined offline and added to `port info` after #60315 is implemented. Determining wheter a port ''is'' available as a binary would require performing an http(s) request to the packages server. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:27:10 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:27:10 -0000 Subject: [MacPorts] #66541: xephem @4.0.1: /bin/sh: nroff: command not found Message-ID: <047.05e8647914f9cbf862aa8666d362ab7e@macports.org> #66541: xephem @4.0.1: /bin/sh: nroff: command not found ------------------------+-------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: xephem ------------------------+-------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5806/steps/install-port/logs/stdio {{{ nroff -man xephem.man > xephem.1 /bin/sh: nroff: command not found make: *** [xephem.1] Error 127 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:32:01 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:32:01 -0000 Subject: [MacPorts] #66542: sshuttle: can't read "env(USER)": no such variable Message-ID: <047.98ad8aabe0fabc2cb03868cc2e3eb85c@macports.org> #66542: sshuttle: can't read "env(USER)": no such variable ------------------------+------------------------- Reporter: ryandesign | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: sshuttle ------------------------+------------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5801/steps/install-port/logs/stdio {{{ DEBUG: Executing proc-pre-org.macports.destroot-destroot-1 DEBUG: Executing proc-pre-org.macports.destroot-destroot-2 Error: Failed to destroot sshuttle: can't read "env(USER)": no such variable DEBUG: Error code: NONE DEBUG: Backtrace: can't read "env(USER)": no such variable }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:33:59 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:33:59 -0000 Subject: [MacPorts] #66543: py39-pyfftw @0.13.0: error: implicit declaration of function 'fftw_plan_dft' is invalid in C99 Message-ID: <047.efd24173668082401f288b260985f87b@macports.org> #66543: py39-pyfftw @0.13.0: error: implicit declaration of function 'fftw_plan_dft' is invalid in C99 ------------------------+------------------------ Reporter: ryandesign | Owner: lpsinger Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: _py-pyfftw ------------------------+------------------------ https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5745/steps/install-port/logs/stdio {{{ /opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- pyfftw/py39-pyfftw/work/.tmp/pyfftw-7n8p7p3n/fftw_plan_dft.c:2:17: error: implicit declaration of function 'fftw_plan_dft' is invalid in C99 [-Werror,-Wimplicit-function-declaration] fftw_plan_dft(); ^ 1 error generated. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:36:49 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:36:49 -0000 Subject: [MacPorts] #66544: py39-pyobjc @9.0: FileNotFoundError: [Errno 2] No such file or directory: '.../pyobjc-framework-metal/setup.py' Message-ID: <047.fc3afcd6d6d123d5bca9eb9af07191da@macports.org> #66544: py39-pyobjc @9.0: FileNotFoundError: [Errno 2] No such file or directory: '.../pyobjc-framework-metal/setup.py' ------------------------+----------------------- Reporter: ryandesign | Owner: danchr Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: py-pyobjc ------------------------+----------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5410/steps/install-port/logs/stdio {{{ Traceback (most recent call last): File "/opt/bblocal/var/buildworker/ports/build/ports/python/py- pyobjc/files/multibuild.py", line 18, in dirs = ["pyobjc-core"] + _install_tool.sorted_framework_wrappers() File "/opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- pyobjc/py39-pyobjc/work/ronaldoussoren-pyobjc-595adfb/development- support/_install_tool.py", line 148, in sorted_framework_wrappers with open(setup) as fp: FileNotFoundError: [Errno 2] No such file or directory: '/opt/local/var/macports/build /_opt_bblocal_var_buildworker_ports_build_ports_python_py- pyobjc/py39-pyobjc/work/ronaldoussoren-pyobjc-595adfb/pyobjc-framework- metal/setup.py' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:44:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:44:04 -0000 Subject: [MacPorts] #66545: wmcpuload @1.0.1: error: implicit declaration of function 'host_statistics' is invalid in C99 Message-ID: <047.dd0ac8013c2da91ebddb0d271b4a956e@macports.org> #66545: wmcpuload @1.0.1: error: implicit declaration of function 'host_statistics' is invalid in C99 ------------------------+----------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: wmcpuload ------------------------+----------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5832/steps/install-port/logs/stdio {{{ cpu_darwin.c:29:1: warning: type specifier missing, defaults to 'int' [-Wimplicit-int] getload(host_cpu_load_info_t cpucounters) ^ cpu_darwin.c:34:10: error: implicit declaration of function 'host_statistics' is invalid in C99 [-Werror,-Wimplicit-function- declaration] kr = host_statistics (host_priv_port, HOST_CPU_LOAD_INFO, (host_info_t) cpucounters, &count); ^ cpu_darwin.c:41:22: error: implicit declaration of function 'mach_host_self' is invalid in C99 [-Werror,-Wimplicit-function- declaration] host_priv_port = mach_host_self(); ^ 1 warning and 2 errors generated. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:51:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:51:13 -0000 Subject: [MacPorts] #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded In-Reply-To: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> References: <044.d5973a99d87e9afa019ea950755bd5dc@macports.org> Message-ID: <059.4332631ef857ccebb5e3722c13ab79d4@macports.org> #66540: iTerm2 v3.4.18: I can't install iTerm2 because it says I don't have Xcode even though I have it downloaded ----------------------+------------------------ Reporter: Imzxhir | Owner: markemer Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: highsierra Port: iTerm2 | ----------------------+------------------------ Changes (by ryandesign): * status: assigned => closed * resolution: => invalid -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:56:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:56:20 -0000 Subject: [MacPorts] #66331: libgcc9: Error: gcc9 9.5.0 is not supported on Darwin 17 i386 In-Reply-To: <049.6fae14d169016ace3c4b2da74437f88d@macports.org> References: <049.6fae14d169016ace3c4b2da74437f88d@macports.org> Message-ID: <064.da3079e2ca2cf6bf60126e12432a40df@macports.org> #66331: libgcc9: Error: gcc9 9.5.0 is not supported on Darwin 17 i386 ---------------------------+------------------------ Reporter: WolfgangFahl | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: highsierra Port: libgcc9 | ---------------------------+------------------------ Comment (by ryandesign): What steps, specifically, do you think the message should suggest? The message comes from the libgcc9 port. The libgcc9 port cannot suggest that you install OpenBLAS with the +gcc11 variant because the libgcc9 port does not know for what reason it was being installed/upgraded. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 18:58:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 18:58:04 -0000 Subject: [MacPorts] #66546: atlas: Atlas could not detect any fortran compiler Message-ID: <047.a04d57784c1e5aa5d1f74eeaccf86f51@macports.org> #66546: atlas: Atlas could not detect any fortran compiler ------------------------+---------------------- Reporter: ryandesign | Owner: Veence Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: atlas ------------------------+---------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/5833/steps/install-port/logs/stdio {{{ Error: Failed to configure atlas: Atlas could not detect any fortran compiler. If you really don?t need the fortran interface to be built, please use the +nofortran option, else install a fortran compiler (e.g. gcc4X) before building Atlas. DEBUG: Error code: NONE }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 19:07:42 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 19:07:42 -0000 Subject: [MacPorts] #66225: libzzip @0.13.67: Downloads things at build time which takes a long time (was: Building libzzip takes an eternity on PPC Mac OS X 10.5.8, Leopard) In-Reply-To: <046.0072c4ff3aa0245e6ee70e93169b89fe@macports.org> References: <046.0072c4ff3aa0245e6ee70e93169b89fe@macports.org> Message-ID: <061.79c7bc628b9fcb939d6ee83e19bd2614@macports.org> #66225: libzzip @0.13.67: Downloads things at build time which takes a long time ------------------------+------------------------- Reporter: ballapete | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: leopard ppc Port: libzzip | ------------------------+------------------------- Changes (by ryandesign): * owner: (none) => mojca * cc: mojca@? (removed) * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 19:24:15 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 19:24:15 -0000 Subject: [MacPorts] #64176: Some perl modules built with +universal only installed arm64 binaries In-Reply-To: <041.e4e5b17ff3c77b115081011d1023c08a@macports.org> References: <041.e4e5b17ff3c77b115081011d1023c08a@macports.org> Message-ID: <056.1f3694ea09a7b33504e2edf6c3226d62@macports.org> #64176: Some perl modules built with +universal only installed arm64 binaries -------------------------------------------------+------------------------- Reporter: jgrg | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: arm64 Port: p5-math-random-isaac-xs p5-params- | x86_64 universal validate p5-www-form-urlencoded-xs | -------------------------------------------------+------------------------- Comment (by ryandesign): Replying to [comment:5 jgrg]: > Binary Perl modules are usually built using the CFLAGS and LDFLAGS that were used to build `perl`, but it seems that MacPorts has some kind of cunning mechanism that keeps whatever flags are needed for universal builds out of the Perl config so that building a universal module doesn't happen by default? Yes, Perl seems to be under the impression that whatever compiler and I guess flags were used to build Perl should be used to build perl modules as well. We do not consider that to be appropriate behavior in MacPorts so we prevent it from happening. From our point of view, every port build should happen with the compiler and flags that were requested for that build. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 19:25:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 19:25:12 -0000 Subject: [MacPorts] #64132: veracrypt @1.24_1: Should use macfuse in place of osxfuse (was: veracrypt @1.24_1: Shoule use macfuse in place of osxfuse) In-Reply-To: <044.347bc810cab67ff7f19141a2771e4a70@macports.org> References: <044.347bc810cab67ff7f19141a2771e4a70@macports.org> Message-ID: <059.ee9ba3d3dabaa88ae07a77584b5b9b29@macports.org> #64132: veracrypt @1.24_1: Should use macfuse in place of osxfuse ------------------------+-------------------- Reporter: bnoctis | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: veracrypt | ------------------------+-------------------- Changes (by ryandesign): * port: => veracrypt -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 20:01:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 20:01:24 -0000 Subject: [MacPorts] #66542: sshuttle: can't read "env(USER)": no such variable In-Reply-To: <047.98ad8aabe0fabc2cb03868cc2e3eb85c@macports.org> References: <047.98ad8aabe0fabc2cb03868cc2e3eb85c@macports.org> Message-ID: <062.91d1ea667403b5a83e5c30cc8a5f587d@macports.org> #66542: sshuttle: can't read "env(USER)": no such variable -------------------------+------------------------- Reporter: ryandesign | Owner: herbygillot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: sshuttle | -------------------------+------------------------- Comment (by jmroot): I expect this is not Ventura-specific, but is likely rare outside of the buildbot environment, though anyone could have `USER` unset. It should probably be using either `${macportsuser}` or `${install.user}` depending on what it's trying to accomplish. (And should presumably only be attempted when running as root.) What user do the files belong to to begin with, anyway? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 20:08:44 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 20:08:44 -0000 Subject: [MacPorts] #66538: Allow suppressing 'Warning: couldn't find file' In-Reply-To: <043.c11081b39d5e3b1911d4567d618536bb@macports.org> References: <043.c11081b39d5e3b1911d4567d618536bb@macports.org> Message-ID: <058.166caf42db1066697fe3e62acac1f9e2@macports.org> #66538: Allow suppressing 'Warning: couldn't find file' --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Actually, it seems it is possible, this flag stops the spam when I install new ports, so will add if to the list of default args meanwhile. {{{ --no-rev-upgrade By default, a binary sanity check called rev-upgrade is run automatically after each successful installation. Pass this flag, if you want to avoid running this step, for example if you want to run it explicitly later after a number of installations using sudo port rev-upgrade, or if you know it will detect problems but want to defer dealing with them }}} By the way, what is `pkg_post_unarchive_deletions` for? Any chance of adjusting this to remove the mistaken files (would also help in removing the useless locales and some other stuff if possible)? (example below didn't change anything). The `unarchive` stage isn't mentioned in the Guide, so not sure what exactly it's used for {{{ # Space-delimited list of files and directories to delete after the unarchive stage and before creating a pkg. Paths are interpreted relative to prefix, and there is no default value. This is useful for removing unnecessary files and directories prior to pkg or mpkg deployment pkg_post_unarchive_deletions share/locale share/helix }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 20:23:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 20:23:55 -0000 Subject: [MacPorts] #66547: algol68g @3.0.6: error: implicitly declaring library function 'finite' with type 'int (double)' Message-ID: <047.8c9c7b59b7c0e80b32dda761801c38fd@macports.org> #66547: algol68g @3.0.6: error: implicitly declaring library function 'finite' with type 'int (double)' ------------------------+---------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: bigsur | Port: algol68g ------------------------+---------------------- https://build.macports.org/builders/ports- 11_arm64-builder/builds/78106/steps/install-port/logs/stdio {{{ ./src/a68g/compiler.c:1187:12: error: implicitly declaring library function 'finite' with type 'int (double)' [-Werror,-Wimplicit-function- declaration] if (!finite (VALUE (&x))) { ^ ./src/a68g/compiler.c:1187:12: note: include the header or explicitly provide a declaration for 'finite' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 20:56:13 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 20:56:13 -0000 Subject: [MacPorts] #66190: gpick-0.2.5_3 build fails with error "Error: Processing of port gpick failed" after upgrading to Ventura 13.0 In-Reply-To: <049.72a9de95ae21b87fd1b7e3015ce30f0e@macports.org> References: <049.72a9de95ae21b87fd1b7e3015ce30f0e@macports.org> Message-ID: <064.3702001b2074149898cb0dcb0b4965a6@macports.org> #66190: gpick-0.2.5_3 build fails with error "Error: Processing of port gpick failed" after upgrading to Ventura 13.0 ---------------------------+-------------------- Reporter: worldleather | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gpick | ---------------------------+-------------------- Comment (by jmroot): The error on the buildbot is {{{ File "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_graphics_gpick/gpick/work/gpick_0.2.5/SConscript", line 51 umask = os.umask(022) ^ SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 23 23:58:12 2022 From: noreply at macports.org (MacPorts) Date: Fri, 23 Dec 2022 23:58:12 -0000 Subject: [MacPorts] #60818: darwintrace cannot inject into binaries of a different architecture (missing arm64e) (was: darwintrace cannot inject into binaries of a different architecture) In-Reply-To: <046.dfefef8a386d195e63dbc3c85aa31ea6@macports.org> References: <046.dfefef8a386d195e63dbc3c85aa31ea6@macports.org> Message-ID: <061.c054adb50434b67b47adf37e80f5294e@macports.org> #60818: darwintrace cannot inject into binaries of a different architecture (missing arm64e) --------------------------+----------------------- Reporter: saagarjha | Owner: (none) Type: enhancement | Status: reopened Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: tracemode Port: | --------------------------+----------------------- Comment (by raimue): The missing part is `arm64e`, which is a new ABI to support Pointer Authentication as specified with ARMv8.3. https://developer.apple.com/documentation/security/preparing_your_app_to_work_with_pointer_authentication However, Apple does not consider this ABI as stable. The use of arm64e seems to be limited to binaries signed by Apple. As I have read, it is actually used in binaries in `/usr/bin` but I cannot confirm this. I assume (!) this limitation also applies to libraries and therefore we cannot just build darwintrace.dylib for arm64e and inject it into the process. Maybe a possible workaround would be to force use of arm64 for such binaries with something like `arch -arm64 /usr/bin/...`? This could be done in the SIP workaround that we have to use anyway. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 01:17:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 01:17:56 -0000 Subject: [MacPorts] #66548: Error: Failed to build libgcc-devel: command execution failed Message-ID: <043.a89dbf3b8d59d8e349382785539a43e1@macports.org> #66548: Error: Failed to build libgcc-devel: command execution failed --------------------+-------------------- Reporter: csmoon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: --------------------+-------------------- [(1014) ~ ]? sudo port install scrcpy ---> Computing dependencies for scrcpy ---> Cleaning scrcpy ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 27 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 Continue? [Y/n]: y ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://fra.de.packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://mse.uk.packages.macports.org/libgcc-devel ---> Building libgcc-devel Error: Failed to build libgcc-devel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: rev-upgrade failed: Error rebuilding webkit2-gtk Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 01:21:15 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 01:21:15 -0000 Subject: [MacPorts] #66548: Error: Failed to build libgcc-devel: command execution failed In-Reply-To: <043.a89dbf3b8d59d8e349382785539a43e1@macports.org> References: <043.a89dbf3b8d59d8e349382785539a43e1@macports.org> Message-ID: <058.2919ef1b1a9beccf208f5f46c484652f@macports.org> #66548: Error: Failed to build libgcc-devel: command execution failed ---------------------+-------------------- Reporter: csmoon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | ---------------------+-------------------- Changes (by csmoon): * Attachment "main.tgz" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 07:12:57 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 07:12:57 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.8afe64c75a603d620cf164c6c5f8a608@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:4 ryandesign]: > Determining whether a port ''is'' available as a binary would require performing an http(s) request to the packages server. Why couldn't it be stored in the local database not introduce this request delay? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 07:25:36 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 07:25:36 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path Message-ID: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path ---------------------------------+---------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: elcapitan legacy-os | Port: qt511-qtimageformats ---------------------------------+---------------------------------- Again, this error occurs when trying to rebuild due to an update of ghostscript and ImageMagick. I?ll attach the logfile. Xcode is 8.2.1. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 07:27:16 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 07:27:16 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.3455a91b3006186c68d793833eb1a25b@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Changes (by thetrial): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 09:42:45 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 09:42:45 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.2e6177dec4556ba20fdbe31467732004@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): Addition: I installed the ports MacOSX10.11.sdk and MacOSX10.12.sdk, hoping that would solve this. It did not. {{{ xcrun --show-sdk-path }}} still gives {{{ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk }}} {{{ --sdk macosx10.12 --show-sdk-version }}} gives {{{ 10.12 }}} {{{ --sdk macosx10.11 --show-sdk-version }}} gives {{{ xcodebuild: error: SDK "macosx10.11" cannot be located. xcodebuild: error: SDK "macosx10.11" cannot be located. xcrun: error: unable to lookup item 'SDKVersion' in SDK 'macosx10.11' }}} What?s wrong? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 09:56:35 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 09:56:35 -0000 Subject: [MacPorts] #66548: libgcc-devel @12-20221212_0+stdlib_flag build failure: sprintf is deprecated (was: Error: Failed to build libgcc-devel: command execution failed) In-Reply-To: <043.a89dbf3b8d59d8e349382785539a43e1@macports.org> References: <043.a89dbf3b8d59d8e349382785539a43e1@macports.org> Message-ID: <058.baeb372c3b112f50d2cb75b5f99bb964@macports.org> #66548: libgcc-devel @12-20221212_0+stdlib_flag build failure: sprintf is deprecated ---------------------------+--------------------- Reporter: csmoon | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: ventura Port: libgcc-devel | ---------------------------+--------------------- Changes (by jmroot): * status: new => closed * keywords: => ventura * resolution: => duplicate * port: => libgcc-devel Old description: > [(1014) ~ ]? sudo port install scrcpy > ---> Computing dependencies for scrcpy > ---> Cleaning scrcpy > ---> Updating database of binaries > ---> Scanning binaries for linking errors > ---> Found 27 broken files, matching files to ports > ---> Found 1 broken port, determining rebuild order > You can always run 'port rev-upgrade' again to fix errors. > The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 > Continue? [Y/n]: y > ---> Computing dependencies for libgcc-devel > ---> Fetching archive for libgcc-devel > ---> Attempting to fetch libgcc- > devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from > https://packages.macports.org/libgcc-devel > ---> Attempting to fetch libgcc- > devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from > https://fra.de.packages.macports.org/libgcc-devel > ---> Attempting to fetch libgcc- > devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from > https://mse.uk.packages.macports.org/libgcc-devel > ---> Building libgcc-devel > Error: Failed to build libgcc-devel: command execution failed > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports > .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log > for details. > Error: rev-upgrade failed: Error rebuilding webkit2-gtk > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. New description: {{{ [(1014) ~ ]? sudo port install scrcpy ---> Computing dependencies for scrcpy ---> Cleaning scrcpy ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 27 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: webkit2-gtk @2.28.2+minibrowser+x11 Continue? [Y/n]: y ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://fra.de.packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc- devel-12-20221212_0+stdlib_flag.darwin_22.arm64.tbz2 from https://mse.uk.packages.macports.org/libgcc-devel ---> Building libgcc-devel Error: Failed to build libgcc-devel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: rev-upgrade failed: Error rebuilding webkit2-gtk Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. }}} -- Comment: #66365 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 09:58:03 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 09:58:03 -0000 Subject: [MacPorts] #66365: libgcc-devel @12-20221202: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.092e714dc81a82f7ddb6ba1b5250c7e2@macports.org> #66365: libgcc-devel @12-20221202: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) -------------------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: gcc-devel libgcc-devel | -------------------------------------+--------------------------- Changes (by jmroot): * port: libgcc-devel => gcc-devel libgcc-devel -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:00:34 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 10:00:34 -0000 Subject: [MacPorts] #66365: libgcc-devel @12-20221202 build failure: sprintf is deprecated [-Werror=deprecated-declarations] (was: libgcc-devel @12-20221202: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64)) In-Reply-To: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> References: <045.ab93b609a9293b468373ec0f77d46a38@macports.org> Message-ID: <060.7359afc3a1bab2737d5e786d91756068@macports.org> #66365: libgcc-devel @12-20221202 build failure: sprintf is deprecated [-Werror =deprecated-declarations] -------------------------------------+--------------------------- Reporter: slackero | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: gcc-devel libgcc-devel | -------------------------------------+--------------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:03:04 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 10:03:04 -0000 Subject: [MacPorts] #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) In-Reply-To: <043.dc96f0184a0798ad208d10790ded6433@macports.org> References: <043.dc96f0184a0798ad208d10790ded6433@macports.org> Message-ID: <058.b89953525cfa793efa6b09451ecb1871@macports.org> #66523: libgcc-devel @12-20221212+stdlib_flag: Failed to build libgcc-devel: command execution failed (gcc-darwin-arm64) ---------------------------+--------------------------- Reporter: tjhart | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: ventura arm64 Port: libgcc-devel | ---------------------------+--------------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate Comment: #66365 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:18:39 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 10:18:39 -0000 Subject: [MacPorts] #66550: py310-pyobjc @9.0_0 fails to build on MacOS 10.10 Message-ID: <046.a97e0f6e101a3c2eaf2a4d7125c8da6a@macports.org> #66550: py310-pyobjc @9.0_0 fails to build on MacOS 10.10 -----------------------+----------------------- Reporter: macdeport | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: Yosemite | Port: py-pyobjc -----------------------+----------------------- {{{ :info:build creating '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/work/.tmp- vdw3xg70/pyobjc_framework_SystemConfiguration-9.0-cp36-abi3-macosx_10_10_x86_64.whl' and adding 'build/bdist.macosx-10.10-x86_64/wheel' to it :info:build adding 'SystemConfiguration/__init__.py' :info:build adding 'SystemConfiguration/_manual.abi3.so' :info:build adding 'SystemConfiguration/_metadata.py' :info:build adding 'pyobjc_framework_SystemConfiguration-9.0.dist- info/LICENSE.txt' :info:build adding 'pyobjc_framework_SystemConfiguration-9.0.dist- info/METADATA' :info:build adding 'pyobjc_framework_SystemConfiguration-9.0.dist- info/WHEEL' :info:build adding 'pyobjc_framework_SystemConfiguration-9.0.dist- info/top_level.txt' :info:build adding 'pyobjc_framework_SystemConfiguration-9.0.dist- info/RECORD' :info:build removing build/bdist.macosx-10.10-x86_64/wheel :info:build * Getting build dependencies for wheel... :info:build Successfully built pyobjc_framework_SystemConfiguration-9.0-cp36-abi3-macosx_10_10_x86_64.whl :info:build Modules/_SceneKit.m:77:5: error: use of undeclared identifier 'simd_float4x4' :info:build simd_float4x4 result; :info:build ^ :info:build Modules/_SceneKit.m:83:5: error: use of undeclared identifier 'result' :info:build result = SCNMatrix4ToMat4(arg); :info:build ^ :info:build Modules/_SceneKit.m:85:61: error: use of undeclared identifier 'result' :info:build return PyObjC_ObjCToPython("{_simd_float4x4=[4<4f>]}", &result); :info:build ^ :info:build Modules/_SceneKit.m:92:5: error: use of undeclared identifier 'simd_float4x4' :info:build simd_float4x4 arg; :info:build ^ :info:build Modules/_SceneKit.m:94:66: error: use of undeclared identifier 'arg'; did you mean 'carg'? :info:build if (PyObjC_PythonToObjC("{_simd_float4x4=[4<4f>]}", vector, &arg) == -1) { :info:build ^~~ :info:build carg :info:build /usr/include/complex.h:147:15: note: 'carg' declared here :info:build extern double carg(double complex); :info:build ^ :info:build Modules/_SceneKit.m:98:33: error: use of undeclared identifier 'arg' :info:build result = SCNMatrix4FromMat4(arg); :info:build ^ :info:build 6 errors generated. :info:build error: command '/usr/bin/clang' failed with exit code 1 :info:build /usr/bin/clang -bundle -undefined dynamic_lookup -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -arch x86_64 -isysroot/ build/temp.macosx-10.10-x86_64-cpython-310/Modules/_PrintCore.o -o build/lib.macosx-10.10-x86_64-cpython-310/PrintCore/_PrintCore.abi3.so -framework ApplicationServices :info:build running egg_info :info:build creating Lib/pyobjc_framework_CoreText.egg-info :info:build writing Lib/pyobjc_framework_CoreText.egg-info/PKG-INFO :info:build writing dependency_links to Lib/pyobjc_framework_CoreText.egg- info/dependency_links.txt :info:build writing requirements to Lib/pyobjc_framework_CoreText.egg- info/requires.txt :info:build writing top-level names to Lib/pyobjc_framework_CoreText.egg- info/top_level.txt :info:build writing manifest file 'Lib/pyobjc_framework_CoreText.egg- info/SOURCES.txt' :info:build ERROR Backend subprocess exited when trying to invoke build_wheel }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 10:21:28 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 10:21:28 -0000 Subject: [MacPorts] #66550: py310-pyobjc @9.0_0 fails to build on MacOS 10.10 In-Reply-To: <046.a97e0f6e101a3c2eaf2a4d7125c8da6a@macports.org> References: <046.a97e0f6e101a3c2eaf2a4d7125c8da6a@macports.org> Message-ID: <061.25a9a42311f481e0e70f1c5324512289@macports.org> #66550: py310-pyobjc @9.0_0 fails to build on MacOS 10.10 ------------------------+---------------------- Reporter: macdeport | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Yosemite Port: py-pyobjc | ------------------------+---------------------- Changes (by macdeport): * Attachment "main.log.zip" added. /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-pyobjc/py310-pyobjc/main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 13:31:53 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 13:31:53 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.0ad99207278b36f4a0cae241107fd0ef@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): you?re on 10.11 but the sdk is 10.12 the portgroup logic is supposed to fall back to the generic sdk in this case, but it thinks it?s finding the 10.11 sdk for some reason when it runs it?s checks? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 13:36:12 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 13:36:12 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.7606a4501e8633fc54872c2c346eb26e@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): have you made any sdk symlinks or otherwise modified the sdk folder in any way? if not, the testing logic is somehow broken for your case? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 14:29:01 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 14:29:01 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.4ec1a8ada9fcc09d6d920bafc04e6945@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): No symlinks anymore. I just installed MacOSX10.11.sdk through MacPorts ad mentioned. But that does not help. So now is the question ? can that be included or is it for nothing? And yes, it seems something is broken. These sdk things occur quite often, with several ports. I had it sometimes, others have it sometimes. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 15:27:02 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 15:27:02 -0000 Subject: [MacPorts] #65417: Rust 1.62.0 is now available In-Reply-To: <048.a3b9a5a4f0f190c13b9c7c444ff8447f@macports.org> References: <048.a3b9a5a4f0f190c13b9c7c444ff8447f@macports.org> Message-ID: <063.966fdd97804ad7883379ff0cd5381466@macports.org> #65417: Rust 1.62.0 is now available --------------------------+--------------------------------- Reporter: herbygillot | Owner: MarcusCalhoun-Lopez Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: Port: rust | --------------------------+--------------------------------- Changes (by herbygillot): * status: assigned => closed * resolution: => fixed Comment: Resolved by https://github.com/macports/macports- ports/commit/70793848c1faeae914d4d1c8b94e32a59afd343a -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 15:44:51 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 15:44:51 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.2d9e24c3d5d605e80750f6e06f8e2eb6@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): What did you install exactly? MacPorts has no committed, debugged, ability to install an SDK. Where did you put it? If you remove it, does it work again? Now that you have a machine that errors, you are in a unique position to debug a fix for it I would say. All my systems work, and as far as I know, all the buildbots too. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:29:54 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 17:29:54 -0000 Subject: [MacPorts] #66550: py310-pyobjc @9.0_0: error: use of undeclared identifier 'simd_float4x4' (was: py310-pyobjc @9.0_0 fails to build on MacOS 10.10) In-Reply-To: <046.a97e0f6e101a3c2eaf2a4d7125c8da6a@macports.org> References: <046.a97e0f6e101a3c2eaf2a4d7125c8da6a@macports.org> Message-ID: <061.f2c4bf6fc809fe09c17ccc74c12efeaf@macports.org> #66550: py310-pyobjc @9.0_0: error: use of undeclared identifier 'simd_float4x4' ------------------------+---------------------- Reporter: macdeport | Owner: danchr Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: yosemite Port: py-pyobjc | ------------------------+---------------------- Changes (by ryandesign): * owner: (none) => danchr * status: new => assigned * keywords: Yosemite => yosemite -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:44:03 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 17:44:03 -0000 Subject: [MacPorts] #66513: podman @4.3.1: env: python3: No such file or directory In-Reply-To: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> References: <047.a5c1a62bdad389c16322705c1e28c171@macports.org> Message-ID: <062.33152c70a4a7732dad1e45514bb739ca@macports.org> #66513: podman @4.3.1: env: python3: No such file or directory -------------------------+---------------------- Reporter: ryandesign | Owner: judaew Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: podman | -------------------------+---------------------- Comment (by Vadym-Valdis Yudaiev ): In [changeset:"37083831afe12004900a101a4831faecfb683047/macports-ports" 37083831afe12004900a101a4831faecfb683047/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="37083831afe12004900a101a4831faecfb683047" podman: Add patch to correctly find Python See https://trac.macports.org/ticket/66513 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 17:47:35 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 17:47:35 -0000 Subject: [MacPorts] #66511: ghostscript: Lost internet connectivity when fetching distfiles (was: Issue installing or upgrading ghostscript port) In-Reply-To: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> References: <045.4aacbfa74b1671898d9cafa3ea1aa188@macports.org> Message-ID: <060.bb53d438c1ae7b1a90795cfd90417da3@macports.org> #66511: ghostscript: Lost internet connectivity when fetching distfiles -----------------------+-------------------- Reporter: Hardies1 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | -----------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 24 19:38:31 2022 From: noreply at macports.org (MacPorts) Date: Sat, 24 Dec 2022 19:38:31 -0000 Subject: [MacPorts] #66217: Update fclones to 0.29.1 In-Reply-To: <048.dff646d959ef310440dc9ca0c0cd57d3@macports.org> References: <048.dff646d959ef310440dc9ca0c0cd57d3@macports.org> Message-ID: <063.b9138144061ee187c02f2541f70b4395@macports.org> #66217: Update fclones to 0.29.1 --------------------------+------------------------- Reporter: herbygillot | Owner: herbygillot Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: fclones | --------------------------+------------------------- Changes (by herbygillot): * status: assigned => closed * resolution: => fixed Comment: Updated in https://github.com/macports/macports- ports/commit/1ac39bb832eab140a55213490d7315e35949298b -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 06:34:20 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 06:34:20 -0000 Subject: [MacPorts] #66551: rapidjson-devel @20180424_1: error: 'sprintf' is deprecated Message-ID: <047.f116b0628e23af368376244777e5e6b2@macports.org> #66551: rapidjson-devel @20180424_1: error: 'sprintf' is deprecated ------------------------+----------------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: rapidjson-devel ------------------------+----------------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/6412/steps/install-port/logs/stdio {{{ example/jsonx/jsonx.cpp:37:43: error: 'sprintf' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Werror,-Wdeprecated-declarations] return WriteNumberElement(buffer, sprintf(buffer, "%d", i)); ^ }}} 20180424 seems like a fairly old version. Perhaps updating the port to a newer version would help. If not, the problem should be reported to the developers. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:19:40 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 08:19:40 -0000 Subject: [MacPorts] #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 In-Reply-To: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> References: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> Message-ID: <059.1d9a5d82790d0e04bfa954f6a9dd6661@macports.org> #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 -----------------------+--------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc11 | -----------------------+--------------------- Comment (by aforeman): Replying to [comment:2 ryandesign]: > Replying to [ticket:66398 imos-99]: > > {{{ > > :info:build xgcc: warning: could not understand version '13.0' > > }}} > > gcc11 might be too old to work on macOS 13. Did you try a newer version of gcc, like gcc12 or gcc-devel? This is installed as a dependancy of other packages. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:49:08 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 08:49:08 -0000 Subject: [MacPorts] #66552: Add a variant that supports 'persist' Message-ID: <043.859ecd723c1784d2c3ba9ba4e0efe9bc@macports.org> #66552: Add a variant that supports 'persist' -------------------------+---------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: opendoas -------------------------+---------------------- As far as I understand from the dev comment below, the `persist` option is unsupported by default and has to be enabled at build time Would you please add such a variant? [https://github.com/Duncaen/OpenDoas/issues/32] {{{ This has to be enabled explicitly at build time by running configure with --with-timestamp, the gentoo build doesn't do that. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 08:49:22 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 08:49:22 -0000 Subject: [MacPorts] #66552: Add a variant that supports 'persist' In-Reply-To: <043.859ecd723c1784d2c3ba9ba4e0efe9bc@macports.org> References: <043.859ecd723c1784d2c3ba9ba4e0efe9bc@macports.org> Message-ID: <058.5524ae68d362244532aae0837a2b6aff@macports.org> #66552: Add a variant that supports 'persist' --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: opendoas | --------------------------+-------------------- Description changed by esbugz: Old description: > As far as I understand from the dev comment below, the `persist` option > is unsupported by default and has to be enabled at build time > > Would you please add such a variant? > > [https://github.com/Duncaen/OpenDoas/issues/32] > {{{ > This has to be enabled explicitly at build time by running configure with > --with-timestamp, the gentoo build doesn't do that. > }}} New description: As far as I understand from the dev's comment below, the `persist` option is unsupported by default and has to be enabled at build time Would you please add such a variant? [https://github.com/Duncaen/OpenDoas/issues/32] {{{ This has to be enabled explicitly at build time by running configure with --with-timestamp, the gentoo build doesn't do that. }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 09:26:36 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 09:26:36 -0000 Subject: [MacPorts] #66512: rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++) In-Reply-To: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> References: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> Message-ID: <063.af404727170c91221247cba946306be1@macports.org> #66512: rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++) ------------------------------+--------------------- Reporter: cooljeanius | Owner: kimuraw Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: rb-eventmachine | ------------------------------+--------------------- Changes (by kimura wataru ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"fb00ab529a7adbb90a55e326b8d8efd3413a5603/macports-ports" fb00ab529a7adbb90a55e326b8d8efd3413a5603/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fb00ab529a7adbb90a55e326b8d8efd3413a5603" ruby/rb-eventmachine: delete old unmaintained ports with its dependencies closes https://trac.macports.org/ticket/66512 - rb-eventmachine -> rb-twitter-stream -> rb-tweetstream - rb19-eventmachine -> rb-em-websocket -> rb-guard-livereload -> rb-thin }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:22:04 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 14:22:04 -0000 Subject: [MacPorts] #66512: rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++) In-Reply-To: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> References: <048.cfcd4f86ff41f227a2ae2521be67f0c9@macports.org> Message-ID: <063.4f794c3f8f1df8252aed14a3ec97a981@macports.org> #66512: rb-eventmachine @0.12.10_1: rb-eventmachine is using libstdc++ (this installation is configured to use libc++) ------------------------------+--------------------- Reporter: cooljeanius | Owner: kimuraw Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: rb-eventmachine | ------------------------------+--------------------- Comment (by cooljeanius): aw man that's not exactly the outcome I was hoping for... oh well, I guess it works... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:53:05 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 14:53:05 -0000 Subject: [MacPorts] #66177: qt5-qtwebkit @5.9.2_4 fails to build In-Reply-To: <044.0893fa41b204973d4be592538766859d@macports.org> References: <044.0893fa41b204973d4be592538766859d@macports.org> Message-ID: <059.3c88e2ba0003cb69cbebde10a14e3d4d@macports.org> #66177: qt5-qtwebkit @5.9.2_4 fails to build ---------------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Changes (by jhoyt4): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports" 8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8b528349a8adb591352e8a81ec884764c7bb8e65" qt5-qtwebkit: Fix build for Big Sur, Monterey, and Ventura with header conflicts On case insensitive file systems, the include search path picks up header files from macports before the local header files causing an error while compiling. This modification places flags the known conflicting ports with conflicts_build. Closes: https://trac.macports.org/ticket/63877 Closes: https://trac.macports.org/ticket/62027 Closes: https://trac.macports.org/ticket/66177 Closes: https://trac.macports.org/ticket/63566 [skip ci] fun }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:53:05 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 14:53:05 -0000 Subject: [MacPorts] #62027: qt5-qtwebkit fails to build on Big Sur 11.1 with Apple silicon In-Reply-To: <043.f0d4a3537c6586a5941cca404e8d0a38@macports.org> References: <043.f0d4a3537c6586a5941cca404e8d0a38@macports.org> Message-ID: <058.5592601186c4c6e79c736fbfd55ad152@macports.org> #62027: qt5-qtwebkit fails to build on Big Sur 11.1 with Apple silicon ---------------------------+--------------------------------- Reporter: dfleck | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: bigsur arm64 Port: qt5-qtwebkit | ---------------------------+--------------------------------- Changes (by jhoyt4): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports" 8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8b528349a8adb591352e8a81ec884764c7bb8e65" qt5-qtwebkit: Fix build for Big Sur, Monterey, and Ventura with header conflicts On case insensitive file systems, the include search path picks up header files from macports before the local header files causing an error while compiling. This modification places flags the known conflicting ports with conflicts_build. Closes: https://trac.macports.org/ticket/63877 Closes: https://trac.macports.org/ticket/62027 Closes: https://trac.macports.org/ticket/66177 Closes: https://trac.macports.org/ticket/63566 [skip ci] fun }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:53:05 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 14:53:05 -0000 Subject: [MacPorts] #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 In-Reply-To: <041.64f540df932b21a27a6730e7853db9e4@macports.org> References: <041.64f540df932b21a27a6730e7853db9e4@macports.org> Message-ID: <056.acf1e0b90b5d87ba5414b2c3264ed7b6@macports.org> #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 ---------------------------+--------------------------------- Reporter: 6aKa | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Changes (by jhoyt4): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports" 8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8b528349a8adb591352e8a81ec884764c7bb8e65" qt5-qtwebkit: Fix build for Big Sur, Monterey, and Ventura with header conflicts On case insensitive file systems, the include search path picks up header files from macports before the local header files causing an error while compiling. This modification places flags the known conflicting ports with conflicts_build. Closes: https://trac.macports.org/ticket/63877 Closes: https://trac.macports.org/ticket/62027 Closes: https://trac.macports.org/ticket/66177 Closes: https://trac.macports.org/ticket/63566 [skip ci] fun }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:53:05 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 14:53:05 -0000 Subject: [MacPorts] #63566: qt5-qtwebkit fails to build on Mojave 10.14.6 In-Reply-To: <044.f2bce41259b840d2f68b66af87b7d8c0@macports.org> References: <044.f2bce41259b840d2f68b66af87b7d8c0@macports.org> Message-ID: <059.e279ae00becc6bec4a991b5987ba2916@macports.org> #63566: qt5-qtwebkit fails to build on Mojave 10.14.6 ---------------------------+--------------------------------- Reporter: ArtKoKo | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Changes (by jhoyt4): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports" 8b528349a8adb591352e8a81ec884764c7bb8e65/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="8b528349a8adb591352e8a81ec884764c7bb8e65" qt5-qtwebkit: Fix build for Big Sur, Monterey, and Ventura with header conflicts On case insensitive file systems, the include search path picks up header files from macports before the local header files causing an error while compiling. This modification places flags the known conflicting ports with conflicts_build. Closes: https://trac.macports.org/ticket/63877 Closes: https://trac.macports.org/ticket/62027 Closes: https://trac.macports.org/ticket/66177 Closes: https://trac.macports.org/ticket/63566 [skip ci] fun }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 14:57:05 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 14:57:05 -0000 Subject: [MacPorts] #62842: webkit2-gtk @2.28.2_2 +debug+minibrowser+quartz: error: use of undeclared identifier 'remoteProcessID' In-Reply-To: <048.d57a709e15594138625630d4fab16728@macports.org> References: <048.d57a709e15594138625630d4fab16728@macports.org> Message-ID: <063.7a59b427db71229b6c84cf63d9eccaff@macports.org> #62842: webkit2-gtk @2.28.2_2 +debug+minibrowser+quartz: error: use of undeclared identifier 'remoteProcessID' --------------------------+------------------------- Reporter: cooljeanius | Owner: cooljeanius Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: haspatch Port: webkit2-gtk | --------------------------+------------------------- Changes (by cooljeanius): * status: new => closed * owner: (none) => cooljeanius * resolution: => fixed Comment: In [changeset:"3549bacfa635797227cb3c1161429d7d829a5115/macports-ports" 3549bacfa635797227cb3c1161429d7d829a5115/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3549bacfa635797227cb3c1161429d7d829a5115" webkit2-gtk: fix quartz build on Big Sur possibly closes: https://trac.macports.org/ticket/62842 (untested) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 15:31:16 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 15:31:16 -0000 Subject: [MacPorts] #63566: qt5-qtwebkit fails to build on Mojave 10.14.6 In-Reply-To: <044.f2bce41259b840d2f68b66af87b7d8c0@macports.org> References: <044.f2bce41259b840d2f68b66af87b7d8c0@macports.org> Message-ID: <059.fa65a1d314c27857e75b93139d1a32cb@macports.org> #63566: qt5-qtwebkit fails to build on Mojave 10.14.6 ---------------------------+--------------------------------- Reporter: ArtKoKo | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by jhoyt4): to get this installed while a more permanent fix is identified do the following: {{{ sudo port -f deactivate libarchive ruby31 ruby30 libevent sudo port install qt5-qtwebkit sudo port -f activate libarchive ruby31 ruby30 libevent }}} Depending on what is installed on your system, you may need to adjust the deactivate/reactivate commands. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 15:31:28 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 15:31:28 -0000 Subject: [MacPorts] #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 In-Reply-To: <041.64f540df932b21a27a6730e7853db9e4@macports.org> References: <041.64f540df932b21a27a6730e7853db9e4@macports.org> Message-ID: <056.3c4ac7bcd17c4a2583189bf55254f841@macports.org> #63877: qt5-qtwebkit fails to build with Xcode 13.1 Big Sur and Monterey 12.0.1 ---------------------------+--------------------------------- Reporter: 6aKa | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by jhoyt4): to get this installed while a more permanent fix is identified do the following: {{{ sudo port -f deactivate libarchive ruby31 ruby30 libevent sudo port install qt5-qtwebkit sudo port -f activate libarchive ruby31 ruby30 libevent }}} Depending on what is installed on your system, you may need to adjust the deactivate/reactivate commands. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 15:31:39 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 15:31:39 -0000 Subject: [MacPorts] #66177: qt5-qtwebkit @5.9.2_4 fails to build In-Reply-To: <044.0893fa41b204973d4be592538766859d@macports.org> References: <044.0893fa41b204973d4be592538766859d@macports.org> Message-ID: <059.82d426fdc58c0ea8c0dc5c6faf2bde59@macports.org> #66177: qt5-qtwebkit @5.9.2_4 fails to build ---------------------------+--------------------------------- Reporter: dershow | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: qt5-qtwebkit | ---------------------------+--------------------------------- Comment (by jhoyt4): to get this installed while a more permanent fix is identified do the following: {{{ sudo port -f deactivate libarchive ruby31 ruby30 libevent sudo port install qt5-qtwebkit sudo port -f activate libarchive ruby31 ruby30 libevent }}} Depending on what is installed on your system, you may need to adjust the deactivate/reactivate commands. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 18:28:19 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 18:28:19 -0000 Subject: [MacPorts] #66553: nethack build error on macos ventura/arm M2 Message-ID: <044.de4c82f72724af7b07bd0512826f253b@macports.org> #66553: nethack build error on macos ventura/arm M2 ---------------------+--------------------- Reporter: asgalon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: nethack ---------------------+--------------------- Build error on port reinstall procedure after upgrade from Monterey to Ventura: {{{ :debug:build SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:build Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ CPP=/usr/bin/cpp :debug:build system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ CPP=/usr/bin/cpp :info:build make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released' :info:build ( cd src ; /Library/Developer/CommandLineTools/usr/bin/make ) :info:build make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released/src' :info:build /usr/bin/clang -Wall -Wextra -Wno-missing-field-initializers -Wimplicit -Wreturn-type -Wunused -Wformat -Wswitch -Wshadow -Wwrite- strings -DGCC_WARN -ansi -pedantic -Wno-long-long -O2 -I../include -DNOMAIL -DNOTPARMDECL -DHACKDIR=\"/opt/local/var/games/nethack\" -DDEFAULT_WINDOW_SYS=\"tty\" -DDLB -DGREPPATH=\"/usr/bin/grep\" -DSYSCF -DSYSCF_FILE=\"/opt/local/var/games/nethack/sysconf\" -DSECURE -c monst.c :info:build In file included from monst.c:6: :info:build In file included from ../include/config.h:581: :info:build In file included from ../include/global.h:9: :info:build In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/stdio.h:64: :info:build In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/_stdio.h:68: :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/sys/cdefs.h:309:39: error: too few arguments provided to function-like macro invocation :info:build #if __has_attribute(warn_unused_result) :info:build ^ :info:build 1 error generated. :info:build make[1]: *** [monst.o] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released/src' :info:build make: *** [nethack] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ CPP=/usr/bin/cpp :info:build Exit code: 2 :error:build Failed to build nethack: command execution failed :debug:build Error code: CHILDSTATUS 99249 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/main.log for details. }}} Informaci?n del hardware: Nombre del modelo: MacBook Air Identificador del modelo: Mac14,2 N?mero de modelo: MLY03Y/A Chip: Apple M2 Cantidad total de n?cleos: 8 (4 de rendimiento y 4 de eficiencia) Memoria: 8 GB Versi?n del firmware del sistema: 8419.41.10 Versi?n del cargador del sistema operativo: 8419.41.10 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 19:35:06 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 19:35:06 -0000 Subject: [MacPorts] #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) In-Reply-To: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> References: <049.a0d0d33d0e031cce6ab53721056712d7@macports.org> Message-ID: <064.38df6bb40297d0b794a6dedb48f28083@macports.org> #66159: gdk-pixbuf2 dependents malloc issue (PPC and Intel) ---------------------------+---------------------------------- Reporter: barracuda156 | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: leopard, snowleopard Port: gdk-pixbuf2 | ---------------------------+---------------------------------- Comment (by barracuda156): Replying to [comment:19 kencu]: Thank you! (Sorry that I dropped out of most discussions recently: travelling and therefore away from most of development work, and also busy with sorting out that huge PR for R.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sun Dec 25 21:54:42 2022 From: noreply at macports.org (MacPorts) Date: Sun, 25 Dec 2022 21:54:42 -0000 Subject: [MacPorts] #63792: valgrind-macos-devel: error: Valgrind works on Darwin 10.x-20.x (Mac OS X 10.6-10.11 and macOS 10.12-11.0) In-Reply-To: <051.94fc52cc2072ed305c1d49e26094740d@macports.org> References: <051.94fc52cc2072ed305c1d49e26094740d@macports.org> Message-ID: <066.d07e3fa45a0e11371808bdd4d50181e8@macports.org> #63792: valgrind-macos-devel: error: Valgrind works on Darwin 10.x-20.x (Mac OS X 10.6-10.11 and macOS 10.12-11.0) -----------------------------------+---------------------- Reporter: sudheerhebbale | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: monterey Port: valgrind-macos-devel | -----------------------------------+---------------------- Comment (by barracuda156): Valgrind is also broken for PPC, despite allegedly supporting 10.5. This is on Rosetta: ``` checking build system type... powerpc-apple-darwin10 checking host system type... powerpc-apple-darwin10 checking for a supported CPU... ok (powerpc) checking for a 64-bit only build... no checking for a 32-bit only build... yes checking for a supported OS... ok (darwin10) checking for the kernel version... Darwin 10.x (10.8.0) / Mac OS X 10.6 Snow Leopard checking for a supported CPU/OS combination... no (ppc32-darwin) configure: error: Valgrind is platform specific. Sorry. Please consider doing a port. ``` -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 02:37:10 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 02:37:10 -0000 Subject: [MacPorts] #65199: libproxy: add python310 variant? In-Reply-To: <043.39e2c0e868af7d928bd9a3c622c7efb3@macports.org> References: <043.39e2c0e868af7d928bd9a3c622c7efb3@macports.org> Message-ID: <058.f2c34128e04a41165c326c0ee5694308@macports.org> #65199: libproxy: add python310 variant? --------------------------+--------------------- Reporter: jowens | Owner: dbevans Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libproxy | --------------------------+--------------------- Changes (by evanmiller): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"59a82d2ee8f4b4d0f9f64ca5a2c74ce9865f2d95/macports-ports" 59a82d2ee8f4b4d0f9f64ca5a2c74ce9865f2d95/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="59a82d2ee8f4b4d0f9f64ca5a2c74ce9865f2d95" libproxy: add python31[01], drop python38 and below Closes: https://trac.macports.org/ticket/65199 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 02:44:25 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 02:44:25 -0000 Subject: [MacPorts] #66554: py-mutagen: add Python 3.11 Message-ID: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> #66554: py-mutagen: add Python 3.11 -------------------------+------------------------ Reporter: radarhere | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-mutagen -------------------------+------------------------ If a Python 3.11 subport could be added to py-mutagen, that would be good. Testing, I find that it works with py-mutagen on GitHub Actions - https://github.com/quodlibet/mutagen/pull/589 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 02:50:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 02:50:13 -0000 Subject: [MacPorts] #66532: MoltenVK: Add universal variant; don't install universal unless universal variant is selected In-Reply-To: <050.478450c82a0eb5cbbc05f9bee8e79303@macports.org> References: <050.478450c82a0eb5cbbc05f9bee8e79303@macports.org> Message-ID: <065.9aa28ef263b3d320872c6c7eb9942f44@macports.org> #66532: MoltenVK: Add universal variant; don't install universal unless universal variant is selected ----------------------------+------------------------ Reporter: MichaelGDev48 | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: MoltenVK | ----------------------------+------------------------ Changes (by Dean M Greer <38226388+Gcenx@?>): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"5a568933a230b358bb4070c4fad55bce00a48234/macports-ports" 5a568933a230b358bb4070c4fad55bce00a48234/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="5a568933a230b358bb4070c4fad55bce00a48234" MoltenVK: Add universal variant and strip arch when not universal closes https://trac.macports.org/ticket/66532 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 04:10:57 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 04:10:57 -0000 Subject: [MacPorts] #66428: helix 22.12: Budle runtime directory In-Reply-To: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> References: <048.8c0cc2c4a81dc9cc6f05a020531c59b6@macports.org> Message-ID: <063.fc67e10d371f82c6cf0f9d094ac3b607@macports.org> #66428: helix 22.12: Budle runtime directory --------------------------+------------------------- Reporter: pascalkuthe | Owner: herbygillot Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: helix | --------------------------+------------------------- Changes (by herbygillot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"3b1ebcfd1530187205e5b2ea6783e61db5c22fc1/macports-ports" 3b1ebcfd1530187205e5b2ea6783e61db5c22fc1/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3b1ebcfd1530187205e5b2ea6783e61db5c22fc1" helix: install wrapper script to set HELIX_RUNTIME - stop including grammar source and debugging symbols by default; these can still be installed through the "devel" variant if needed. Fixes: https://trac.macports.org/ticket/66428 Fixes: https://trac.macports.org/ticket/66525 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 04:10:58 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 04:10:58 -0000 Subject: [MacPorts] #66525: helix runtime should exclude SOURCES for grammars and debugging symbols to save 90+% In-Reply-To: <043.948d21a8b146efe0b608ead394d6cd91@macports.org> References: <043.948d21a8b146efe0b608ead394d6cd91@macports.org> Message-ID: <058.dabac695e6774e6e78aa95d3bf8d6b71@macports.org> #66525: helix runtime should exclude SOURCES for grammars and debugging symbols to save 90+% --------------------------+------------------------- Reporter: esbugz | Owner: herbygillot Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: helix | --------------------------+------------------------- Changes (by herbygillot): * status: new => closed * owner: (none) => herbygillot * resolution: => fixed Comment: In [changeset:"3b1ebcfd1530187205e5b2ea6783e61db5c22fc1/macports-ports" 3b1ebcfd1530187205e5b2ea6783e61db5c22fc1/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3b1ebcfd1530187205e5b2ea6783e61db5c22fc1" helix: install wrapper script to set HELIX_RUNTIME - stop including grammar source and debugging symbols by default; these can still be installed through the "devel" variant if needed. Fixes: https://trac.macports.org/ticket/66428 Fixes: https://trac.macports.org/ticket/66525 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 04:33:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 04:33:13 -0000 Subject: [MacPorts] #66534: LibreOffice fails to configure on install in macOS Ventura (13.1) because it can't find the correct macOS SDK. In-Reply-To: <050.67493431e544c05c6109577d7bd5f08b@macports.org> References: <050.67493431e544c05c6109577d7bd5f08b@macports.org> Message-ID: <065.aa9a11ebeec4e115fe5d0dfa3d867a5c@macports.org> #66534: LibreOffice fails to configure on install in macOS Ventura (13.1) because it can't find the correct macOS SDK. ----------------------------+---------------------- Reporter: LinuxRocks101 | Owner: Tatsh Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libreoffice | ----------------------------+---------------------- Comment (by LinuxRocks101): The repository was updated, and it gets farther. But now it fails to build: {{{ /bin/sh: line 1: 45835 Illegal instruction: 4 ( DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH:+$DYLD_LIBRARY_PATH:}"$I/LibreOffice.app/Contents/Frameworks:$I/LibreOffice.app/Contents/Frameworks" $I/LibreOffice.app/Contents/MacOS/gengal --build-tree --destdir file://$S/extras/source/gallery --name "backgrounds" --path $W/Gallery/backgrounds --filenames file://$RESPONSEFILE -env:UserInstallation=file://$W/Gallery/backgrounds/user ) > $W/Gallery/backgrounds.done.log 2>&1 gmake[1]: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1/solenv/gbuild/Gallery.mk:57: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1/workdir/Gallery/backgrounds.done] Error 1 gmake[1]: *** Waiting for unfinished jobs.... /bin/sh: line 1: 45839 Illegal instruction: 4 ( DYLD_LIBRARY_PATH=${DYLD_LIBRARY_PATH:+$DYLD_LIBRARY_PATH:}"$I/LibreOffice.app/Contents/Frameworks:$I/LibreOffice.app/Contents/Frameworks" $I/LibreOffice.app/Contents/MacOS/gengal --build-tree --destdir file://$S/extras/source/gallery --name "sounds" --path $W/Gallery/sounds --filenames file://$RESPONSEFILE -env:UserInstallation=file://$W/Gallery/sounds/user ) > $W/Gallery/sounds.done.log 2>&1 gmake[1]: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1/solenv/gbuild/Gallery.mk:57: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1/workdir/Gallery/sounds.done] Error 1 gmake[1]: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1' gmake: *** [Makefile:289: build] Error 2 gmake: Leaving directory '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_office_libreoffice/libreoffice/work/libreoffice-7.4.4.1" && /opt/local/bin/gmake -j4 -w build Exit code: 2 Error: Failed to build libreoffice: command execution failed }}} {{{ :debug:build Error code: CHILDSTATUS 5045 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" }}} It also throws a lot of these warnings around while building: {{{ ld: warning: dylib (*.dylib) was built for newer macOS version (13.0) than being linked (10.13) }}} Also, sorry if this isn't the right place for this. Just wanted to give an update from my end. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 07:04:38 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 07:04:38 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.d5ddd37bd1e8e32d5f5a8c3af0e7105c@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): I'm sorry, I was wrong. I missed that a MacOSX10.11.sdk port was added. Sorry. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 08:10:08 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 08:10:08 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.305f2d9c7ec17556cf0a50ad2be5362a@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): could you check to see if you have the MacOSX10.11.sdk in both or either of: /Library/Developer/CommandLineTools/SDKs and /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ I'm not really sure how things would work out if you had it in only one or the other place, but not both places. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 08:52:56 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 08:52:56 -0000 Subject: [MacPorts] #66491: py-pylint: The 'astroid<=2.12.0-dev0, >=2.11.6' distribution was not found and is required by pylint In-Reply-To: <041.3aee0b1f38554f7761985667fc3d8519@macports.org> References: <041.3aee0b1f38554f7761985667fc3d8519@macports.org> Message-ID: <056.29514d80375871407be18e651cc90f76@macports.org> #66491: py-pylint: The 'astroid<=2.12.0-dev0,>=2.11.6' distribution was not found and is required by pylint ------------------------------------+---------------------- Reporter: mf2k | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: fixed | Keywords: Port: py-pylint, py-astroid | ------------------------------------+---------------------- Changes (by reneeotten): * status: assigned => closed * resolution: => fixed Comment: fixed in [changeset:40de048dd63c55403915c99abf9e68579b8435b1/macports- ports this commit] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 08:54:42 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 08:54:42 -0000 Subject: [MacPorts] #66528: py311-pyqt5 missing dependency dbus-python311 In-Reply-To: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> References: <043.b34b59e53ae54d090f962ec4f51250e0@macports.org> Message-ID: <058.56f95a19994959fa6e8ccfba4fb30df2@macports.org> #66528: py311-pyqt5 missing dependency dbus-python311 -----------------------------------+------------------------ Reporter: Fut1l3 | Owner: reneeotten Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-pyqt5 dbus-python | -----------------------------------+------------------------ Changes (by reneeotten): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"a1a7e1421f7425555623639616d9367aab7c13b2/macports-ports" a1a7e1421f7425555623639616d9367aab7c13b2/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a1a7e1421f7425555623639616d9367aab7c13b2" dbus-python: add py311 subport Closes: https://trac.macports.org/ticket/66528 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 11:08:05 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 11:08:05 -0000 Subject: [MacPorts] #66555: Why MacPorts could consider to rename its ''master'' branch to **main** Message-ID: <045.11114328b79374db7bc31cbc3107c90b@macports.org> #66555: Why MacPorts could consider to rename its ''master'' branch to **main** ----------------------+----------------------------- Reporter: Zweihorn | Owner: (none) Type: request | Status: new Priority: Low | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Keywords: | Port: ----------------------+----------------------------- Hi, The MacPorts Project may consider to rename its ''master'' branch to **main** For the rationale please refer to this news article: - - - Why GitHub renamed its ''master'' branch to **main** The GitHub master branch is no more. Developers used to think it was untouchable, but that's not the case. Here's why GitHub made the switch from master branch to main branch. https://www.theserverside.com/feature/Why-GitHub-renamed-its-master- branch-to-main - - - Keep on the good work and prosper. NB - Merry Christmas Cheers, Zweihorn -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 11:29:35 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 11:29:35 -0000 Subject: [MacPorts] #66555: Why MacPorts could consider to rename its ''master'' branch to **main** In-Reply-To: <045.11114328b79374db7bc31cbc3107c90b@macports.org> References: <045.11114328b79374db7bc31cbc3107c90b@macports.org> Message-ID: <060.627be05e1b72faff4845b5a990bdc2b1@macports.org> #66555: Why MacPorts could consider to rename its ''master'' branch to **main** -----------------------+----------------------------- Reporter: Zweihorn | Owner: (none) Type: request | Status: new Priority: Low | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | -----------------------+----------------------------- Comment (by Zweihorn): Maybe @raimue should be aware of this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 11:49:39 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 11:49:39 -0000 Subject: [MacPorts] #66555: Why MacPorts could consider to rename its ''master'' branch to **main** In-Reply-To: <045.11114328b79374db7bc31cbc3107c90b@macports.org> References: <045.11114328b79374db7bc31cbc3107c90b@macports.org> Message-ID: <060.c657fd5a2cf32d699d16c3b07386ae23@macports.org> #66555: Why MacPorts could consider to rename its ''master'' branch to **main** -----------------------+----------------------------- Reporter: Zweihorn | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | -----------------------+----------------------------- Changes (by Zweihorn): * priority: Low => Normal Comment: Priority changed to 'normal' after a 'low' start to not get lost, hopefully. However, this may be of low priority and considered as a request for the MacPorts Future in general please. Cheers, Zweihorn -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 14:29:58 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 14:29:58 -0000 Subject: [MacPorts] #66556: Error Building poppler-qt4-mac Message-ID: <042.8ec96dada093e691bf99987de76ccadd@macports.org> #66556: Error Building poppler-qt4-mac --------------------+----------------------------- Reporter: neilt | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: poppler-qt4-mac --------------------+----------------------------- {{{ version:1 :debug:main Starting logging for poppler-qt4-mac @0.61.1_3 :debug:sysinfo macOS 12.6.2 (darwin/21.6.0) arch i386 :debug:sysinfo MacPorts 2.8.0 :debug:sysinfo Xcode 14.2, CLT 14.2.0.0.1.1668646533 :debug:sysinfo SDK 12 :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 12.0 }}} {{{ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_graphics_poppler-qt4-mac/poppler- qt4-mac/work/poppler-0.61.1/glib/poppler-action.cc:28:1: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_graphics_poppler-qt4-mac/poppler- qt4-mac/work/poppler-0.61.1/glib/poppler-action.cc:96:1: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_graphics_poppler-qt4-mac/poppler- qt4-mac/work/poppler-0.61.1/glib/poppler-document.cc:1743:1: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 15:00:43 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 15:00:43 -0000 Subject: [MacPorts] #66555: Why MacPorts could consider to rename its ''master'' branch to **main** In-Reply-To: <045.11114328b79374db7bc31cbc3107c90b@macports.org> References: <045.11114328b79374db7bc31cbc3107c90b@macports.org> Message-ID: <060.050807a762d240f81e4fbceb53234a59@macports.org> #66555: Why MacPorts could consider to rename its ''master'' branch to **main** -----------------------+----------------------------- Reporter: Zweihorn | Owner: (none) Type: request | Status: closed Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: Port: | -----------------------+----------------------------- Changes (by raimue): * status: new => closed * resolution: => invalid Comment: Thank you for bringing this to our attention. The rename of the git branch has been suggested before, but many of the [https://github.com/macports /macports-infrastructure/ infrastructure scripts] still depend on the "master" branch name. Previous answer from Ryan: https://lists.macports.org/pipermail/macports- dev/2021-March/043075.html Furthermore, renaming the branch in git would only be one thing. To take this seriously, there would be more changes needed, most prominently the `master_sites` option in Portfiles. Unfortunately, I do not think this ticket will bring the issue forward. This ticket is phrased to consider a rename, but the problem is not that anyone has to take a decision, but it needs someone to execute it. I do not believe this could be coordinated over a single ticket, as it is a change spread over multiple repositories and servers. I am therefore closing this ticket, but I do not mean to dismiss the issue. Please bring it up on the [wiki:MailingLists macports-dev mailing list] instead, as first of all we need people willing to invest time into this transition. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 16:22:38 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 16:22:38 -0000 Subject: [MacPorts] #66557: Add to MacPorts Guide an explanation how to disable sudo password requirements for non-sensitive commands Message-ID: <043.75bb3c93405887259a94b599f34eca38@macports.org> #66557: Add to MacPorts Guide an explanation how to disable sudo password requirements for non-sensitive commands -------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Keywords: | Port: -------------------------+-------------------- One of the more painful elements of using MacPorts vs Homebrew is the need for `sudo` for most operations. While some operations may benefit from such a security limit, not all do. For example, updating MacPorts itself or the port registry isn't a dangerous operation that installing a new package can be But it's possible to remove the pain and exclude these commands from requiring a password by editing your `/etc/sudoers` file (see an example below). It would be great is this were mentioned prominently in the **Guide** {{{ ## !change 'YourUserNAME' below to your actual user name #? MacPorts: user can selfupdate, upgrade/uninstall any package (or use %staff group instead of YourUserName) YourUserNAME ALL=(root) NOPASSWD: /opt/local/bin/port selfupdate * # MacPorts: update MacPorts base code & Portfiles YourUserNAME ALL=(root) NOPASSWD: /opt/local/bin/port upgrade * # MacPorts: upgrade a package YourUserNAME ALL=(root) NOPASSWD: /opt/local/bin/port clean * # MacPorts: clean intermediate files YourUserNAME ALL=(root) NOPASSWD: /opt/local/bin/port reclaim * # MacPorts: cleanup inactive ports YourUserNAME ALL=(root) NOPASSWD: /opt/local/bin/port_cutleaves # MacPorts: uninstall unneded dependencies (leaves) YourUserNAME ALL=(root) NOPASSWD: /opt/local/bin/port uninstall * # MacPorts: uninstall a package # #UserList HostList=EffectiveUserList TagList CommandList #? list of users already created # ? list of hosts where the users can run sudo # ? list of the users who might be running as an alias # tags such as NOPASSWD ? # commands we don't want to write the passwords to? }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 17:18:33 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 17:18:33 -0000 Subject: [MacPorts] #66558: Problem with Control key. Message-ID: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> #66558: Problem with Control key. ---------------------+----------------------------- Reporter: eazy0ne | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: Keywords: | Port: atari800 ---------------------+----------------------------- Control key does not work, so special characters cannot be entered in Atari BASIC. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 18:30:37 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 18:30:37 -0000 Subject: [MacPorts] #66559: gtk-doc: update to python 3.11? Message-ID: <043.1adf593d517732f393065f4ec1c567cb@macports.org> #66559: gtk-doc: update to python 3.11? --------------------+--------------------- Reporter: jowens | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gtk-doc --------------------+--------------------- Currently python310 is the default and there's no 311 variant. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 18:31:53 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 18:31:53 -0000 Subject: [MacPorts] #66560: itstool: update to python 3.11? Message-ID: <043.cfd3ccc88b08499e00caae5c0ce071f8@macports.org> #66560: itstool: update to python 3.11? --------------------+--------------------- Reporter: jowens | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: itstool --------------------+--------------------- itstool has variants up to python 3.10. Would it be possible to add a 3.11 variant? Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 18:35:13 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 18:35:13 -0000 Subject: [MacPorts] #66561: py-altair: add python311? Message-ID: <043.ee8c8d9ce11878212be00389d0010426@macports.org> #66561: py-altair: add python311? --------------------+----------------------- Reporter: jowens | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-altair --------------------+----------------------- Any chance of adding python 3.11 to py-altair? Thanks. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 18:40:42 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 18:40:42 -0000 Subject: [MacPorts] #66555: Why MacPorts could consider to rename its ''master'' branch to **main** In-Reply-To: <045.11114328b79374db7bc31cbc3107c90b@macports.org> References: <045.11114328b79374db7bc31cbc3107c90b@macports.org> Message-ID: <060.f92516733d1a3d03a6725ed1b802cee1@macports.org> #66555: Why MacPorts could consider to rename its ''master'' branch to **main** -----------------------+----------------------------- Reporter: Zweihorn | Owner: (none) Type: request | Status: closed Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.8.0 Resolution: invalid | Keywords: Port: | -----------------------+----------------------------- Comment (by Zweihorn): THX I am rather neutral on this and just wanted to learn of your deliberations (or not). You already fully met my expectations by this friendly reply and kind advice. What might have looked like a simple name change at first could bring MacPorts ports and update process into troubled water, apparently. As the word 'master' should in no way be problematic itself the a.m. rationale from you is more than sufficient IMO. Case closed. Conversation most appreciated. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 19:30:39 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 19:30:39 -0000 Subject: [MacPorts] #66562: provide cutting edge Minetest by minetest-devel Message-ID: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> #66562: provide cutting edge Minetest by minetest-devel -------------------------+---------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: x86_64 | Port: minetest -------------------------+---------------------- The long standing minetest port derives new versions by just updating the sources and the checksums apparently. Certain defaults and specialities in the build seem to have been overlooked from the start of this almost historic port or have changed over time. If not for the well maintained irrlichtmt port this unmaintained port could be called rather outdated in some aspects. Anyway the resulting App cannot be called optimal. My cc to the maintainer of the irrlichtmt port is just for information. Naturally, combined with my most friendly thank you for his commitment. (A) There is a new port minetest-devel in the making and a new PR already in the queue to come around. The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 and MT 5.6.1. The current MT runs on Big Sur as a local port as was done with all the predecessors before on othe macOS versions respectively. (B) My PR may solve the below issue too, although I have to check the details again first. Or do you? - #66408 (C) You may note I would volunteer to become the maintainer of both the new minetest-devel as the legacy minetest port together, if this would find your approval. (D) Please kindly note that I already advertised for MacPorts at the Minetest community in the past with at least some success. Please have a look at: - https://forum.minetest.net/viewtopic.php?f=42&t=22427 - https://www.minetest.net/downloads/ --> macOS - MacPorts My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in parallel to my now re-opened old account at the MT Forum for technical reasons only. (E) Only after well establishing minetest-devel and learning if the expectations raised by my work are met on most if not all platforms, I would consider improving minetest e.g., by making the build more consistant and introducing a '--legacy' variant to help some users of the legacy port. (F) In the future both ports minetest and minetest-devel should continue, as a new MT 5.6.2 may be understood stable but a new MT 5.7.0 would be work in progress. AFAIK on top of that it is tradition with Minetest players to stick with an older version as long as possible. (G) Please accept my sincere apologies in advance if I do not cover all aspects of your ticket process as I only came back recently after some longe break. Obviously, I have to make myself more familiar with MacPort internals again. Some if not all of the above will be copied in to a.m. PR in due time. Stay tuned. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 19:41:22 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 19:41:22 -0000 Subject: [MacPorts] #66562: provide cutting edge Minetest by minetest-devel In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.323f424d43209906501bad2473452266@macports.org> #66562: provide cutting edge Minetest by minetest-devel --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+-------------------- Comment (by Zweihorn): NB - Merry Christmas and a Happy New Year Keep on the good work and prosper. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 21:00:59 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 21:00:59 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.88334ef1d4d0aa8f7e0ee2289fe81626@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: fixed | Keywords: Port: svt-av1 | ----------------------+------------------------ Changes (by mf2k): * status: assigned => closed * resolution: => fixed Comment: This was fixed at some point. Possibly in the cmake portgroup. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 21:06:07 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 21:06:07 -0000 Subject: [MacPorts] #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build/_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. In-Reply-To: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> References: <041.e7de96f63ef62bcab97d6247eebc975e@macports.org> Message-ID: <056.19535fd9007e0df8b4fc02d2c2429152@macports.org> #66437: svt-av1: CMake Error: The source directory "/opt/local/var/macports/build /_opt_mports_macports-ports_multimedia_svt-av1/svt-av1/work/SVT-AV1-1.4.0" does not exist. ----------------------+------------------------ Reporter: mf2k | Owner: i0ntempest Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: svt-av1 | ----------------------+------------------------ Changes (by mf2k): * status: closed => reopened * resolution: fixed => Comment: Sorry, not fixed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 22:21:25 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 22:21:25 -0000 Subject: [MacPorts] #66562: provide cutting edge Minetest by minetest-devel In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.7bebb3e388bc4ba23cf952ef5392ed5c@macports.org> #66562: provide cutting edge Minetest by minetest-devel --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+-------------------- Comment (by Zweihorn): New PR titled "the new minetest-devel port delivering a cutting edge Minetest to MacPorts # 17061" available at GitHub. The a.m. PR is WIP at: https://github.com/macports/macports- ports/pull/17061 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 22:30:26 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 22:30:26 -0000 Subject: [MacPorts] #66487: gtk3 menues broken with macos ventura - update needed In-Reply-To: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> References: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> Message-ID: <061.eb8c9f0615c1a398fc7eefb7701561ec@macports.org> #66487: gtk3 menues broken with macos ventura - update needed ------------------------+---------------------- Reporter: MStraeten | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gtk3 | ------------------------+---------------------- Comment (by dqh-au): (VICE emulator mac maintainer here, we use MacPorts to make our Intel binaries for macOS 10.10+) This problem is fixed in 3.24.36, which Homebrew have updated to in the last couple of days. Could MacPorts please update to 3.24.36? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:00:56 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 23:00:56 -0000 Subject: [MacPorts] #66563: refurb @1.9.1: ModuleNotFoundError: No module named 'poetry' Message-ID: <047.8554fa019e643f510c80c939cf1eba51@macports.org> #66563: refurb @1.9.1: ModuleNotFoundError: No module named 'poetry' ------------------------+------------------------ Reporter: ryandesign | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: refurb ------------------------+------------------------ https://build.macports.org/builders/ports- 12_arm64-builder/builds/79324/steps/install-port/logs/stdio {{{ * Getting build dependencies for wheel... Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pep517/wrappers.py", line 319, in _call_hook raise BackendUnavailable(data.get('traceback', '')) pep517.wrappers.BackendUnavailable: Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/pep517/in_process/_in_process.py", line 77, in _build_backend obj = import_module(mod_path) File "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 992, in _find_and_load_unlocked File "", line 241, in _call_with_frames_removed File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 992, in _find_and_load_unlocked File "", line 241, in _call_with_frames_removed File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 992, in _find_and_load_unlocked File "", line 241, in _call_with_frames_removed File "", line 1050, in _gcd_import File "", line 1027, in _find_and_load File "", line 1004, in _find_and_load_unlocked ModuleNotFoundError: No module named 'poetry' ERROR Backend 'poetry.core.masonry.api' is not available. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:05:54 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 23:05:54 -0000 Subject: [MacPorts] #66564: funny typo at MP Account's Profile Web GUI Message-ID: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> #66564: funny typo at MP Account's Profile Web GUI ----------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: website | Version: Keywords: | Port: ----------------------+-------------------- Please correct the typo "Mange" into the correct "Manage"at https://ports.macports.org/accounts/profile/ At least "GitHub" and "Email" have this funny typo, I presume. See red brackets in the attach. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:07:18 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 23:07:18 -0000 Subject: [MacPorts] #66564: funny typo at MP Account's Profile Web GUI In-Reply-To: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> References: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> Message-ID: <060.e43c8ad227569e94cbd35830005cf4a5@macports.org> #66564: funny typo at MP Account's Profile Web GUI -----------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: website | Version: Resolution: | Keywords: Port: | -----------------------+-------------------- Changes (by Zweihorn): * Attachment "Bildschirmfoto 2022-12-27 um 00.00.42.png" added. picture of the GUI with typo marked in red boxes -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Mon Dec 26 23:36:04 2022 From: noreply at macports.org (MacPorts) Date: Mon, 26 Dec 2022 23:36:04 -0000 Subject: [MacPorts] #66487: gtk3 menues broken with macos ventura - update needed In-Reply-To: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> References: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> Message-ID: <061.c20e062bf1c261e27dd3c05aa8c1c199@macports.org> #66487: gtk3 menues broken with macos ventura - update needed ------------------------+---------------------- Reporter: MStraeten | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gtk3 | ------------------------+---------------------- Comment (by dqh-au): Ugh, they dropped autoconf so the port file needs to be updated to use meson :( -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:34:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:34:49 -0000 Subject: [MacPorts] #66564: funny typo at MP Account's Profile Web GUI In-Reply-To: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> References: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> Message-ID: <060.db754d1c4e34c2793a018cde5f293562@macports.org> #66564: funny typo at MP Account's Profile Web GUI -----------------------+------------------------ Reporter: Zweihorn | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: website | Version: Resolution: | Keywords: Port: | -----------------------+------------------------ Changes (by ryandesign): * status: new => accepted * owner: (none) => ryandesign Comment: Thanks for reporting this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:38:24 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:38:24 -0000 Subject: [MacPorts] #66564: funny typo at MP Account's Profile Web GUI In-Reply-To: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> References: <045.1bc080277fd5f64de03fa2a986982f53@macports.org> Message-ID: <060.265e9b37a0d409000bdf3d6f24ca46f0@macports.org> #66564: funny typo at MP Account's Profile Web GUI -----------------------+------------------------ Reporter: Zweihorn | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: website | Version: Resolution: fixed | Keywords: Port: | -----------------------+------------------------ Changes (by ryandesign): * status: accepted => closed * resolution: => fixed Comment: Fixed in [8bcb219c6d6a82e5042307f3b61ec892cb5aed25/macports-webapp]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:38:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:38:41 -0000 Subject: [MacPorts] #66565: Recognize macports-webapp GitHub repository Message-ID: <047.2e625d01c01140a892417855750e24a4@macports.org> #66565: Recognize macports-webapp GitHub repository ------------------------+--------------------- Reporter: ryandesign | Owner: admin@? Type: defect | Status: new Priority: Normal | Milestone: Component: trac | Version: Keywords: | Port: ------------------------+--------------------- Please recognize the GitHub repository "macports-webapp" so that I can write TracLinks to its commits, etc. (such as in comment:ticket:66564:2). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:39:33 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:39:33 -0000 Subject: [MacPorts] #66558: atari800: Problem with Control key. (was: Problem with Control key.) In-Reply-To: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> References: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> Message-ID: <059.fcf942b9f96d9724b6049ef16de68b05@macports.org> #66558: atari800: Problem with Control key. -----------------------+---------------------- Reporter: eazy0ne | Owner: krischik Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: atari800 | -----------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: (none) => krischik * milestone: MacPorts Future => Comment: The "Milestone" field is only used when the "Component" field is "base". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:41:16 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:41:16 -0000 Subject: [MacPorts] #66556: poppler-qt4-mac: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') (was: Error Building poppler-qt4-mac) In-Reply-To: <042.8ec96dada093e691bf99987de76ccadd@macports.org> References: <042.8ec96dada093e691bf99987de76ccadd@macports.org> Message-ID: <057.6021e8a48f61ed5499d52d96f3bd55b8@macports.org> #66556: poppler-qt4-mac: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') ------------------------------+-------------------- Reporter: neilt | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: poppler-qt4-mac | ------------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:43:26 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:43:26 -0000 Subject: [MacPorts] #66553: nethack: error: too few arguments provided to function-like macro invocation (was: nethack build error on macos ventura/arm M2) In-Reply-To: <044.de4c82f72724af7b07bd0512826f253b@macports.org> References: <044.de4c82f72724af7b07bd0512826f253b@macports.org> Message-ID: <059.8d10384c5740a040970f9ae74165a571@macports.org> #66553: nethack: error: too few arguments provided to function-like macro invocation ----------------------+---------------------- Reporter: asgalon | Owner: jflude Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: nethack | ----------------------+---------------------- Changes (by ryandesign): * status: new => assigned * cc: Nax (added) * owner: (none) => jflude * keywords: => ventura Old description: > Build error on port reinstall procedure after upgrade from Monterey to > Ventura: > > {{{ > :debug:build > SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' > :info:build Executing: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" > && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ > CPP=/usr/bin/cpp > :debug:build system: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" > && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ > CPP=/usr/bin/cpp > :info:build make: Entering directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work > /NetHack-NetHack-3.6.6_Released' > :info:build ( cd src ; /Library/Developer/CommandLineTools/usr/bin/make ) > :info:build make[1]: Entering directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work > /NetHack-NetHack-3.6.6_Released/src' > :info:build /usr/bin/clang -Wall -Wextra -Wno-missing-field-initializers > -Wimplicit -Wreturn-type -Wunused -Wformat -Wswitch -Wshadow -Wwrite- > strings -DGCC_WARN -ansi -pedantic -Wno-long-long -O2 -I../include > -DNOMAIL -DNOTPARMDECL -DHACKDIR=\"/opt/local/var/games/nethack\" > -DDEFAULT_WINDOW_SYS=\"tty\" -DDLB -DGREPPATH=\"/usr/bin/grep\" -DSYSCF > -DSYSCF_FILE=\"/opt/local/var/games/nethack/sysconf\" -DSECURE -c monst.c > :info:build In file included from monst.c:6: > :info:build In file included from ../include/config.h:581: > :info:build In file included from ../include/global.h:9: > :info:build In file included from > /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/stdio.h:64: > :info:build In file included from > /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/_stdio.h:68: > :info:build > /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/sys/cdefs.h:309:39: > error: too few arguments provided to function-like macro invocation > :info:build #if __has_attribute(warn_unused_result) > :info:build ^ > :info:build 1 error generated. > :info:build make[1]: *** [monst.o] Error 1 > :info:build make[1]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work > /NetHack-NetHack-3.6.6_Released/src' > :info:build make: *** [nethack] Error 2 > :info:build make: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work > /NetHack-NetHack-3.6.6_Released' > :info:build Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" > && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ > CPP=/usr/bin/cpp > :info:build Exit code: 2 > :error:build Failed to build nethack: command execution failed > :debug:build Error code: CHILDSTATUS 99249 2 > :debug:build Backtrace: command execution failed > :debug:build while executing > :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" > :debug:build invoked from within > :debug:build "command_exec -callback > portprogress::target_progress_callback build" > :debug:build (procedure "portbuild::build_main" line 8) > :debug:build invoked from within > :debug:build "$procedure $targetname" > :error:build See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/main.log > for details. > > }}} > > Informaci?n del hardware: > > Nombre del modelo: MacBook Air > Identificador del modelo: Mac14,2 > N?mero de modelo: MLY03Y/A > Chip: Apple M2 > Cantidad total de n?cleos: 8 (4 de rendimiento y 4 de eficiencia) > Memoria: 8 GB > Versi?n del firmware del sistema: 8419.41.10 > Versi?n del cargador del sistema operativo: 8419.41.10 New description: Build error on port reinstall procedure after upgrade from Monterey to Ventura: {{{ :debug:build SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk' :info:build Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ CPP=/usr/bin/cpp :debug:build system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ CPP=/usr/bin/cpp :info:build make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released' :info:build ( cd src ; /Library/Developer/CommandLineTools/usr/bin/make ) :info:build make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released/src' :info:build /usr/bin/clang -Wall -Wextra -Wno-missing-field-initializers -Wimplicit -Wreturn-type -Wunused -Wformat -Wswitch -Wshadow -Wwrite- strings -DGCC_WARN -ansi -pedantic -Wno-long-long -O2 -I../include -DNOMAIL -DNOTPARMDECL -DHACKDIR=\"/opt/local/var/games/nethack\" -DDEFAULT_WINDOW_SYS=\"tty\" -DDLB -DGREPPATH=\"/usr/bin/grep\" -DSYSCF -DSYSCF_FILE=\"/opt/local/var/games/nethack/sysconf\" -DSECURE -c monst.c :info:build In file included from monst.c:6: :info:build In file included from ../include/config.h:581: :info:build In file included from ../include/global.h:9: :info:build In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/stdio.h:64: :info:build In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/_stdio.h:68: :info:build /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/sys/cdefs.h:309:39: error: too few arguments provided to function-like macro invocation :info:build #if __has_attribute(warn_unused_result) :info:build ^ :info:build 1 error generated. :info:build make[1]: *** [monst.o] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released/src' :info:build make: *** [nethack] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work /NetHack-NetHack-3.6.6_Released' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/work/nethack-3.6.6" && /usr/bin/make -j1 -w all CC=/usr/bin/clang CXX=/usr/bin/clang++ CPP=/usr/bin/cpp :info:build Exit code: 2 :error:build Failed to build nethack: command execution failed :debug:build Error code: CHILDSTATUS 99249 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_games_nethack/nethack/main.log for details. }}} {{{ Informaci?n del hardware: Nombre del modelo: MacBook Air Identificador del modelo: Mac14,2 N?mero de modelo: MLY03Y/A Chip: Apple M2 Cantidad total de n?cleos: 8 (4 de rendimiento y 4 de eficiencia) Memoria: 8 GB Versi?n del firmware del sistema: 8419.41.10 Versi?n del cargador del sistema operativo: 8419.41.10 }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:43:41 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:43:41 -0000 Subject: [MacPorts] #66553: nethack: error: too few arguments provided to function-like macro invocation In-Reply-To: <044.de4c82f72724af7b07bd0512826f253b@macports.org> References: <044.de4c82f72724af7b07bd0512826f253b@macports.org> Message-ID: <059.98c308beb2fb36d3593140593b00925e@macports.org> #66553: nethack: error: too few arguments provided to function-like macro invocation ------------------------+--------------------- Reporter: asgalon | Owner: jflude Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: ventura Port: nethack | ------------------------+--------------------- Changes (by ryandesign): * status: assigned => closed * resolution: => duplicate Comment: Duplicate of #66092. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:44:26 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:44:26 -0000 Subject: [MacPorts] #66092: nethack: error: too few arguments provided to function-like macro invocation (was: nethack: build failure on macOS 13) In-Reply-To: <049.0be152501cd40086b61e90ef054178aa@macports.org> References: <049.0be152501cd40086b61e90ef054178aa@macports.org> Message-ID: <064.2c38e3e6583c929c47cff4f729d4294f@macports.org> #66092: nethack: error: too few arguments provided to function-like macro invocation ---------------------------+---------------------- Reporter: ShadSterling | Owner: jflude Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: nethack | ---------------------------+---------------------- Changes (by ryandesign): * cc: asgalon (added) Comment: Has duplicate #66553. jflude, it sounded like you had an idea of how this might be fixed; if so, please share it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 00:45:06 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 00:45:06 -0000 Subject: [MacPorts] #66552: opendoas: Add a variant that supports 'persist' (was: Add a variant that supports 'persist') In-Reply-To: <043.859ecd723c1784d2c3ba9ba4e0efe9bc@macports.org> References: <043.859ecd723c1784d2c3ba9ba4e0efe9bc@macports.org> Message-ID: <058.0c31647f8fccf1ba1d25086f48d49938@macports.org> #66552: opendoas: Add a variant that supports 'persist' --------------------------+---------------------- Reporter: esbugz | Owner: danchr Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: opendoas | --------------------------+---------------------- Changes (by ryandesign): * cc: danchr (removed) * status: new => assigned * owner: (none) => danchr -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 01:11:54 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 01:11:54 -0000 Subject: [MacPorts] #65329: ruby-build @20220426: Improper dependency specification In-Reply-To: <047.7e6604dc0168b16b33124847ae26d9b6@macports.org> References: <047.7e6604dc0168b16b33124847ae26d9b6@macports.org> Message-ID: <062.d753ba20b2b10846d7a6078369770714@macports.org> #65329: ruby-build @20220426: Improper dependency specification -------------------------+---------------------- Reporter: halostatue | Owner: mojca Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: Port: ruby-build | -------------------------+---------------------- Comment (by halostatue): I have implemented this both ways: * [[https://github.com/macports/macports-ports/pull/16274|#16274]], where `rbenv` now has a variant to add `ruby-build` and `ruby-build` no longer depends on `rbenv`. This is the *correct* fix, but it may be deemed incompatible with existing versions. * [[https://github.com/macports/macports-ports/pull/16273|#16273]], where `ruby-build` now as a variant `+standalone` to skip installing `rbenv`. This is not the correct fix, but it is more compatible. I personally prefer the former, but would like to see this resolved. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 02:06:45 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 02:06:45 -0000 Subject: [MacPorts] #66559: gtk-doc: add python311 variant (was: gtk-doc: update to python 3.11?) In-Reply-To: <043.1adf593d517732f393065f4ec1c567cb@macports.org> References: <043.1adf593d517732f393065f4ec1c567cb@macports.org> Message-ID: <058.04474f44ad755c2436b85cfcfcd2bd60@macports.org> #66559: gtk-doc: add python311 variant --------------------------+---------------------- Reporter: jowens | Owner: mascguy Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtk-doc | --------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * owner: (none) => mascguy * type: update => enhancement -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 02:07:18 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 02:07:18 -0000 Subject: [MacPorts] #66560: itstool: add python311 variant (was: itstool: update to python 3.11?) In-Reply-To: <043.cfd3ccc88b08499e00caae5c0ce071f8@macports.org> References: <043.cfd3ccc88b08499e00caae5c0ce071f8@macports.org> Message-ID: <058.a37e55249278953d6b6e305c3cc7d2b9@macports.org> #66560: itstool: add python311 variant --------------------------+-------------------- Reporter: jowens | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: itstool | --------------------------+-------------------- Changes (by ryandesign): * type: update => enhancement -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 02:08:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 02:08:23 -0000 Subject: [MacPorts] #66561: py-altair: add py311-altair subport (was: py-altair: add python311?) In-Reply-To: <043.ee8c8d9ce11878212be00389d0010426@macports.org> References: <043.ee8c8d9ce11878212be00389d0010426@macports.org> Message-ID: <058.3fa8bf943242761b34f9e3388792080d@macports.org> #66561: py-altair: add py311-altair subport --------------------------+---------------------- Reporter: jowens | Owner: stromnov Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-altair | --------------------------+---------------------- Changes (by ryandesign): * type: defect => enhancement -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 03:23:24 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 03:23:24 -0000 Subject: [MacPorts] #66562: provide cutting edge Minetest by minetest-devel In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.093d9fcee9fe3a12055a5586613e6c4b@macports.org> #66562: provide cutting edge Minetest by minetest-devel --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+-------------------- Changes (by jmroot): * cc: @? (removed) * cc: l2dy (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 04:06:08 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 04:06:08 -0000 Subject: [MacPorts] #66566: py-selenium: add Python 3.11 Message-ID: <046.8efbd24961b6e653970719038031ea8a@macports.org> #66566: py-selenium: add Python 3.11 -------------------------+------------------------- Reporter: radarhere | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-selenium -------------------------+------------------------- If a Python 3.11 subport could be added to py-selenium, that would be good. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 04:12:30 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 04:12:30 -0000 Subject: [MacPorts] #65748: jemalloc @5.3.0: constant expression evaluates to -12 which cannot be narrowed to type 'unsigned int' In-Reply-To: <043.43d4c4c2bd918d1196edc679a413e0a4@macports.org> References: <043.43d4c4c2bd918d1196edc679a413e0a4@macports.org> Message-ID: <058.91eb4718d538c6a0b12df46bb9cb8d26@macports.org> #65748: jemalloc @5.3.0: constant expression evaluates to -12 which cannot be narrowed to type 'unsigned int' -----------------------+------------------------------ Reporter: dsteck | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: monterey ventura Port: jemalloc | -----------------------+------------------------------ Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"b96e6fc66897b29c45391b8cf70dd191f9d78167/macports-ports" b96e6fc66897b29c45391b8cf70dd191f9d78167/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b96e6fc66897b29c45391b8cf70dd191f9d78167" jemalloc: fix universal build on arm64 if rosetta is installed the test for address bits fails when running the x86_64 configure. closes: https://trac.macports.org/ticket/65671 closes: https://trac.macports.org/ticket/65748 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 04:12:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 04:12:31 -0000 Subject: [MacPorts] #65671: jemalloc @5.3.0_2: universal build fails for Monterey M1 arm64 when building x86_64 slice In-Reply-To: <045.e964cbc732c9fa0659a302a070712622@macports.org> References: <045.e964cbc732c9fa0659a302a070712622@macports.org> Message-ID: <060.b38d0d2b07f67a49a1ce8d4a12fc61dc@macports.org> #65671: jemalloc @5.3.0_2: universal build fails for Monterey M1 arm64 when building x86_64 slice -----------------------+---------------------- Reporter: potterpg | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: monterey Port: jemalloc | -----------------------+---------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"b96e6fc66897b29c45391b8cf70dd191f9d78167/macports-ports" b96e6fc66897b29c45391b8cf70dd191f9d78167/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b96e6fc66897b29c45391b8cf70dd191f9d78167" jemalloc: fix universal build on arm64 if rosetta is installed the test for address bits fails when running the x86_64 configure. closes: https://trac.macports.org/ticket/65671 closes: https://trac.macports.org/ticket/65748 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 04:12:31 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 04:12:31 -0000 Subject: [MacPorts] #66452: muniversal portgroups add unnecessary dep on diffutils-for-muniversal In-Reply-To: <047.b708a40d43d38b02b64a946dc53bb9dd@macports.org> References: <047.b708a40d43d38b02b64a946dc53bb9dd@macports.org> Message-ID: <062.1767121d7f58708f9b5c552b61a11d78@macports.org> #66452: muniversal portgroups add unnecessary dep on diffutils-for-muniversal -------------------------+-------------------- Reporter: ryandesign | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: muniversal | -------------------------+-------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"4abb2e5109fed79103b78fd349287d41638e9806/macports-ports" 4abb2e5109fed79103b78fd349287d41638e9806/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4abb2e5109fed79103b78fd349287d41638e9806" muniversal-*: trim diffutils-for-muniversal use only require it if building universal closes: https://trac.macports.org/ticket/66452 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 04:23:22 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 04:23:22 -0000 Subject: [MacPorts] #66536: warzone2100: set `platforms any` for music and videos In-Reply-To: <043.de97dab41595d8bd6b390f5141b14b64@macports.org> References: <043.de97dab41595d8bd6b390f5141b14b64@macports.org> Message-ID: <058.ff7ea35c28a4f913e90f1b8e2a1c69c1@macports.org> #66536: warzone2100: set `platforms any` for music and videos --------------------------+------------------------ Reporter: jmroot | Owner: jasonliu-- Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: warzone2100 | --------------------------+------------------------ Changes (by jmroot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"6c63ebddcc186593c2c42c95e149f292ffa28b6a/macports-ports" 6c63ebddcc186593c2c42c95e149f292ffa28b6a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6c63ebddcc186593c2c42c95e149f292ffa28b6a" warzone2100-{music,videos}: set platforms any Maintainer timeout. Closes: https://trac.macports.org/ticket/66536 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 04:23:22 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 04:23:22 -0000 Subject: [MacPorts] #66563: refurb @1.9.1: ModuleNotFoundError: No module named 'poetry' In-Reply-To: <047.8554fa019e643f510c80c939cf1eba51@macports.org> References: <047.8554fa019e643f510c80c939cf1eba51@macports.org> Message-ID: <062.1626c6e2ba2fa229cb18af229f3257af@macports.org> #66563: refurb @1.9.1: ModuleNotFoundError: No module named 'poetry' -------------------------+------------------------ Reporter: ryandesign | Owner: reneeotten Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: refurb | -------------------------+------------------------ Changes (by jmroot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"13b40d773dee8c3353b986e1ca390ba777ff7de2/macports-ports" 13b40d773dee8c3353b986e1ca390ba777ff7de2/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="13b40d773dee8c3353b986e1ca390ba777ff7de2" refurb: set correct pep517_backend Fixes: https://trac.macports.org/ticket/66563 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 06:55:21 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 06:55:21 -0000 Subject: [MacPorts] #54744: coexistence of libressl, libressl-devel, openssl, boringssl, etc. In-Reply-To: <047.293df8e461dc164c4e1604d2f5a5662e@macports.org> References: <047.293df8e461dc164c4e1604d2f5a5662e@macports.org> Message-ID: <062.ee198fa255637f6f0f80576979e26b65@macports.org> #54744: coexistence of libressl, libressl-devel, openssl, boringssl, etc. -------------------------------+---------------------- Reporter: ryandesign | Owner: artkiver Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl openssl | -------------------------------+---------------------- Comment (by Zweihorn): Hi, I just want to express my **sincere gratitude** to the ''new maintainer'' of both libressl and libressl-devel. Lacking some open commitment from myself to help the former maintainers, I was dependig on just bumping myself my ''local port defintion'' for libressl for years, unfortunately. However, the current updates for libressl and libressl-devel in parallel look very promising. I highly appreciate the curent reasonable approach to meet the LibreSSL upstream update cicle in an applicable way. I would like to understand this approach as: * libressl at 3.6.x until the 3.8 or newer comes around or 3.6 becomes EOL * libressl-devel at 3.7.x until this development version becomes more mature or until the 3.8 or newer comes around IMO this fits. Last not least would like to express my **strong support for this port**. For certain reasons I am a long standing user of LibreSSL on all my Mac OS X / macOS platforms for years and will continue using it. Thank you very much. Keep on the good work and prosper. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 06:56:33 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 06:56:33 -0000 Subject: [MacPorts] #66567: Macports qemu doesn't support VNC by default Message-ID: <049.ee766b34bba51bd5714527803eda3c95@macports.org> #66567: Macports qemu doesn't support VNC by default --------------------------+-------------------- Reporter: aabdelfattah | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: qemu --------------------------+-------------------- When trying to use vnc argument i get this error: {{{ qemu-system-x86_64: -display vnc=127.0.0.1:1: VNC support is disabled }}} My command {{{ qemu-system-x86_64 -drive file=my-image-ui- qemux86-64.wic,if=virtio,format=raw -kernel bzImage \ ????-append 'root=/dev/vda2 rw mem=8192M ip=dhcp console=hvc0 oprofile.timer=1' \ ????-m 8192 -cpu SandyBridge-v1 -smp 6 -device virtio-serial -chardev stdio,id=cons -device virtconsole,chardev=cons \ ????-vga virtio -display vnc=127.0.0.1:1 -M accel=hvf -usb -device usb- tablet \ ????-object rng-random,filename=/dev/urandom,id=rng0 \ ????-device virtio-rng-pci,rng=rng0 -usb -device usb-ehci -object cryptodev-backend-builtin,id=cy0 \ ????-device virtio-crypto-pci,id=crypto0,cryptodev=cy0 -device virtio- keyboard-pci -device virtio-mouse-pci \ ????-device virtio-tablet-pci -device intel-hda -device hda-output \ ????-netdev user,id=net0,hostfwd=tcp::5555-:22,net=192.168.7.0/24,host=192.168.7.1,dhcpstart=192.168.7.2 \ ????-device virtio-net-pci,netdev=net0 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 07:24:26 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 07:24:26 -0000 Subject: [MacPorts] #66567: Macports qemu doesn't support VNC by default In-Reply-To: <049.ee766b34bba51bd5714527803eda3c95@macports.org> References: <049.ee766b34bba51bd5714527803eda3c95@macports.org> Message-ID: <064.598b74934b1c0ba068c35d27d7e24bd6@macports.org> #66567: Macports qemu doesn't support VNC by default ---------------------------+---------------------- Reporter: aabdelfattah | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qemu | ---------------------------+---------------------- Changes (by jmroot): * status: new => assigned * owner: (none) => raimue Comment: There is a `vnc` variant. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 07:26:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 07:26:55 -0000 Subject: [MacPorts] #66561: py-altair: add py311-altair subport In-Reply-To: <043.ee8c8d9ce11878212be00389d0010426@macports.org> References: <043.ee8c8d9ce11878212be00389d0010426@macports.org> Message-ID: <058.dce1f8eb085b24b7d021b788e95310ec@macports.org> #66561: py-altair: add py311-altair subport --------------------------+---------------------- Reporter: jowens | Owner: stromnov Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-altair | --------------------------+---------------------- Changes (by stromnov): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"fa16972bb434581a4364f5e60007a1d2d949e36c/macports-ports" fa16972bb434581a4364f5e60007a1d2d949e36c/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="fa16972bb434581a4364f5e60007a1d2d949e36c" py-altair: add py311 subport Closes: https://trac.macports.org/ticket/66561 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 07:31:34 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 07:31:34 -0000 Subject: [MacPorts] #54744: coexistence of libressl, libressl-devel, openssl, boringssl, etc. In-Reply-To: <047.293df8e461dc164c4e1604d2f5a5662e@macports.org> References: <047.293df8e461dc164c4e1604d2f5a5662e@macports.org> Message-ID: <062.39d7349e616794d38ce7d000e7becee9@macports.org> #54744: coexistence of libressl, libressl-devel, openssl, boringssl, etc. -------------------------------+---------------------- Reporter: ryandesign | Owner: artkiver Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl openssl | -------------------------------+---------------------- Comment (by artkiver): Replying to [comment:16 Zweihorn]: Thank you for the kind words, and you are most welcome; admittedly, I also would be remiss in not also thanking neverpanic for volunteering to be co- maintainer. Regarding your inquiry as far as the differentiation between libressl and libressl-devel, it ''should'' be the case that libressl-devel follows releases described as Development from the LibreSSL project (currently 3.7.0) though we can probably expect LibreSSL 3.7.1 (as a "stable" release, and thus better suited to the libressl MacPort than libressl- devel) at some point (indeed there have been hints of such things to address some issues on the LibreSSL mailing list), which will be merged into the MacPort whenever I see a release announcement and do local testing and submit a PR. Based on past release versions from the upstream project, we probably won't see 3.8.x LibreSSL variants until OpenBSD starts tagging their branches for version 7.3 of their OS release probably? That is just an educated guess on my part though, despite doing volunteer editing for undeadly.org, I am not an OpenBSD committer and more just an assiduous observer of its development and related projects. There was an instance where both libressl and libressl-devel were at 3.6.1, mostly thanks to neverpanic's suggestion so as to iron out an issue where I had incorrectly submitted a PR for a non Development release which was merged for libressl-devel, but I think as things presently stand, it is consistent with the upstream project and hopefully moving forward we will endeavor to maintain that consistency! I've attempted to do a little bit of sprucing up of some other related ports as well e.g. there was a libevent patch with some upstream changes not yet in a versioned release that improved compatibility with LibreSSL which I tested and they were merged successfully (https://github.com/macports/macports-ports/pull/16681), though someone else submitted that PR. I submitted a PR for xar, which made it a bit more LibreSSL friendly by using the dynamic library which got merged as well (https://github.com/macports/macports-ports/pull/16977). Currently, I have one uncommitted PR for rpki-client (https://github.com/macports/macports-ports/pull/16987) because I am pretty sure there there must be a better way to modify the Portfile, but I figured submitting a PR was at least one method to try to get some other eyeballs on it. Essentially, rpki-client will function with LibreSSL without issues; however if referencing the dynamic library, it *can* use OpenSSL as the previous version Portfile defaults reference, but only if LibreTLS is also a dependency. There is doubtlessly a better way to handle that than my attempt, but I figured better to submit some attempt and get additional input than to ignore it completely? I have been contemplating other ways to handle that, but haven't had a lot of time to give it more attention with the holidays. Honestly, it would be easier to submit a Portfile which requires LibreSSL instead of the dynamic library in that instance, but I didn't want to upset previous rpki-client users who were probably already accustomed to the OpenSSL and LibreTLS dependencies by leaving them out in the cold entirely. There are probably other rough edges too which hopefully in time and with sufficient cooperation we can smooth out as well. As for me, I mostly started taking a took at at such things when a JWZ blogpost brought to my attention an issue with an old version of LibreSSL and Let's Encrypt last year. Thankfully, the version of macOS's LibreSSL has been updated with Ventura, though macOS versions prior to Ventura were shipping with a version of LibreSSL which was about four years old, so it seemed worthwhile to try to keep the MacPorts' version a little more up to date. As it currently stands, both libressl and libressl-devel are approximately 9 months ahead of the version shipping with Ventura, and I imagine that disparity will probably continue just given the nature of the upstream projects' release cycles as well as the nebulous nature of the whims of Apple's attention to their CLI tools. It's certainly my intention to continue to focus time and attention on keeping the ports as current as seems possible and I am guessing neverpanic shares similar sentiments. Thank you for noticing! > Hi, > > I just want to express my **sincere gratitude** to the ''new maintainer'' of both libressl and libressl-devel. > > Lacking some open commitment from myself to help the former maintainers, I was dependig on just bumping myself my ''local port defintion'' for libressl for years, unfortunately. However, the current updates for libressl and libressl-devel in parallel look very promising. > > I highly appreciate the curent reasonable approach to meet the LibreSSL upstream update cicle in an applicable way. > > I would like to understand this approach as: > * libressl at 3.6.x until the 3.8 or newer comes around (then itself switching to 3.7.x) or 3.6 becomes EOL > * libressl-devel at 3.7.x until the new development 3.8 or newer version comes around > IMO this fits. > > Last not least would like to express my **strong support for this port**. For certain reasons I am a long standing user of LibreSSL on all my Mac OS X / macOS platforms for years and will continue using it. > > Thank you very much. Keep on the good work and prosper. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 07:51:45 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 07:51:45 -0000 Subject: [MacPorts] #66568: improve the Livecheck of libressl Message-ID: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> #66568: improve the Livecheck of libressl -------------------------+---------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: x86_64 | Port: libressl -------------------------+---------------------- I appreciate the current parallel update to libressl and libressl-devel by the new maintainers. However, would it be possible to **improve / enhance** the ''Livecheck'' procedure of libressl in a way that this port does not flag an "outdated" if just one major version behind libressl-devel port? Example and proposal: * libressl 3.6.1 should not be outdated because of 3.7.x * libressl 3.6.1 shall become outdated if 3.6.2 upstream * libressl 3.6.x shall become outdated if 3.8 or newer upstream * libressl-devel 3.7.0 should continue being outdated by 3.7.1 or 3.8 or newer IMO this enhancement would improve the user experience including the view on the port library GUI (see attach). My five cents. Furthermore, you may approach me to volunteer with more commitment by myself providing an improved Livecheck formula. However, I may be slow in response and/or slow on meeting a schedule. Naturally, you could set the priority of this Ticket to Low until I meet your expections in due time. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 07:52:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 07:52:49 -0000 Subject: [MacPorts] #66568: improve the Livecheck of libressl In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.0778fbd3cd3a62a3669b355126853cf5@macports.org> #66568: improve the Livecheck of libressl --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: x86_64 Port: libressl | --------------------------+-------------------- Changes (by Zweihorn): * Attachment "Bildschirmfoto 2022-12-27 um 08.30.06.png" added. port MacPorts web GUI and libressl port flagging "outdated" -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 07:59:09 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 07:59:09 -0000 Subject: [MacPorts] #66568: improve the Livecheck of libressl In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.e7db3978f1073f2579c7ee071fb44971@macports.org> #66568: improve the Livecheck of libressl --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: x86_64 Port: libressl | --------------------------+-------------------- Description changed by Zweihorn: Old description: > I appreciate the current parallel update to libressl and libressl-devel > by the new maintainers. > > However, would it be possible to **improve / enhance** the ''Livecheck'' > procedure of libressl in a way that this port does not flag an "outdated" > if just one major version behind libressl-devel port? > > Example and proposal: > * libressl 3.6.1 should not be outdated because of 3.7.x > * libressl 3.6.1 shall become outdated if 3.6.2 upstream > * libressl 3.6.x shall become outdated if 3.8 or newer upstream > * libressl-devel 3.7.0 should continue being outdated by 3.7.1 or 3.8 > or newer > > IMO this enhancement would improve the user experience including the view > on the port library GUI (see attach). > > My five cents. > > Furthermore, you may approach me to volunteer with more commitment by > myself providing an improved Livecheck formula. However, I may be slow in > response and/or slow on meeting a schedule. > > Naturally, you could set the priority of this Ticket to Low until I meet > your expections in due time. New description: I appreciate the current parallel update to libressl and libressl-devel by the new maintainers. However, would it be possible to **improve / enhance** the ''Livecheck'' procedure of libressl in a way that this port does not flag an "outdated" if just one major version behind libressl-devel port? Example and proposal: * libressl 3.6.1 should not be outdated because of 3.7.x * libressl 3.6.1 shall become outdated if 3.6.2 upstream * libressl 3.6.x shall become outdated if 3.8 or newer upstream * libressl-devel 3.7.0 shall continue being outdated by 3.7.1 or 3.8 or newer IMO this enhancement would improve the user experience including the view on the port library GUI (see attach). My five cents. Furthermore, you may approach me to volunteer with more commitment by myself providing an improved Livecheck formula. However, I may be slow in response and/or slow on meeting a schedule. Naturally, you could set the priority of this Ticket to Low until I meet your expections in due time. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:10:42 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:10:42 -0000 Subject: [MacPorts] #66566: py-selenium: add py311-selenium subport (was: py-selenium: add Python 3.11) In-Reply-To: <046.8efbd24961b6e653970719038031ea8a@macports.org> References: <046.8efbd24961b6e653970719038031ea8a@macports.org> Message-ID: <061.172611407b9ef268213784d431dff97d@macports.org> #66566: py-selenium: add py311-selenium subport --------------------------+---------------------- Reporter: radarhere | Owner: dstrubbe Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-selenium | --------------------------+---------------------- Changes (by ryandesign): * cc: dstrubbe (removed) * status: new => assigned * owner: (none) => dstrubbe -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:16:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:16:23 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck (was: improve the Livecheck of libressl) In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.facda13c40e3e8f80bdb58ef3f877aab@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Changes (by ryandesign): * status: new => assigned * cc: neverpanic (added) * keywords: x86_64 => * owner: (none) => artkiver Comment: See also https://github.com/libressl-portable/portable/issues/362 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:17:00 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:17:00 -0000 Subject: [MacPorts] #66567: qemu: doesn't support VNC by default (was: Macports qemu doesn't support VNC by default) In-Reply-To: <049.ee766b34bba51bd5714527803eda3c95@macports.org> References: <049.ee766b34bba51bd5714527803eda3c95@macports.org> Message-ID: <064.3844a9d8fbd4c9d8cef7ba3b61ee2cbf@macports.org> #66567: qemu: doesn't support VNC by default ---------------------------+---------------------- Reporter: aabdelfattah | Owner: raimue Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qemu | ---------------------------+---------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:28:14 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:28:14 -0000 Subject: [MacPorts] #66554: py-mutagen: add py311-mutagen subport (was: py-mutagen: add Python 3.11) In-Reply-To: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> References: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> Message-ID: <061.b9557069cce7540924d81cd2007ea94c@macports.org> #66554: py-mutagen: add py311-mutagen subport --------------------------+-------------------- Reporter: radarhere | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-mutagen | --------------------------+-------------------- Comment (by ryandesign): This port has no maintainer. Feel free to submit a pull request to implement this enhancement. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:29:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:29:23 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.04df36b304d6a568317ff61a787a3c51@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): MacPorts installs the sdk to /opt/local/Developer/SDKs/ ? without comment. I tried to link MacOSX10.11.sdk to /Library/Developer/CommandLineTools/SDKs and /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ ? but that does not help. xcrun --show-sdk-path points only to 10.12. It's a bit annoying ? I have xcode 8.2.1, the ?regular? xcode f?r 10.11. That one has the sdk pointing to 1.12 instead 10.11. It seems, an older 7.3 points to 10.11. But I use 8.2.1 from the beginning on. And it is strange that a) the ports can?t handle that and b) the (via MacPorts) installed sdk does not have an effect. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:35:39 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:35:39 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.1bf113190763fc1d6cde1d0cba07c87f@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): Seems to be a known issue, but I don?t see a solution: https://developer.apple.com/forums/thread/62870 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:43:44 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:43:44 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.2f0b7efa98bcddf5bf5b7a698c6fd6d6@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): I am not too familiar with the Livecheck code. However, that referenced GitHub ticket seems to be checking a releases page, whereas the ChangeLog (e.g. https://github.com/libressl- portable/portable/blob/master/ChangeLog) is probably a better resource as it more definitively seems to indicate which releases are Development (and thus should presumably best be associated with libressl-devel) and which are Stable (and thus should are probably best associated with the libressl port). However, even the ChangeLog has releases marked as: "Reliability fix" or "Security release". In such instances, it seems to me that those should still be good for the main libressl Portfile updates, but I am less sure if we should have libressl-devel track them? Regardless, thank you for bringing this to our attention, I hadn't been away of that libressl-portable issue previously and it appears as if that is still open and may be able to benefit from some additional commentary given it's been (checks date) more than five years since it was opened! Wow. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 08:55:54 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 08:55:54 -0000 Subject: [MacPorts] #35727: dmake: an enhanced make utility In-Reply-To: <045.026a1a200417f98c29c6a4d663dae744@macports.org> References: <045.026a1a200417f98c29c6a4d663dae744@macports.org> Message-ID: <060.f13c9fa2778728332d49868e1608238b@macports.org> #35727: dmake: an enhanced make utility -------------------------+-------------------------------- Reporter: ajdudman | Owner: macports-tickets@? Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.99 Resolution: fixed | Keywords: Port: dmake | -------------------------+-------------------------------- Changes (by ryandesign): * status: new => closed * resolution: => fixed Comment: In [changeset:"f77081fd7cf7a0e8d7e786044024bb68660b4ee6/macports-ports" f77081fd7cf7a0e8d7e786044024bb68660b4ee6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="f77081fd7cf7a0e8d7e786044024bb68660b4ee6" dmake: New port, version 4.13.1 Closes: https://trac.macports.org/ticket/35727 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 09:48:21 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 09:48:21 -0000 Subject: [MacPorts] #66558: atari800: Problem with Control key. In-Reply-To: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> References: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> Message-ID: <059.d10cee25378c9c7a36c23d7001ddb54b@macports.org> #66558: atari800: Problem with Control key. -----------------------+---------------------- Reporter: eazy0ne | Owner: krischik Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: atari800 | -----------------------+---------------------- Comment (by krischik): You should report this bug to https://github.com/atari800/atari800/issues Notice that a similar bug has been reported for GNOME: https://github.com/atari800/atari800/issues/176 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 10:22:21 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 10:22:21 -0000 Subject: [MacPorts] #66558: atari800: Problem with Control key. In-Reply-To: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> References: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> Message-ID: <059.398e6672be2c523b2e71a66355a92b17@macports.org> #66558: atari800: Problem with Control key. -----------------------+---------------------- Reporter: eazy0ne | Owner: krischik Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: atari800 | -----------------------+---------------------- Comment (by krischik): I can confirm the problem both for the MacPorts version as well as the Brew version of '''atari800'''. I also noted that the display is now correct both with `VIDEO_ACCEL=0` and `VIDEO_ACCEL=1`. See Issue 104: https://github.com/atari800/atari800/issues/104 The `VIDEO_ACCEL` originated in '''libsdl''' so this might be a problem of one bug fixed and a new one gained. Either way nothing to do with the build itself. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 10:35:30 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 10:35:30 -0000 Subject: [MacPorts] #66558: atari800: Problem with Control key. In-Reply-To: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> References: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> Message-ID: <059.f097c3403293f887f030271ca8bb7d4d@macports.org> #66558: atari800: Problem with Control key. -----------------------+---------------------- Reporter: eazy0ne | Owner: krischik Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: atari800 | -----------------------+---------------------- Comment (by krischik): I wrote an but report upstream: https://github.com/atari800/atari800/issues/177 ? That's all I can do. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 11:32:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 11:32:55 -0000 Subject: [MacPorts] #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar In-Reply-To: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> References: <043.4df94e5ef6fe05cbff240bbaf8157332@macports.org> Message-ID: <058.8a946618d2ddac66b199bc7706d3d6cf@macports.org> #66499: Significantly reduce MacPorts base install size by removing base.tar and compressing ports.tar --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:5 kencu]: > I think the entire base TCL installation is something like 14MB > > {{{ > % du -sh tcl* > }}} Why would you ignore all the other junk that doesn't have `tcl*` prefix??? The whole `base/vendor` folder is ~125m - 52m `tcl8.6.12` - ~10m of which a very helpful `tests`/`doc`/`changelogs`, so almost your "entire base" - ~70m is `tcllib-1.21` with similarly useful `tests` and docs in the modules taking most(?) of the space (7/9m for `pt` is `tests`) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 11:39:43 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 11:39:43 -0000 Subject: [MacPorts] #66562: provide cutting edge Minetest by minetest-devel In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.197cb54df605a9c1589213e7184609f8@macports.org> #66562: provide cutting edge Minetest by minetest-devel --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+-------------------- Description changed by Zweihorn: Old description: > The long standing minetest port derives new versions by just updating the > sources and the checksums apparently. Certain defaults and specialities > in the build seem to have been overlooked from the start of this almost > historic port or have changed over time. If not for the well maintained > irrlichtmt port this unmaintained port could be called rather outdated in > some aspects. Anyway the resulting App cannot be called optimal. > > My cc to the maintainer of the irrlichtmt port is just for information. > Naturally, combined with my most friendly thank you for his commitment. > > (A) > There is a new port minetest-devel in the making and a new PR already in > the queue to come around. > The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 > and MT 5.6.1. The current MT runs on Big Sur as a local port as was done > with all the predecessors before on othe macOS versions respectively. > > (B) > My PR may solve the below issue too, although I have to check the details > again first. Or do you? > - #66408 > > (C) > You may note I would volunteer to become the maintainer of both the new > minetest-devel as the legacy minetest port together, if this would find > your approval. > > (D) > Please kindly note that I already advertised for MacPorts at the > Minetest community in the past with at least some success. > > Please have a look at: > > - https://forum.minetest.net/viewtopic.php?f=42&t=22427 > > - https://www.minetest.net/downloads/ --> macOS - MacPorts > > My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in > parallel to my now re-opened old account at the MT Forum for technical > reasons only. > > (E) > Only after well establishing minetest-devel and learning if the > expectations raised by my work are met on most if not all platforms, I > would consider improving minetest e.g., by making the build more > consistant and introducing a '--legacy' variant to help some users of the > legacy port. > > (F) > In the future both ports minetest and minetest-devel should continue, as > a new MT 5.6.2 may be understood stable but a new MT 5.7.0 would be work > in progress. AFAIK on top of that it is tradition with Minetest players > to stick with an older version as long as possible. > > (G) > Please accept my sincere apologies in advance if I do not cover all > aspects of your ticket process as I only came back recently after some > longe break. Obviously, I have to make myself more familiar with MacPort > internals again. > > Some if not all of the above will be copied in to a.m. PR in due time. > > Stay tuned. New description: The minetest port is at current MT 5.6.1, however the build may be **not optimal** IMO. The long standing minetest port derives new versions by just updating the sources and the checksums apparently. Certain defaults and specialities in the build seem to have been overlooked from the start of this almost historic port or have changed over time. If not for the well maintained irrlichtmt port this unmaintained port could be called rather outdated in some aspects. Anyway the resulting App cannot be called optimal. My cc to the maintainer of the irrlichtmt port is just for information. Naturally, combined with my most friendly thank you for his commitment. (A) There is a new port minetest-devel in the making and a new PR already in the queue to come around. The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 and MT 5.6.1. The current MT runs on Big Sur as a local port as was done with all the predecessors before on othe macOS versions respectively. (B) My PR may solve the below issue too, although I have to check the details again first. Or do you? - #66408 (C) You may note I would volunteer to become the maintainer of both the new minetest-devel as the legacy minetest port together, if this would find your approval. (D) Please kindly note that I already advertised for MacPorts at the Minetest community in the past with at least some success. Please have a look at: - https://forum.minetest.net/viewtopic.php?f=42&t=22427 - https://www.minetest.net/downloads/ --> macOS - MacPorts My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in parallel to my now re-opened old account at the MT Forum for technical reasons only. (E) Only after well establishing minetest-devel and learning if the expectations raised by my work are met on most if not all platforms, I would consider improving minetest e.g., by making the build more consistant and introducing a '--legacy' variant to help some users of the legacy port. (F) In the future both ports minetest and minetest-devel should continue, as a new MT 5.6.2 may be understood stable but a new MT 5.7.0 would be work in progress. AFAIK on top of that it is tradition with Minetest players to stick with an older version as long as possible. (G) Please accept my sincere apologies in advance if I do not cover all aspects of your ticket process as I only came back recently after some longe break. Obviously, I have to make myself more familiar with MacPort internals again. Some if not all of the above will be copied in to a.m. PR in due time. Stay tuned. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 13:33:14 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 13:33:14 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.83b191c36c290362f8e20222c0729bee@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): this has to do with the way we wrote the tests to see which sdks you have installed. They should cover your case. please show me the exact contents of the two sdk folders I referenced above. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 13:52:48 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 13:52:48 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.85a2065cbf14f2ac8d9b2a72087e047b@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): the testing code has been rewritten a few times. https://github.com/macports/macports- ports/blob/master/aqua/qt511/Portfile#L987 it seems the current version of it isn?t working for your setup. I can see a few potential possible issues with it, but to debug it we?ll need to know what sdks are in your sdks folders. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:28:35 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 14:28:35 -0000 Subject: [MacPorts] #66569: libgcc11 failed to install on MacOs Ventura Message-ID: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> #66569: libgcc11 failed to install on MacOs Ventura ---------------------+--------------------------- Reporter: djmagma | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libgcc 11.3.0 ---------------------+--------------------------- Hello everybody, since I installed MacOS Ventura, I also updated/upgraded MacPorts. After successfully installing many ports, when updating **libgcc** I get the following error: {{{ :info:build xgcc: warning: could not understand version '13.0' :info:build lipo -output libgcc_s.1.1.dylib \ :info:build -create libgcc_s.1.1.dylib_T* :info:build rm libgcc_s.1.1.dylib_T* :info:build MLIBS=`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking --print- multi-lib | sed -e 's/;.*$//'` ; \ :info:build for mlib in $MLIBS ; do \ :info:build cp ../${mlib}/libgcc/${mlib}/libgcc_s.dylib \ :info:build ./libgcc_s.1.1.dylib_T_${mlib} || exit 1 ; \ :info:build arch=`lipo -info libgcc_s.1.1.dylib_T_${mlib} | sed -e 's/.*:\ //'` ; \ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/./gcc/ -B/opt/local/x86_64-apple-darwin22/bin/ -B/opt/local/x86_64-apple- darwin22/lib/ -isystem /opt/local/x86_64-apple-darwin22/include -isystem /opt/local/x86_64-apple-darwin22/sys-include -fno-checking -arch ${arch} -nodefaultlibs -dynamiclib -nodefaultrpaths \ :info:build -o libgcc_s.1.dylib_T_${mlib} \ :info:build -Wl,-reexport_library,libgcc_s.1.1.dylib_T_${mlib} \ :info:build -lSystem \ :info:build -Wl,-reexported_symbols_list,/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/gcc-11.3.0/libgcc/config /darwin-unwind.ver \ :info:build -install_name @rpath/libgcc_s.1.dylib \ :info:build -compatibility_version 1 -current_version 1.1 ; \ :info:build done :info:build xgcc: warning: could not understand version '13.0' :info:build xgcc: warning: could not understand version '13.0' :info:build ld: targeted OS version does not support -reexported_symbols_list :info:build collect2: error: ld returned 1 exit status :info:build make[3]: *** [libgcc_s.1.dylib] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build/x86_64 -apple-darwin22/libgcc' :info:build make[2]: *** [all-stage1-target-libgcc] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build make[1]: *** [stage1-bubble] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build make: *** [bootstrap-lean] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/work/build" && /usr/bin/make -j8 -w bootstrap-lean :info:build Exit code: 2 :error:build Failed to build libgcc11: command execution failed :debug:build Error code: CHILDSTATUS 27680 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc11/libgcc11/main.log for details. }}} Am I missing something? Thanks in advance for any suggestions. Daniele -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:39:37 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 14:39:37 -0000 Subject: [MacPorts] #66569: libgcc11 failed to install on MacOs Ventura In-Reply-To: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> References: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> Message-ID: <059.fe678aee8f7ddc543f7d1e9dbc7c5670@macports.org> #66569: libgcc11 failed to install on MacOs Ventura ----------------------------+-------------------- Reporter: djmagma | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: libgcc 11.3.0 | ----------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => duplicate Comment: Hi, thanks for the report. this issue is being tracked here #66398 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:41:53 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 14:41:53 -0000 Subject: [MacPorts] #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 In-Reply-To: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> References: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> Message-ID: <059.85de0a570cce0593de0b0defe2616ed7@macports.org> #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 -----------------------+--------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc11 | -----------------------+--------------------- Comment (by kencu): no packages should depend on gcc11/libgcc11 at present. can you see which package is calling for it? {{{ port -v installed | grep gcc11 }}} might tell you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:43:55 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 14:43:55 -0000 Subject: [MacPorts] #66558: atari800: Problem with Control key. In-Reply-To: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> References: <044.d18770d9a90e1bf9fcc1bc27950fca68@macports.org> Message-ID: <059.bc052f8e0a6f18c0f4d8b80857055930@macports.org> #66558: atari800: Problem with Control key. -----------------------+---------------------- Reporter: eazy0ne | Owner: krischik Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: atari800 | -----------------------+---------------------- Comment (by eazy0ne): Replying to [comment:5 krischik]: OK, thank you. I hope the problem can be solved. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 14:45:53 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 14:45:53 -0000 Subject: [MacPorts] #66569: libgcc11 failed to install on MacOs Ventura In-Reply-To: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> References: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> Message-ID: <059.376110ebe6fd5f16e37cb32e5d1d3153@macports.org> #66569: libgcc11 failed to install on MacOs Ventura ----------------------------+-------------------- Reporter: djmagma | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: libgcc 11.3.0 | ----------------------------+-------------------- Comment (by djmagma): Thanks a lot, that resolved. Daniele -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:06:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 16:06:23 -0000 Subject: [MacPorts] #66570: gobject-introspection: upgrade to py311 (or allow as an alternative)? Message-ID: <043.62110448fb3ff2eb2878c2c28142679c@macports.org> #66570: gobject-introspection: upgrade to py311 (or allow as an alternative)? -------------------------+----------------------------------- Reporter: jowens | Owner: mascguy Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gobject-introspection -------------------------+----------------------------------- Currently it appears to be hardwired to 310. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:36:36 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 16:36:36 -0000 Subject: [MacPorts] #66551: rapidjson-devel @20180424_1: error: 'sprintf' is deprecated In-Reply-To: <047.f116b0628e23af368376244777e5e6b2@macports.org> References: <047.f116b0628e23af368376244777e5e6b2@macports.org> Message-ID: <062.4fd3f86e5b1e433b6a49de6fd5fd0ae8@macports.org> #66551: rapidjson-devel @20180424_1: error: 'sprintf' is deprecated ------------------------------+--------------------- Reporter: ryandesign | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: rapidjson-devel | ------------------------------+--------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"6516b7b69d4bb5351be59aa1c171875e7be44e6d/macports-ports" 6516b7b69d4bb5351be59aa1c171875e7be44e6d/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="6516b7b69d4bb5351be59aa1c171875e7be44e6d" rapidjson-devel: disable Werror closes: https://trac.macports.org/ticket/66551 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:44:49 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 16:44:49 -0000 Subject: [MacPorts] #66242: python311 @3.11.0 +lto +optimizations failed to build: No such file or directory: '/opt/local/include/proj_api.h' (was: python311 @3.11.0 +lto +optimizations failed to build) In-Reply-To: <046.4daf2328ef43290b34926dc800960514@macports.org> References: <046.4daf2328ef43290b34926dc800960514@macports.org> Message-ID: <061.deb1d611887d486ad1ef35f32528ab68@macports.org> #66242: python311 @3.11.0 +lto +optimizations failed to build: No such file or directory: '/opt/local/include/proj_api.h' ------------------------+---------------------- Reporter: bakergilx | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: python311 | ------------------------+---------------------- Comment (by kencu): current python311 does install on arm Ventura: {{{ % port -v installed python311 The following ports are currently installed: python311 @3.11.1_0+lto+optimizations (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T21:37:07-0800' }}} I don't have any version of {{{proj}}} installed, however. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:49:21 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 16:49:21 -0000 Subject: [MacPorts] #66420: soxr @0.1.3 Building on Ventura fails with ffmpeg from homebrew installed In-Reply-To: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> References: <044.fc7e25384916f8855d0dcdfa5e8268ab@macports.org> Message-ID: <059.e5c703664621f97d9e60b3afca20ca7d@macports.org> #66420: soxr @0.1.3 Building on Ventura fails with ffmpeg from homebrew installed -------------------------+--------------------- Reporter: kaestel | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: worksforme | Keywords: ventura Port: soxr | -------------------------+--------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: installs {{{ % port -v installed soxr The following ports are currently installed: soxr @0.1.3_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-27T08:48:10-0800' }}} without a conflicting ffmpeg from homebrew. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 16:59:19 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 16:59:19 -0000 Subject: [MacPorts] #66182: soxr @0.1.3: fatal error: 'omp.h' file not found In-Reply-To: <045.522656a8d83d453fa2317e0789320192@macports.org> References: <045.522656a8d83d453fa2317e0789320192@macports.org> Message-ID: <060.23f25c2add6f15de4866509d9c17022c@macports.org> #66182: soxr @0.1.3: fatal error: 'omp.h' file not found -------------------------+--------------------- Reporter: kolydart | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura Port: soxr | -------------------------+--------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: This builds for me on current arm Ventura, with or without {{{libomp}}} installed: {{{ -- Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES) -- Could NOT find OpenMP (missing: OpenMP_C_FOUND) }}} {{{ % port -v installed soxr The following ports are currently installed: soxr @0.1.3_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-27T08:48:10-0800' }}} please reopen with new information if this is still an issue for you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 18:03:23 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 18:03:23 -0000 Subject: [MacPorts] #66571: gimp2 @2.10.32+python27 fails to upgrade (build) on mavericks 2.10.32_2 < 2.10.32_3 Message-ID: <043.bb5e02145fb82d5f8d6ad5bfbba17f10@macports.org> #66571: gimp2 @2.10.32+python27 fails to upgrade (build) on mavericks 2.10.32_2 < 2.10.32_3 --------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: gimp2 --------------------+-------------------- {{{ error: incompatible pointer to integer conversion returning 'void *' from a function with result type 'gint32' (aka 'int') }}} please see attached main.log... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 18:03:57 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 18:03:57 -0000 Subject: [MacPorts] #66571: gimp2 @2.10.32+python27 fails to upgrade (build) on mavericks 2.10.32_2 < 2.10.32_3 In-Reply-To: <043.bb5e02145fb82d5f8d6ad5bfbba17f10@macports.org> References: <043.bb5e02145fb82d5f8d6ad5bfbba17f10@macports.org> Message-ID: <058.440c0a45232422c15d72ccc9d1f71b89@macports.org> #66571: gimp2 @2.10.32+python27 fails to upgrade (build) on mavericks 2.10.32_2 < 2.10.32_3 ---------------------+-------------------- Reporter: tehcog | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gimp2 | ---------------------+-------------------- Changes (by tehcog): * Attachment "gimp2_main.log" added. main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 18:50:46 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 18:50:46 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.df9e18ac20fe86a4db02fb21765296c7@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): Both folders have MacOSX.sdk as folder and MacOSX10.12.sdk as link to that folder inside of them. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:03:29 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 20:03:29 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.e68d5cc45f53fcd5492c168e136fe742@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Changes (by kencu): * cc: jmroot (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:07:01 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 20:07:01 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.dfcf457c67c3021c30b2c847656688bc@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): OK, then that is supposed to work. The portfile logic should find that using macosx10.11 fails, and so falls back to use just macosx instead. Josh last rewrote the code, so I?ll loop him in here to help sort it out. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 20:21:57 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 20:21:57 -0000 Subject: [MacPorts] #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 In-Reply-To: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> References: <044.6b77bf82e371b21ae3cd99be1be9ef5c@macports.org> Message-ID: <059.90682fbf656383967a2f42bf255a03c4@macports.org> #66398: libgcc11 installation error (when installing gcc11) on Ventura 13.0.1 -----------------------+--------------------- Reporter: imos-99 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: ventura Port: libgcc11 | -----------------------+--------------------- Comment (by imos-99): You are right, there are no dependencies. I compiled my own package, which also compiles fine with gcc12. Thanks! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 21:07:33 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 21:07:33 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.e51b81d15213004d36eb1b3ee4b6627b@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): So the 10.11 sdk that I installed via MacPorts is irrelevant? I thought, this could solve problems. What for was/is this port? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 21:34:27 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 21:34:27 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.1ce33e51f4f2cb26227d2a38d04d9b3e@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): Yeah, the new SDK you installed is only useful if software knows where to look for it. If the MacOSX10.11.sdk was in both: {{{ /Library/Developer/CommandLineTools/SDKs and /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ }}} then you should be in business. You might try playing around with symlinking the MacOSX10.11.sdk you installed into those two locations, just for fun, I guess. There was a lot of stuff added to the testing logic that I'm not up on (configure.developer_dir, etc) so I will leave the rest of this to Josh. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 22:32:22 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 22:32:22 -0000 Subject: [MacPorts] #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 In-Reply-To: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> References: <050.53336ecc7cf30571ca4e84b5f771475a@macports.org> Message-ID: <065.cebb190cd7c38add2465c0d01968c68a@macports.org> #66454: libopus @1.3.1_0+universal: Configure & build fail on G4/PPC 10.5.8 ----------------------------+-------------------- Reporter: xanda-escuyer | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libopus | ----------------------------+-------------------- Comment (by xanda-escuyer): We followed the guidance here at: [https://trac.macports.org/wiki/howto/PatchLocal How to Patch a Port on Your System] ... and made the suggested Portfile changes. The result was as follows:- {{{ $: port -v installed libopus-devel The following ports are currently installed: libopus-devel @1.3.1_0+universal (active) requested_variants='+universal' platform='darwin 9' archs='i386 ppc' date='2022-12-27T21:15:00+0000' }}} All the same we've had to scrub/reinstall MacPorts but thanks again for the assist. :-) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 22:35:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 22:35:15 -0000 Subject: [MacPorts] #66562: provide cutting edge Minetest by minetest-devel In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.8736ed837edb8a1e5faed54eadaee5e7@macports.org> #66562: provide cutting edge Minetest by minetest-devel --------------------------+-------------------- Reporter: Zweihorn | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+-------------------- Comment (by Zweihorn): A more **mature PR** named as " establish minetest-devel (new port) # 17080 " was provided at: - https://github.com/macports/macports-ports/pull/17080 This new PR makes the former a.m. draft PR # 17061 **obsolete.** Related to this new PR is the PR " minetest new maintainer # 17077 " at: - https://github.com/macports/macports-ports/pull/17077 Hope this helps. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 22:43:27 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 22:43:27 -0000 Subject: [MacPorts] #66501: rrdtool: configure: error: I need a copy of *nroff to format the documentation In-Reply-To: <047.8bca49f39d5e1f458f4392f1deea7dbd@macports.org> References: <047.8bca49f39d5e1f458f4392f1deea7dbd@macports.org> Message-ID: <062.8e6f3a1822490c2e4e983f199dc7c977@macports.org> #66501: rrdtool: configure: error: I need a copy of *nroff to format the documentation -------------------------+--------------------- Reporter: ryandesign | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: rrdtool | -------------------------+--------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"94e8f71f214da1112b418e9bb621f243eeecbc2d/macports-ports" 94e8f71f214da1112b418e9bb621f243eeecbc2d/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="94e8f71f214da1112b418e9bb621f243eeecbc2d" rrdtool: needs groff on Ventura Ventura+ does not come with a system groff tool closes: https://trac.macports.org/ticket/66501 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 23:05:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 23:05:15 -0000 Subject: [MacPorts] #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. Message-ID: <048.a8e918ed423c3d176105232994289c34@macports.org> #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. -------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: iulib -------------------------+-------------------- Trying to rev-upgrade after the latest tiff update: {{{ scons: Reading SConscript files ... File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_iulib/iulib/work /tmbdev-iulib-b2b66db/SConstruct", line 63 print "WARNING: compile with -DUNSAFE or high optimization only for production use" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_iulib/iulib/work /iulib-b2b66dbcbbbfcb4aac0784ea9f07db998077dbc1" && /opt/local/bin/scons -j16 Exit code: 2 Error: Failed to build iulib: command execution failed DEBUG: Error code: CHILDSTATUS 8744 2 }}} I'm on Big Sur with Xcode 13. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Tue Dec 27 23:07:15 2022 From: noreply at macports.org (MacPorts) Date: Tue, 27 Dec 2022 23:07:15 -0000 Subject: [MacPorts] #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. In-Reply-To: <048.a8e918ed423c3d176105232994289c34@macports.org> References: <048.a8e918ed423c3d176105232994289c34@macports.org> Message-ID: <063.459ff29001e46221c2f1a8ee171f8a15@macports.org> #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: iulib | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "iulib_main.log" added. main.log for iulib -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 00:15:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 00:15:41 -0000 Subject: [MacPorts] #66565: Recognize macports-webapp GitHub repository In-Reply-To: <047.2e625d01c01140a892417855750e24a4@macports.org> References: <047.2e625d01c01140a892417855750e24a4@macports.org> Message-ID: <062.58c1f08c87168df4d79bb0463b5c1962@macports.org> #66565: Recognize macports-webapp GitHub repository -------------------------+--------------------- Reporter: ryandesign | Owner: admin@? Type: defect | Status: closed Priority: Normal | Milestone: Component: trac | Version: Resolution: fixed | Keywords: Port: | -------------------------+--------------------- Changes (by raimue): * status: new => closed * resolution: => fixed Comment: Added the repository to Trac with [a939f78907f0d4df6a102215e88865ec73b7d0b7/trac.macports.org] and added the git clone to the host. The link in the mentioned comment now links to GitHub as expected. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 00:31:51 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 00:31:51 -0000 Subject: [MacPorts] #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. In-Reply-To: <048.a8e918ed423c3d176105232994289c34@macports.org> References: <048.a8e918ed423c3d176105232994289c34@macports.org> Message-ID: <063.03edd6e7bdd04cc6f6fe3894df68b44f@macports.org> #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: iulib | --------------------------+-------------------- Comment (by Schamschula): Apparently, there haven't been any updates since 2014. There were PRs in 2017, but they haven't been merged. Also, see #42353 In other words, it needs to be fixed by patching in MacPorts. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 00:33:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 00:33:49 -0000 Subject: [MacPorts] #66570: gobject-introspection: switch to python311 on January 1 (was: gobject-introspection: upgrade to py311 (or allow as an alternative)?) In-Reply-To: <043.62110448fb3ff2eb2878c2c28142679c@macports.org> References: <043.62110448fb3ff2eb2878c2c28142679c@macports.org> Message-ID: <058.e7277fd6c2279abf45f5f9848ed17dd9@macports.org> #66570: gobject-introspection: switch to python311 on January 1 ------------------------------------+---------------------- Reporter: jowens | Owner: mascguy Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gobject-introspection | ------------------------------------+---------------------- Comment (by ryandesign): Ports that do not offer a choice of Python version are supposed to use Python 3.10 at this time. On January 1 each year, the recommended Python version is increased. See https://lists.macports.org/pipermail/macports- dev/2021-December/044043.html. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 00:34:10 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 00:34:10 -0000 Subject: [MacPorts] #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. In-Reply-To: <048.a8e918ed423c3d176105232994289c34@macports.org> References: <048.a8e918ed423c3d176105232994289c34@macports.org> Message-ID: <063.81874f55190f108e2c994b38a6b75974@macports.org> #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: iulib | --------------------------+-------------------- Comment (by Schamschula): It was written for Python 2.7, but we're now using Python 3.x. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 00:41:11 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 00:41:11 -0000 Subject: [MacPorts] #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. In-Reply-To: <048.a8e918ed423c3d176105232994289c34@macports.org> References: <048.a8e918ed423c3d176105232994289c34@macports.org> Message-ID: <063.db6028a6b8faeee70984589a0c2f436f@macports.org> #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: iulib | --------------------------+-------------------- Comment (by ryandesign): Replying to [comment:2 Schamschula]: > It ?the SConstruct file? > was written for Python 2.7, but we're now using Python 3.x. ?for scons. This is an example of the fallout I anticipated in #59303. Adding the parentheses to the `print` call is easy. Haven't checked yet if that's the only problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 00:45:16 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 00:45:16 -0000 Subject: [MacPorts] #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. In-Reply-To: <048.a8e918ed423c3d176105232994289c34@macports.org> References: <048.a8e918ed423c3d176105232994289c34@macports.org> Message-ID: <063.d2cf53839ebd1d1a5b25c867e79fb419@macports.org> #66572: iulib @0.4-20141216_3: SyntaxError: Missing parentheses in call to 'print'. -------------------------+------------------------------------------------- Reporter: | Owner: Marius Schamschula cooljeanius | Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: iulib | -------------------------+------------------------------------------------- Changes (by Marius Schamschula ): * owner: (none) => Marius Schamschula * status: new => closed * resolution: => fixed Comment: In [changeset:"7012dabc7b7c8ff8f70bf79e92026873f9ee406b/macports-ports" 7012dabc7b7c8ff8f70bf79e92026873f9ee406b/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7012dabc7b7c8ff8f70bf79e92026873f9ee406b" iulib: Fix Python 2.7 to 3.x print ssyntax merge implicit.patch into patch-SConstruct.diff Closes: https://trac.macports.org/ticket/66572 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:14:21 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 01:14:21 -0000 Subject: [MacPorts] #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility Message-ID: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility -----------------------+-------------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: tcp_wrappers -----------------------+-------------------------- Just did an upgrade in my macports and not able to install this package because it appears to be missing. It is required by another package. "tcp_wrappers-20_5.darwin_22.arm64.tbz2" Is there any way to use the previous version since my port tree does not show it available? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:24:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 01:24:49 -0000 Subject: [MacPorts] #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility In-Reply-To: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> References: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> Message-ID: <061.fdc9b58901bc034822b734dbc8a07a40@macports.org> #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility ---------------------------+-------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: tcp_wrappers | ---------------------------+-------------------- Comment (by ryandesign): It is correct that there are no arm64 binary archives of any port available for Darwin 22 at this time. That need not be a problem. In the absence of binary archives, MacPorts will build from source. Is that failing for you? If so, please attach the main.log file so we can investigate what went wrong. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:27:20 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 01:27:20 -0000 Subject: [MacPorts] #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility In-Reply-To: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> References: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> Message-ID: <061.2f106b892a740889565ff162ecb5e9c9@macports.org> #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility ---------------------------+-------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: tcp_wrappers | ---------------------------+-------------------- Comment (by ryandesign): If it's a checksum mismatch, then that's #66539. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:33:44 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 01:33:44 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.d41fd03690ca7892b46e2897f7112f98@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): Any locally-stored information would be out-of-date. A binary could have been produced on the build servers between the time that your local database was updated and the time that you asked whether a binary archive of a port was available. Also, there is no local database. And if one were to be created for this purpose, there is no server-side source of information from which that database could be populated. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:36:22 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 01:36:22 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.33d6c184d8e2478bba7d5e3b735d4479@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): Replying to [comment:6 ryandesign]: > there is no local database. There is the PortIndex, which is where `port info` gets its information. The PortIndex is generated by parsing the Portfiles. Most users receive a PortIndex that was created on our servers. Entries in the PortIndex are only updated when the `portindex` command is run and only if the corresponding Portfile has changed on disk. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 01:49:37 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 01:49:37 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.d1e2d0cf281de4cc4875fbcf9bc013f3@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by ryandesign): Replying to [comment:5 esbugz]: > stored in the local database If you were referring to the ports.macports.org web site, then yes, I believe it does have a database that is populated by first updating the PortIndex and then parsing it somehow. The web site also contains information that didn't come from the PortIndex, like livecheck information; the web site periodically runs `port livecheck` on every port (performing an http(s) request for each one) to update that information. Yes, presumably a similar process could be used to perform http(s) requests for each port for each OS version and architecture, periodically, to see if a binary archive exists on the server. (Bear in mind that there are currently 30,000 ports ? 21 OS version/architecture combinations on which MacPorts works, so that would be a lot of http(s) requests.) If you would like to suggest that as a feature request for the ports.macports.org web site, that would be handled at https://github.com/macports/macports- webapp/issues. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:02:40 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:02:40 -0000 Subject: [MacPorts] #66092: nethack: error: too few arguments provided to function-like macro invocation In-Reply-To: <049.0be152501cd40086b61e90ef054178aa@macports.org> References: <049.0be152501cd40086b61e90ef054178aa@macports.org> Message-ID: <064.018df502270bf5a12fe3c1f89e32094c@macports.org> #66092: nethack: error: too few arguments provided to function-like macro invocation ---------------------------+---------------------- Reporter: ShadSterling | Owner: jflude Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: nethack | ---------------------------+---------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/17085 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:12:46 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:12:46 -0000 Subject: [MacPorts] #66569: libgcc11 @11.3.0 failed to install on MacOs Ventura (was: libgcc11 failed to install on MacOs Ventura) In-Reply-To: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> References: <044.a740e7f3d4478fed1a25bea93bdfbeac@macports.org> Message-ID: <059.76fce31169552f5ebec7b38424ebf1d0@macports.org> #66569: libgcc11 @11.3.0 failed to install on MacOs Ventura ------------------------+-------------------- Reporter: djmagma | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: duplicate | Keywords: Port: libgcc11 | ------------------------+-------------------- Changes (by jmroot): * port: libgcc 11.3.0 => libgcc11 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:17:44 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:17:44 -0000 Subject: [MacPorts] #66570: gobject-introspection: switch to python311 on January 1 In-Reply-To: <043.62110448fb3ff2eb2878c2c28142679c@macports.org> References: <043.62110448fb3ff2eb2878c2c28142679c@macports.org> Message-ID: <058.d2e95d1ce30e5458604d820133a12b56@macports.org> #66570: gobject-introspection: switch to python311 on January 1 ------------------------------------+---------------------- Reporter: jowens | Owner: mascguy Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gobject-introspection | ------------------------------------+---------------------- Comment (by jmroot): The more permanent documentation of that is at wiki:Python#VersionPolicy BTW. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:18:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:18:47 -0000 Subject: [MacPorts] #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility In-Reply-To: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> References: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> Message-ID: <061.1acad76c3e73fc50fa080adadc0f85ac@macports.org> #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility ---------------------------+-------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: tcp_wrappers | ---------------------------+-------------------- Changes (by rbirkline): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:19:00 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:19:00 -0000 Subject: [MacPorts] #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility In-Reply-To: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> References: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> Message-ID: <061.ebc5a550e7dc4b6526cdb4b4e10797b5@macports.org> #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility ---------------------------+-------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: tcp_wrappers | ---------------------------+-------------------- Comment (by rbirkline): That looks like it is related when I looked at the main.log attached. Is there a way to get it to download from the correct place? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:23:29 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:23:29 -0000 Subject: [MacPorts] #66571: gimp2 @2.10.32+python27 fails to upgrade (build) on mavericks 2.10.32_2 < 2.10.32_3 In-Reply-To: <043.bb5e02145fb82d5f8d6ad5bfbba17f10@macports.org> References: <043.bb5e02145fb82d5f8d6ad5bfbba17f10@macports.org> Message-ID: <058.872ac908bc58cdf073e5fd237d792f92@macports.org> #66571: gimp2 @2.10.32+python27 fails to upgrade (build) on mavericks 2.10.32_2 < 2.10.32_3 ---------------------+---------------------- Reporter: tehcog | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gimp2 | ---------------------+---------------------- Changes (by jmroot): * owner: (none) => mascguy * status: new => assigned * cc: mascguy (removed) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:27:27 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:27:27 -0000 Subject: [MacPorts] #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility In-Reply-To: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> References: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> Message-ID: <061.56ee9af428b8c389d04455b27539612e@macports.org> #66573: tcp_wrappers 20_5.darwin_22.arm64 availablility ---------------------------+-------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: tcp_wrappers | ---------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => duplicate -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:28:27 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:28:27 -0000 Subject: [MacPorts] #66573: tcp_wrappers @20_5 checksum mismatch (was: tcp_wrappers 20_5.darwin_22.arm64 availablility) In-Reply-To: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> References: <046.e337be84c38f9ccb8a544b75b6e7d92d@macports.org> Message-ID: <061.7faa2f2057b265d2416238082f9d9f73@macports.org> #66573: tcp_wrappers @20_5 checksum mismatch ---------------------------+-------------------- Reporter: rbirkline | Owner: (none) Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: tcp_wrappers | ---------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:46:55 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:46:55 -0000 Subject: [MacPorts] #66539: tcp_wrappers: master_sites has moved In-Reply-To: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> References: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> Message-ID: <059.137e0f765d337dc5f51c08161831e1e1@macports.org> #66539: tcp_wrappers: master_sites has moved ---------------------------+---------------------- Reporter: 4d724ce | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: tcp_wrappers | ---------------------------+---------------------- Comment (by kencu): I just fixed this locally, but I could not get the GitHub PortGroup to obey my commands. I tried every option for the GitHub port group that there is. The only thing that worked for me was to put the entire URL to the file in as master_sites (minus the filename), and I know nobody accepts that, so I didn't PR it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:55:01 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:55:01 -0000 Subject: [MacPorts] #66539: tcp_wrappers: master_sites has moved In-Reply-To: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> References: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> Message-ID: <059.46d5fedd3ea6298c6085c9546851b6e2@macports.org> #66539: tcp_wrappers: master_sites has moved ---------------------------+--------------------- Reporter: 4d724ce | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: tcp_wrappers | ---------------------------+--------------------- Changes (by jmroot): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"a51d1fad372e701e16443e5a1b0ecb61457cc2bf/macports-ports" a51d1fad372e701e16443e5a1b0ecb61457cc2bf/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a51d1fad372e701e16443e5a1b0ecb61457cc2bf" tcp_wrappers: fix checksum mismatch Closes: https://trac.macports.org/ticket/66539 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 02:56:40 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 02:56:40 -0000 Subject: [MacPorts] #66539: tcp_wrappers: master_sites has moved In-Reply-To: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> References: <044.769fdc5e67138f3cff645ef739af9c8d@macports.org> Message-ID: <059.7c12214ccab4cf612c3807b69417ae53@macports.org> #66539: tcp_wrappers: master_sites has moved ---------------------------+--------------------- Reporter: 4d724ce | Owner: mascguy Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: tcp_wrappers | ---------------------------+--------------------- Comment (by jmroot): If you already fetched the mismatched file, run `sudo port clean --dist tcp_wrappers` and try again once the change propagates. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 03:31:06 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 03:31:06 -0000 Subject: [MacPorts] #66554: py-mutagen: add py311-mutagen subport In-Reply-To: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> References: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> Message-ID: <061.0c5293306d4d7908d3519421838223ce@macports.org> #66554: py-mutagen: add py311-mutagen subport --------------------------+-------------------- Reporter: radarhere | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-mutagen | --------------------------+-------------------- Comment (by radarhere): I've created https://github.com/macports/macports-ports/pull/17088 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 05:53:59 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 05:53:59 -0000 Subject: [MacPorts] #66562: minetest-devel: new port provides cutting edge Minetest (was: provide cutting edge Minetest by minetest-devel) In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.24134fd4fd41d65442c07f75ae1274c2@macports.org> #66562: minetest-devel: new port provides cutting edge Minetest --------------------------+---------------------- Reporter: Zweihorn | Owner: Zweihorn Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+---------------------- Changes (by Zweihorn): * owner: (none) => Zweihorn * status: new => assigned Old description: > The minetest port is at current MT 5.6.1, however the build may be **not > optimal** IMO. > > The long standing minetest port derives new versions by just updating the > sources and the checksums apparently. Certain defaults and specialities > in the build seem to have been overlooked from the start of this almost > historic port or have changed over time. If not for the well maintained > irrlichtmt port this unmaintained port could be called rather outdated in > some aspects. Anyway the resulting App cannot be called optimal. > > My cc to the maintainer of the irrlichtmt port is just for information. > Naturally, combined with my most friendly thank you for his commitment. > > (A) > There is a new port minetest-devel in the making and a new PR already in > the queue to come around. > The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 > and MT 5.6.1. The current MT runs on Big Sur as a local port as was done > with all the predecessors before on othe macOS versions respectively. > > (B) > My PR may solve the below issue too, although I have to check the details > again first. Or do you? > - #66408 > > (C) > You may note I would volunteer to become the maintainer of both the new > minetest-devel as the legacy minetest port together, if this would find > your approval. > > (D) > Please kindly note that I already advertised for MacPorts at the > Minetest community in the past with at least some success. > > Please have a look at: > > - https://forum.minetest.net/viewtopic.php?f=42&t=22427 > > - https://www.minetest.net/downloads/ --> macOS - MacPorts > > My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in > parallel to my now re-opened old account at the MT Forum for technical > reasons only. > > (E) > Only after well establishing minetest-devel and learning if the > expectations raised by my work are met on most if not all platforms, I > would consider improving minetest e.g., by making the build more > consistant and introducing a '--legacy' variant to help some users of the > legacy port. > > (F) > In the future both ports minetest and minetest-devel should continue, as > a new MT 5.6.2 may be understood stable but a new MT 5.7.0 would be work > in progress. AFAIK on top of that it is tradition with Minetest players > to stick with an older version as long as possible. > > (G) > Please accept my sincere apologies in advance if I do not cover all > aspects of your ticket process as I only came back recently after some > longe break. Obviously, I have to make myself more familiar with MacPort > internals again. > > Some if not all of the above will be copied in to a.m. PR in due time. > > Stay tuned. New description: MT 5.6.1 ''minetest-devel'' provides **better compatibility with other ports** and **greatly improves the internal performance** of the Minetest App by providing particular options to the build of the port. The long standing ''minetest'' port derived new versions by just **bumping** the sources and the checksums apparently. Certain defaults and specialities in the build seem to have been overlooked from the start of this almost historic port or have changed only upstream **without maintenance** over time. If not for the well maintained ''irrlichtmt'' port the **unmaintained ''minetest'' port** could be called rather outdated in some aspects. Anyway the resulting App is **not optimal**. My cc to the maintainer of the irrlichtmt port is just for information. Naturally, combined with my most friendly thank you for his commitment. (A) There is a new port minetest-devel in the making and a new PR already in the queue to come around. The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 and MT 5.6.1. The current MT runs on Big Sur as a local port as was done with all the predecessors before on othe macOS versions respectively. (B) My PR may solve the below issue too, although I have to check the details again first. Or do you? - #66408 (C) You may note I would volunteer to become the maintainer of both the new minetest-devel as the legacy minetest port together, if this would find your approval. (D) Please kindly note that I already advertised for MacPorts at the Minetest community in the past with at least some success. Please have a look at: - https://forum.minetest.net/viewtopic.php?f=42&t=22427 - https://www.minetest.net/downloads/ --> macOS - MacPorts My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in parallel to my now re-opened old account at the MT Forum for technical reasons only. (E) Only after well establishing minetest-devel and learning if the expectations raised by my work are met on most if not all platforms, I would consider improving minetest e.g., by making the build more consistant and introducing a '--legacy' variant to help some users of the legacy port. (F) In the future both ports minetest and minetest-devel should continue, as a new MT 5.6.2 may be understood stable but a new MT 5.7.0 would be work in progress. AFAIK on top of that it is tradition with Minetest players to stick with an older version as long as possible. (G) Please accept my sincere apologies in advance if I do not cover all aspects of your ticket process as I only came back recently after some longe break. Obviously, I have to make myself more familiar with MacPort internals again. Some if not all of the above will be copied in to a.m. PR in due time. Stay tuned. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 05:58:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 05:58:49 -0000 Subject: [MacPorts] #66297: id3v2 @0.1.12: /bin/sh: nroff: command not found In-Reply-To: <046.c5061dd47047e8813127c9e891438ba2@macports.org> References: <046.c5061dd47047e8813127c9e891438ba2@macports.org> Message-ID: <061.97ae356f6ec3b37ba097d27708549be7@macports.org> #66297: id3v2 @0.1.12: /bin/sh: nroff: command not found ------------------------+--------------------- Reporter: sptrakesh | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: ventura Port: id3v2 | ------------------------+--------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"2d36e96465b50a35f34599a807695256963296f8/macports-ports" 2d36e96465b50a35f34599a807695256963296f8/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2d36e96465b50a35f34599a807695256963296f8" id3v2: fix build on Ventura+ needs groff, no longer provided by system closes: https://trac.macports.org/ticket/66297 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 06:01:33 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 06:01:33 -0000 Subject: [MacPorts] #66358: extract phase fails in trace-mode on macOS 13 In-Reply-To: <047.e6fe989fc104c2c0375afa5734c385c8@macports.org> References: <047.e6fe989fc104c2c0375afa5734c385c8@macports.org> Message-ID: <062.46595dccbfdf01e66c1c087497446c49@macports.org> #66358: extract phase fails in trace-mode on macOS 13 -------------------------+--------------------- Reporter: reneeotten | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: ventura Port: | -------------------------+--------------------- Comment (by kencu): if anyone knows a workaround for this, I'd like to hear it. As much as possible, I try to use trace mode to verify builds, but this makes it difficult. Extracting normally and then building in trace mode fails. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 06:07:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 06:07:35 -0000 Subject: [MacPorts] #66492: mpir requires texinfo but is not a requirement.... In-Reply-To: <046.fd4a020c28b22c6c7c4b3f404668ac03@macports.org> References: <046.fd4a020c28b22c6c7c4b3f404668ac03@macports.org> Message-ID: <061.b09d9d033d8a400f1b7680a40f5b3fbc@macports.org> #66492: mpir requires texinfo but is not a requirement.... ------------------------+----------------------- Reporter: sck-nogas | Owner: michaelld Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: ventura Port: mpir | ------------------------+----------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"345a6f2d0a54e8f1e868829e069c467222c55139/macports-ports" 345a6f2d0a54e8f1e868829e069c467222c55139/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="345a6f2d0a54e8f1e868829e069c467222c55139" mpir: fix build on Ventura+ requires makeinfo, no longer supplied by system closes: https://trac.macports.org/ticket/66492 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 07:13:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 07:13:58 -0000 Subject: [MacPorts] #66574: lenstool @7.1.1 fails to build with recent Xcode Message-ID: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> #66574: lenstool @7.1.1 fails to build with recent Xcode --------------------+---------------------- Reporter: jmroot | Owner: ejullo Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: lenstool --------------------+---------------------- Implicit declaration errors: {{{ o_pixsource.c:33:6: error: implicitly declaring library function 'strcmp' with type 'int (const char *, const char *)' [-Werror,-Wimplicit-function- declaration] if( strcmp(M.centerfile, "") ) ^ o_pixsource.c:33:6: note: include the header or explicitly provide a declaration for 'strcmp' o_pixsource.c:161:3: error: implicit declaration of function 'd_rbf' is invalid in C99 [-Werror,-Wimplicit-function-declaration] d_rbf(source, ps.nx, ps.ny, 1.); ^ 2 errors generated. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 07:15:05 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 07:15:05 -0000 Subject: [MacPorts] #66574: lenstool @7.1.1 fails to build with recent Xcode In-Reply-To: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> References: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> Message-ID: <058.4e928d3c0f07c33abac0ba18d7619759@macports.org> #66574: lenstool @7.1.1 fails to build with recent Xcode -----------------------+---------------------- Reporter: jmroot | Owner: ejullo Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lenstool | -----------------------+---------------------- Changes (by jmroot): * cc: eric.jullo@? (added) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 09:44:13 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 09:44:13 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.49354427ec76df6d926c894420d0861b@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): I tried to symlink this sdk into the two locations, namely to a homonymous folder ? but that did not work. I?m not sure how the mechanism of --show- sdk-path works. Perhaps not with simple detection but with switches somewhere in a plist. If MacPorts offers to install additional sdks it would be nie if there was a postflight script, adding the necessary elements to use these sdks when they are needed. I?m really not sure if I should not give up the adequate macOS el capitan xcode 8.2.1, get rid of it and install xcode 7.3. This would be a strange and maybe big step, but these problems are annoying. Though it worked until this last stumble. But but my revbump hangs. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 09:46:12 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 09:46:12 -0000 Subject: [MacPorts] #66575: ncplot @4.11.0: ld: library not found for -lfl Message-ID: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> #66575: ncplot @4.11.0: ld: library not found for -lfl ------------------------+---------------------- Reporter: ryandesign | Owner: mf2k Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: ncplot ------------------------+---------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/7833/steps/install-port/logs/stdio {{{ ld: library not found for -lfl }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 10:53:32 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 10:53:32 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.a54ff1608764ce96b6cd46b5e7cad782@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by jmroot): The silly thing about all this is that you don't even need to use an SDK on < 10.14; all the headers and libs are present under `/` (i.e. `/usr/include` for headers) if you have the CLTs installed. I think that's the logic behind Apple not including a 10.11 SDK with Xcode 8 or the CLTs. Downloading Xcode 7.3.1 and copying the 10.11 SDK out of the app bundle and into `/Library/Developer/CommandLineTools/SDKs` does seem to work, at least for the purposes of `env DEVELOPER_DIR=/Library/Developer/CommandLineTools xcrun --sdk macosx10.11 --show-sdk-path`. However it seems like it would be preferable to patch whatever needs to be patched to convince the build system that the SDK flags can simply be omitted on these older OS versions. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 11:02:55 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 11:02:55 -0000 Subject: [MacPorts] #66575: ncplot @4.11.0: ld: library not found for -lfl In-Reply-To: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> References: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> Message-ID: <062.df7d317533534d601f2e43deaaa31bad@macports.org> #66575: ncplot @4.11.0: ld: library not found for -lfl -------------------------+---------------------- Reporter: ryandesign | Owner: mf2k Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: ncplot | -------------------------+---------------------- Changes (by jmroot): * keywords: ventura => Comment: Looks like it's failing everywhere since the last update. `libfl` is provided by flex. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 12:47:20 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 12:47:20 -0000 Subject: [MacPorts] #66554: py-mutagen: add py311-mutagen subport In-Reply-To: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> References: <046.64a03ad1ee7563a4de768f4f29f14848@macports.org> Message-ID: <061.bdcb98596181847a6e259dc025ca52ec@macports.org> #66554: py-mutagen: add py311-mutagen subport --------------------------+-------------------- Reporter: radarhere | Owner: (none) Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-mutagen | --------------------------+-------------------- Changes (by reneeotten): * status: new => closed * resolution: => fixed Comment: Fixed in [changeset:449babd171f14f5e8facc55970443c6c90e1584/macports-ports this commit] -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 12:55:30 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 12:55:30 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.9aad08ff5b3f8c71a32cc5c0e1664543@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): the real issue is the current portgile testing shows he has the 10.11 sdk when he doesn?t have it: {{{ 105 :debug:configure qt5 Portfile: the initial SDK value is: macosx10.11 106 :debug:configure qt5 Portfile: testing for system-specific SDK: 107 :debug:configure qt5 Portfile: system-specific SDK was found. 108 :debug:configure qt5 Portfile: the final SDK value is: macosx10.11 }}} so he doesn?t properly fall back. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 13:15:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 13:15:49 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.cbf693b949be4ffd1d19f3ec5d38b90d@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): I could have another go at fixing that testing code, as I have the 10.11 system right in frontbof me, but I thought I would better leave it to you, as you just took it all apart and put it together again, and I don?t want to step on your toes about fixing it. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 13:42:54 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 13:42:54 -0000 Subject: [MacPorts] #66576: py-cython tries using Xcode clang on Rosetta (for ppc), needs to be blacklisted Message-ID: <049.ebd74547d5b916a2157cad2cbae08cf8@macports.org> #66576: py-cython tries using Xcode clang on Rosetta (for ppc), needs to be blacklisted -------------------------------------------+----------------------- Reporter: barracuda156 | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: snowleopard, rosetta, powerpc | Port: py-cython -------------------------------------------+----------------------- {{{ /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -arch ppc -isysroot/ -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- cython/py311-cython/work/Cython-0.29.32/Cython/Compiler/Scanning.c -o build/temp.macosx-10.6-ppc- cpython-311/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- cython/py311-cython/work/Cython-0.29.32/Cython/Compiler/Scanning.o clang: warning: not using the clang compiler for the 'powerpc' architecture }}} Either {clang < 421} should be added to blacklist or, if it works fine on x86, Xcode clang is to be blacklisted for PPC. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 14:37:03 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 14:37:03 -0000 Subject: [MacPorts] #66577: py311-numpy uses -march=native on PPC, which breaks the build Message-ID: <049.72f631eb12f24cd79a0d84fcec21ba06@macports.org> #66577: py311-numpy uses -march=native on PPC, which breaks the build -------------------------------------------+------------------------- Reporter: barracuda156 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: snowleopard, rosetta, powerpc | Port: py311-numpy -------------------------------------------+------------------------- {{{ :info:build INFO: compile options: '-Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -Inumpy/core/src/_simd -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -Ibuild/src.macosx-10.6-ppc-3.11/numpy/core/src/common -Ibuild/src.macosx-10.6-ppc-3.11/numpy/core/src/npymath -c' :info:build extra options: '-march=native' :info:build WARN: CCompilerOpt.dist_test[630] : CCompilerOpt._dist_test_spawn[764] : Command (/opt/local/bin/gcc-mp-12 -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -arch ppc -isysroot/ -Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -Inumpy/core/src/_simd -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -Ibuild/src.macosx-10.6-ppc-3.11/numpy/core/src/common -Ibuild/src.macosx-10.6-ppc-3.11/numpy/core/src/npymath -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/numpy-1.23.5/numpy/distutils/checks/test_flags.c -o /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/.tmp/tmpgbslfmky/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/numpy-1.23.5/numpy/distutils/checks/test_flags.o -MMD -MF /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/.tmp/tmpgbslfmky/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/numpy-1.23.5/numpy/distutils/checks/test_flags.o.d -march=native) failed with exit status 1 output -> :info:build gcc-mp-12: error: unrecognized command-line option '-march=native'; did you mean '-mcpu=native'? :info:build WARN: CCompilerOpt.cc_test_flags[1077] : testing failed :info:build INFO: CCompilerOpt.cc_test_flags[1073] : testing flags (-O3) }}} And then: {{{ :info:build ########### CLIB COMPILER OPTIMIZATION ########### :info:build INFO: Platform : :info:build Architecture: unsupported :info:build Compiler : gcc :info:build CPU baseline : :info:build Requested : optimization disabled :info:build Enabled : none :info:build Flags : none :info:build Extra checks: none :info:build Requested : optimization disabled :info:build CPU dispatch : :info:build Enabled : none :info:build Generated : none :info:build INFO: CCompilerOpt.cache_flush[857] : write cache to path -> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/numpy-1.23.5/build/temp.macosx-10.6-ppc-3.11/ccompiler_opt_cache_clib.py :info:build * Building wheel... :info:build ERROR Backend subprocess exited when trying to invoke build_wheel :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- numpy/py311-numpy/work/numpy-1.23.5" && /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 -m build --wheel --no-isolation --outdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py-numpy/py311-numpy/work --skip-dependency-check :info:build Exit code: 1 :error:build Failed to build py311-numpy: command execution failed :debug:build Error code: CHILDSTATUS 90500 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 14:38:32 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 14:38:32 -0000 Subject: [MacPorts] #66577: py311-numpy uses -march=native on PPC, which breaks the build In-Reply-To: <049.72f631eb12f24cd79a0d84fcec21ba06@macports.org> References: <049.72f631eb12f24cd79a0d84fcec21ba06@macports.org> Message-ID: <064.f70545adf7f476ee8dd3d9392d8c84e5@macports.org> #66577: py311-numpy uses -march=native on PPC, which breaks the build ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard, rosetta, powerpc Port: py311-numpy | ---------------------------+------------------------------------------- Changes (by barracuda156): * Attachment "main.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 16:03:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 16:03:58 -0000 Subject: [MacPorts] #66577: py311-numpy uses -march=native on PPC, which breaks the build In-Reply-To: <049.72f631eb12f24cd79a0d84fcec21ba06@macports.org> References: <049.72f631eb12f24cd79a0d84fcec21ba06@macports.org> Message-ID: <064.737ad31220bab6b6ed335674e54c9a6b@macports.org> #66577: py311-numpy uses -march=native on PPC, which breaks the build ---------------------------+------------------------------------------- Reporter: barracuda156 | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: snowleopard, rosetta, powerpc Port: py311-numpy | ---------------------------+------------------------------------------- Comment (by kencu): is this on a 10.6 system running rosetta, or on 10.6-for-PPC? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 16:26:49 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 16:26:49 -0000 Subject: [MacPorts] #66265: llvm-9.0 @9.0.1_3+emulated_tls: CMake Error at CMakeLists.txt:653 (if): if given arguments: "VERSION_LESS" "2.7" Unknown arguments specified In-Reply-To: <042.ff77b1c44aa9363aecd27a6f5e55ea3d@macports.org> References: <042.ff77b1c44aa9363aecd27a6f5e55ea3d@macports.org> Message-ID: <057.2c608c792d975e8fb26988dbe9c8c90c@macports.org> #66265: llvm-9.0 @9.0.1_3+emulated_tls: CMake Error at CMakeLists.txt:653 (if): if given arguments: "VERSION_LESS" "2.7" Unknown arguments specified -----------------------+---------------------- Reporter: deril | Owner: jeremyhu Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: llvm-9.0 | -----------------------+---------------------- Comment (by kencu): llvms up to 9.0 were fixed by https://github.com/macports/macports- ports/commit/e582f39cb5e4807717275bf4ebf804db0830f2f7 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:05:35 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:05:35 -0000 Subject: [MacPorts] #66265: llvm-9.0 @9.0.1_3+emulated_tls: CMake Error at CMakeLists.txt:653 (if): if given arguments: "VERSION_LESS" "2.7" Unknown arguments specified In-Reply-To: <042.ff77b1c44aa9363aecd27a6f5e55ea3d@macports.org> References: <042.ff77b1c44aa9363aecd27a6f5e55ea3d@macports.org> Message-ID: <057.e3ba143e75b7ec1d21a343ac3f66f9fc@macports.org> #66265: llvm-9.0 @9.0.1_3+emulated_tls: CMake Error at CMakeLists.txt:653 (if): if given arguments: "VERSION_LESS" "2.7" Unknown arguments specified -----------------------+---------------------- Reporter: deril | Owner: jeremyhu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: llvm-9.0 | -----------------------+---------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: and llvm-10 by: https://github.com/macports/macports- ports/commit/67447d13907e656c05d5556cdaf7d659a0dc2b99 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:20:25 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:20:25 -0000 Subject: [MacPorts] #58275: octave does not build graphics toolkit qt with qt4 In-Reply-To: <051.66fffa1efd3f8b1db74eb40466f5b28f@macports.org> References: <051.66fffa1efd3f8b1db74eb40466f5b28f@macports.org> Message-ID: <066.8e640152c274e766a7c77677bf4b1a8f@macports.org> #58275: octave does not build graphics toolkit qt with qt4 -----------------------------+--------------------------------- Reporter: chrisjohgorman | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.5.4 Resolution: wontfix | Keywords: Port: octave | -----------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => wontfix Comment: I am sorry we were never able to resolve this issue, but Octave no longer supports Qt 4. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:25:50 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:25:50 -0000 Subject: [MacPorts] #66504: geda-gaf @1.10.2: /bin/sh: no: command not found In-Reply-To: <047.96a7e22c955739d344853ca74de452cd@macports.org> References: <047.96a7e22c955739d344853ca74de452cd@macports.org> Message-ID: <062.47a44c686990aab42e6439ae78059582@macports.org> #66504: geda-gaf @1.10.2: /bin/sh: no: command not found -------------------------+---------------------- Reporter: ryandesign | Owner: markemer Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: ventura Port: geda-gaf | -------------------------+---------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"e6e7a38939c2dfb0545a894680ab40b3430843f2/macports-ports" e6e7a38939c2dfb0545a894680ab40b3430843f2/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="e6e7a38939c2dfb0545a894680ab40b3430843f2" geda-gaf: requires groff groff is not present in the system on Ventura+ closes: https://trac.macports.org/ticket/66504 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:28:02 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:28:02 -0000 Subject: [MacPorts] #61126: verilator: fails to compile "trace" output In-Reply-To: <043.4ebe02ebe015215470523e4ce2b4cf36@macports.org> References: <043.4ebe02ebe015215470523e4ce2b4cf36@macports.org> Message-ID: <058.b61bcdf20fb4eb35cdffccd99bf858ec@macports.org> #61126: verilator: fails to compile "trace" output ------------------------+--------------------------------- Reporter: ragge0 | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: verilator | ------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => invalid Comment: I do not believe this is a verilator problem.\\ The code seems to require [https://en.cppreference.com/w/cpp/memory/new/align_val_t C++17]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:35:58 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:35:58 -0000 Subject: [MacPorts] #60438: ports that use rust no longer able to build universal with i386 In-Reply-To: <047.13b9d6df74a5b585c4ee286ce02a6fc7@macports.org> References: <047.13b9d6df74a5b585c4ee286ce02a6fc7@macports.org> Message-ID: <062.ecdf529aeb63b214672a03b040436790@macports.org> #60438: ports that use rust no longer able to build universal with i386 -------------------------------------------------+------------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: Port: rust librsvg racer geckodriver | newsboat sequoia-pgp | -------------------------------------------------+------------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => fixed Comment: i386 support in Rust should now [https://github.com/macports/macports- ports/commit/f193cea557f10ce4ff70121240620d9fc5f19eeb be available] back to 10.5. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:41:22 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:41:22 -0000 Subject: [MacPorts] #65775: rust @1.61.0_2 fails to build on Monterey/arm64 In-Reply-To: <043.542e30448379ecbfb441de5ab217868e@macports.org> References: <043.542e30448379ecbfb441de5ab217868e@macports.org> Message-ID: <058.48c1ecce8ec7197edc9ec193458c0b55@macports.org> #65775: rust @1.61.0_2 fails to build on Monterey/arm64 ---------------------+--------------------------------- Reporter: dsteck | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: fixed | Keywords: monterey, arm64 Port: rust | ---------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: Rust is now at version 1.66.0, and should be building on Apple Silicon machines.\\ Please feel free to reopen if this is not the case. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:48:41 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:48:41 -0000 Subject: [MacPorts] #65607: rust -- [OSX 10.6.8] linking with `cc` failed [while building wheel for cryptography] In-Reply-To: <044.9838323895b711c64100c5c24d244a43@macports.org> References: <044.9838323895b711c64100c5c24d244a43@macports.org> Message-ID: <059.d456db6d9d6a738587564d6889ca6e3d@macports.org> #65607: rust -- [OSX 10.6.8] linking with `cc` failed [while building wheel for cryptography] ----------------------+-------------------- Reporter: lawlist | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: rust | ----------------------+-------------------- Changes (by MarcusCalhoun-Lopez): * status: new => closed * resolution: => invalid Comment: Unfortunately, on older systems, the default build tools do not work.\\ In MacPorts, the rust PG goes to a great deal of trouble to set the [https://github.com/macports/macports- ports/blob/e6e7a38939c2dfb0545a894680ab40b3430843f2/_resources/port1.0/group/rust-1.0.tcl#L696 compilers] and the [https://github.com/macports/macports- ports/blob/e6e7a38939c2dfb0545a894680ab40b3430843f2/_resources/port1.0/group/rust-1.0.tcl#L667 linker].\\ Also, the linker needs to be the one [https://github.com/macports /macports- ports/blob/e6e7a38939c2dfb0545a894680ab40b3430843f2/_resources/port1.0/group/rust-1.0.tcl#L768 provided by MacPorts]. My suggestion would be to create a [https://guide.macports.org/chunked/development.html port] for tda-api so that you can take advantage of the MacPorts infrastructure. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:51:52 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:51:52 -0000 Subject: [MacPorts] #60511: move to quartz as default backend In-Reply-To: <044.79ec6e6b91fdbf38d8f6f63acc927bbc@macports.org> References: <044.79ec6e6b91fdbf38d8f6f63acc927bbc@macports.org> Message-ID: <059.d2d4f90f763267cbfb59f27c7c958d60@macports.org> #60511: move to quartz as default backend -------------------------------------------------+------------------------- Reporter: ra1nb0w | Owner: mascguy Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: R Togl VLC VLC2 avahi cairo cairo- | devel cairomm cherrytree clutter cogl | gWakeOnLAN gconf gegl gegl-0.3 gegl-devel | geoclue2 glade glib2 glib2-devel glibmm | gnome-themes-extra gnubg gnucash-docs gtk- | sharp2 gtk2 gtk3 gtkextra3 gtkimageview gtkmm | gtkmm3 gtkspell2 inkscape inkscape-devel | inkscape-gtk3-devel lablgtk2 libVLC libVLC2 | librsvg meld netgen opencolorio pan2 pango | pango-devel pangomm pdfpc pidgin pspp pspp- | devel py-cairo py-gobject py-pygtk reinteract | tix tk tkdnd tkimg tktable ufraw webkit2-gtk | webkit2-gtk-devel wxgtk-3.0 | -------------------------------------------------+------------------------- Changes (by MarcusCalhoun-Lopez): * cc: inyeollee (added) Comment: https://trac.macports.org/ticket/49376 has been marked as a duplicate of this ticket. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 17:51:56 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 17:51:56 -0000 Subject: [MacPorts] #49376: tk defaults to using X11, not OS X native graphics In-Reply-To: <046.504787c1fe965e616c64843bf3b1ffcd@macports.org> References: <046.504787c1fe965e616c64843bf3b1ffcd@macports.org> Message-ID: <061.272d1f66446856eedf4f8c579b486dfc@macports.org> #49376: tk defaults to using X11, not OS X native graphics ------------------------+--------------------------------- Reporter: inyeollee | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: duplicate | Keywords: Port: tk | ------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => duplicate Comment: This ticket has been superseded by [https://trac.macports.org/ticket/60511 a more general discussion]. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 18:35:00 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 18:35:00 -0000 Subject: [MacPorts] #66284: gdb @12.1 build failure on macOS 13: 'makeinfo' is missing on your system. In-Reply-To: <046.9cb10daf211f91b792fde957d46f599f@macports.org> References: <046.9cb10daf211f91b792fde957d46f599f@macports.org> Message-ID: <061.0ea3cab18b8d0bf5df487dfdeef42ac8@macports.org> #66284: gdb @12.1 build failure on macOS 13: 'makeinfo' is missing on your system. ------------------------+--------------------- Reporter: JonTrepte | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: gdb | ------------------------+--------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"b8b7db202cebf75504e7d30f9e46116010ad93a6/macports-ports" b8b7db202cebf75504e7d30f9e46116010ad93a6/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="b8b7db202cebf75504e7d30f9e46116010ad93a6" gdb: fix build on Intel Ventura Ventura does not come with makeinfo, so add dep for texinfo if needed fix makeinfo test in libctf to not fail when makeinfo is newer than 7.x closes: https://trac.macports.org/ticket/66284 arm build is still not fixed as yet. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 19:16:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 19:16:47 -0000 Subject: [MacPorts] #66575: ncplot @4.11.0: ld: library not found for -lfl In-Reply-To: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> References: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> Message-ID: <062.1646d2f858c24d62760d4fcabe931dc0@macports.org> #66575: ncplot @4.11.0: ld: library not found for -lfl -------------------------+-------------------- Reporter: ryandesign | Owner: mf2k Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ncplot | -------------------------+-------------------- Changes (by Frank Schima ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"31702d06ea32a928b81d84c0bd84d42b80b2bba8/macports-ports" 31702d06ea32a928b81d84c0bd84d42b80b2bba8/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="31702d06ea32a928b81d84c0bd84d42b80b2bba8" ncplot: Add flex as dependency - Add worksrcdir fix for latest base Fixes: https://trac.macports.org/ticket/66575 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 20:30:14 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 20:30:14 -0000 Subject: [MacPorts] #66578: mcfly @0.7.1: upgrading shell integration results in prompts saying "error: The argument '--append-to-histfile ' requires a value but none was supplied" Message-ID: <048.7ccba4222c419f4a4759c9e9abb912fa@macports.org> #66578: mcfly @0.7.1: upgrading shell integration results in prompts saying "error: The argument '--append-to-histfile ' requires a value but none was supplied" -------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: mcfly -------------------------+-------------------- I recently upgraded mcfly to 0.7.1, and now after every shell prompt I get a message saying: {{{ error: The argument '--append-to-histfile ' requires a value but none was supplied For more information try '--help' }}} The mcfly port already contains the following notes: {{{ $ port notes mcfly ---> mcfly has the following notes: If you are running bash as your shell, add: if [[ -r "/opt/local/share/mcfly/mcfly.bash" ]]; then source "/opt/local/share/mcfly/mcfly.bash" fi ...to your ~/.bashrc, then run: $ . ~/.bashrc If you are running zsh as your shell, add: if [[ -r "/opt/local/share/mcfly/mcfly.zsh" ]]; then source "/opt/local/share/mcfly/mcfly.zsh" fi ...to your .zshrc, then run: $ . ~/.zshrc If you are running fish as your shell, add: if [[ -r "/opt/local/share/mcfly/mcfly.fish" ]]; then source "/opt/local/share/mcfly/mcfly.fish" fi ...to your ~/.config/fish/config.fish, then run: $ source ~/.config/fish/config.fish }}} It seems as though these notes about shell integration might need to be updated? (I'm using bash for my shell, btw) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:49:12 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 22:49:12 -0000 Subject: [MacPorts] #66579: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64) Message-ID: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> #66579: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64) --------------------+-------------------------- Reporter: ronf | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py310-cython --------------------+-------------------------- I recently upgraded my Mac to Ventura and have not been able to install py310-cython (which a number of other ports depend on). The problem appears to be related to setuptools/distutils, but attempts to uninstall and reinstall those haven't made a difference. Here's some of the relevant log output from the failure: {{{:info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'python_requires' :info:build warnings.warn(msg) :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'zip_safe' :info:build warnings.warn(msg) :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'entry_points' :info:build warnings.warn(msg) :info:build usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] :info:build or: setup.py --help [cmd1 cmd2 ...] :info:build or: setup.py --help-commands :info:build or: setup.py cmd --help :info:build error: invalid command 'egg_info' :info:build ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py- cython/py310-cython/work/Cython-0.29.32" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 -m build --wheel --no-isolation --outdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-cython/py310-cython/work :info:build Exit code: 1 }}} This is on a fresh install of MacPorts and all its pots after the OS upgrade, following the usual "Migration" documentation. Prior to the upgrade, the python install was working fine. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:50:48 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 22:50:48 -0000 Subject: [MacPorts] #66579: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64) In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.99144d06729296ca39898a02544780f3@macports.org> #66579: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64) ---------------------------+-------------------- Reporter: ronf | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py310-cython | ---------------------------+-------------------- Changes (by ronf): * Attachment "main.log" added. Full log from attempt to install py310-cython -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 22:51:47 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 22:51:47 -0000 Subject: [MacPorts] #66579: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64) In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.96c76308b7e18b1acf0616139ae6bd6d@macports.org> #66579: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64) ---------------------------+-------------------- Reporter: ronf | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py310-cython | ---------------------------+-------------------- Description changed by ronf: Old description: > I recently upgraded my Mac to Ventura and have not been able to install > py310-cython (which a number of other ports depend on). The problem > appears to be related to setuptools/distutils, but attempts to uninstall > and reinstall those haven't made a difference. Here's some of the > relevant log output from the failure: > > {{{:info:build > /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 > /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown > distribution option: 'python_requires' > :info:build warnings.warn(msg) > :info:build > /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 > /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown > distribution option: 'zip_safe' > :info:build warnings.warn(msg) > :info:build > /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 > /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown > distribution option: 'entry_points' > :info:build warnings.warn(msg) > :info:build usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 > [cmd2_opts] ...] > :info:build or: setup.py --help [cmd1 cmd2 ...] > :info:build or: setup.py --help-commands > :info:build or: setup.py cmd --help > :info:build error: invalid command 'egg_info' > :info:build ERROR Backend subprocess exited when trying to invoke > get_requires_for_build_wheel > :info:build Command failed: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports > .org_release_tarballs_ports_python_py- > cython/py310-cython/work/Cython-0.29.32" && > /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 > -m build --wheel --no-isolation --outdir > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports > .org_release_tarballs_ports_python_py-cython/py310-cython/work > :info:build Exit code: 1 > }}} > > This is on a fresh install of MacPorts and all its pots after the OS > upgrade, following the usual "Migration" documentation. Prior to the > upgrade, the python install was working fine. New description: I recently upgraded my Mac to Ventura and have not been able to install py310-cython (which a number of other ports depend on). The problem appears to be related to setuptools/distutils, but attempts to uninstall and reinstall those haven't made a difference. Here's some of the relevant log output from the failure: {{{ :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'python_requires' :info:build warnings.warn(msg) :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'zip_safe' :info:build warnings.warn(msg) :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'entry_points' :info:build warnings.warn(msg) :info:build usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] :info:build or: setup.py --help [cmd1 cmd2 ...] :info:build or: setup.py --help-commands :info:build or: setup.py cmd --help :info:build error: invalid command 'egg_info' :info:build ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py- cython/py310-cython/work/Cython-0.29.32" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 -m build --wheel --no-isolation --outdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-cython/py310-cython/work :info:build Exit code: 1 }}} This is on a fresh install of MacPorts and all its pots after the OS upgrade, following the usual "Migration" documentation. Prior to the upgrade, the python install was working fine. -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 23:35:00 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 23:35:00 -0000 Subject: [MacPorts] #66580: heimdal @7.7.0: makeinfo: command not found Message-ID: <047.5e9f69ba5729eb1b84879a555ef38574@macports.org> #66580: heimdal @7.7.0: makeinfo: command not found ------------------------+--------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: heimdal ------------------------+--------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/8113/steps/install-port/logs/stdio {{{ /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_net_heimdal/heimdal/work/heimdal-7.7.0/missing: line 81: makeinfo: command not found WARNING: 'makeinfo' is missing on your system. You should only need it if you modified a '.texi' file, or any other file indirectly affecting the aspect of the manual. You might want to install the Texinfo package: The spurious makeinfo call might also be the consequence of using a buggy 'make' (AIX, DU, IRIX), in which case you might want to install GNU make: make[1]: *** [heimdal.info] Error 127 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Wed Dec 28 23:35:57 2022 From: noreply at macports.org (MacPorts) Date: Wed, 28 Dec 2022 23:35:57 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' (was: Error installing latest py310-cython (@0.29.32) on macOS Ventura (arm64)) In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.e95106f83f7c0e521e949862efd5761e@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Changes (by ryandesign): * owner: (none) => stromnov * keywords: => ventura arm64 * status: new => assigned * port: py310-cython => py-cython -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:31:08 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 00:31:08 -0000 Subject: [MacPorts] #66580: heimdal @7.7.0: makeinfo: command not found In-Reply-To: <047.5e9f69ba5729eb1b84879a555ef38574@macports.org> References: <047.5e9f69ba5729eb1b84879a555ef38574@macports.org> Message-ID: <062.c3eaea2c650356c99297a1169c33e3ae@macports.org> #66580: heimdal @7.7.0: makeinfo: command not found -------------------------+--------------------- Reporter: ryandesign | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: heimdal | -------------------------+--------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"a23a7573bb03e8cbbea8cc4c04c004e624741ef0/macports-ports" a23a7573bb03e8cbbea8cc4c04c004e624741ef0/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a23a7573bb03e8cbbea8cc4c04c004e624741ef0" heimdal: requires makeinfo closes: https://trac.macports.org/ticket/66580 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 00:36:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 00:36:13 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.acc8846e93b641012b123b1578240f86@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by kencu): I can't reproduce this - py310-cython installs without trouble for me: {{{ % port -v installed py310-cython The following ports are currently installed: py310-cython @0.29.32_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T21:42:35-0800' }}} I installed it with no ports active, and let it call in what it wanted: {{{ % port -v installed | grep active bzip2 @1.0.8_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:30:37-0800' cython_select @0.1_2 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:11-0800' expat @2.5.0_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:35:24-0800' gettext-runtime @0.21_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:19:55-0800' libedit @20221030-3.1_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:35:33-0800' libffi @3.4.4_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:25:58-0800' libiconv @1.17_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:19:19-0800' ncurses @6.3_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:20:28-0800' openssl @3_8 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:36:36-0800' openssl3 @3.0.7_2+legacy (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:36:31-0800' py310-build @0.9.0_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:11-0800' py310-cython @0.29.32_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T21:42:35-0800' py310-installer @0.6.0_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:12-0800' py310-packaging @22.0_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:11-0800' py310-pep517 @0.13.0_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:11-0800' py310-setuptools @65.6.3_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:13-0800' py310-tomli @2.0.1_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:11-0800' py310-wheel @0.38.4_0 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T21:42:13-0800' python3_select @0.0_3 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T19:36:38-0800' python310 @3.10.9_0+lto+optimizations (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:39:42-0800' python_select @0.3_10 (active) requested_variants='' platform='darwin 22' archs='noarch' date='2022-12-25T19:36:38-0800' sqlite3 @3.40.0_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:37:01-0800' xz @5.2.9_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:27:39-0800' zlib @1.2.13_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:27:43-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 01:22:07 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 01:22:07 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.d0cdaa43c46f7213fbb85c36329a76b7@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by jmroot): Saying I rewrote this code is giving me a bit too much credit I think; all I did was a fix a couple of bugs, the basic logic is as you wrote it in [fbdae6e6c2cc9c2a8b8a625e322aeee6bd00e610/macports-ports]. I don't have any special insight into the behaviour of xcrun on 10.11. But I do strongly recommend using the equivalent of no SDK flags or `-isysroot /` if at all possible, because that's what we do everywhere else on the systems where it's possible. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 03:14:24 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 03:14:24 -0000 Subject: [MacPorts] #65184: rust fails to mirror and fails to fetch on i386 In-Reply-To: <043.f4367b519bb57704fa5bbee4df62ebb4@macports.org> References: <043.f4367b519bb57704fa5bbee4df62ebb4@macports.org> Message-ID: <058.ec095fe9be27ea3acb1e2336d3d218b6@macports.org> #65184: rust fails to mirror and fails to fetch on i386 ---------------------+--------------------------------- Reporter: jmroot | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by jmroot): In [changeset:"7c4d20e6f97d2bd28230d66ea8ccc48df8240dc5/macports-ports" 7c4d20e6f97d2bd28230d66ea8ccc48df8240dc5/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7c4d20e6f97d2bd28230d66ea8ccc48df8240dc5" rust pg: don't add nonexistent Tiger distfiles See: https://trac.macports.org/ticket/65184 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 03:42:31 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 03:42:31 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.6e586720479ed146b101f3b029f07680@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by jmroot): In [changeset:"bd429607980029c1f569741f40839e58e3c3e60a/macports-ports" bd429607980029c1f569741f40839e58e3c3e60a/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="bd429607980029c1f569741f40839e58e3c3e60a" spice-server: attempt to use the right python See: https://trac.macports.org/ticket/66535 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 03:42:31 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 03:42:31 -0000 Subject: [MacPorts] #65184: rust fails to mirror and fails to fetch on i386 In-Reply-To: <043.f4367b519bb57704fa5bbee4df62ebb4@macports.org> References: <043.f4367b519bb57704fa5bbee4df62ebb4@macports.org> Message-ID: <058.f70d0590ddfe64b05cf46c16ca9334fc@macports.org> #65184: rust fails to mirror and fails to fetch on i386 ---------------------+--------------------------------- Reporter: jmroot | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by jmroot): In [changeset:"280f2d7a6b5d8d2358b4da62a80fb9fa3f3aa3c5/macports-ports" 280f2d7a6b5d8d2358b4da62a80fb9fa3f3aa3c5/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="280f2d7a6b5d8d2358b4da62a80fb9fa3f3aa3c5" rust: add workaround for mirroring i386 distfile See: https://trac.macports.org/ticket/65184 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 03:58:19 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 03:58:19 -0000 Subject: [MacPorts] #66581: No images displayed in standard mail (image viewer settings not working) Message-ID: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> #66581: No images displayed in standard mail (image viewer settings not working) -----------------------+------------------------ Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: claws-mail -----------------------+------------------------ Claws Mail has options in the Preferences under the "Message View" header for the built-in "Image Viewer". The problem is none of these seem to be currently working in the port -- none of the images are displayed in regular emails (non-HTML). I'm not sure if this is a dependency issue (if Claws Mail is relying on a library that isn't present to render/display the images), if it's a bug/omission in the port, or if I'm missing something. The logs don't seem to show anything wrong either -- Claws Mail doesn't seem to realise there is a problem. To replicate the issue, tick all the Image Viewer settings to be on, and relaunch Claws Mail. If there are image attachments in an email, Claws Mail won't show them in the mail (only links to the files). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:11:07 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:11:07 -0000 Subject: [MacPorts] #66244: db46 failed in patching mp/mp_region.c on osx 13 Ventura In-Reply-To: <044.84fe69d7cb45c7a9cc75ad1d68da7478@macports.org> References: <044.84fe69d7cb45c7a9cc75ad1d68da7478@macports.org> Message-ID: <059.e5f16a024a50e5e7968767a65000d9ad@macports.org> #66244: db46 failed in patching mp/mp_region.c on osx 13 Ventura ----------------------+--------------------- Reporter: dlamija | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: db46 | ----------------------+--------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"1eb314a2f52ac980eece16c0216876e99667d006/macports-ports" 1eb314a2f52ac980eece16c0216876e99667d006/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1eb314a2f52ac980eece16c0216876e99667d006" db46: fix patching on Ventura+ the patch command that comes with Ventura does not handle the variant line endings the way earlier versions of the patch command did. use gpatch instead closes: https://trac.macports.org/ticket/66244 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:12:51 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:12:51 -0000 Subject: [MacPorts] #66244: db46 failed in patching mp/mp_region.c on osx 13 Ventura In-Reply-To: <044.84fe69d7cb45c7a9cc75ad1d68da7478@macports.org> References: <044.84fe69d7cb45c7a9cc75ad1d68da7478@macports.org> Message-ID: <059.8a322e7e7837e1e7c1f479f55c60108a@macports.org> #66244: db46 failed in patching mp/mp_region.c on osx 13 Ventura ----------------------+--------------------- Reporter: dlamija | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: db46 | ----------------------+--------------------- Comment (by kencu): You are right, copying that patch file to the files directory and then converting it to UNIX format allows patch to work on Ventura. I tried using the "--binary" option to patch, which some said worked for this, but it didn't work here on Ventura for me. One of the patches is fairly large, the last one: {{{ % ls -la total 23320 drwxr-xr-x 7 macports wheel 224 28 Dec 19:20 . drwxr-xr-x 3 root wheel 96 28 Dec 19:20 .. -rw-r--r-- 1 macports wheel 11881885 28 Dec 19:20 db-4.6.21.tar.gz -rw-r--r-- 1 macports wheel 2475 28 Dec 19:20 patch.4.6.21.1 -rw-r--r-- 1 macports wheel 892 28 Dec 19:20 patch.4.6.21.2 -rw-r--r-- 1 macports wheel 1911 28 Dec 19:20 patch.4.6.21.3 -rw-r--r-- 1 macports wheel 41501 28 Dec 19:20 patch.4.6.21.4 }}} and downloading that one at least seems desirable. The .1, .2, and .3 patches could be moved into the files directory, or just the .2 patch moved in there. It's a bit confusing no matter which option is picked. this didn't work: {{{ depends_patch-append port:dos2unix pre-patch { system "${prefix}/bin/dos2unix [shellescape ${distpath}/patch.${version}.2]" } }}} {{{ Executing: cd "/opt/local/var/macports/build /_opt_macportsofficial_macports-ports_databases_db46/db46/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/db4/4.6.21_6/db-4.6.21.tar.gz' | /usr/bin/tar -xf - dos2unix: Failed to open temporary output file: Operation not permitted dos2unix: problems converting file /opt/local/var/macports/distfiles/db4/4.6.21_6/patch.4.6.21.2 Command failed: /opt/local/bin/dos2unix /opt/local/var/macports/distfiles/db4/4.6.21_6/patch.4.6.21.2 Exit code: 1 Error: Failed to patch db46: command execution failed }}} but this does work: {{{ if {${os.platform} eq "darwin" && ${os.major} >=22 } { depends_patch-append port:gpatch patch.cmd ${prefix}/bin/gpatch patch.pre_args-append --read-only=ignore } }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:32:44 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:32:44 -0000 Subject: [MacPorts] #66276: Grace configure fails on Ventura In-Reply-To: <045.3cf87486827775e923864fd36a4d7ea2@macports.org> References: <045.3cf87486827775e923864fd36a4d7ea2@macports.org> Message-ID: <060.d64099896cca0cbf12fe1365f2133ce9@macports.org> #66276: Grace configure fails on Ventura -----------------------+--------------------- Reporter: Vahid999 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: grace | -----------------------+--------------------- Comment (by kencu): I tried this tonight on Ventura arm64: {{{ % sudo port -f deactivate active % sudo port -v -N install grace ---> Computing dependencies for grace................................................................................... ---> Dependencies to be installed: libjpeg-turbo libpng zlib openbrowser p5.34-mac-propertylist p5.34-xml-entities p5.34-html-parser p5.34-html- tagset perl5.34 db48 gdbm gettext-runtime libiconv readline ncurses p5.34 -http-message p5.34-clone p5.34-b-cow p5.34-test-simple p5.34-xsloader p5.34-compress-raw-bzip2 p5.34-test-cpan-meta p5.34-test-cpan-meta-json p5.34-json p5.34-json-xs p5.34-canary-stability p5.34-common-sense p5.34 -types-serialiser p5.34-test-pod p5.34-pod-simple p5.34-encode p5.34-pod- escapes p5.34-compress-raw-zlib p5.34-encode-locale p5.34-http-date p5.34 -time-local p5.34-timedate p5.34-io-compress p5.34-io-compress-brotli p5.34-file-slurper p5.34-getopt-long p5.34-time-hires p5.34-io-html p5.34 -lwp-mediatypes p5.34-uri openmotif Xft2 expat fontconfig freetype brotli bzip2 ossp-uuid xrender xorg-libX11 xorg-libXau xorg-xorgproto xorg- libXdmcp xorg-libxcb xorg-libpthread-stubs xorg-xcb-proto libxml2 icu xz bison bison-runtime libtextstyle m4 flex gettext gettext-tools-libs pkgconfig xbitmaps xorg-libXext xorg-libXmu xorg-libXt xorg-libsm xorg- libice xorg-libXp pdflib xpm xorg-util-macros }}} I noticed first that {{{llvm-10}}} was not requested in the list of ports to install, as you can see. After that, all those ports built without trouble and {{{grace}}} was installed without any issues: {{{ % port -v installed grace The following ports are currently installed: grace @5.1.25_5 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-28T20:25:50-0800' }}} After installing {{{xorg-server}}}, {{{xmgrace}}} opened without troubles and on brief assessment appears to be functional. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:36:43 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:36:43 -0000 Subject: [MacPorts] #66276: Grace configure fails on Ventura In-Reply-To: <045.3cf87486827775e923864fd36a4d7ea2@macports.org> References: <045.3cf87486827775e923864fd36a4d7ea2@macports.org> Message-ID: <060.3ec2ee400fda0c21fa6dcf90fd942947@macports.org> #66276: Grace configure fails on Ventura -------------------------+--------------------- Reporter: Vahid999 | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura Port: grace | -------------------------+--------------------- Changes (by kencu): * status: new => closed * resolution: => worksforme Comment: Because this built easily for me here (although on arm64, admittedly) and because the attached failure log is for llvm-10 and not for grace, as you point out, I'm going to close this as "worksforme" and we can help you out further if you have trouble with grace in the future. I realize you got a bit of the run-around, but we will indeed help you get up to speed if you are stuck. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:40:01 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:40:01 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.666a0453d10126a11c785c439c13512f@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by jmroot): The most recent error in the log is different to the one quoted in the ticket description: {{{ :info:build ModuleNotFoundError: No module named 'setuptools.build_meta' }}} What does `port installed py310-setuptools` say? What happens if you start MacPorts python3.10 in your terminal and run `import setuptools.build_meta`? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:41:59 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:41:59 -0000 Subject: [MacPorts] #66581: claws-mail: No images displayed in standard mail (image viewer settings not working) (was: No images displayed in standard mail (image viewer settings not working)) In-Reply-To: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> References: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> Message-ID: <061.18832406e26d90dfe3efad35bcaf4de3@macports.org> #66581: claws-mail: No images displayed in standard mail (image viewer settings not working) -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: claws-mail | -------------------------+-------------------- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:44:58 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:44:58 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.56174f2e20235a4101eac3d48c7f34d0@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by ronf): Thanks for looking into this! I didn't have a second ARM64 machine available here to test on, but I was able to spin up a fresh macOS Ventura VM and install Xcode and MacPorts on it, and I can confirm in a completely fresh install I also did not see the problem. The py310-cython package and all its dependencies installed just fine. I'm going to take a closer look at the resulting files on the two systems, especially around files from setuptools, to see what differences might exist. What's odd here is that going through the "Migration" steps after upgrading to Ventura involved uninstalling ALL of the ports and installing fresh copies of all of them into an empty repository. So, other than the order ports were installed, it should have been very close to this fresh install. Also, manually uninstalling and reinstalling things like py310-setuptools hasn't helped. Here's what I get for "port installed py310-setuptools": {{{ The following ports are currently installed: py310-setuptools @65.6.3_0 (active) }}} There doesn't appear to be any "build_meta" in setuptools, though: {{{ ultra:~#python3.10 Python 3.10.9 (main, Dec 28 2022, 13:05:08) [Clang 14.0.0 (clang-1400.0.29.202)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import setuptools.build_meta Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'setuptools.build_meta' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:48:17 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:48:17 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.dbcf8e92ac76d98dbd7583766c096d8f@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by ronf): Checking the fresh VM, "import setuptools.build_meta" does work there, so perhaps there's some older version of setuptools which is being picked up on the machine with the error, despite the fact that both claim to have version 65.6.3_0 installed. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 04:59:49 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 04:59:49 -0000 Subject: [MacPorts] #65184: rust fails to mirror and fails to fetch on i386 In-Reply-To: <043.f4367b519bb57704fa5bbee4df62ebb4@macports.org> References: <043.f4367b519bb57704fa5bbee4df62ebb4@macports.org> Message-ID: <058.59aec25bfdd92cc98e61ecdc445caaf7@macports.org> #65184: rust fails to mirror and fails to fetch on i386 ---------------------+--------------------------------- Reporter: jmroot | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: rust | ---------------------+--------------------------------- Changes (by jmroot): * status: assigned => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 05:04:07 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 05:04:07 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.b2e22f862b40276f9bb7ab091f926766@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by ronf): Ok - I checked the setuptools directory, and definitely found some weirdness. For instance, __init.py__ didn't exist on my system even after a setuptools reinstall, but there was a file called __init__.py..mp_1648743825. That generally happens when multiple packages have found conflicts in which port owns a given file. Even after wiping out everything in /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools and doing a forced uninstall/reinstall, I'm still getting errors, though: I don't see anything about build_meta after manually cleaning out the setuptools site-packages dir. After that, "import setuptools.build_meta" worked on the original system, but the build is still failing, with the error about egg_info and some of the config options not being recognized: {{{ :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'python_requires' :info:build warnings.warn(msg) :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'zip_safe' :info:build warnings.warn(msg) :info:build /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'entry_points' :info:build warnings.warn(msg) :info:build usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] :info:build or: setup.py --help [cmd1 cmd2 ...] :info:build or: setup.py --help-commands :info:build or: setup.py cmd --help :info:build error: invalid command 'egg_info' :info:build ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py- cython/py310-cython/work/Cython-0.29.32" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 -m build --wheel --no-isolation --outdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-cython/py310-cython/work :info:build Exit code: 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 05:04:18 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 05:04:18 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.e787dfc35d75c813e26cbb64a787a326@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by jmroot): Nope. Have to define the option manually apparently. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 05:13:31 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 05:13:31 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.0bdba107cdd896cd33b4e617142105cc@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by jmroot): In [changeset:"c07be806f6d49fa9555ac722cbae383e2bc886d0/macports-ports" c07be806f6d49fa9555ac722cbae383e2bc886d0/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c07be806f6d49fa9555ac722cbae383e2bc886d0" spice-server: add python option to build system See: https://trac.macports.org/ticket/66535 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 05:14:46 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 05:14:46 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.43badfe000b4cd9375a9bbc687abfe93@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by kencu): when this happens, often the best solution is to nuke your installation of MacPorts and reinstall your ports?. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 06:06:20 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 06:06:20 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.879dcf11966157a14628b7d42a74fab3@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: spice-server | ---------------------------+-------------------- Comment (by jmroot): In [changeset:"aaac542bffcf9caa2b7d60536b3162c1e92a23f9/macports-ports" aaac542bffcf9caa2b7d60536b3162c1e92a23f9/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="aaac542bffcf9caa2b7d60536b3162c1e92a23f9" spice-server: add python option at top level too See: https://trac.macports.org/ticket/66535 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 06:14:44 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 06:14:44 -0000 Subject: [MacPorts] #66535: spice-server: configure: no module named 'six' In-Reply-To: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> References: <043.1d881f4e8715ad0e33da1867f3cb20f1@macports.org> Message-ID: <058.697d821dea3f1896b0437644d0771107@macports.org> #66535: spice-server: configure: no module named 'six' ---------------------------+-------------------- Reporter: vallon | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: spice-server | ---------------------------+-------------------- Changes (by jmroot): * status: new => closed * resolution: => fixed Comment: OK, fails on older platforms still, but that's a different issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 07:34:57 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 07:34:57 -0000 Subject: [MacPorts] #63020: xephem @4.0.1: install fails with "ld: library not found for -lXp" In-Reply-To: <045.4e2c574e64605afd06fc68e38a022559@macports.org> References: <045.4e2c574e64605afd06fc68e38a022559@macports.org> Message-ID: <060.b41250be6da02d50efe4474d3efc769a@macports.org> #63020: xephem @4.0.1: install fails with "ld: library not found for -lXp" -----------------------+-------------------------- Reporter: vidakris | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: bigsur arm64 Port: xephem | -----------------------+-------------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"4ce46e2e0925ede76d16d4c4e42038a615171ebe/macports-ports" 4ce46e2e0925ede76d16d4c4e42038a615171ebe/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4ce46e2e0925ede76d16d4c4e42038a615171ebe" xephem: fix build on Ventura add dep on groff if needed supported archs are i386 / x86_64 / ppc based on bundled library this may be fixable at some point in the future add build arch closes: https://trac.macports.org/ticket/66541 closes: https://trac.macports.org/ticket/63020 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 07:34:57 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 07:34:57 -0000 Subject: [MacPorts] #66541: xephem @4.0.1: /bin/sh: nroff: command not found In-Reply-To: <047.05e8647914f9cbf862aa8666d362ab7e@macports.org> References: <047.05e8647914f9cbf862aa8666d362ab7e@macports.org> Message-ID: <062.96fa8520e0afb5dcaaefd2307fdd5434@macports.org> #66541: xephem @4.0.1: /bin/sh: nroff: command not found -------------------------+--------------------- Reporter: ryandesign | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: xephem | -------------------------+--------------------- Changes (by kencu): * owner: (none) => kencu * status: new => closed * resolution: => fixed Comment: In [changeset:"4ce46e2e0925ede76d16d4c4e42038a615171ebe/macports-ports" 4ce46e2e0925ede76d16d4c4e42038a615171ebe/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4ce46e2e0925ede76d16d4c4e42038a615171ebe" xephem: fix build on Ventura add dep on groff if needed supported archs are i386 / x86_64 / ppc based on bundled library this may be fixable at some point in the future add build arch closes: https://trac.macports.org/ticket/66541 closes: https://trac.macports.org/ticket/63020 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 07:56:21 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 07:56:21 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.7c07b97926f45027f450f3400d8a6564@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by ronf): Sadly, after spending a couple of hours attempting to reinstall all the ports again from scratch, I'm seeing the same error. Everything else installs just fine, but py310-cython is still complaining about egg_info and the various other config options above. So, there's something outside of whatever MacPorts is writing to that's causing this, but I have no idea why it isn't affecting any of the other ports. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 08:15:34 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 08:15:34 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.a8cfd34016742b87ed40351471b722b8@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' ------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura arm64 Port: py-cython | ------------------------+--------------------------- Comment (by ronf): Ok - I think I found it. Somehow, in addition to setuptools-65.6.3.dist- info being present in /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10 /site-packages, there was also a directory named setuptools-62.1.0.dist- info present alongside it. Even though the "setuptools" in that same parent directory appeared to be the new version, somehow the presence of this older version was confusing things. Once that was removed, the cython install succeeded. Once again, I have no idea why cython was sensitive to this, though, while nothing else using setuptools in python 3.10 had any problems. Sorry for wasting your time here. I appreciate the help! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 08:35:06 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 08:35:06 -0000 Subject: [MacPorts] #66556: poppler-qt4-mac: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') In-Reply-To: <042.8ec96dada093e691bf99987de76ccadd@macports.org> References: <042.8ec96dada093e691bf99987de76ccadd@macports.org> Message-ID: <057.f50f03a1c94f7c4d637b1e629310f20c@macports.org> #66556: poppler-qt4-mac: error: cannot initialize a parameter of type 'unsigned long *' with an rvalue of type 'typename std::remove_reference::type *' (aka 'volatile unsigned long *') ------------------------------+-------------------- Reporter: neilt | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: poppler-qt4-mac | ------------------------------+-------------------- Comment (by cooljeanius): noticed this after rev-upgrade tried to rebuild it due to the tiff update; it's blocking the rest of the rebuilds that rev-upgrade is trying to do for me: {{{ You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: emacs-app @28.2+imagemagick+rsvg+xwidgets djview @4.12 squirrel-ime @0.15.2 py27-Pillow @6.2.1 py35-Pillow @6.2.1 py39-wxpython-4.0 @4.1.1 wxPython-3.0 @3.0.2+debug+stdlib emacs @28.2+dbus+imagemagick+motif+x11 enblend @4.2 oath-toolkit @2.6.6 gegl-0.3 @0.3.34+html_doc+quartz+workshop poppler-qt4-mac @0.61.1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 10:47:39 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 10:47:39 -0000 Subject: [MacPorts] #66582: Gnucash 4.11_2 fails to build on Monterey (intel) Message-ID: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> #66582: Gnucash 4.11_2 fails to build on Monterey (intel) ----------------------+-------------------- Reporter: fondacio | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: ----------------------+-------------------- Multiple attempts to build Gnucash 4.11_2 have failed, both when building using "port install gnucash" or "port install gnucash +quartz". Tail end of build log (used "port install gnucash +quartz"): {{{ :info:build [ 55%] Built target scm-deprecated-gnucash-superseded-module :info:build wrote `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build/lib/guile/2.2 /site-ccache/gnucash/app-utils/fin.go' :info:build wrote `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build/lib/guile/2.2 /site-ccache/gnucash/app-utils/c-interface.go' :info:build wrote `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build/lib/guile/2.2 /site-ccache/gnucash/app-utils/date-utilities.go' :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build' :info:build [ 55%] Built target scm-app-utils-1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/work/build" && /usr/bin/make -j8 -w all VERBOSE=ON :info:build Exit code: 2 :error:build Failed to build gnucash: command execution failed :debug:build Error code: CHILDSTATUS 35647 2 :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring" :debug:build invoked from within :debug:build "command_exec -callback portprogress::target_progress_callback build" :debug:build (procedure "portbuild::build_main" line 8) :debug:build invoked from within :debug:build "$procedure $targetname" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/main.log for details. }}} I am attaching the full log as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 10:48:54 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 10:48:54 -0000 Subject: [MacPorts] #66582: Gnucash 4.11_2 fails to build on Monterey (intel) In-Reply-To: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> References: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> Message-ID: <060.fd7933ac2d2914fa56e4c0b48260f795@macports.org> #66582: Gnucash 4.11_2 fails to build on Monterey (intel) -----------------------+-------------------- Reporter: fondacio | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: | -----------------------+-------------------- Changes (by fondacio): * Attachment "main.log" added. /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_gnome_gnucash/gnucash/main.log -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 11:19:17 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 11:19:17 -0000 Subject: [MacPorts] #66583: py37-sympy @1.11.1: SymPy requires Python 3.8 or newer. Python 3.7 detected Message-ID: <048.dd8ac5901432679f4942ccb362bc28af@macports.org> #66583: py37-sympy @1.11.1: SymPy requires Python 3.8 or newer. Python 3.7 detected -------------------------+------------------------ Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py37-sympy -------------------------+------------------------ {{{ DEBUG: system: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- sympy/py37-sympy/work/sympy-1.11.1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 setup.py --no-user-cfg build -j16 SymPy requires Python 3.8 or newer. Python 3.7 detected Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_macports_release_tarballs_ports_python_py- sympy/py37-sympy/work/sympy-1.11.1" && /opt/local/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7 setup.py --no-user-cfg build -j16 Exit code: 255 Error: Failed to build py37-sympy: command execution failed DEBUG: Error code: CHILDSTATUS 23234 255 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 11:21:58 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 11:21:58 -0000 Subject: [MacPorts] #66583: py37-sympy @1.11.1: SymPy requires Python 3.8 or newer. Python 3.7 detected In-Reply-To: <048.dd8ac5901432679f4942ccb362bc28af@macports.org> References: <048.dd8ac5901432679f4942ccb362bc28af@macports.org> Message-ID: <063.927f5fd91a42f3da8c7ae2197f6895a6@macports.org> #66583: py37-sympy @1.11.1: SymPy requires Python 3.8 or newer. Python 3.7 detected --------------------------+-------------------- Reporter: cooljeanius | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py37-sympy | --------------------------+-------------------- Changes (by cooljeanius): * Attachment "py37-sympy_main.log" added. main.log for py37-sympy -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 12:05:35 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 12:05:35 -0000 Subject: [MacPorts] #66408: Minetest: links to gmp opportunistically In-Reply-To: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> References: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> Message-ID: <067.5f43c38641c1ed222a7042691853947c@macports.org> #66408: Minetest: links to gmp opportunistically ------------------------------+-------------------------- Reporter: programmingkidx | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: minetest gmp Port: minetest | ------------------------------+-------------------------- Comment (by Zweihorn): Closed by: https://github.com/macports/macports-ports/pull/17077 Thank for addressing this issue to us. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 12:26:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 12:26:42 -0000 Subject: [MacPorts] #66562: minetest: new maintainer & new Portfile (was: minetest-devel: new port provides cutting edge Minetest) In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.a93f8ca5bca1b2b520ee551f98747324@macports.org> #66562: minetest: new maintainer & new Portfile --------------------------+---------------------- Reporter: Zweihorn | Owner: Zweihorn Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: x86_64 Port: minetest | --------------------------+---------------------- Old description: > MT 5.6.1 ''minetest-devel'' provides **better compatibility with other > ports** and **greatly improves the internal performance** of the Minetest > App by providing particular options to the build of the port. > > The long standing ''minetest'' port derived new versions by just > **bumping** the sources and the checksums apparently. Certain defaults > and specialities in the build seem to have been overlooked from the start > of this almost historic port or have changed only upstream **without > maintenance** over time. If not for the well maintained ''irrlichtmt'' > port the **unmaintained ''minetest'' port** could be called rather > outdated in some aspects. Anyway the resulting App is **not optimal**. > > My cc to the maintainer of the irrlichtmt port is just for information. > Naturally, combined with my most friendly thank you for his commitment. > > (A) > There is a new port minetest-devel in the making and a new PR already in > the queue to come around. > The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 > and MT 5.6.1. The current MT runs on Big Sur as a local port as was done > with all the predecessors before on othe macOS versions respectively. > > (B) > My PR may solve the below issue too, although I have to check the details > again first. Or do you? > - #66408 > > (C) > You may note I would volunteer to become the maintainer of both the new > minetest-devel as the legacy minetest port together, if this would find > your approval. > > (D) > Please kindly note that I already advertised for MacPorts at the > Minetest community in the past with at least some success. > > Please have a look at: > > - https://forum.minetest.net/viewtopic.php?f=42&t=22427 > > - https://www.minetest.net/downloads/ --> macOS - MacPorts > > My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in > parallel to my now re-opened old account at the MT Forum for technical > reasons only. > > (E) > Only after well establishing minetest-devel and learning if the > expectations raised by my work are met on most if not all platforms, I > would consider improving minetest e.g., by making the build more > consistant and introducing a '--legacy' variant to help some users of the > legacy port. > > (F) > In the future both ports minetest and minetest-devel should continue, as > a new MT 5.6.2 may be understood stable but a new MT 5.7.0 would be work > in progress. AFAIK on top of that it is tradition with Minetest players > to stick with an older version as long as possible. > > (G) > Please accept my sincere apologies in advance if I do not cover all > aspects of your ticket process as I only came back recently after some > longe break. Obviously, I have to make myself more familiar with MacPort > internals again. > > Some if not all of the above will be copied in to a.m. PR in due time. > > Stay tuned. New description: MT 5.6.1 ''minetest'' **Revision 1** provides **better compatibility with other ports** and **greatly improves the overall performance** of the Minetest App by providing particular options to the build of the port. Ref PR - https://github.com/macports/macports-ports/pull/17077 The long standing ''minetest'' port derived new versions by just **bumping** the sources and the checksums apparently. Certain defaults and specialities in the build seem to have been overlooked from the start of this almost historic port or have changed only upstream **without maintenance** over time. If not for the well maintained ''irrlichtmt'' port the **unmaintained ''minetest'' port** could be called rather outdated in some aspects. Anyway the resulting App is **not optimal**. My cc to the maintainer of the irrlichtmt port is just for information. Naturally, combined with my most friendly thanks for his commitment. (A) The new Portfile was tested and improved since MT 0.4+, MT 5+, MT 5.5.0 and MT 5.6.1. The current MT runs on Big Sur as a local port as was done with all the predecessors before on othe macOS versions respectively. (B) The a.m. PR solves issue: - #66408 (C) I volunteer as new maintainer to this port. (D) Please kindly note that I already advertised for MacPorts at the Minetest community in the past with at least some success. Please have a look at: - https://forum.minetest.net/viewtopic.php?f=42&t=22427 - https://www.minetest.net/downloads/ --> macOS - **MacPorts** My alter ego there is 'snoopy' and I got a new 'Zweihorn' account in parallel to my now re-opened old account at the MT Forum for technical reasons only. (E) - outdated - (F) - outdated - (G) Please accept my sincere apologies in advance if I do not cover all aspects of your ticket process as I only came back recently after some longe break. Obviously, I have to make myself more familiar with MacPort internals again. Ref PR(s) see below. Stay tuned. -- Comment (by Zweihorn): Update the Description to meet the current PR and resolve -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:25:22 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 13:25:22 -0000 Subject: [MacPorts] #66516: cantor @4.14.3_5 +debug+docs: error: unknown type name 'string'; did you mean 'std::string'? In-Reply-To: <048.9979c211aaf62ee806c7efa1e9b92358@macports.org> References: <048.9979c211aaf62ee806c7efa1e9b92358@macports.org> Message-ID: <063.a7151aeca440c391e24345a3e06df983@macports.org> #66516: cantor @4.14.3_5 +debug+docs: error: unknown type name 'string'; did you mean 'std::string'? --------------------------+---------------------------------------------- Reporter: cooljeanius | Owner: NicosPavlov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: cantor | --------------------------+---------------------------------------------- Changes (by NicosPavlov ): * status: new => closed * owner: (none) => NicosPavlov * resolution: => fixed Comment: In [changeset:"c0761cad0ce2f1271856d07bf59893b67497dccc/macports-ports" c0761cad0ce2f1271856d07bf59893b67497dccc/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="c0761cad0ce2f1271856d07bf59893b67497dccc" cantor: fix string definition (fixes https://trac.macports.org/ticket/66516) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:54:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 13:54:42 -0000 Subject: [MacPorts] #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib Message-ID: <043.106280199b19cab59e9d1ffd188d4249@macports.org> #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib --------------------+------------------------------- Reporter: harens | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: lua50, lua52, lua --------------------+------------------------------- As part of the `src-makefile` patch, the lua binary is linked to liblua.dylib. {{{#!diff +$(LUA_DYLIB): $(BASE_O) + @echo "Building dynamic library (dylib)" + $(CC) -o $@ $(MYLDFLAGS) -dynamiclib -install_name @PREFIX@/lib/lua- at BRANCH@/liblua- at BRANCH@.dylib \ + -compatibility_version @BRANCH@ -current_version @VERSION@ $^ + $(LUA_T): $(LUA_O) $(LUA_A) - $(CC) -o $@ $(LDFLAGS) $(LUA_O) $(LUA_A) $(LIBS) + $(CC) -o $@ -L. $(MYLDFLAGS) $(MYCFLAGS) $(LIBS) -llua- at BRANCH@ lua.c $(LUAC_T): $(LUAC_O) $(LUA_A) - $(CC) -o $@ $(LDFLAGS) $(LUAC_O) $(LUA_A) $(LIBS) + $(CC) -o $@ $(MYLDFLAGS) $(LUAC_O) $(LUA_DYLIB) $(LIBS) }}} The tests, which run the lua binary, then fail since it expects liblua.dylib to be in `${prefix}/lib`. It is instead in `${worksrcpath}/src`. {{{#!shell ---> Testing lua Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_github .com_macports_macports-ports_lang_lua/lua/work/lua-5.3.5" && /usr/bin/make test src/lua -v dyld[12412]: Library not loaded: /opt/local/lib/liblua.dylib Referenced from: /opt/local/var/macports/build/_opt_local_var_macports_sources_github .com_macports_macports-ports_lang_lua/lua/work/lua-5.3.5/src/lua Reason: tried: '/opt/local/lib/liblua.dylib' (no such file), '/usr/local/lib/liblua.dylib' (no such file), '/usr/lib/liblua.dylib' (no such file) make: *** [test] Abort trap: 6 }}} I tried setting `test.env DYLD_LIBRARY_PATH=${worksrcpath}/src`, which didn't seem to work. lua51 builds the dynamic library, but either rightly or wrongly doesn't link to it, and so its tests pass. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:55:01 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 13:55:01 -0000 Subject: [MacPorts] #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib In-Reply-To: <043.106280199b19cab59e9d1ffd188d4249@macports.org> References: <043.106280199b19cab59e9d1ffd188d4249@macports.org> Message-ID: <058.3f0fe8eaa1d7c324507815fc3e5e3969@macports.org> #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib --------------------------------+-------------------- Reporter: harens | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lua50, lua52, lua | --------------------------------+-------------------- Changes (by harens): * Attachment "lua5.3.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:55:10 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 13:55:10 -0000 Subject: [MacPorts] #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib In-Reply-To: <043.106280199b19cab59e9d1ffd188d4249@macports.org> References: <043.106280199b19cab59e9d1ffd188d4249@macports.org> Message-ID: <058.3db32b4deca7c719b7070de57c751e32@macports.org> #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib --------------------------------+-------------------- Reporter: harens | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lua50, lua52, lua | --------------------------------+-------------------- Changes (by harens): * Attachment "lua5.2.log" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 13:56:11 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 13:56:11 -0000 Subject: [MacPorts] #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib In-Reply-To: <043.106280199b19cab59e9d1ffd188d4249@macports.org> References: <043.106280199b19cab59e9d1ffd188d4249@macports.org> Message-ID: <058.7a3e2451e253f8f1776df2644dd8942b@macports.org> #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib --------------------------------+-------------------- Reporter: harens | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lua50, lua52, lua | --------------------------------+-------------------- Changes (by harens): * Attachment "lua5.0.log" added. Different errors but the missing library is still the problem -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 14:46:14 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 14:46:14 -0000 Subject: [MacPorts] #66582: Gnucash 4.11_2 fails to build on Monterey (intel) In-Reply-To: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> References: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> Message-ID: <060.ca056c93ef12c7de419a7c87f974b6a7@macports.org> #66582: Gnucash 4.11_2 fails to build on Monterey (intel) -----------------------+---------------------- Reporter: fondacio | Owner: drkp Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gnucash | -----------------------+---------------------- Changes (by jmroot): * owner: (none) => drkp * cc: drkp, openmaintainer (removed) * status: new => assigned * port: => gnucash -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 14:46:25 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 14:46:25 -0000 Subject: [MacPorts] #66582: Gnucash 4.11_2 fails to build on Monterey (intel) In-Reply-To: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> References: <045.0e885ad38359c57723cf85e9dfd55c81@macports.org> Message-ID: <060.099019d0a47c565e21b419ac36d889e3@macports.org> #66582: Gnucash 4.11_2 fails to build on Monterey (intel) ------------------------+-------------------- Reporter: fondacio | Owner: drkp Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: duplicate | Keywords: Port: gnucash | ------------------------+-------------------- Changes (by jmroot): * status: assigned => closed * resolution: => duplicate Comment: #66119 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:14:32 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 15:14:32 -0000 Subject: [MacPorts] #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib In-Reply-To: <043.106280199b19cab59e9d1ffd188d4249@macports.org> References: <043.106280199b19cab59e9d1ffd188d4249@macports.org> Message-ID: <058.65209445dfbc4e87592433f63091aa8a@macports.org> #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib --------------------------------+-------------------- Reporter: harens | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lua50, lua52, lua | --------------------------------+-------------------- Comment (by kencu): the lua port does try to set things up for testing: https://github.com/macports/macports- ports/blob/e4c2977140da3d850df8125acb5a9e1c3c969150/lang/lua/Portfile#L59 but newer macosx versions with SIP no longer follow/obey DYLD_LIBRARY_PATH, as it is a security hole, eg https://developer.apple.com/forums/thread/703757 practically, you either have to use rpaths, which meson and cmake do automatically, or install the library to it?s final location then run the tests. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:25:06 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 15:25:06 -0000 Subject: [MacPorts] #66487: gtk3 menues broken with macos ventura - update needed In-Reply-To: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> References: <046.fcc63798ed597fd433a4ef94e24250ab@macports.org> Message-ID: <061.67d934d13ecf0d8c53889f71cd3586b4@macports.org> #66487: gtk3 menues broken with macos ventura - update needed ------------------------+---------------------- Reporter: MStraeten | Owner: mascguy Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: gtk3 | ------------------------+---------------------- Comment (by ctreleaven): I believe this will affect gramps but don't have a Ventura system to check with. Upstream's bundled version was updated to address these issues: https://gramps-project.org/bugs/view.php?id=12754 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:30:01 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 15:30:01 -0000 Subject: [MacPorts] #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib In-Reply-To: <043.106280199b19cab59e9d1ffd188d4249@macports.org> References: <043.106280199b19cab59e9d1ffd188d4249@macports.org> Message-ID: <058.ae12015bf9415d1d79658d0d6a435db3@macports.org> #66584: lua50, lua52, lua @ 5.3.5_0: tests fail due to missing liblua.dylib --------------------------------+-------------------- Reporter: harens | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lua50, lua52, lua | --------------------------------+-------------------- Comment (by kencu): or build with certain library paths and then rewrite the library paths everywhere during the install phase to their final locations, which is part of what meson and cmake can do automatically as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:32:51 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 15:32:51 -0000 Subject: [MacPorts] #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild In-Reply-To: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> References: <043.34fa0c6f4f5adac3291d0f3f459e553f@macports.org> Message-ID: <058.f7d5d1c0cb80b4b3d6d487bd97b895d7@macports.org> #66537: Add a field to port information that specifies whether that port is distributed as a binary or requires a lengthy rebuild --------------------------+-------------------- Reporter: esbugz | Owner: (none) Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.8.0 Resolution: | Keywords: Port: | --------------------------+-------------------- Comment (by esbugz): Replying to [comment:6 ryandesign]: > Any locally-stored information would be out-of-date. > A binary could have been produced on the build servers between the time that your local database was updated and the time that you asked whether a binary archive of a port was available. Nothing `selfupdate` couldn't fix > And if one were to be created for this purpose, there is no server-side source of information from which that database could be populated. ??? The list of prebuilt binaries located on the server is the source of information > Most users receive a PortIndex that was created on our servers. Exactly, and your servers have information about what prebuilt binaries they host, so they can add that information to the index synced with the users' machines > Yes, presumably a similar process could be used to perform http(s) requests for each port for each OS version and architecture, periodically, to see if a binary archive exists on the server Why would you need to a gazillion of individual http requests instead of: - (full rebuild) simply making the server produce a recursive list of all the prebuilt binaries it hosts, and then refreshing the database - on every upload/removal of a prebuilt binary to the server you could get this log info and similarly update the database -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 15:57:46 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 15:57:46 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.95156b4dbb86db71d6b00ff94c072637@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' -------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura arm64 Port: py-cython | -------------------------+--------------------------- Changes (by kencu): * status: assigned => closed * resolution: => worksforme Comment: glad you got it sorted out -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:00:41 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:00:41 -0000 Subject: [MacPorts] #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' In-Reply-To: <047.b2a6f78403bc429024835ff15b37694e@macports.org> References: <047.b2a6f78403bc429024835ff15b37694e@macports.org> Message-ID: <062.13e8c68223dd673c6f2774ca36dc2064@macports.org> #66440: py27-m2r @0.2.1: AttributeError: 'module' object has no attribute 'BlockGrammar' ---------------------------------+--------------------------------- Reporter: ryandesign | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-m2r, py-mistune | ---------------------------------+--------------------------------- Changes (by kencu): * keywords: ventura => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:02:00 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:02:00 -0000 Subject: [MacPorts] #66108: qrupdate @1.1.2: parallel build failure In-Reply-To: <044.b1c671227eaa7903899b7200f3cb86e8@macports.org> References: <044.b1c671227eaa7903899b7200f3cb86e8@macports.org> Message-ID: <059.3563300c369cc3efb435ae2d00b1ce28@macports.org> #66108: qrupdate @1.1.2: parallel build failure -----------------------+-------------------- Reporter: murrayE | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: qrupdate | -----------------------+-------------------- Changes (by kencu): * keywords: ventura => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:02:42 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:02:42 -0000 Subject: [MacPorts] #66242: python311 @3.11.0 +lto +optimizations failed to build: No such file or directory: '/opt/local/include/proj_api.h' In-Reply-To: <046.4daf2328ef43290b34926dc800960514@macports.org> References: <046.4daf2328ef43290b34926dc800960514@macports.org> Message-ID: <061.3d574f814f550c7c13d8ba1fdb80fb94@macports.org> #66242: python311 @3.11.0 +lto +optimizations failed to build: No such file or directory: '/opt/local/include/proj_api.h' ------------------------+---------------------- Reporter: bakergilx | Owner: jmroot Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: python311 | ------------------------+---------------------- Changes (by kencu): * keywords: ventura => -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:19:00 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:19:00 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.a88c6d969141644b9da5f16ad882c4bb@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' -------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura arm64 Port: py-cython | -------------------------+--------------------------- Comment (by jmroot): Sounds like you may have used pip or similar to install modules into the MacPorts prefix at some point. That's not recommended because it can cause just these kind of conflicts. Best to use pip's `--user` option or install into a venv. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:25:23 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:25:23 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.eebfc131abc389c843db33111fdadaa6@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): So shall I wait and not delete Xcode 8.2? That would be the best solution indeed, as 8.2 is the typically given last Xcode under 10.11 (I guess). But, what for are the MacPorts? given SDKs then? I guess I can remove that afterwards, can I? It does not aid in problematic situations like this. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:36:40 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:36:40 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.475195223a10f5818530b1e3b5bc3b40@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by kencu): I?ll fix this in time, but the SDK symlimks should have worked for you? I also use Xcode 8.2 on 10.11, but I physically copied the 10.11 SDK into the two required locations, and that works 100% of the time for me, including with this port. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:40:59 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:40:59 -0000 Subject: [MacPorts] #66579: py310-cython @0.29.32: error: invalid command 'egg_info' In-Reply-To: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> References: <041.ef879ec6a71503a9858e231181e7a1f3@macports.org> Message-ID: <056.60aa7dd0d82c4299dd2ce37bad0f10df@macports.org> #66579: py310-cython @0.29.32: error: invalid command 'egg_info' -------------------------+--------------------------- Reporter: ronf | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: ventura arm64 Port: py-cython | -------------------------+--------------------------- Comment (by ronf): Yeah, thanks - I need to start using venv more. What I still don't understand is why cython is the only port that gave me a problem here, though. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 16:45:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 16:45:27 -0000 Subject: [MacPorts] #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path In-Reply-To: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> References: <045.03978175ac3e93a402c9a56d447ee1b2@macports.org> Message-ID: <060.31b30dbf1a64c20598d92433c6c208e9@macports.org> #66549: qt511-qtimageformats @5.11.3_2: Could not resolve SDK Path for 'macosx10.11' using --show-sdk-path -----------------------------------+--------------------------------- Reporter: thetrial | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: elcapitan legacy-os Port: qt511-qtimageformats | -----------------------------------+--------------------------------- Comment (by thetrial): Hm ? the symlinks did not work ? though, did I symlink? Maybe I just linked via Finder. I now copied the sdk physically as you said ? and the rev-upgrade ran through. Oh. Nice. Now I don?t know if that also would have worked with symlinks, I?ll tray on another machine next year. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 17:18:17 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 17:18:17 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366530=3A_py310-spyder_=405=2E4?= =?utf-8?q?=2E0=5F1_+pil_=E2=80=93_Spyder_won=27t_start_on_M1_pro?= =?utf-8?q?_machine_=28Potentially_an_issue_with_the_version_of_p?= =?utf-8?q?ort_py310-codestyle_=402=2E9=2E1=5F0_being_=22too_old?= =?utf-8?q?=22_rather_than_spyder=29?= In-Reply-To: <044.55db2b732ff6862bccb8754439625e94@macports.org> References: <044.55db2b732ff6862bccb8754439625e94@macports.org> Message-ID: <059.9f67bc2f8c7d3dc49d8e33fc1e5a41a0@macports.org> #66530: py310-spyder @5.4.0_1 +pil ? Spyder won't start on M1 pro machine (Potentially an issue with the version of port py310-codestyle @2.9.1_0 being "too old" rather than spyder) ------------------------+------------------------ Reporter: Gandoon | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-spyder | ------------------------+------------------------ Comment (by Gandoon): Just to confirm: This issue has now been resolved on Apple M1 pro. Recently `py310-codestyle @2.10.0_0` was made available, and as the traceback cited hinted, this seems to have solved the problem. Why it seemed to work on Intel silicon but not chips from "The Fruit Company" I do not know, but either way, it works now. This ticket can probably be closed now. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:02:40 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 18:02:40 -0000 Subject: [MacPorts] #66585: smlnj @110.99.2: Script .arch-n-opsys fails on this machine. Message-ID: <047.16499e9612948ae9a64a206733d1045d@macports.org> #66585: smlnj @110.99.2: Script .arch-n-opsys fails on this machine. ------------------------+-------------------------- Reporter: ryandesign | Owner: tobypeterson Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: smlnj ------------------------+-------------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/8553/steps/install-port/logs/stdio {{{ /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_smlnj/smlnj/work/smlnj-110.99.2/config/install.sh: installing /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_smlnj/smlnj/work/smlnj-110.99.2/bin/.arch-n-opsys /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_smlnj/smlnj/work/smlnj-110.99.2/config/install.sh: !!! Script /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_smlnj/smlnj/work/smlnj-110.99.2/bin/.arch-n-opsys fails on this machine. /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_smlnj/smlnj/work/smlnj-110.99.2/config/install.sh: !!! You must patch /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_smlnj/smlnj/work/smlnj-110.99.2/bin/.arch-n-opsys by hand and repeat the installation. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:53:10 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 18:53:10 -0000 Subject: [MacPorts] #66575: ncplot @4.11.0: ld: library not found for -lfl In-Reply-To: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> References: <047.a4d96c566d75485a796c13e0fb94ef12@macports.org> Message-ID: <062.05c30935801e323f4b8de319f58a701c@macports.org> #66575: ncplot @4.11.0: ld: library not found for -lfl -------------------------+-------------------- Reporter: ryandesign | Owner: mf2k Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: ncplot | -------------------------+-------------------- Comment (by ryandesign): Replying to [comment:2 Frank Schima ]: > ncplot: Add flex as dependency Adding a library dependency requires increasing the revision. > - Add worksrcdir fix for latest base It's not intended for you to need to do this in each port, so let's figure out what's going wrong and fix it correctly. Does reverting [6306106231c1c0eb278d9431ee9bbeb1d9f620a1/macports-ports] fix it? (Not that I want to revert it, but let's see if that's in the general area of the problem.) -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 18:55:44 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 18:55:44 -0000 Subject: [MacPorts] #62260: github and bitbucket portgroups: Remove post-extract block In-Reply-To: <047.38b5718b5ec3d5bde717c861ba6bea1a@macports.org> References: <047.38b5718b5ec3d5bde717c861ba6bea1a@macports.org> Message-ID: <062.ae7e0dee07ec9d206085b1b3f8e8ff3e@macports.org> #62260: github and bitbucket portgroups: Remove post-extract block -------------------------------+----------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: portgroup Port: github bitbucket | -------------------------------+----------------------- Comment (by ryandesign): Replying to [ticket:62260 ryandesign]: > The entire post-extract block should be superfluous as of MacPorts 2.6.0 which creates a symlink of the expected name for you. This change in base was reverted after MacPorts 2.8. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 21:46:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 21:46:13 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366530=3A_py310-spyder_=405=2E4?= =?utf-8?q?=2E0=5F1_+pil_=E2=80=93_Spyder_won=27t_start_on_M1_pro?= =?utf-8?q?_machine_=28Potentially_an_issue_with_the_version_of_p?= =?utf-8?q?ort_py310-codestyle_=402=2E9=2E1=5F0_being_=22too_old?= =?utf-8?q?=22_rather_than_spyder=29?= In-Reply-To: <044.55db2b732ff6862bccb8754439625e94@macports.org> References: <044.55db2b732ff6862bccb8754439625e94@macports.org> Message-ID: <059.29e2ed35ca5a6df2cc65b6f3eb17aacf@macports.org> #66530: py310-spyder @5.4.0_1 +pil ? Spyder won't start on M1 pro machine (Potentially an issue with the version of port py310-codestyle @2.9.1_0 being "too old" rather than spyder) -------------------------+------------------------ Reporter: Gandoon | Owner: reneeotten Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: worksforme | Keywords: Port: py-spyder | -------------------------+------------------------ Changes (by kencu): * status: assigned => closed * resolution: => worksforme Comment: thanks for the report -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 22:06:26 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 22:06:26 -0000 Subject: [MacPorts] #66574: lenstool @7.1.1 fails to build with recent Xcode In-Reply-To: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> References: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> Message-ID: <058.b467a927f4c79954df936efc849e041f@macports.org> #66574: lenstool @7.1.1 fails to build with recent Xcode -----------------------+---------------------- Reporter: jmroot | Owner: ejullo Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lenstool | -----------------------+---------------------- Comment (by ejullo): This should be fixed in the new version 8.0.4 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 22:44:10 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 22:44:10 -0000 Subject: [MacPorts] #66586: Macports will not reinstall ports on Ventura using migration instructions Message-ID: <046.638d00d1067980537931285ce3cef5eb@macports.org> #66586: Macports will not reinstall ports on Ventura using migration instructions -----------------------+-------------------- Reporter: hopper333 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -----------------------+-------------------- I have followed the migration instructions exactly I believe, including downloading the ventura base, cleaning old ports out etc. and adding arm64 as build_arch in macports.conf, but this happens when I am running the command line instructions: {{{ mwh at NewAir:~$ xattr -d com.apple.quarantine restore_ports.tcl xattr: restore_ports.tcl: No such xattr: com.apple.quarantine mwh at NewAir:~$ sudo ./restore_ports.tcl myports.txt Warning: Skipping clang-4.0 (not in the ports tree) Error: ld64: Variant ld64_274 conflicts with ld64_xcode Error evaluating variants while executing "error "Error evaluating variants"" (procedure "mportopen" line 63) invoked from within "mportopen $portInfo(porturl) [list subport $portInfo(name)] $variantInfo" Unable to open port 'ld64': Error evaluating variants while executing "dependenciesForPort $name $variants" (procedure "sort_ports" line 57) invoked from within "sort_ports $portList" invoked from within "set operationList [sort_ports $portList]" (file "./restore_ports.tcl" line 297) }}} I have no idea what this means. Please advise! Michael -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 22:49:14 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 22:49:14 -0000 Subject: [MacPorts] #66586: Macports will not reinstall ports on Ventura using migration instructions In-Reply-To: <046.638d00d1067980537931285ce3cef5eb@macports.org> References: <046.638d00d1067980537931285ce3cef5eb@macports.org> Message-ID: <061.0294d877f764e4ea3bd88e259bdc7649@macports.org> #66586: Macports will not reinstall ports on Ventura using migration instructions ------------------------+-------------------- Reporter: hopper333 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | ------------------------+-------------------- Comment (by kencu): Some of your installed ports are so old that they don't exist any more, and others don't build on a current system or are no longer appropriate for a current system. If there were salaried engineers working on MacPorts, perhaps the restore script would look for this and fix it up for you, but it's a volunteer project and nobody has fixed up the restore scripts to that degree, so far at least. If you want to start completely fresh, just look through your list and install the ones you actually want, like octave or whatever, and let them pull in current supporting ports. If you want some help, you can post up your list here and someone will help you trim off the stuff that is too old to restore, if you prefer that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:02:47 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:02:47 -0000 Subject: [MacPorts] #66266: scotch @6.0.9 build failure on Ventura In-Reply-To: <052.bf6d39d3369766698e5ea9b9bae15004@macports.org> References: <052.bf6d39d3369766698e5ea9b9bae15004@macports.org> Message-ID: <067.e0d7c30e8c44531e50c0f80f2b0b4736@macports.org> #66266: scotch @6.0.9 build failure on Ventura ------------------------------+--------------------------------- Reporter: Yashwanth131091 | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: scotch | ------------------------------+--------------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: scotch has been updated, it appears, and the current version builds on Ventura without error: {{{ % port -v installed scotch The following ports are currently installed: scotch @7.0.1_0+mpich (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-29T15:00:44-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:11:27 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:11:27 -0000 Subject: [MacPorts] #66311: splint @3.1.2: fatal error: 'signature.tab.h' file not found In-Reply-To: <051.24ccdb5bc90d774e0435998cd1516903@macports.org> References: <051.24ccdb5bc90d774e0435998cd1516903@macports.org> Message-ID: <066.ef46f386bdb01df16e5b5f11bdd7b206@macports.org> #66311: splint @3.1.2: fatal error: 'signature.tab.h' file not found -----------------------------+------------------------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: bigsur monterey ventura Port: splint | -----------------------------+------------------------------------- Comment (by kencu): I can't reproduce this. {{{splint}}} installs easily on Ventura arm64 without issue: {{{ sudo port -f deactivate active sudo port -v -N install splint ... % port -v installed splint The following ports are currently installed: splint @3.1.2_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-29T15:09:05-0800' % port -v installed | grep active flex @2.6.4_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T21:20:11-0800' gettext @0.21_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:25:28-0800' gettext-runtime @0.21_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:19:55-0800' gettext-tools-libs @0.21_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:23:20-0800' libiconv @1.17_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:19:19-0800' libtextstyle @0.21_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:21:08-0800' m4 @1.4.19_1 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:26:57-0800' ncurses @6.3_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:20:28-0800' splint @3.1.2_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-29T15:09:05-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:16:26 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:16:26 -0000 Subject: [MacPorts] #66311: splint @3.1.2: fatal error: 'signature.tab.h' file not found In-Reply-To: <051.24ccdb5bc90d774e0435998cd1516903@macports.org> References: <051.24ccdb5bc90d774e0435998cd1516903@macports.org> Message-ID: <066.61de4ffa458e778f827809b605a8fd24@macports.org> #66311: splint @3.1.2: fatal error: 'signature.tab.h' file not found -----------------------------+------------------------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: bigsur monterey ventura Port: splint | -----------------------------+------------------------------------- Changes (by kencu): * Attachment "splint.log" added. log of successful build, Ventura arm64 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:22:18 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:22:18 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366286=3A_gettext-tools-libs=3A?= =?utf-8?q?_builld_failure_=E2=80=9CSource_option_6_is_no_longer_?= =?utf-8?q?supported=2E_Use_7_or_later=2E=E2=80=9D?= In-Reply-To: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> References: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> Message-ID: <062.98551823f5934b5f3ae9d7327e1a1510@macports.org> #66286: gettext-tools-libs: builld failure ?Source option 6 is no longer supported. Use 7 or later.? -------------------------+------------------------ Reporter: vrepetenko | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: gettext | -------------------------+------------------------ Comment (by kencu): I can't reproduce this either: {{{ % port -v installed | grep gettext-tools-libs gettext-tools-libs @0.21_0 requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-25T19:23:20-0800' gettext-tools-libs @0.21_0+universal requested_variants='+universal' platform='darwin 22' archs='arm64 x86_64' date='2022-12-28T23:17:46-0800' }}} does it only happen if java is installed, or some similar special situation? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:36:09 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:36:09 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366286=3A_gettext-tools-libs=3A?= =?utf-8?q?_builld_failure_=E2=80=9CSource_option_6_is_no_longer_?= =?utf-8?q?supported=2E_Use_7_or_later=2E=E2=80=9D?= In-Reply-To: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> References: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> Message-ID: <062.a6325d492e82e3b6dd509d35d81b8cbd@macports.org> #66286: gettext-tools-libs: builld failure ?Source option 6 is no longer supported. Use 7 or later.? -------------------------+------------------------ Reporter: vrepetenko | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: gettext | -------------------------+------------------------ Comment (by kencu): doesn't seem to matter if java is installed. I installed the current java19 from Oracle, and then reinstalled {{{gettext-tools-libs}}} without issue. {{{ % sudo port -v installed gettext-tools-libs The following ports are currently installed: gettext-tools-libs @0.21_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-29T15:34:36-0800' }}} so will close this as fixed, unless someone reopens with new information . -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:36:29 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:36:29 -0000 Subject: =?utf-8?q?Re=3A_=5BMacPorts=5D_=2366286=3A_gettext-tools-libs=3A?= =?utf-8?q?_builld_failure_=E2=80=9CSource_option_6_is_no_longer_?= =?utf-8?q?supported=2E_Use_7_or_later=2E=E2=80=9D?= In-Reply-To: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> References: <047.d9e761e79230c6f424ec0a5df0e98fa3@macports.org> Message-ID: <062.8df71ba70dea09cfce40aae6a5bf207d@macports.org> #66286: gettext-tools-libs: builld failure ?Source option 6 is no longer supported. Use 7 or later.? -------------------------+------------------------ Reporter: vrepetenko | Owner: ryandesign Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: gettext | -------------------------+------------------------ Changes (by kencu): * status: accepted => closed * resolution: => fixed -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Thu Dec 29 23:41:13 2022 From: noreply at macports.org (MacPorts) Date: Thu, 29 Dec 2022 23:41:13 -0000 Subject: [MacPorts] #66311: splint @3.1.2: fatal error: 'signature.tab.h' file not found In-Reply-To: <051.24ccdb5bc90d774e0435998cd1516903@macports.org> References: <051.24ccdb5bc90d774e0435998cd1516903@macports.org> Message-ID: <066.b0539f703150b33dd0d4e2617785ac87@macports.org> #66311: splint @3.1.2: fatal error: 'signature.tab.h' file not found -----------------------------+------------------------------------- Reporter: sudheerhebbale | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: bigsur monterey ventura Port: splint | -----------------------------+------------------------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: I installed MacPorts' version of flex, in case it was conflicting, but splint still builds through without any issues. closing as fixed, therefore. Please reopen with new information if this still fails for you. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 01:13:52 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 01:13:52 -0000 Subject: [MacPorts] #66574: lenstool @7.1.1 fails to build with recent Xcode In-Reply-To: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> References: <043.dd0a9b671a94d806f9d906b1f8c60958@macports.org> Message-ID: <058.999bb2f0eb7cf58d326f9fe75a23fd4f@macports.org> #66574: lenstool @7.1.1 fails to build with recent Xcode -----------------------+-------------------- Reporter: jmroot | Owner: ejullo Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: lenstool | -----------------------+-------------------- Changes (by ejullo ): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"1c1c669deadefe8044a60c1b8627988b252fbc66/macports-ports" 1c1c669deadefe8044a60c1b8627988b252fbc66/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="1c1c669deadefe8044a60c1b8627988b252fbc66" lenstool: update to 8.0.4 Closes: https://trac.macports.org/ticket/66574 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 01:21:32 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 01:21:32 -0000 Subject: [MacPorts] #66379: onetbb fails to build as +universal on 10.6.8 (i386+x86_64): error: unused function 'impl_zone_enable_discharge_checking' In-Reply-To: <049.79abdc933203116287962171b077fa27@macports.org> References: <049.79abdc933203116287962171b077fa27@macports.org> Message-ID: <064.f099ced5b1fc05c916a57c1980691e93@macports.org> #66379: onetbb fails to build as +universal on 10.6.8 (i386+x86_64): error: unused function 'impl_zone_enable_discharge_checking' ---------------------------+------------------------- Reporter: barracuda156 | Owner: catap Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: snowleopard Port: onetbb | ---------------------------+------------------------- Changes (by catap): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"ab65a73b4ce3ab3aadbf0a4482d1fd2324af7a56/macports-ports" ab65a73b4ce3ab3aadbf0a4482d1fd2324af7a56/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="ab65a73b4ce3ab3aadbf0a4482d1fd2324af7a56" onetbb: fix +universal build on macOS 10.6 Closes: https://trac.macports.org/ticket/66379 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 02:00:30 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 02:00:30 -0000 Subject: [MacPorts] #66581: claws-mail: No images displayed in standard mail (image viewer settings not working) In-Reply-To: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> References: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> Message-ID: <061.93372807042a57818fe3fa8486a94b0e@macports.org> #66581: claws-mail: No images displayed in standard mail (image viewer settings not working) -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: claws-mail | -------------------------+-------------------- Comment (by Rezzy-dev): Found the cause! The built-in image viewer is working, it's just that Claws Mail assigns the wrong MIME type to image attachments. They're automatically given an undetermined MIME type: application/octetstream. They should be image/jpeg and image/png. When I manually change their MIME type at the time of attachment, the images show as expected in the sent and received mail. How does Claws Mail determine/assign the MIME types for attachments? Where is its MIME database stored? It seems to be having trouble deciding what MIME type files attached from the Mac HD are. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 03:11:27 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 03:11:27 -0000 Subject: [MacPorts] #66581: claws-mail: No images displayed in standard mail (image viewer settings not working) In-Reply-To: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> References: <046.0a657394ac6cf0fea0839d9bf429a62e@macports.org> Message-ID: <061.7fea47e97a9f5bcaca293addf0984e68@macports.org> #66581: claws-mail: No images displayed in standard mail (image viewer settings not working) -------------------------+-------------------- Reporter: Rezzy-dev | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: claws-mail | -------------------------+-------------------- Comment (by Rezzy-dev): Solution found! Claws Mail relies on /etc/mime.types for file MIME type associations when adding attachments to mail. The solution is to create the /opt/local/etc/mime.types configuration/text file and populate it with: {{{ image/jpeg jpg jpeg image/png png image/gif gif image/webp webp }}} After this, the images for attached image files display as excepted in mail (Claws Mail assigns the correct MIME type to the attachments). -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 03:25:53 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 03:25:53 -0000 Subject: [MacPorts] #66586: ld64 selects conflicting variant when using migration instructions (was: Macports will not reinstall ports on Ventura using migration instructions) In-Reply-To: <046.638d00d1067980537931285ce3cef5eb@macports.org> References: <046.638d00d1067980537931285ce3cef5eb@macports.org> Message-ID: <061.6903da69ed04d965ad4ab59760a4532f@macports.org> #66586: ld64 selects conflicting variant when using migration instructions ------------------------+-------------------- Reporter: hopper333 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ld64 | ------------------------+-------------------- Changes (by jmroot): * cc: jeremyhu (added) * port: => ld64 Comment: In this case, the ld64 port is choosing a different default variant on your new system than it did on your old system. There is a bug here in that if the old variant will still work, it shouldn't automatically set a conflicting variant as well, and if the old variant doesn't work on the new system, the port shouldn't be offering that variant at all on that system. You can probably work around the problem by editing your `myports.txt`. Find the line with ld64, which should look something like: {{{ ld64 @3_4+ld64_274 (active) requested_variants='+ld64_274' platform='darwin 20' archs='x86_64' date='2022-02-07T14:54:41+1100' }}} The important part is the `requested_variants`, don't worry if the other values differ from what I've shown. Delete the `+ld64_274` inside the single quotes, i.e. change `requested_variants='+ld64_274'` to `requested_variants=''`. Then save the file, run `sudo port clean ld64`, and you are ready to try again. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 03:48:33 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 03:48:33 -0000 Subject: [MacPorts] #65650: cargo-c: Add universal variant In-Reply-To: <045.6cf51bf7b4f86a060cb1ffd3362ab677@macports.org> References: <045.6cf51bf7b4f86a060cb1ffd3362ab677@macports.org> Message-ID: <060.74370edf22f807a1742de0bf6e2db59c@macports.org> #65650: cargo-c: Add universal variant --------------------------+--------------------------------- Reporter: potterpg | Owner: MarcusCalhoun-Lopez Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: cargo-c | --------------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"a7d24062d6ae449702fa55e81dbfaf8e40dce58e/macports-ports" a7d24062d6ae449702fa55e81dbfaf8e40dce58e/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="a7d24062d6ae449702fa55e81dbfaf8e40dce58e" cargo-c: use rust PG features including universal No revbump since the installed files do not change. Fixes https://trac.macports.org/ticket/65650 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 04:12:33 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 04:12:33 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.2e6ce5835d60909853459d1b140a2f0d@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by ryandesign): The suggestion in that issue was: > You can check the stable version on http://www.libressl.org/ as "The latest stable release is x.x.x" . Is that not suitable? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 04:16:54 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 04:16:54 -0000 Subject: [MacPorts] #66587: py310-xlsx2csv @0.8.0: ERROR Missing dependencies: setuptools_scm[toml]>=3.4.3 Message-ID: <047.e2a604d409d43eff3149b519f3022bc6@macports.org> #66587: py310-xlsx2csv @0.8.0: ERROR Missing dependencies: setuptools_scm[toml]>=3.4.3 ------------------------+---------------------------- Reporter: ryandesign | Owner: kurthindenburg Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py-xlsx2csv ------------------------+---------------------------- https://build.macports.org/builders/ports- 11_arm64-builder/builds/79390/steps/install-port/logs/stdio {{{ running egg_info writing xlsx2csv.egg-info/PKG-INFO writing dependency_links to xlsx2csv.egg-info/dependency_links.txt writing entry points to xlsx2csv.egg-info/entry_points.txt writing top-level names to xlsx2csv.egg-info/top_level.txt reading manifest file 'xlsx2csv.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'README' adding license file 'LICENSE.txt' writing manifest file 'xlsx2csv.egg-info/SOURCES.txt' ERROR Missing dependencies: setuptools_scm[toml]>=3.4.3 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 04:45:57 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 04:45:57 -0000 Subject: [MacPorts] #64088: cargo-c fails to build on 10.13 In-Reply-To: <045.090030d424cbe1b826c5873b2f307cf7@macports.org> References: <045.090030d424cbe1b826c5873b2f307cf7@macports.org> Message-ID: <060.b751d29ead35625be8949ab3799361a5@macports.org> #64088: cargo-c fails to build on 10.13 -----------------------+--------------------------------- Reporter: bK4gYuRo | Owner: MarcusCalhoun-Lopez Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: highsierra Port: cargo-c | -----------------------+--------------------------------- Changes (by MarcusCalhoun-Lopez): * status: assigned => closed * resolution: => fixed Comment: cargo-c seems to be successfully building on the [https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/175728 buildbots], so I think this ticket can be closed.\\ Please feel free to reopen if this issue has not been resolved. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:30:26 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 05:30:26 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.61f8caa2ac4199e5fc8ad3ee285ce024@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): I mean, that may be suitable? Regardless, the livecheck code is part of https://github.com/macports/macports-base I think? I don't know much about it, though I have started looking into it, tips and hints and suggestions are welcome. Replying to [comment:4 ryandesign]: > The suggestion in that issue was: > > > You can check the stable version on http://www.libressl.org/ as "The latest stable release is x.x.x" . > > Is that not suitable? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:41:28 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 05:41:28 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.fdd95c55531074ad0fc2edaadca128d8@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): From the extant Portfile we have: livecheck.type regex livecheck.url https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ livecheck.regex "(\\d+\\.\\d+\\.\\d+)" running %sudo port -v livecheck Results in: libressl seems to have been updated (port version: 3.6.1, new version: 3.7.0) But how that is processed, is totally opaque to me. I am reading https://guide.macports.org/chunked/reference.livecheck.html without many additional insights. Whereas https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ is basically just a directory, so I am guessing it is just enumerating whatever the most recent version is from that, but if I for example, change that to https://www.libressl.org it doesn't seem to break, but it doesn't change anything either, nor does adding for example: livecheck.distname "The latest stable release" In other words, I would love to know where to look to get a deeper understanding of the livecheck code itself, but I am currently a bit out of my depth. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:43:17 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 05:43:17 -0000 Subject: [MacPorts] #66092: nethack: error: too few arguments provided to function-like macro invocation In-Reply-To: <049.0be152501cd40086b61e90ef054178aa@macports.org> References: <049.0be152501cd40086b61e90ef054178aa@macports.org> Message-ID: <064.67ea33d0fb10e6999e891d4cbeb1705a@macports.org> #66092: nethack: error: too few arguments provided to function-like macro invocation ---------------------------+--------------------- Reporter: ShadSterling | Owner: jflude Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: nethack | ---------------------------+--------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"2fcec9af954931269141830fead4bed78dcf66c1/macports-ports" 2fcec9af954931269141830fead4bed78dcf66c1/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="2fcec9af954931269141830fead4bed78dcf66c1" nethack: fix build on Ventura closes: https://trac.macports.org/ticket/66092 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:45:11 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 05:45:11 -0000 Subject: [MacPorts] #66586: ld64 selects conflicting variant when using migration instructions In-Reply-To: <046.638d00d1067980537931285ce3cef5eb@macports.org> References: <046.638d00d1067980537931285ce3cef5eb@macports.org> Message-ID: <061.a85e33fb14b4a168ef81bb315a691c66@macports.org> #66586: ld64 selects conflicting variant when using migration instructions ------------------------+-------------------- Reporter: hopper333 | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: ld64 | ------------------------+-------------------- Comment (by kencu): Unfortunately, you should not be installing ld64_274 at all, however. It is wholly inappropriate for your current system. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 05:49:52 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 05:49:52 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.b90cfb8ce5c313afcd6acbc41eae6d49@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): Changing these lines: {{{ livecheck.type regex livecheck.url https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ livecheck.regex "(\\d+\\.\\d+\\.\\d+)" }}} to: {{{ livecheck.type regex livecheck.url https://www.libressl.org/ livecheck.regex "The latest stable release is (\\d+\\.\\d+\\.\\d+)" }}} Results in: sudo port -v livecheck libressl seems to be up to date Which is presumably, closer to what you want? I can prep a PR for that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 06:03:22 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 06:03:22 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.306b67ce0bdd311e02de85729805a4ad@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): PR submitted here: https://github.com/macports/macports-ports/pull/17125 I will see if I can create something similar to improve libressl-devel's livecheck as well. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 06:14:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 06:14:20 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.085c81326e5d08d02ac8fcca4de0a45b@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): Submitted this PR for libressl-devel as well: https://github.com/macports /macports-ports/pull/17126 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 07:22:14 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 07:22:14 -0000 Subject: [MacPorts] #66486: sendfile @2.1b-20110604: error: no member named 'ut_user' in 'struct utmp' In-Reply-To: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> References: <046.aab57c3ec6baf0f5adb9923f4425bff9@macports.org> Message-ID: <061.f9786f09faeb82d1214e6c9be52c30c2@macports.org> #66486: sendfile @2.1b-20110604: error: no member named 'ut_user' in 'struct utmp' ------------------------+--------------------- Reporter: MStraeten | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: ventura Port: sendfile | ------------------------+--------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"299650c43ef5dcf328d52d4084f3e54f616eea7c/macports-ports" 299650c43ef5dcf328d52d4084f3e54f616eea7c/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="299650c43ef5dcf328d52d4084f3e54f616eea7c" sendfile: delete port no installs in past year not maintained since 2011 doesn't build on any systems closes: https://trac.macports.org/ticket/66486 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 08:45:15 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 08:45:15 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.d329f9be86f130679495368c95b591b3@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libressl | --------------------------+---------------------- Changes (by artkiver): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"7e0d0afcdafa03cdb5a15ac2754dde16afd28809/macports-ports" 7e0d0afcdafa03cdb5a15ac2754dde16afd28809/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="7e0d0afcdafa03cdb5a15ac2754dde16afd28809" libressl: improve livecheck. * Closes: https://trac.macports.org/ticket/66568 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 09:49:20 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 09:49:20 -0000 Subject: [MacPorts] #66568: libressl: improve livecheck In-Reply-To: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> References: <045.47c52abdc90ab7f3e2a6c74f4ca223a1@macports.org> Message-ID: <060.04fa91bd7f47b1175ac75bb94dbd62b2@macports.org> #66568: libressl: improve livecheck --------------------------+---------------------- Reporter: Zweihorn | Owner: artkiver Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libressl | --------------------------+---------------------- Comment (by artkiver): https://github.com/macports/macports-ports/pull/17127 (I ended up deleting 17126 accidentally after running into some issues with branches) was also merged for libressl-devel. Hopefully moving forward, those changes will result in more accurate results for each. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 10:41:58 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 10:41:58 -0000 Subject: [MacPorts] #66588: emacs @28.2_1+nativecomp - does not configure if gmake is active, at least on El Capitan Message-ID: <046.2098b4c7616a85ad8f0baa6232d1c7f7@macports.org> #66588: emacs @28.2_1+nativecomp - does not configure if gmake is active, at least on El Capitan -----------------------+------------------------- Reporter: snowflake | Owner: drkp Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Keywords: | Port: emacs gmake -----------------------+------------------------- I noticed that the buildbots were building emacs without any problems. Here on my machines, there was a problem on El Capitan, but not on Monterey. There was a segmentation fault during the configure phase. I deactivated `gmake` and the configure phase completed. Here is the tail of the log: {{{ config.status: creating nt/Makefile config.status: creating test/Makefile config.status: creating admin/charsets/Makefile config.status: creating admin/unidata/Makefile config.status: creating admin/grammars/Makefile config.status: creating src/config.h config.status: executing src/epaths.h commands ./config.status: line 2469: 88402 Segmentation fault: 11 ${MAKE-make} MAKEFILE_NAME=do-not-make-Makefile epaths-force config.status: error: 'src/epaths.h' could not be made. Command failed: cd "/opt/local/var/macports/build/_Users_davidevans_macports_sources_github .com_macports_macports-ports_editors_emacs/emacs/work/emacs-28.2" && ./configure --prefix=/opt/local --disable-silent-rules --without-ns --without-x --without-dbus --without-gconf --without-libotf --without- m17n-flt --with-libgmp --with-gnutls --with-json --with-xml2 --with- modules --infodir /opt/local/share/info/emacs --with-native-compilation Exit code: 1 Error: Failed to configure emacs: consult /opt/local/var/macports/build/_Users_davidevans_macports_sources_github .com_macports_macports- ports_editors_emacs/emacs/work/emacs-28.2/config.log Error: Failed to configure emacs: configure failure: command execution failed DEBUG: Error code: NONE DEBUG: Backtrace: configure failure: command execution failed DEBUG: while executing DEBUG: "$procedure $targetname" Error: See /opt/local/var/macports/logs/_Users_davidevans_macports_sources_github .com_macports_macports-ports_editors_emacs/emacs/main.log for details. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 15:32:02 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 15:32:02 -0000 Subject: [MacPorts] #66589: py311-pyqt5 does not install Message-ID: <048.57d814a21a617c9aff40fb977ac1ba50@macports.org> #66589: py311-pyqt5 does not install -------------------------+------------------------- Reporter: josephsacco | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: py311-pyqt5 -------------------------+------------------------- System: OSX 12.6.2, SDK12 See below. -Joseph {{{ :debug:destroot Executing proc-post-org.macports.destroot-destroot-0 :debug:destroot Executing proc-post-org.macports.destroot-destroot-1 :debug:destroot Executing portdestroot::destroot_finish :debug:destroot Fixing glibtool .la files in destroot for py311-pyqt5 :error:destroot No files have been installed in the destroot directory! :error:destroot Please make sure that this software supports 'make install DESTDIR=${destroot}' or implement an alternative destroot mechanism in the Portfile. :error:destroot Files might have been installed directly into your system, check before proceeding. :error:destroot Failed to destroot py311-pyqt5: Staging py311-pyqt5 into destroot failed :debug:destroot Error code: NONE :debug:destroot Backtrace: Staging py311-pyqt5 into destroot failed :debug:destroot while executing :debug:destroot "$postrun $targetname" }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 15:32:47 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 15:32:47 -0000 Subject: [MacPorts] #66589: py311-pyqt5 does not install In-Reply-To: <048.57d814a21a617c9aff40fb977ac1ba50@macports.org> References: <048.57d814a21a617c9aff40fb977ac1ba50@macports.org> Message-ID: <063.cfd1e7e8fec3b6ed132675686c0dbc8b@macports.org> #66589: py311-pyqt5 does not install --------------------------+-------------------- Reporter: josephsacco | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py311-pyqt5 | --------------------------+-------------------- Changes (by josephsacco): * Attachment "main.log" added. py311-pyqt5 log file -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:02:09 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 16:02:09 -0000 Subject: [MacPorts] #66247: kdelibs4: build failure on macOS 13 In-Reply-To: <049.d30def2f2b97fc3010faf6ae66ba8b3d@macports.org> References: <049.d30def2f2b97fc3010faf6ae66ba8b3d@macports.org> Message-ID: <064.6b2588d7937c06a9742daf7e85ed8eb1@macports.org> #66247: kdelibs4: build failure on macOS 13 ---------------------------+------------------------- Reporter: ShadSterling | Owner: NicosPavlov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: kdelibs4 | ---------------------------+------------------------- Comment (by ShadSterling): Trying again today it only happens with `+docs`; with `kdelibs4 -docs` installed successfully -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:12:15 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 16:12:15 -0000 Subject: [MacPorts] #66590: Failed to build zig: command execution failed Message-ID: <044.7dca48b272ee96b328c2154fc31e8077@macports.org> #66590: Failed to build zig: command execution failed ---------------------+-------------------- Reporter: dfousek | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: zig ---------------------+-------------------- Full Name: zig @0.10.0_0 :info:build [100%] Linking CXX executable zig2 :info:build /opt/local/bin/cmake -E cmake_link_script CMakeFiles/zig2.dir/link.txt --verbose=ON :info:build /opt/local/bin/clang++-mp-15 -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=1$ :info:build ld: warning: directory not found for option '-L/opt/local/share/cmake/Modules' :info:build Undefined symbols for architecture x86_64: :info:build "___ulock_wait2", referenced from: :info:build _std.Thread.Futex.DarwinImpl.wait in zig2.o :info:build "__availability_version_check", referenced from: :info:build ___isPlatformVersionAtLeast in zig2.o :info:build "_posix_spawn_file_actions_addchdir_np", referenced from: :info:build _posix_spawn.Actions.chdirZ in zig2.o :info:build "_posix_spawn_file_actions_addfchdir_np", referenced from: :info:build _posix_spawn.Actions.fchdir in zig2.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[2]: *** [zig2] Error 1 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 16:35:28 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 16:35:28 -0000 Subject: [MacPorts] #66590: zig @0.10.0_0 : Failed to build zig - command execution failed (was: Failed to build zig: command execution failed) In-Reply-To: <044.7dca48b272ee96b328c2154fc31e8077@macports.org> References: <044.7dca48b272ee96b328c2154fc31e8077@macports.org> Message-ID: <059.fcaa8c1ce16f15f2ad319016cf97dc66@macports.org> #66590: zig @0.10.0_0 : Failed to build zig - command execution failed ----------------------+-------------------- Reporter: dfousek | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: zig | ----------------------+-------------------- Description changed by dfousek: Old description: > Full Name: zig @0.10.0_0 > > :info:build [100%] Linking CXX executable zig2 > :info:build /opt/local/bin/cmake -E cmake_link_script > CMakeFiles/zig2.dir/link.txt --verbose=ON > :info:build /opt/local/bin/clang++-mp-15 -pipe -Os -DNDEBUG > -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=1$ > :info:build ld: warning: directory not found for option > '-L/opt/local/share/cmake/Modules' > :info:build Undefined symbols for architecture x86_64: > :info:build "___ulock_wait2", referenced from: > :info:build _std.Thread.Futex.DarwinImpl.wait in zig2.o > :info:build "__availability_version_check", referenced from: > :info:build ___isPlatformVersionAtLeast in zig2.o > :info:build "_posix_spawn_file_actions_addchdir_np", referenced from: > :info:build _posix_spawn.Actions.chdirZ in zig2.o > :info:build "_posix_spawn_file_actions_addfchdir_np", referenced from: > :info:build _posix_spawn.Actions.fchdir in zig2.o > :info:build ld: symbol(s) not found for architecture x86_64 > :info:build clang: error: linker command failed with exit code 1 (use -v > to see invocation) > :info:build make[2]: *** [zig2] Error 1 New description: {{{ :info:build [100%] Linking CXX executable zig2 :info:build /opt/local/bin/cmake -E cmake_link_script CMakeFiles/zig2.dir/link.txt --verbose=ON :info:build /opt/local/bin/clang++-mp-15 -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=1$ :info:build ld: warning: directory not found for option '-L/opt/local/share/cmake/Modules' :info:build Undefined symbols for architecture x86_64: :info:build "___ulock_wait2", referenced from: :info:build _std.Thread.Futex.DarwinImpl.wait in zig2.o :info:build "__availability_version_check", referenced from: :info:build ___isPlatformVersionAtLeast in zig2.o :info:build "_posix_spawn_file_actions_addchdir_np", referenced from: :info:build _posix_spawn.Actions.chdirZ in zig2.o :info:build "_posix_spawn_file_actions_addfchdir_np", referenced from: :info:build _posix_spawn.Actions.fchdir in zig2.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[2]: *** [zig2] Error 1 }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 17:15:04 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 17:15:04 -0000 Subject: [MacPorts] #65765: kdelibs4: Error: Cannot install kdelibs4 for the arch 'arm64' because its dependency qt4-mac only supports the archs 'ppc ppc64 i386 x86_64' In-Reply-To: <044.0f7acdce89c8bdf5ac76ae3175505d7e@macports.org> References: <044.0f7acdce89c8bdf5ac76ae3175505d7e@macports.org> Message-ID: <059.dcfdc260f433e3ba219dcdccfcd8c2f5@macports.org> #65765: kdelibs4: Error: Cannot install kdelibs4 for the arch 'arm64' because its dependency qt4-mac only supports the archs 'ppc ppc64 i386 x86_64' -----------------------+---------------------------- Reporter: ferdiga | Owner: NicosPavlov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: arm64 monterey Port: kdelibs4 | -----------------------+---------------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"67e7251ea9df28359f4c0ec392ccf0ccf91f1bf8/macports-ports" 67e7251ea9df28359f4c0ec392ccf0ccf91f1bf8/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="67e7251ea9df28359f4c0ec392ccf0ccf91f1bf8" qt4 PortGroup: indicate supported archs closes: https://trac.macports.org/ticket/65765 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 17:19:49 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 17:19:49 -0000 Subject: [MacPorts] #66587: py310-xlsx2csv @0.8.0: ERROR Missing dependencies: setuptools_scm[toml]>=3.4.3 In-Reply-To: <047.e2a604d409d43eff3149b519f3022bc6@macports.org> References: <047.e2a604d409d43eff3149b519f3022bc6@macports.org> Message-ID: <062.cb999c1b3334c01561df0eab698fabb8@macports.org> #66587: py310-xlsx2csv @0.8.0: ERROR Missing dependencies: setuptools_scm[toml]>=3.4.3 --------------------------+---------------------------- Reporter: ryandesign | Owner: kurthindenburg Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: Port: py-xlsx2csv | --------------------------+---------------------------- Changes (by kurthindenburg): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"80e970ab52a60da7bb895da298e86a4cb5f162a9/macports-ports" 80e970ab52a60da7bb895da298e86a4cb5f162a9/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="80e970ab52a60da7bb895da298e86a4cb5f162a9" py-xlsx2csv: add missing dependency closes: https://trac.macports.org/ticket/66587 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 17:33:52 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 17:33:52 -0000 Subject: [MacPorts] #66247: kdelibs4: build failure on macOS 13 In-Reply-To: <049.d30def2f2b97fc3010faf6ae66ba8b3d@macports.org> References: <049.d30def2f2b97fc3010faf6ae66ba8b3d@macports.org> Message-ID: <064.71021749c72ca33c24b0d04d30d05f9b@macports.org> #66247: kdelibs4: build failure on macOS 13 ---------------------------+------------------------- Reporter: ShadSterling | Owner: NicosPavlov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: ventura Port: kdelibs4 | ---------------------------+------------------------- Comment (by kencu): looks like something to do with either not linking in jasper, or perhaps linking in the wrong jasper... have to dig in on that. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 18:51:01 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 18:51:01 -0000 Subject: [MacPorts] #65908: lzma @22.01_0 does not use MacPorts CFLAGS/CXXFLAGS In-Reply-To: <043.8ce5ec54a18b9cd59498397621b1f9c9@macports.org> References: <043.8ce5ec54a18b9cd59498397621b1f9c9@macports.org> Message-ID: <058.b5921520ae467b40edac16eb80556924@macports.org> #65908: lzma @22.01_0 does not use MacPorts CFLAGS/CXXFLAGS ---------------------+------------------------------- Reporter: RobK88 | Owner: ryandesign Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.7.2 Resolution: | Keywords: lion mountainlion Port: lzma | ---------------------+------------------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/17133 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 19:34:50 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 19:34:50 -0000 Subject: [MacPorts] #66589: py311-pyqt5 does not install In-Reply-To: <048.57d814a21a617c9aff40fb977ac1ba50@macports.org> References: <048.57d814a21a617c9aff40fb977ac1ba50@macports.org> Message-ID: <063.b94f73c9a4b1a405a06f3beb2dba0f6c@macports.org> #66589: py311-pyqt5 does not install --------------------------+------------------------ Reporter: josephsacco | Owner: reneeotten Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-pyqt5 | --------------------------+------------------------ Changes (by jmroot): * owner: (none) => reneeotten * status: new => assigned * port: py311-pyqt5 => py-pyqt5 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 19:35:40 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 19:35:40 -0000 Subject: [MacPorts] #66590: zig @0.10.0_0 : Failed to build zig - command execution failed In-Reply-To: <044.7dca48b272ee96b328c2154fc31e8077@macports.org> References: <044.7dca48b272ee96b328c2154fc31e8077@macports.org> Message-ID: <059.67e31d84dbed1c0c84338b50e3615a19@macports.org> #66590: zig @0.10.0_0 : Failed to build zig - command execution failed ----------------------+---------------------- Reporter: dfousek | Owner: felix Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: zig | ----------------------+---------------------- Changes (by jmroot): * cc: felix@? (added) * owner: (none) => felix * status: new => assigned -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 20:26:35 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 20:26:35 -0000 Subject: [MacPorts] #66193: py310-llvmlite @0.39.1 build failure on Ventura In-Reply-To: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> References: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> Message-ID: <058.ddf85db01cecb8425632e0c5ed0fd8b2@macports.org> #66193: py310-llvmlite @0.39.1 build failure on Ventura --------------------------+---------------------- Reporter: dbl001 | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-llvmlite | --------------------------+---------------------- Comment (by jsalort): For the record, I get the exact same error message on arm64. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 20:33:08 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 20:33:08 -0000 Subject: [MacPorts] #66193: py310-llvmlite @0.39.1 build failure on Ventura In-Reply-To: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> References: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> Message-ID: <058.85dc292cf0fdd20ecdad4abad0dc12ca@macports.org> #66193: py310-llvmlite @0.39.1 build failure on Ventura --------------------------+---------------------- Reporter: dbl001 | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-llvmlite | --------------------------+---------------------- Comment (by kencu): This smells like a c++ standard issue, and I see this build is rather confused about the c++ standard as it is setting it several different ways on the build line already. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 21:23:21 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 21:23:21 -0000 Subject: [MacPorts] #59945: botan +universal: build failure In-Reply-To: <052.f0f34aa294a1627bda6d50516ac86c63@macports.org> References: <052.f0f34aa294a1627bda6d50516ac86c63@macports.org> Message-ID: <067.75c7ab5b7f4710f4105ff4a8ade99341@macports.org> #59945: botan +universal: build failure ------------------------------+---------------------- Reporter: TheLastLovemark | Owner: (none) Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: | Keywords: Port: botan | ------------------------------+---------------------- Comment (by kencu): a potential universal fix, that works with arm64/x86_64 at least: https://github.com/macports/macports-ports/pull/17135 not tested to see if it fixes the situation where an older or different botan library is already installed, but wouldn't expect it to, if that is still an issue. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 22:07:02 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 22:07:02 -0000 Subject: [MacPorts] #63635: libgcrypt +universal Failed to destroot: libgcrypt.pc differs in .../destroot-arm64/... and .../destroot-ppc-intel/... and cannot be merged In-Reply-To: <049.e03f8ad28ef2bdb5b1e6cb5049607404@macports.org> References: <049.e03f8ad28ef2bdb5b1e6cb5049607404@macports.org> Message-ID: <064.7195dbfef1b5d159d3ea162cb43f6720@macports.org> #63635: libgcrypt +universal Failed to destroot: libgcrypt.pc differs in .../destroot-arm64/... and .../destroot-ppc-intel/... and cannot be merged ---------------------------+-------------------- Reporter: ShadSterling | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: Port: libgcrypt | ---------------------------+-------------------- Comment (by kencu): https://github.com/macports/macports-ports/pull/17136 -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 22:14:22 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 22:14:22 -0000 Subject: [MacPorts] #61709: stack: Cannot be installed on Apple Silicon In-Reply-To: <052.00a8ed032bed291d728defbb2f0ec0d8@macports.org> References: <052.00a8ed032bed291d728defbb2f0ec0d8@macports.org> Message-ID: <067.6aa1fc24fc84e72241fb3b1adef1f789@macports.org> #61709: stack: Cannot be installed on Apple Silicon ------------------------------+----------------------- Reporter: Gregory-Gelfond | Owner: essandess Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: worksforme | Keywords: arm64 Port: stack | ------------------------------+----------------------- Changes (by kencu): * status: assigned => closed * resolution: => worksforme Comment: both pandas and stack automatically install the x86_64 binary on Apple Silicon now. this is the current workaround until the entire Haskell environment is supported on Apple Silicon. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 22:15:55 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 22:15:55 -0000 Subject: [MacPorts] #61766: nss @3.59: "Compiler option is invalid" In-Reply-To: <048.856cb07f144fd55d68c15476f2bab83d@macports.org> References: <048.856cb07f144fd55d68c15476f2bab83d@macports.org> Message-ID: <063.85f7b8edf7a9574a79ddb5a9410ce90f@macports.org> #61766: nss @3.59: "Compiler option is invalid" --------------------------+-------------------- Reporter: MaddTheSane | Owner: (none) Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: arm64 Port: nss | --------------------------+-------------------- Changes (by kencu): * status: new => closed * resolution: => fixed Comment: nss builds on Apple Silicon now, including universal: {{{ % port -v installed nss The following ports are currently installed: nss @3.86_0 requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-29T12:37:20-0800' nss @3.86_0+universal (active) requested_variants='+universal' platform='darwin 22' archs='arm64 x86_64' date='2022-12-30T13:39:51-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Fri Dec 30 22:18:24 2022 From: noreply at macports.org (MacPorts) Date: Fri, 30 Dec 2022 22:18:24 -0000 Subject: [MacPorts] #61821: geos @3.8.1 build failure on Apple Silicon In-Reply-To: <047.8ec3ff46a62ed7360e2521e794aca20e@macports.org> References: <047.8ec3ff46a62ed7360e2521e794aca20e@macports.org> Message-ID: <062.a9468d7ccdf029fb555d73610e80b96d@macports.org> #61821: geos @3.8.1 build failure on Apple Silicon -------------------------+---------------------- Reporter: PaulWessel | Owner: stromnov Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.4 Resolution: fixed | Keywords: arm64 Port: geos | -------------------------+---------------------- Changes (by kencu): * status: assigned => closed * resolution: => fixed Comment: as noted: {{{ % port -v installed geos The following ports are currently installed: geos @3.11.0_0 (active) requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-30T14:17:37-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 00:41:15 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 00:41:15 -0000 Subject: [MacPorts] #66466: libiodbc @3.52.15_2+libodbc+x11: Build errors, mostly from drvconn.c In-Reply-To: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> References: <044.dd5d2d517ff3d837708e805d63f5879c@macports.org> Message-ID: <059.1449c14e2feca12d7083eac1630bcbe2@macports.org> #66466: libiodbc @3.52.15_2+libodbc+x11: Build errors, mostly from drvconn.c -----------------------+---------------------- Reporter: gregyao | Owner: nerdling Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: libiodbc | -----------------------+---------------------- Comment (by kencu): as a starting point, it can build "-x11" on Ventura: {{{ % port -v installed libiodbc The following ports are currently installed: libiodbc @3.52.15_2+libodbc+universal (active) requested_variants='+universal-x11' platform='darwin 22' archs='arm64 x86_64' date='2022-12-30T16:28:08-0800' }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 01:44:14 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 01:44:14 -0000 Subject: [MacPorts] #63635: libgcrypt +universal Failed to destroot: libgcrypt.pc differs in .../destroot-arm64/... and .../destroot-ppc-intel/... and cannot be merged In-Reply-To: <049.e03f8ad28ef2bdb5b1e6cb5049607404@macports.org> References: <049.e03f8ad28ef2bdb5b1e6cb5049607404@macports.org> Message-ID: <064.1b7d64e4dd05a298d8085a7f84c69b79@macports.org> #63635: libgcrypt +universal Failed to destroot: libgcrypt.pc differs in .../destroot-arm64/... and .../destroot-ppc-intel/... and cannot be merged ---------------------------+-------------------- Reporter: ShadSterling | Owner: kencu Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: fixed | Keywords: Port: libgcrypt | ---------------------------+-------------------- Changes (by kencu): * status: new => closed * owner: (none) => kencu * resolution: => fixed Comment: In [changeset:"3fd961ba60c083fefd0d6f054acb306ff5730307/macports-ports" 3fd961ba60c083fefd0d6f054acb306ff5730307/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="3fd961ba60c083fefd0d6f054acb306ff5730307" libgcrypt: allow cross-arch universal building strip host= from pc file closes: https://trac.macports.org/ticket/63635 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 02:12:44 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 02:12:44 -0000 Subject: [MacPorts] #66588: emacs @28.2_1+nativecomp - does not configure if gmake is active, at least on El Capitan In-Reply-To: <046.2098b4c7616a85ad8f0baa6232d1c7f7@macports.org> References: <046.2098b4c7616a85ad8f0baa6232d1c7f7@macports.org> Message-ID: <061.a5018bf09029b50361129539c49f3e59@macports.org> #66588: emacs @28.2_1+nativecomp - does not configure if gmake is active, at least on El Capitan --------------------------+---------------------- Reporter: snowflake | Owner: drkp Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.99 Resolution: | Keywords: Port: emacs gmake | --------------------------+---------------------- Comment (by ryandesign): Can you attach the crash log? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 02:23:16 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 02:23:16 -0000 Subject: [MacPorts] #66408: Minetest: links to gmp opportunistically In-Reply-To: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> References: <052.8fffc54ca8237db2f661937584ebd4ea@macports.org> Message-ID: <067.326dcd7b1faf588273802a5ddc58cdce@macports.org> #66408: Minetest: links to gmp opportunistically ------------------------------+------------------------------------------- Reporter: programmingkidx | Owner: Zweihorn <4863737+Zweihorn@?> Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: minetest gmp Port: minetest | ------------------------------+------------------------------------------- Changes (by Zweihorn <4863737+Zweihorn@?>): * status: new => closed * owner: (none) => Zweihorn <4863737+Zweihorn@?> * resolution: => fixed Comment: In [changeset:"878d316473ca383f32dafeb2dc8b158c6a2d7bd0/macports-ports" 878d316473ca383f32dafeb2dc8b158c6a2d7bd0/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="878d316473ca383f32dafeb2dc8b158c6a2d7bd0" minetest: assume maintainership, update dependencies Closes: https://trac.macports.org/ticket/66562 Closes: https://trac.macports.org/ticket/66408 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 02:23:17 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 02:23:17 -0000 Subject: [MacPorts] #66562: minetest: new maintainer & new Portfile In-Reply-To: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> References: <045.9d5fb14e515581ebcff9a61e87e57685@macports.org> Message-ID: <060.5d10082b1cff707a9d8ffe8462e69a62@macports.org> #66562: minetest: new maintainer & new Portfile --------------------------+---------------------- Reporter: Zweihorn | Owner: Zweihorn Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: fixed | Keywords: x86_64 Port: minetest | --------------------------+---------------------- Changes (by Zweihorn <4863737+Zweihorn@?>): * status: assigned => closed * resolution: => fixed Comment: In [changeset:"878d316473ca383f32dafeb2dc8b158c6a2d7bd0/macports-ports" 878d316473ca383f32dafeb2dc8b158c6a2d7bd0/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="878d316473ca383f32dafeb2dc8b158c6a2d7bd0" minetest: assume maintainership, update dependencies Closes: https://trac.macports.org/ticket/66562 Closes: https://trac.macports.org/ticket/66408 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 03:08:50 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 03:08:50 -0000 Subject: [MacPorts] #59945: botan +universal: build failure In-Reply-To: <052.f0f34aa294a1627bda6d50516ac86c63@macports.org> References: <052.f0f34aa294a1627bda6d50516ac86c63@macports.org> Message-ID: <067.b0bd340c020831c443531ef16d9df91d@macports.org> #59945: botan +universal: build failure -----------------------------+--------------------------------------------- Reporter: | Owner: Dean M Greer <38226388+Gcenx@?> TheLastLovemark | Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.6.2 Resolution: fixed | Keywords: Port: botan | -----------------------------+--------------------------------------------- Changes (by Dean M Greer <38226388+Gcenx@?>): * owner: (none) => Dean M Greer <38226388+Gcenx@?> * status: reopened => closed * resolution: => fixed Comment: In [changeset:"4fdf0eee0bd52de8e65b5dfb7328f3aaa79c4ee9/macports-ports" 4fdf0eee0bd52de8e65b5dfb7328f3aaa79c4ee9/macports-ports] (master): {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="4fdf0eee0bd52de8e65b5dfb7328f3aaa79c4ee9" botan: fix cross-arch universal building allows universal arm64/x86_64 and others closes: https://trac.macports.org/ticket/59945 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 04:01:00 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 04:01:00 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 Message-ID: <042.d6c8b85acb14b46603652c25795d521f@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 --------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: rust --------------------+--------------------------------- the universal build of rust is needed for certain ports to build universal hoping Marcus has some insights on how to proceed here -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 04:02:26 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 04:02:26 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.9a46108d0cc1ce80e8944312a88069b9@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Changes (by kencu): * Attachment "rust-universal-arm-Intel-fail.log.zip" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 04:39:49 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 04:39:49 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.3a23ea8fbda75a5dfec75d791bab73fb@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): The error seems to be {{{ :info:build : Error allocating TSD }}} I have not encounter this problem.\\ On the same machine, does building with `build_arch=x86_64 -universal` work?\\ Does commenting out `--set=rust.jemalloc` in the Portfile allow a successful build?\\ At the very least, one of these two steps may help narrow down the problem. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 05:10:00 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 05:10:00 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.96f5d0ef099cf3c6c88c512375c47db5@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): thank you for your attentions -- I will try both of those. By the way, this new 16" MacBookPro M1 I'm typing on is just a screaming fast machine -- the NVME drive hits 6000 MB/s, and there are 10 fast cores -- for when you go shopping :.. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 05:54:49 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 05:54:49 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.16134fac5f010137f9f2349b971905eb@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): building like this: {{{ % sudo port -v destroot rust build_arch=x86_64 -universal }}} gives the same error it seems: {{{ error: process didn't exit successfully: `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.66.0-src/build/bootstrap/debug/rustc -vV` (exit status: 254) --- stdout Did not run successfully: signal: 6 (SIGABRT) "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.66.0-src/build/x86_64 -apple-darwin/stage1/bin/rustc" "-vV" "-Wrust_2018_idioms" "-Wunused_lifetimes" "-Wsemicolon_in_expressions_from_macros" "-Dwarnings" "-Clinker=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/compwrap/ld/usr/bin/clang" "-Zunstable-options" "--check-cfg=values(bootstrap)" "-Z" "force-unstable- if-unmarked" ------------- --- stderr : Error allocating TSD rustc exited with signal: 6 (SIGABRT) command did not execute successfully: "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/cargo-1.65.0-x86_64 -apple-darwin/cargo/bin/cargo" "build" "--target" "x86_64-apple-darwin" "-Zcheck-cfg=names,values,output" "-Zbinary-dep-depinfo" "-j" "10" "-v" "-v" "--release" "--features" "panic-unwind backtrace" "--manifest-path" "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust/work/rustc-1.66.0-src/library/test/Cargo.toml" "--message-format" "json-render-diagnostics" expected success, got: exit status: 101 }}} will try the other next. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 06:59:47 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 06:59:47 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.08b688ec9255882c17069e052d6bfd5d@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): disabling jemalloc indeed allowed the build to finish. There is a bit of a hiccup in the muniversal destrooting -- I'll see if I can fix that. New log attached. Thanks, Marcus! -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 07:00:08 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 07:00:08 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.302ec38a2edb7a9bb1d83045c41a9528@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Changes (by kencu): * Attachment "rust-universal-fail2.log.zip" added. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 08:49:38 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 08:49:38 -0000 Subject: [MacPorts] #66592: sdcc @4.2.0: makeinfo: command not found Message-ID: <047.ea168ec6394c8702d706984f0075c448@macports.org> #66592: sdcc @4.2.0: makeinfo: command not found ------------------------+---------------------- Reporter: ryandesign | Owner: nerdling Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: ventura | Port: sdcc ------------------------+---------------------- https://build.macports.org/builders/ports- 13_x86_64-builder/builds/9643/steps/install-port/logs/stdio {{{ /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_sdcc/sdcc/work/sdcc/support/sdbinutils/missing: line 81: makeinfo: command not found WARNING: 'makeinfo' is missing on your system. You should only need it if you modified a '.texi' file, or any other file indirectly affecting the aspect of the manual. You might want to install the Texinfo package: The spurious makeinfo call might also be the consequence of using a buggy 'make' (AIX, DU, IRIX), in which case you might want to install GNU make: gnumake[4]: *** [bfd.info] Error 127 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 10:16:59 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 10:16:59 -0000 Subject: [MacPorts] #66193: py310-llvmlite @0.39.1 build failure on Ventura In-Reply-To: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> References: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> Message-ID: <058.d2afad4368d192bbba8b2db9f309ee8c@macports.org> #66193: py310-llvmlite @0.39.1 build failure on Ventura --------------------------+---------------------- Reporter: dbl001 | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-llvmlite | --------------------------+---------------------- Comment (by jsalort): There is actually a PR, https://github.com/macports/macports-ports/pull/16640 but currently marked as "DO NOT MERGE". -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 14:00:47 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 14:00:47 -0000 Subject: [MacPorts] #66593: qt6 references file in /opt/local/bin, which do not exist Message-ID: <045.0ddf103b64b1a22645865b98a0f749ee@macports.org> #66593: qt6 references file in /opt/local/bin, which do not exist ----------------------+-------------------- Reporter: kgarrels | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ----------------------+-------------------- Hi, got this error now building cmake projects, works if I uninstall all of qt6 and use qt5 instead. Any suggestions? Happy New Year, kai {{{ CMake Error at /opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsTargets.cmake:154 (message): The imported target "Qt6::moc" references the file "/opt/local/bin/moc" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsTargets.cmake" but not all the files it references. Call Stack (most recent call first): /opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsConfig.cmake:37 (include) /opt/local/lib/cmake/Qt6Core/Qt6CoreDependencies.cmake:76 (find_package) /opt/local/lib/cmake/Qt6Core/Qt6CoreConfig.cmake:40 (include) /opt/local/lib/cmake/Qt6/Qt6Config.cmake:209 (find_package) CMakeLists.txt:124 (find_package) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 14:12:27 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 14:12:27 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.c2492cfbc8b6a2e5a764818bdb7d23ce@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): I built jemalloc on both an x86_64 machine and on an Apple Silicon machine with `build_arch=x86_64`.\\ The only difference I could find was `#define CPU_SPINWAIT __asm__ volatile("pause")` on the actual x86_64 machine.\\ That particular difference went away went I used version 1.1 of the muniveral PG.\\ I have no idea if that is the cause of the problem, but it might be worth a look.\\ Unfortunately, I cannot test it at the moment, but there is a [https://github.com/macports/macports-ports/pull/17149 pull request] with what I tried. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 14:13:05 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 14:13:05 -0000 Subject: [MacPorts] #66593: qt6 references file in /opt/local/bin, which do not exist In-Reply-To: <045.0ddf103b64b1a22645865b98a0f749ee@macports.org> References: <045.0ddf103b64b1a22645865b98a0f749ee@macports.org> Message-ID: <060.8ae85d82eddf01142ac9f677b61b5a61@macports.org> #66593: qt6 references file in /opt/local/bin, which do not exist -----------------------+-------------------- Reporter: kgarrels | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: | -----------------------+-------------------- Description changed by kgarrels: Old description: > Hi, > > got this error now building cmake projects, works if I uninstall all of > qt6 and use qt5 instead. > > Any suggestions? > > Happy New Year, > kai > > > {{{ > CMake Error at > /opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsTargets.cmake:154 > (message): > The imported target "Qt6::moc" references the file > > "/opt/local/bin/moc" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > > "/opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsTargets.cmake" > > but not all the files it references. > > Call Stack (most recent call first): > /opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsConfig.cmake:37 (include) > /opt/local/lib/cmake/Qt6Core/Qt6CoreDependencies.cmake:76 > (find_package) > /opt/local/lib/cmake/Qt6Core/Qt6CoreConfig.cmake:40 (include) > /opt/local/lib/cmake/Qt6/Qt6Config.cmake:209 (find_package) > CMakeLists.txt:124 (find_package) > }}} New description: Hi, got this error now building cmake projects, works if I uninstall all of qt6 and use qt5 instead. All qt6 version 6.2.4_2+openssl Any suggestions? Happy New Year, kai {{{ CMake Error at /opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsTargets.cmake:154 (message): The imported target "Qt6::moc" references the file "/opt/local/bin/moc" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsTargets.cmake" but not all the files it references. Call Stack (most recent call first): /opt/local/lib/cmake/Qt6CoreTools/Qt6CoreToolsConfig.cmake:37 (include) /opt/local/lib/cmake/Qt6Core/Qt6CoreDependencies.cmake:76 (find_package) /opt/local/lib/cmake/Qt6Core/Qt6CoreConfig.cmake:40 (include) /opt/local/lib/cmake/Qt6/Qt6Config.cmake:209 (find_package) CMakeLists.txt:124 (find_package) }}} -- -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 14:26:46 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 14:26:46 -0000 Subject: [MacPorts] #66193: py310-llvmlite @0.39.1 build failure on Ventura In-Reply-To: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> References: <043.64ad337fb2ff9d662182fe5abcb9d9b4@macports.org> Message-ID: <058.b5b0ec276829fcc5773470550691763a@macports.org> #66193: py310-llvmlite @0.39.1 build failure on Ventura --------------------------+---------------------- Reporter: dbl001 | Owner: stromnov Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: Port: py-llvmlite | --------------------------+---------------------- Comment (by kencu): thanks for that, indeed, helpful -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:10:45 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 17:10:45 -0000 Subject: [MacPorts] #63309: Dependency libidn could be replaced by libidn2 In-Reply-To: <041.85e1296f81dfc499387138f6bfa9a5cb@macports.org> References: <041.85e1296f81dfc499387138f6bfa9a5cb@macports.org> Message-ID: <056.62a59af10fe8a9f0fc4b722877c2b247@macports.org> #63309: Dependency libidn could be replaced by libidn2 -------------------------------------------------+------------------------- Reporter: ednl | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: Port: cpuminer echoping elinks-devel | FileZilla finch ghostscript gloox html-xml- | utils hydra Io jabber jabberd knot kopete | libgsasl libpurple libVLC2 loudmouth lynx | maildrop monotone monotone-devel mutt p5-net- | libidn pidgin podofo proftpd prosody psi | skipfish tin VLC2 | -------------------------------------------------+------------------------- Comment (by nickgaya): Ghostscript uses libidn's `stringprep` function to normalize Unicode password strings. This functionality is not supported in libidn2, so the upgrade is essentially blocked for this port. See https://bugs.ghostscript.com/show_bug.cgi?id=698774 The libidn2 manual states: > The original libidn library includes functionality for the stringprep processing in `stringprep.h`. That functionality was an integral part of an IDNA2003 implementation, but it does not apply to IDNA2008. Furthermore, stringprep processing has been replaced by the PRECIS framework (RFC8264). > > For the reasons above, libidn2 does not implement stringprep or any other string processing protocols unrelated to IDNA2008. Applications requiring the stringprep processing should continue using the original libidn, and new applications should consider using the PRECIS framework. https://www.gnu.org/software/libidn/libidn2/manual/html_node/Converting- from-libidn.html -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 17:14:31 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 17:14:31 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.a21827ad81271b69761b77edd8bf85d4@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): unfortunately same TSD error building universal rust with the new build of jemalloc. I'll go back to disabling it and see if I can fix that destroot issue for now. I notice two things about jemalloc; first of all, there are these warnings during the build, involving interestingly the TSD area in question: {{{ ccache /usr/bin/clang -std=gnu11 -Werror=unknown-warning-option -Wall -Wextra -Wshorten-64-to-32 -Wsign-compare -Wundef -Wno-format-zero-length -Wpointer-arith -Wno-missing-braces -Wno-missing-field-initializers -pipe -g3 -Wimplicit-fallthrough -O3 -funroll-loops -pipe -Os -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk -arch arm64 -c -I/opt/local/include -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.sdk -D_REENTRANT -Iinclude -Iinclude -o src/bin_info.o src/bin_info.c In file included from src/jemalloc_cpp.cpp:10: In file included from include/jemalloc/internal/jemalloc_internal_includes.h:51: In file included from include/jemalloc/internal/prof_structs.h:4: In file included from include/jemalloc/internal/ckh.h:4: In file included from include/jemalloc/internal/tsd.h:310: include/jemalloc/internal/tsd_generic.h:91:24: warning: suggest braces around initialization of subobject [-Wmissing-braces] tsd_t initializer = TSD_INITIALIZER; ^~~~~~~~~~~~~~~ include/jemalloc/internal/tsd.h:150:9: note: expanded from macro 'TSD_INITIALIZER' TSD_DATA_SLOW_INITIALIZER \ ^~~~~~~~~~~~~~~~~~~~~~~~~ include/jemalloc/internal/tsd.h:121:24: note: expanded from macro 'TSD_DATA_SLOW_INITIALIZER' /* tcache_slow */ TCACHE_SLOW_ZERO_INITIALIZER, \ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/jemalloc/internal/tcache_types.h:22:39: note: expanded from macro 'TCACHE_SLOW_ZERO_INITIALIZER' #define TCACHE_SLOW_ZERO_INITIALIZER {0} ^ In file included from src/jemalloc_cpp.cpp:10: In file included from include/jemalloc/internal/jemalloc_internal_includes.h:51: In file included from include/jemalloc/internal/prof_structs.h:4: In file included from include/jemalloc/internal/ckh.h:4: In file included from include/jemalloc/internal/tsd.h:310: include/jemalloc/internal/tsd_generic.h:134:22: warning: suggest braces around initialization of subobject [-Wmissing-braces] tsd_t initializer = TSD_INITIALIZER; ^~~~~~~~~~~~~~~ include/jemalloc/internal/tsd.h:150:9: note: expanded from macro 'TSD_INITIALIZER' TSD_DATA_SLOW_INITIALIZER \ ^~~~~~~~~~~~~~~~~~~~~~~~~ include/jemalloc/internal/tsd.h:121:24: note: expanded from macro 'TSD_DATA_SLOW_INITIALIZER' /* tcache_slow */ TCACHE_SLOW_ZERO_INITIALIZER, \ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/jemalloc/internal/tcache_types.h:22:39: note: expanded from macro 'TCACHE_SLOW_ZERO_INITIALIZER' #define TCACHE_SLOW_ZERO_INITIALIZER {0} ^ }}} so perhaps doing something to stop those warnings might be of use to preventing the error in rust. The other thing about jemalloc is that it forces itself to try to link against libstdc++: {{{ DSO_LDFLAGS : -shared -Wl,-install_name,$(LIBDIR)/$(@F) LIBS : -lstdc++ -pthread RPATH_EXTRA : }}} I am not sure if it actually does link against it. {{{ % otool -L /opt/local/lib/libjemalloc.dylib /opt/local/lib/libjemalloc.dylib (architecture x86_64): /opt/local/lib/libjemalloc.2.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0) /opt/local/lib/libjemalloc.dylib (architecture arm64): /opt/local/lib/libjemalloc.2.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0) }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:36:02 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 18:36:02 -0000 Subject: [MacPorts] #63309: Dependency libidn could be replaced by libidn2 In-Reply-To: <041.85e1296f81dfc499387138f6bfa9a5cb@macports.org> References: <041.85e1296f81dfc499387138f6bfa9a5cb@macports.org> Message-ID: <056.4db9915646e34a810661e1d5c996ec98@macports.org> #63309: Dependency libidn could be replaced by libidn2 -------------------------------------------------+------------------------- Reporter: ednl | Owner: (none) Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.7.1 Resolution: | Keywords: Port: cpuminer echoping elinks-devel | FileZilla finch ghostscript gloox html-xml- | utils hydra Io jabber jabberd knot kopete | libgsasl libpurple libVLC2 loudmouth lynx | maildrop monotone monotone-devel mutt p5-net- | libidn pidgin podofo proftpd prosody psi | skipfish tin VLC2 | -------------------------------------------------+------------------------- Comment (by RJVB): Could Ghostscript be patched (easily) to use that precis framework? -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:45:18 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 18:45:18 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.d8ea70a3b411b56a2b7b46d426624a31@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): success: {{{ % port -v installed rust The following ports are currently installed: rust @1.66.0_0 requested_variants='' platform='darwin 22' archs='arm64' date='2022-12-29T12:00:46-0800' rust @1.66.0_0+universal (active) requested_variants='+universal' platform='darwin 22' archs='arm64 x86_64' date='2022-12-31T10:40:31-0800' }}} It's a little weird, in that the dylibs for each arch have different names: {{{ % port contents rust | grep dylib | xargs file /opt/local/lib/librustc_driver-3b79dae3146d75e8.dylib: Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/librustc_driver-9cb14be8a64d2368.dylib: Mach-O 64-bit dynamically linked shared library arm64 /opt/local/lib/libstd-556e5c085d373926.dylib: Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/libstd-c11d89f5f427923f.dylib: Mach-O 64-bit dynamically linked shared library arm64 /opt/local/lib/libtest-127f34b82a1e8ad5.dylib: Mach-O 64-bit dynamically linked shared library arm64 /opt/local/lib/libtest-61048579174a71f6.dylib: Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/rustlib/aarch64-apple-darwin/lib/libstd- c11d89f5f427923f.dylib: Mach-O 64-bit dynamically linked shared library arm64 /opt/local/lib/rustlib/aarch64-apple-darwin/lib/libtest- 127f34b82a1e8ad5.dylib: Mach-O 64-bit dynamically linked shared library arm64 /opt/local/lib/rustlib/x86_64-apple-darwin/lib/libstd- 556e5c085d373926.dylib: Mach-O 64-bit dynamically linked shared library x86_64 /opt/local/lib/rustlib/x86_64-apple-darwin/lib/libtest- 61048579174a71f6.dylib: Mach-O 64-bit dynamically linked shared library x86_64 }}} but perhaps that is how rust works. The binaries are fat: {{{ % file /opt/local/bin/rustc /opt/local/bin/rustc: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64] /opt/local/bin/rustc (for architecture x86_64): Mach-O 64-bit executable x86_64 /opt/local/bin/rustc (for architecture arm64): Mach-O 64-bit executable arm64 }}} we'll see how it works. I'll put up a PR for the minor rust changes. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 18:49:57 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 18:49:57 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.10e20b6f60818a01de1866351777b593@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): quick hack fix, full PR in a bit once universal rust is tested. {{{ % cat ~/patch-rust-portfile-universal.diff diff --git a/lang/rust/Portfile b/lang/rust/Portfile index 41450176a4e..2e48cb7117e 100644 --- a/lang/rust/Portfile +++ b/lang/rust/Portfile @@ -132,9 +132,10 @@ if { ${os.platform} eq "darwin" && ${os.major} < 9 } { configure.args-append --disable-rpath } if { "port:jemalloc" in ${depends_lib} } { - configure.args-append --set=rust.jemalloc +# configure.args-append --set=rust.jemalloc } +muniversal.dont_diff /opt/local/lib/rustlib/manifest-rustfmt- preview triplet.add_build all triplet.add_host all }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 19:21:24 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 19:21:24 -0000 Subject: [MacPorts] #66054: ruby31 fails to build on 10.8.5: No rule to make target `all' In-Reply-To: <049.790b1660bcd8785fc5efccb6e77805c7@macports.org> References: <049.790b1660bcd8785fc5efccb6e77805c7@macports.org> Message-ID: <064.79f232f43a2461995944ac0c589c4f99@macports.org> #66054: ruby31 fails to build on 10.8.5: No rule to make target `all' ---------------------------+------------------------------------ Reporter: barracuda156 | Owner: kimuraw Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Resolution: | Keywords: mountainlion mavericks Port: ruby31 | ---------------------------+------------------------------------ Comment (by aeiouaeiouaeiouaeiouaeiouaeiou): [https://ports.macports.org/port/ruby32/details/ ruby32] is also affected by this error. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 20:46:43 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 20:46:43 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.13d4c34bb702f59ec837490ec734ee5a@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): This approach doesn't work to build universal ports using rust so far. With either version of the muniversal PortGroup, you just wind up with both of the built architectures being the host architecture. According to this: https://rust-lang.github.io/rustup/cross- compilation.html what is needed instead is to get the one install host version of rust to install the toolchain needed to support the arch you are cross-compiling to, and then tell it to build for that alternative toolchain using something like this: {{{ cargo build --target=x86_64-apple-darwin22.2.0 cargo build --target=arm64-apple-darwin22.2.0 }}} and then lips those together with the muniversal PG. SO -- step one is to get a cross-compiling version of rust/cargo working... -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 21:48:20 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 21:48:20 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.a20f93dbbee695a56f8454889c4a6f2c@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by MarcusCalhoun-Lopez): Plese forgive me if I am missing something, but aren't all of these steps already finished?\\ I have tested the universal Rust build much more thoroughly on i386 and x86_64 (as evidenced by the recently discovered bugs).\\ However, I believe the principles should be the same for arm64 and x86_64. By installing the Rust for both architectures, you get the entire toolchains for both architectures.\\ `cargo` then builds the correct binary through [https://github.com/macports/macports- ports/blob/4b71a42acbc70de82b51bdfbaff9d678858574a9/_resources/port1.0/group/rust-1.0.tcl#L731 CARGO_BUILD_TARGET]. Is there some reason to believe this strategy is not working? I am in the process of trying to install arm64/x86_64 universal build of Rust to test things out, but I am not there yet. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 22:30:21 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 22:30:21 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.cd27943e72d0671ecfc03381795de85a@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): Looking forward to it! Yes, it's not working quite as planned as yet. What you get when you try to install something universal arm64/x86_64 built with rust/cargo is the primary dylib of the finished build is just a text file saying that the two attempted dylib differed and could not be merged :> In the work folder, all the dylibs (x86_64 folder and arm64 folder) are arm64 dylibs, with nothing cross compiled. Happy to work with you more when you can get there too -- it's hard to explain and do this remotely, and will be much easier when you see it for yourself. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 22:45:13 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 22:45:13 -0000 Subject: [MacPorts] #66591: rust @1.66.0: trouble building universal arm64/x86_64 In-Reply-To: <042.d6c8b85acb14b46603652c25795d521f@macports.org> References: <042.d6c8b85acb14b46603652c25795d521f@macports.org> Message-ID: <057.ec9fdfae57e4c68c737a0a430cdeac9d@macports.org> #66591: rust @1.66.0: trouble building universal arm64/x86_64 ---------------------+--------------------------------- Reporter: kencu | Owner: MarcusCalhoun-Lopez Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: rust | ---------------------+--------------------------------- Comment (by kencu): BTW to build universal rust on an M1, I believe I have either pushed or PR'd all the fixes needed to get through to universal rust, except for the small patch in this ticket for rust. So if something fails to build, it's probably PR'd. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 23:15:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 23:15:56 -0000 Subject: [MacPorts] #66593: qt6 references file in /opt/local/bin, which do not exist In-Reply-To: <045.0ddf103b64b1a22645865b98a0f749ee@macports.org> References: <045.0ddf103b64b1a22645865b98a0f749ee@macports.org> Message-ID: <060.e3b90413f7c53d65904c6f50d906e580@macports.org> #66593: qt6 references file in /opt/local/bin, which do not exist -------------------------+-------------------- Reporter: kgarrels | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt6-qtbase | -------------------------+-------------------- Changes (by ryandesign): * port: => qt6-qtbase Comment: qt6-qtbase installs /opt/local/libexec/qt6/bin/moc. -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 23:16:48 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 23:16:48 -0000 Subject: [MacPorts] #66594: libmowgli @1.0.0: /bin/sh: CPP@: command not found Message-ID: <047.af3cc97fade2eab25bc8d427ddcb5186@macports.org> #66594: libmowgli @1.0.0: /bin/sh: CPP@: command not found ------------------------+----------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: libmowgli ------------------------+----------------------- https://build.macports.org/builders/ports- 12_arm64-builder/builds/80310/steps/install-port/logs/stdio {{{ /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found /bin/sh: CPP@: command not found make[6]: *** [mowgli_allocation_policy.dep] Error 1 make[6]: *** Waiting for unfinished jobs.... make[6]: *** [mowgli_formatter.dep] Error 1 make[6]: *** [mowgli_argstack.dep] Error 1 make[6]: *** [mowgli_error_backtrace.dep] Error 1 make[6]: *** [mowgli_alloc.dep] Error 1 make[6]: *** [mowgli_bitvector.dep] Error 1 make[6]: *** [mowgli_allocator.dep] Error 1 make[6]: *** [mowgli_dictionary.dep] Error 1 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 23:18:37 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 23:18:37 -0000 Subject: [MacPorts] #66595: tree-sitter-swift @0.3.4: Failed to run `node`: Os { code: 2, kind: NotFound, message: "No such file or directory" } Message-ID: <047.ec2f537ca67cfbdf382e8614b94f014d@macports.org> #66595: tree-sitter-swift @0.3.4: Failed to run `node`: Os { code: 2, kind: NotFound, message: "No such file or directory" } ------------------------+------------------------------- Reporter: ryandesign | Owner: amake Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: tree-sitter-swift ------------------------+------------------------------- https://build.macports.org/builders/ports- 12_arm64-builder/builds/80304/steps/install-port/logs/stdio {{{ thread 'main' panicked at 'Failed to run `node`: Os { code: 2, kind: NotFound, message: "No such file or directory" }', cli/src/generate/mod.rs:176:10 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Command failed: /opt/local/bin/tree-sitter generate Exit code: 101 }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 23:21:50 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 23:21:50 -0000 Subject: [MacPorts] #66596: py27-qscintilla-qt5 @2.11.6: Error: QScintilla 2.13.3 is being used but the Python bindings 2.11.6 are being built. Please use matching versions. Message-ID: <047.76408e264085d3718516273450036463@macports.org> #66596: py27-qscintilla-qt5 @2.11.6: Error: QScintilla 2.13.3 is being used but the Python bindings 2.11.6 are being built. Please use matching versions. ------------------------+------------------------ Reporter: ryandesign | Owner: michaelld Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.8.0 Keywords: | Port: qscintilla ------------------------+------------------------ https://build.macports.org/builders/ports- 12_arm64-builder/builds/80300/steps/install-port/logs/stdio {{{ Error: QScintilla 2.13.3 is being used but the Python bindings 2.11.6 are being built. Please use matching versions. }}} -- Ticket URL: MacPorts Ports system for macOS From noreply at macports.org Sat Dec 31 23:35:56 2022 From: noreply at macports.org (MacPorts) Date: Sat, 31 Dec 2022 23:35:56 -0000 Subject: [MacPorts] #66597: net6 @1.3.14: Undefined symbols: _libintl_bind_textdomain_codeset _libintl_bindtextdomain _libintl_dgettext _libintl_dngettext Message-ID: <047.6b6e7e09d345c97d33af0e16a901c9eb@macports.org> #66597: net6 @1.3.14: Undefined symbols: _libintl_bind_textdomain_codeset _libintl_bindtextdomain _libintl_dgettext _libintl_dngettext ------------------------+-------------------- Reporter: ryandesign | Owner: (none) Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: net6 ------------------------+-------------------- https://build.macports.org/builders/ports- 12_arm64-builder/builds/80295/steps/install-port/logs/stdio {{{ checking where the gettext function comes from... external libintl checking how to link with libintl... -lintl -Wl,-framework -Wl,CoreFoundation }}} {{{ /bin/sh ./libtool --tag=CXX --mode=link /usr/bin/clang++ -pipe -Os -std=c++11 -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch arm64 -version-info 0:0:0 -release 1.3 -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch arm64 -o libnet6.la -rpath /opt/local/lib libnet6_la-non_copyable.lo libnet6_la-gettext_package.lo libnet6_la-common.lo libnet6_la- default_accumulator.lo libnet6_la-error.lo libnet6_la-main.lo libnet6_la- serialise.lo libnet6_la-address.lo libnet6_la-socket.lo libnet6_la- encrypt.lo libnet6_la-select.lo libnet6_la-queue.lo libnet6_la-packet.lo libnet6_la-connection.lo libnet6_la-user.lo libnet6_la-object.lo libnet6_la-local.lo libnet6_la-client.lo libnet6_la-server.lo libnet6_la- host.lo -L/opt/local/lib -lsigc-2.0 -lgnutls libtool: link: /usr/bin/clang++ -dynamiclib -o .libs/libnet6-1.3.0.dylib .libs/libnet6_la-non_copyable.o .libs/libnet6_la-gettext_package.o .libs /libnet6_la-common.o .libs/libnet6_la-default_accumulator.o .libs /libnet6_la-error.o .libs/libnet6_la-main.o .libs/libnet6_la-serialise.o .libs/libnet6_la-address.o .libs/libnet6_la-socket.o .libs/libnet6_la- encrypt.o .libs/libnet6_la-select.o .libs/libnet6_la-queue.o .libs /libnet6_la-packet.o .libs/libnet6_la-connection.o .libs/libnet6_la-user.o .libs/libnet6_la-object.o .libs/libnet6_la-local.o .libs/libnet6_la- client.o .libs/libnet6_la-server.o .libs/libnet6_la-host.o -L/opt/local/lib -lsigc-2.0 -lgnutls -Os -arch arm64 -Wl,-headerpad_max_install_names -Wl,-syslibroot -Wl,/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch arm64 -install_name /opt/local/lib/libnet6-1.3.0.dylib -compatibility_version 1 -current_version 1.0 -Wl,-single_module Undefined symbols for architecture arm64: "_libintl_bind_textdomain_codeset", referenced from: net6::gettext_package::gettext_package(std::__1::basic_string, std::__1::allocator > const&, std::__1::basic_string, std::__1::allocator > const&) in libnet6_la-gettext_package.o "_libintl_bindtextdomain", referenced from: net6::gettext_package::gettext_package(std::__1::basic_string, std::__1::allocator > const&, std::__1::basic_string, std::__1::allocator > const&) in libnet6_la-gettext_package.o "_libintl_dgettext", referenced from: net6::gettext_package::gettext(char const*) const in libnet6_la- gettext_package.o "_libintl_dngettext", referenced from: net6::gettext_package::ngettext(char const*, char const*, unsigned long) const in libnet6_la-gettext_package.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) }}} Looks like configure determined that `-lintl` should be used, but it has not been used. Also, there's no dependency on any gettext ports. -- Ticket URL: MacPorts Ports system for macOS