Hi,
I lost the original thread about libgcc revbumps and good measures for
revbumping ... but it seems that all cross-compilers are now broken
and need a revbump.
Maybe we should put some comments on top of isl. From what I remember
in the past isl would also often just work with newer gcc and fo
> That took only took 10secs and a bit of time for the buildbots to build.
Respectfully, I would disagree with this assessment.
We are forcing everyone who builds from source (like myself) to rebuild a
fairly large port.
For those of us with somewhat less than state of the art machines, this can
Hi,
> On 5 May 2019, at 7:57 pm, Marcus Calhoun-Lopez wrote:
>
> I am sorry for not being clear.
>
>> If the builds differ, then it needs rev-bumpig.
>
> The build is immaterial.
> The files that get installed are the important thing.
>
> If you look through https://packages.macports.org/libg
I am sorry for not being clear.
> If the builds differ, then it needs rev-bumpig.
The build is immaterial.
The files that get installed are the important thing.
If you look through https://packages.macports.org/libgcc9/,
libgcc9-9.1.0_0.darwin_18.x86_64.tbz2 and
libgcc9-9.1.0_1.darwin_18.x86_64.
Hi,
Currently the MacPorts website & documentation need some improvements to both
design and content. To that end, I started work on a redesigned website for
macports-www and macports-guide which you can find here:
https://constantin-p.github.io/macports-site/
The scope of this proposal is to i
>
>
>
>
> From what I understand from the stackoverflow post you're right that
> cmxpchg16b will not give a consistent view of the 16 bytes of memory
> across multiple NUMA nodes. However, maybe two 4 byte values right next
> to each other would be sufficient for your use case and could then be
> c
> On 5 May 2019, at 4:48 pm, Marcus Calhoun-Lopez wrote:
>
> Greetings.
>
> With different versions of isl, the builds of libgccX may be slightly
> different, but if what is installed is *exactly* the same (see, e.g.,
> https://packages.macports.org/libgcc9/).
If the builds differ, then it
Greetings.
With different versions of isl, the builds of libgccX may be slightly
different, but if what is installed is *exactly* the same (see, e.g.,
https://packages.macports.org/libgcc9/).
Since there is no change in what is installed, then rev bumping is not
necessary.
-Marcus
> On May 5,
Hi,
GccX and libgccX are built from exactly the same source, more or less the same
build. Only differ in what gets installed. Both therefore depend on isl, so
both needed rev bumping when it was updated.
Chris
> On 5 May 2019, at 4:08 pm, Marcus Calhoun-Lopez wrote:
>
> Please forgive my ig
Please forgive my ignorance, but could you please say a little more about the
rationale behind this change?
Please correct me if I am wrong, but I thought that only the GCC compilers (not
the libraries) depended on isl.
When the isl library name changes, must the compiler also be updated, as seem
Hi :)
I noticed that the main website today (or yesterday) got a little
refresh with the bright blue tone being more prominent. Is someone
already working on updating the guide's stylesheet to also reflect that
change? If not, then I'd also like to update the typography there
(larger font size wit
11 matches
Mail list logo
