Hi Vasile,

Are you refering to the problem with the Linux compiler I posted?

I found this page about the subject you mentioned (never heard of it btw): 
https://wiki.musl-libc.org/building-llvm.html

It does not seem an easy task to do.

About the Linux compiler. I had compiled it with gcc version 9.0 due to an 
upgrade of my Ubuntu system which cause the issue with GLIBC. The problem was 
solved by recompiling it with gcc version 7. The server of Kyle should work 
with that version but for some reason the new compiler is not picked up so the 
build (the validation of the samples and the compile of all samples) keeps 
failing.

I am working with Matt to move the validation, compilation and release to the 
server of Matt that also hosts the website since the compiler works there 
without a problem and it seems more logical to have it all on the same server.

In parallel I am doing the validation and compilation of all samples after a 
check-in on GitHub using GitHub actions. In fact it does the same validation 
that the server of Kyle does when you commit someting to GitHub. GitHub sends 
me a nice e-mail about this validation task if it is succesfull or not , 
screenshot below. And since I was playing with GitHub actions I also managed to 
create a JAL Linux compiler and a JAL MAC compiler both only 64-bit. I also 
created a 64-bit Windows compiler but the strange thing is that I cannot run it 
on my Windows 10 system (access denied) even when all rights are set correctly. 
Internet does not provide a solution for this specific problem.  A complete 
mystery to me. For now I will still create the compilers locally but if needed 
they can also be build using GitHub Actions by a press of a button (I do not 
create the compilers after a push to GitHub, only to be started by hand).

[cid:af156801-2e71-4ae6-bb8c-3f5ff30118b7]


________________________________
Van: [email protected] <[email protected]> namens vasi vasi 
<[email protected]>
Verzonden: dinsdag 30 mei 2023 15:39
Aan: [email protected] <[email protected]>
Onderwerp: Re: [jallib] [jallib build] buildbot failure in jallib on jallib-bee

If the binary files of the compiler are distributed anyway, for Linux what 
about compiling it in a musl/llvm based system (as gcc in Linux can't compile 
static if math lib from libc is required) as a truly static binary?

On Sun, May 28, 2023 at 4:09 PM <[email protected]<mailto:[email protected]>> 
wrote:
Hi guys,

This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this 
build
Build Source Stamp: HEAD
Blamelist:

BUILD FAILED: failed package
Logs are attached.

sincerely,
 -The Buildbot

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:jallib%[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/E1q3G8t-00089o-Fj%40casadeyork.com.


--
Vasi

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CABsDq%3D-DD%2BNeLtQPXB7%3DUOAZHKi9wcnXn3jBUypCa9aj9h4Msw%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D-DD%2BNeLtQPXB7%3DUOAZHKi9wcnXn3jBUypCa9aj9h4Msw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D68AC2D4081307062909E64B9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Reply via email to