Fwd: Re: github

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Fwd: Re: github

Robert Hölzl
I did macOS test with the help of vagrant.

You can download any OS from their platform:
https://app.vagrantup.com/boxes/search

and its very convenient as it automates the generation and integration
(ssh connection, shared folders, ...).
And as it is a VM it is 100% macOS (no emulation with its quirks)

robert

Am 21.04.2020 um 16:25 schrieb Federico Bianchi:

> How about Darling?
>
> https://darlinghq.org/
>
> Regards
> -- Federico Bianchi
> polo 4 @ SID UniPI.IT
>
> On Tue, 21 Apr 2020, Christian Jullien wrote:
>
>>> Are there macOS images?  Because if so, I could probably look at
>>> adding Mach-O support on a rainy day.  Without access to MacOS
>>> that's going to be difficult :)
>>
>> Wouah! I'd love to have it.
>>
>> -----Original Message-----
>> From: Tinycc-devel
>> [mailto:tinycc-devel-bounces+eligis=[hidden email]] On Behalf
>> Of Michael Matz
>> Sent: Tuesday, April 21, 2020 16:05
>> To: [hidden email]
>> Subject: Re: [Tinycc-devel] github
>>
>> Hello,
>>
>> On Sun, 19 Apr 2020, Giovanni Mascellani wrote:
>>
>>>> TinyCC is great because it supports so much configurations (3 OSes,
>>>> even
>>>> more CPU archs).
>>>>
>>>> But the downside is, that nobody can ensure that his change wont break
>>>> any of these configurations.
>>>> (Probably most of us are testing only on their own PC, which is one OS
>>>> with probably x86-64).
>>>>
>>>> How about a CI?
>>>
>>> I am not a core dev, but I set up a CI for tcc:
>>>
>>>  https://gitlab.com/giomasce/tinycc/pipelines
>>>
>>> Unfortunately it is currently broken. I believe the CI is broken, not
>>> tcc, because it wasn't broken before my last round of CI script
>>> maintenance. I'll try to fix them as soon as I have some time, but if
>>> someone wants to check them out in the meantime I won't complain.
>>
>> Yeah, I've seen the breakages, but had no bright idea, see below.
>>
>>> Currently armhf fails with "Illegal instruction", and I don't know if
>>> the problem is QEMU emulation or tcc itself, because the same commit did
>>> work before I did my last round of changes.
>>
>> Yeah, I figured something must be up with the emulator.  No way TCC
>> is generating genuinely illegal instructions :)  It would be helpful
>> if the emulator would give some hint of the instruction bytes it
>> thinks are illegal :)  (One guess of mine was that the emulator is
>> run in a mode where e.g. Neon instructions are invalid?)
>>
>>> riscv64 has a failing test, and that could be a genuine tcc bug. If
>>> so, it is probably introduced by recent "win32: long double as
>>> distinct C-type" commit. Broken test is
>>> "70_floating_point_literals", see the log[1].
>>
>> Yeah, but I don't think there's a TCC problem.  The failure in
>> riscv64 is random (i.e. changes place from test to test, when the
>> pipelines are re-triggered by unrelated changes, just browse the
>> different fails).  I've looked at one of the testcases claimed to be
>> failing and it's definitely correct code.
>>
>>> [1] https://gitlab.com/giomasce/tinycc/-/jobs/507946108
>>>
>>> As soon as I have some time, I'd like to fix these problems and
>>> eventually support Windows and macOS too. I believe this
>>> architecture with QEMU running in GitLab CI can work, but suitable
>>> Windows and macOS images have to be prepared and compilation scripts
>>> adapted. QEMU TCG emulation is slowish, but if we prepare images
>>> with a snapshot so that the VM doesn't have to go through the whole
>>> boot sequence it might be reasonable.
>>
>> Are there macOS images?  Because if so, I could probably look at
>> adding Mach-O support on a rainy day.  Without access to MacOS that's
>> going to be difficult :)
>>
>>
>> Ciao,
>> Michael.
>>
>> _______________________________________________
>> Tinycc-devel mailing list
>> [hidden email]
>> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>>
>>
>> _______________________________________________
>> Tinycc-devel mailing list
>> [hidden email]
>> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>
> _______________________________________________
> Tinycc-devel mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: github

Daniel Glöckner-2
On Wed, Apr 22, 2020 at 10:44:37AM +0200, Robert Hölzl wrote:
> I did macOS test with the help of vagrant.
>
> You can download any OS from their platform:
> https://app.vagrantup.com/boxes/search
>
> and its very convenient as it automates the generation and
> integration (ssh connection, shared folders, ...).
> And as it is a VM it is 100% macOS (no emulation with its quirks)

The thing is that the macOS license AFAIK allows the use only on Apple
hardware. There is no "official" macOS VM on Vagrant. All macOS VMs you
can find on Vagrant have been provided by users.

In another project we are using a machine provided by MacStadium, but
OSS projects need regular releases (and a logo) to quality for a free
machine. Yes, they should really consider shared hosting for projects
that don't need a dedicated machine...

