On Feb 14, 2025, at 19:31, Zhenfu Shi wrote:
>
> the two tarballs under the release notes are automatically generated by
> GitHub and (I think) is what `github.tarball_from tarball` will get you.
No, those two auto-generated tarballs are what you access with
"github.tarball_from archive".
"gi
Zhenfu and Josh, thanks for explaining. Now I know what to watch out for
next time.
On Fri, Feb 14, 2025 at 6:31 PM Zhenfu Shi wrote:
> A release tarball is like a release binary file where the dev creates
> manually either with a script or by hand and uploads it to the release
> page. This pr
A release tarball is like a release binary file where the dev creates manually
either with a script or by hand and uploads it to the release page. This
project does not have one, the two tarballs under the release notes are
automatically generated by GitHub and (I think) is what `github.tarball_
This project clearly provides a Github "Releases" page with tarballs listed
under each release. What do you mean by "This project does not provide
release tarballs"? You are probably right, but I need to better under
stand the mixed message here. Thank you for your advice.
On Fri, Feb 14, 2025
On 15/2/2025 11:57, Dave Allured - NOAA Affiliate via macports-dev wrote:
I am trying to switch from "github.tarball_from tarball" to the
recommended "releases". The original "tarball" setting works fine, but
"releases" fails to download. The upstream release and my Portfile
lines are:
http
This project does not provide release tarballs. Others might, but may use non
standard file names such that you need to change distname in your portfile. For
this project, use `github.tarball_from archive`.
Zhenfu
> On Feb 15, 2025, at 11:57, Dave Allured - NOAA Affiliate via macports-dev
> w
I am trying to switch from "github.tarball_from tarball" to the recommended
"releases". The original "tarball" setting works fine, but "releases"
fails to download. The upstream release and my Portfile lines are:
https://github.com/Unidata/netcdf-c/releases/tag/v4.9.3
github.setup
Artax:~ multix$ gcc-mp-7
gcc-mp-7: fatal error: no input files
compilation terminated.
Artax:~ multix$ gcc-mp-6
gcc-mp-6: fatal error: no input files
compilation terminated.
those errors are to be expected as you didn't give gcc anything to
compile ...
Please run
> port rdeps gcc7
> sudo port install gcc7
and post what you get
Chris
On 14/02/2025 3:53 pm, Riccardo Mottola via macports-dev wrote:
Hi,
some time ago we bumped to gcc14, I remember a long discussion. I had no
issues at a first glance on my systems. MDD G4, MB i386 and MB x8
Hi,
some time ago we bumped to gcc14, I remember a long discussion. I had no
issues at a first glance on my systems. MDD G4, MB i386 and MB x86-64.
Apparently on my MacBook i386 e.g. gcc 7 works, just used it today
However, today on MacBook x86-64 I was trying out various compilers with
a st
10 matches
Mail list logo
