There are multiple tickets on M4. There is a fix in the works. Yours
seems like the same thing. Please see PR
https://github.com/macports/macports-ports/pull/22984 .
On Thu, Mar 14, 2024 at 7:16 PM Larry Stone
wrote:
> This seems like an Xcode issue more than MacPorts but since MacPorts is
Following Ryan's suggestion, I am working on an update which should remove
the mozjs102 dependency, and enable gjs and glade for Sonoma. Please try
the portfile from PR https://github.com/macports/macports-ports/pull/22974 .
On Thu, Mar 7, 2024 at 5:22 PM Lukas Oberhuber wrote:
> i was never
On Thu, Mar 7, 2024 at 5:22 PM Lukas Oberhuber wrote:
> i was never able to get gjs to work (at least when included in GIMP. It
> did compile, at least when I last tried (which was at least a year ago).
>
> On Thu, 7 Mar 2024 at 12:23, Ryan Schmidt wrote:
>
>> On Mar 6, 2024, at 06:13, Gregory
urself. That is precisely what `sudo
> port select gcc` is there for
>
> On 02/03/2024 4:43 am, Dave Allured - NOAA Affiliate via macports-users
> wrote:
> > Yes, that is it. Macports implementation decided to decorate the name
> > of the executable. There is no naked
Yes, that is it. Macports implementation decided to decorate the name of
the executable. There is no naked "gfortran". It is gfortran-mp-12,
gfortran-mp-13, etc. This way you can have multiple versions installed
side by side, if you wish. For convenience, I usually sym link "gfortran"
to the
Thanks, Joshua. Also, Pavel, your project might do better to simply use
standard Macports in sub shells as your Macports library manager, rather
than accessing mirrors directly. This will take care of many issues for
you, such as updates, dependencies, and mirror changes, as well as what
Joshua
Use one of the several mirror sites for pre-built binary distributions.
Look under section "Archives" here:
https://trac.macports.org/wiki/Mirrors
Because each home page is huge, I find it convenient to postfix the package
name for use in a browser, e.g.:
Yes, the linker in CLT 15.0 is also affected. I believe it is exactly the
same linker as the one in Xcode 15.0.
On Sat, Oct 7, 2023 at 9:46 AM Jim Secan wrote:
> A related question - I install and use only the CLI toolkit for Xcode, not
> the entire Xcode package. Does this linker problem
On Fri, Oct 6, 2023 at 4:08 PM Henning Hraban Ramm wrote:
> Am 07.10.23 um 00:00 schrieb Riccardo Mottola via macports-users:
> > Hi,
> >
> > as I opened this bug report some months ago, at a certain point meld
> > stopped working properly on Mac Quartz
> > https://trac.macports.org/ticket/67169
Maxim, thanks. Yours is the third report of compile or link problems
related to Command Line Tools 15.0, released only two days ago, that I have
seen. I do not know what to make of that error message. I have not heard
of "xcodebuild -version" failing when Xcode was actually installed. Other
There is a Macports FAQ on checksum errors. It would be helpful if you
would figure out whether this is a stealth update, or something else.
On Sat, Aug 5, 2023 at 12:38 PM wrote:
> I'm getting a checksum error on tree-sitter-go-mod:
>
> ---> Verifying checksums for tree-sitter-go-mod
>
Please read about checksum failures and when to build from source, in the
Macports FAQ. I would guess that you experienced either an intermittent
server outage, or a stealth update. You can self diagnose this by trying a
manual download with curl. Examine the result file.
Macports is designed
Raf, I can not directly answer your question about the download URL.
Recent work added a new codeberg portgroup to make this simpler. I suggest
you see what was done in the portfiles for other recent codeberg ports:
smake, star, cdrtools. There are also a few older codeberg ports to
examine,
There is a new upstream version just released today, that advertises to fix
your new compile errors. I suggest file a port update ticket. My guess is
that #60772 is stale and the old problem was already solved.
On Wed, Apr 26, 2023 at 12:51 PM wrote:
> I see a related trac ticket from 3
Stealth update. Read about that in the Macports FAQ. Please file a trac
ticket on this port.
This one looks legitimate. Looking around their github site, they were
working on their automated release system. It spat out two releases with
the same dist file name, several weeks apart.
If you
So *that's* what I was missing. Ouch.
On Mon, Feb 13, 2023 at 1:54 PM Clemens Lang wrote:
> Hi again,
>
> On Mon, Feb 13, 2023 at 07:43:43PM +0100, Clemens Lang wrote:
>
> > On Sun, Feb 12, 2023 at 01:53:20PM -0500, Dave Allured - NOAA Affiliate
> via macports-users
Nope. That's a dual python310/311 ticket. Same issue for both.
On Sun, Feb 12, 2023 at 1:47 PM chilli.names...@gmail.com <
chilli.names...@gmail.com> wrote:
> Nope. That's python311. I'm looking for an open python310 build fail
> ticket, which is whatever
>
> this
>
I looked at the Audacity website, https://www.audacityteam.org . It looks
like Audacity is in robust current maintenance, sources are available, and
legacy and modern Mac OS versions are supported through Ventura and
Intel/M1/M2. The current release is 3.2.4, almost two years ahead of the
Also, the TeXShop upstream developer just now agreed to start using
suffixes rather than stealth updates. So disregard my suggestion to write
to them.
On Fri, Sep 16, 2022 at 9:07 AM Dave Allured - NOAA Affiliate <
dave.allu...@noaa.gov> wrote:
> The upstream developer said they intend to
The upstream developer said they intend to release TeXShop 5.03 later
today. So port maintainers might as well wait for that, before portfile
repair.
On Fri, Sep 16, 2022 at 7:30 AM Dave Allured - NOAA Affiliate <
dave.allu...@noaa.gov> wrote:
> Stealth upgrade detected. This means the
Stealth upgrade detected. This means the TeXShop developers changed their
published source code file without changing the file name. Version 5.02
was published on September 2. Checksums in the Macports portfile were last
fixed on September 5. Then the upstream developers changed the source
I like ncftp for command line use. It includes command line utilities for
recursive remote directory listing, and recursive bulk downloading.
On Wed, Aug 24, 2022 at 12:30 PM André-John Mas
wrote:
> If you already know the destination path, then scp would be the way to go,
> otherwise sftp. I
On Mon, Apr 4, 2022 at 5:26 PM Ryan Schmidt wrote:
> On Apr 4, 2022, at 14:25, Dave Allured - NOAA Affiliate wrote:
> > On Sun, Apr 3, 2022 at 4:23 PM Ryan Schmidt wrote:
> >> On Apr 1, 2022, at 13:09, Artemio González López wrote:
> >>
> >> > After executing “port diagnose” in my 2020 13”
On Sun, Apr 3, 2022 at 4:23 PM Ryan Schmidt wrote:
> On Apr 1, 2022, at 13:09, Artemio González López wrote:
>
> > After executing “port diagnose” in my 2020 13” MacBook Pro running the
> latest version of the operating system (Monterrey 12.1.3, I believe) I got
> the following output:
> >
> >
On Github:
https://github.com/macports/macports-ports/tree/master/_resources/port1.0/group
In your local install:
/opt/local/var/macports/sources/
rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group
On Fri, Apr 1, 2022 at 9:36 PM Peter West wrote:
> Where are the
I don't know about true binary editors. However it seems like you might be
trying to bridge older vs. newer character sets, like me. For this I have
found the following approaches to be better than your "vi" experience. If
your purpose is more general than character set translation, then
Petr, you originally said you wanted cantera. All this trouble with
sundials2, atlas, etc. is because the cantera port at v2.3.0 is more than
three years out of date. Many versions have passed. Sundials2 (v2.7.0)
and atlas should both be considered obsolete ports as far as modern
machines are
*Sigh*. The ports.macports.org site has not been getting updates since Feb
20. See recent threads. Yes, this is *usually* reliable. Not this month.
On Sat, Mar 13, 2021 at 8:23 AM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> > Having heard that python39 is the only one (so
in a rush to move to IMv7. I use sips often in
> conjuction with imagemagick, the sips color profile and metadata handling
> is excellent
>
> Sean
>
>
> On Friday, September 25, 2020, Dave Allured - NOAA Affiliate via
> macports-users wrote:
>
>> Sean,
>&
Sean,
"possible to invoke the previous parser" -- Do you mean that some of the
IMv6 commands can be used with IMv7, simply by prefixing with "magick" and
a space? I wonder how many of the many ports depending on IMv6 could be
satisfied with this simple patch.
On Fri, Sep 25, 2020 at 12:32 PM
On Tue, Jul 21, 2020 at 8:20 AM dan d. wrote:
> I used this suggested work around:
>
> port clean --work mplayer-devel>
>
> After getting additional error messages with ways to fix the issue, I
> finally saw what looks like a typical install of mplayer-devel.
>
> However it doesn't show up in
Port mplayer-devel is from the same code base, but it is based on recent
SVN versions, not release versions. Therefore it is more recently updated
than version 1.4. Will mplayer-devel be satisfactory for your application?
On Sat, Jul 18, 2020 at 5:58 AM dan d. wrote:
>
> The currentt version
Christoph, consider using Apple Terminal (in Utilities), rather than
Xterm. This does not directly answer your question, but it was definitely
an improvement for me. After I started using Mac OS a long time ago, I
discovered Apple Terminal as an alternative to Xterm. As a native Apple
Greg, I am repeatedly building port NCARG with a simple recipe, as part of
my local testing regime. I never use any special options related to a
clang version or OpenMP. This seems to work fine every time. I am on a
Mac Pro, currently running OS 10.14.6 Mojave and Xcode 11.3. This also
worked
On Wed, Jan 22, 2020 at 12:34 AM Bill Cole <
macportsusers-20171...@billmail.scconsult.com> wrote:
> On 21 Jan 2020, at 18:11, Artemio González López via macports-users
> wrote:
>
> > Bitdefender has flagged two files from the db48 MacPorts port
> > installed in my Mac, namely
> >
> >
My apologies, I am unfamiliar with Bitdefender. Did you mean that you
reported this to bitdefender.com, or added to an exception list on your
local system?
On Wed, Jan 22, 2020 at 11:11 AM Artemio González López via macports-users <
macports-users@lists.macports.org> wrote:
> Thank you all. I
On Tue, Jan 21, 2020 at 6:12 PM Christopher Chavez
wrote:
> On 1/21/2020 7:03 PM, Christopher Chavez wrote:
> > VirusTotal doesn't report anything for
> > http://packages.macports.org/db48/db48-4.8.30_4.darwin_17.x86_64.tbz2:
> > see
> >
>
On Sat, Jan 18, 2020 at 3:20 AM Mojca Miklavec wrote:
> On Fri, 17 Jan 2020 at 23:44, Christopher Jones
> wrote:
> > On 17 Jan 2020, at 10:36 pm, Dave Allured - NOAA Affiliate via
> macports-users wrote:
> >
> > Chris, thanks for the quick reply. You are
time option.
>
> Chris
>
> On 17 Jan 2020, at 9:33 pm, Dave Allured - NOAA Affiliate via
> macports-users wrote:
>
> I am on a corporate network with ports installed normally in /opt/local,
> controlled by system admins. Users do not have any write access into
> syste
I am on a corporate network with ports installed normally in /opt/local,
controlled by system admins. Users do not have any write access into
system directories. I would like to use a local portfile repository in
user space, as described in Macports guide 4.6.
How can I test ports in the local
On Fri, Nov 29, 2019 at 7:41 PM Ryan Schmidt
wrote:
> On Nov 29, 2019, at 10:01, Dave Allured wrote:
>
> > I have the longer user home prefix because my institutional network
> policy prevents all write access to /opt/anything.
>
> I still think the suggestion I made in
>
Thanks to Ryan, Bill, Richard for all the advice about stack and maximum
command length. I think the relation to stack size is something I picked
up from a Linux discussion. Apparently some versions of Linux work this
way.
I have the longer user home prefix because my institutional network
I am trying to solve "Argument list too long" when building gdal@3.0.1_3
from source under macports. The command that fails is "libtool clang++",
used here to combine a large number of objects into a single library
libgdal.la. The trac ticket is https://trac.macports.org/ticket/59510 .
I found
On Sun, Aug 4, 2019 at 8:14 PM Christopher Chavez
wrote:
>
> > On Aug 4, 2019, at 7:32 PM, Richard L. Hamilton
> wrote:
> >
> > That got me to wondering if there's a way to get the equivalent of "port
> list all", all on one page, over the web; for someone that might not want to
> > install
Hi Dave et al.
>
> I repeated the curl. The md5 checks: the xfer was completed correctly.
>
> Advice welcome!
>
> Sam
>
>
> On Apr 13, 2019, at 5:57 PM, Dave Allured - NOAA Affiliate via
> macports-users wrote:
>
> I think you all are overlooking this report
I think you all are overlooking this report from a few days back. The
requested "curl" test passed on Sam's machine. This strongly indicates a
problem within Sam's Macports software, NOT a network problem. Excerpt:
On Mon, Apr 8, 2019 at 10:54 AM Lee Finn wrote:
> Hi Chris ... Thanks for
On Thu, Apr 4, 2019 at 11:27 AM Bill Cole <
macportsusers-20171...@billmail.scconsult.com> wrote:
> On 4 Apr 2019, at 12:45, Dave Allured - NOAA Affiliate via
> macports-users wrote:
>
> > On Wed, Apr 3, 2019 at 11:11 PM Mojca Miklavec
> > wrote:
> >
> &g
On Thu, Apr 4, 2019 at 2:23 PM Ryan Schmidt wrote:
>
> On Apr 4, 2019, at 11:45, Dave Allured wrote:
>
> > That *is* relevant. My Mac is behind an institutional firewall, so this
> might be aggravating the problem. Also I am not able to duplicate the
> headers as Ryan showed using curl -I, not
On Wed, Apr 3, 2019 at 11:11 PM Mojca Miklavec wrote:
> On Thu, 4 Apr 2019 at 06:34, wrote:
> >
> > it's wierd. i'm seeing the same Content-Encoding header
> > but curl doesn't un-gzip the download for me. neither
> > /usr/bin/curl (7.43.0) nor /opt/local/bin/curl (7.64.1).
> > neither does
On Tue, Apr 2, 2019 at 10:38 PM Ryan Schmidt
wrote:
> On Apr 2, 2019, at 23:21, Bill Cole wrote:
>
> > On 2 Apr 2019, at 23:45, Dave Allured - NOAA Affiliate wrote:
> >
> > [snip]
> >>
> >> I have never before seen this sort of fradulent behavior, silent
> unpacking,
> >> from either an http
I'm new to this mailing list. I ran into a strange problem tonight with
one of the mirror sites. While running a port update on a different port,
I got a checksum error on this distfile:
http://mirror.facebook.net/gnu/groff/groff-1.22.4.tar.gz
I tried manually downloading using curl, from both
51 matches
Mail list logo