Best regards,

  Daniel

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: github

Robert Hölzl

Am 22.04.2020 um 11:58 schrieb Daniel Glöckner:

> On Wed, Apr 22, 2020 at 10:44:37AM +0200, Robert Hölzl wrote:
>> I did macOS test with the help of vagrant.
>>
>> You can download any OS from their platform:
>> https://app.vagrantup.com/boxes/search
>>
>> and its very convenient as it automates the generation and
>> integration (ssh connection, shared folders, ...).
>> And as it is a VM it is 100% macOS (no emulation with its quirks)
> The thing is that the macOS license AFAIK allows the use only on Apple
> hardware. There is no "official" macOS VM on Vagrant. All macOS VMs you
> can find on Vagrant have been provided by users.
>
> In another project we are using a machine provided by MacStadium, but
> OSS projects need regular releases (and a logo) to quality for a free
> machine. Yes, they should really consider shared hosting for projects
> that don't need a dedicated machine...
>
> Best regards,
>
>    Daniel
On my current projects I use vagrant only for developing new features on
my local PC (Although I am aware that the licencing issue is problematic).
For regular testing (via CI) I use "GitHub actions" which provides legal
macOS (and Windows) boxes for free.
> _______________________________________________
> Tinycc-devel mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: github

Michael Matz-4
In reply to this post by Daniel Glöckner-2
Hello,

On Wed, 22 Apr 2020, Daniel Glöckner wrote:

>> I did macOS test with the help of vagrant.
>>
>> You can download any OS from their platform:
>> https://app.vagrantup.com/boxes/search
>>
>> and its very convenient as it automates the generation and
>> integration (ssh connection, shared folders, ...).
>> And as it is a VM it is 100% macOS (no emulation with its quirks)
>
> The thing is that the macOS license AFAIK allows the use only on Apple
> hardware. There is no "official" macOS VM on Vagrant. All macOS VMs you
> can find on Vagrant have been provided by users.
Yeah, thought so.  But darling might be a way indeed (haven't yet looked
at it, but if the low-level userspace is complete enough, and it must be
from what they claim to be able to run, it should be enough for tinycc).

(But I didn't know about the other macos possibilities either, so thanks
for the info)


Ciao,
Michael.
_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: github

Austin English-2
On Wed, Apr 22, 2020 at 11:35 AM Michael Matz <[hidden email]> wrote:
Hello,

On Wed, 22 Apr 2020, Daniel Glöckner wrote:

>> I did macOS test with the help of vagrant.
>>
>> You can download any OS from their platform:
>> https://app.vagrantup.com/boxes/search
>>
>> and its very convenient as it automates the generation and
>> integration (ssh connection, shared folders, ...).
>> And as it is a VM it is 100% macOS (no emulation with its quirks)
>
> The thing is that the macOS license AFAIK allows the use only on Apple
> hardware. There is no "official" macOS VM on Vagrant. All macOS VMs you
> can find on Vagrant have been provided by users.

Yeah, thought so.  But darling might be a way indeed (haven't yet looked
at it, but if the low-level userspace is complete enough, and it must be
from what they claim to be able to run, it should be enough for tinycc).

(But I didn't know about the other macos possibilities either, so thanks
for the info)

Travis-CI integrates with github well, and supports linux and osx (no windows though):
https://docs.travis-ci.com/user/multi-os/


--
-Austin
GPG: 267B CC1F 053F 0749 (expires 2021/02/18)

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: github

James Mills
I would go with Github Actions if it were up to me.
But write the "CI" logic in shell scripts as much as you can with the goal of being able to run what CI does locally (if the need arises, and it always does).

At our company we've had a lot of success with Github Actions and they are nicely tightly integrated right there alongside your Github Repo.

Kind regards

James

James Mills / prologic

E: [hidden email]


On Thu, Apr 23, 2020 at 8:28 AM Austin English <[hidden email]> wrote:
On Wed, Apr 22, 2020 at 11:35 AM Michael Matz <[hidden email]> wrote:
Hello,

On Wed, 22 Apr 2020, Daniel Glöckner wrote:

>> I did macOS test with the help of vagrant.
>>
>> You can download any OS from their platform:
>> https://app.vagrantup.com/boxes/search
>>
>> and its very convenient as it automates the generation and
>> integration (ssh connection, shared folders, ...).
>> And as it is a VM it is 100% macOS (no emulation with its quirks)
>
> The thing is that the macOS license AFAIK allows the use only on Apple
> hardware. There is no "official" macOS VM on Vagrant. All macOS VMs you
> can find on Vagrant have been provided by users.

Yeah, thought so.  But darling might be a way indeed (haven't yet looked
at it, but if the low-level userspace is complete enough, and it must be
from what they claim to be able to run, it should be enough for tinycc).

(But I didn't know about the other macos possibilities either, so thanks
for the info)

Travis-CI integrates with github well, and supports linux and osx (no windows though):
https://docs.travis-ci.com/user/multi-os/


--
-Austin
GPG: 267B CC1F 053F 0749 (expires 2021/02/18)
_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel