From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: WIP: julia: update to 1.7.1.
Date: Thu, 13 Oct 2022 15:23:25 +0200 [thread overview]
Message-ID: <20221013132325.vhcNWUcS2zjh6WGcQdF4TaAzWDUMCHNcFEfaAO_BtcE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35270@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
There's a closed pull request on the void-packages repository
WIP: julia: update to 1.7.1.
https://github.com/void-linux/void-packages/pull/35270
Description:
Still need to finish building/testing locally and separating out into logical commits, but I thought I should put this here to make sure there's no duplicated effort since I'm not sure when I'll finish this up, and libblastrampoline was annoying to get to build correctly.
[ci skip] for building llvm.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-10-13 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35270@inbox.vuxu.org>
2022-01-30 8:23 ` kwshi
2022-01-30 13:45 ` Piraty
2022-01-30 17:33 ` Piraty
2022-01-30 17:50 ` Piraty
2022-01-30 18:41 ` non-Jedi
2022-02-04 2:36 ` non-Jedi
2022-02-04 2:38 ` [PR PATCH] [Updated] " non-Jedi
2022-02-05 4:51 ` non-Jedi
2022-02-05 4:53 ` non-Jedi
2022-02-05 4:55 ` non-Jedi
2022-02-05 4:57 ` non-Jedi
2022-02-05 4:57 ` non-Jedi
2022-02-05 7:03 ` kwshi
2022-02-22 19:06 ` [PR REVIEW] " ahesford
2022-02-22 19:06 ` ahesford
2022-02-22 19:06 ` ahesford
2022-02-25 5:52 ` Rabioli
2022-04-21 21:04 ` Piraty
2022-07-06 22:31 ` Piraty
2022-10-05 2:13 ` github-actions
2022-10-13 13:23 ` Piraty
2022-10-13 13:23 ` Piraty [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221013132325.vhcNWUcS2zjh6WGcQdF4TaAzWDUMCHNcFEfaAO_BtcE@z \
--to=piraty@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).