[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gforth] [bug #55675] Cannot build from git commit d505b1be
From: |
Bernd Paysan |
Subject: |
Re: [Bug-gforth] [bug #55675] Cannot build from git commit d505b1be |
Date: |
Fri, 08 Feb 2019 18:50:19 +0100 |
Am Freitag, 8. Februar 2019, 18:42:37 CET schrieb Reuben Thomas:
> Follow-up Comment #5, bug #55675 (project gforth):
>
> I still cannot build from git. I get a different error each time, perhaps
> because you use make -j (so do I by default, but I removed my custom
> MAKEFLAGS from the environment before trying to build gforth!).
>
> For example I get:
>
> libtool: link: gcc -Wl,--export-dynamic -pthread .libs/liblibmain.o -o
> .libs/libgforth-itc /home/rrt/Desktop/gforth/engine/.libs/libgforth-itc.so
> -pthread -Wl,-rpath -Wl,/home/rrt/.local/lib/x86_64-linux-gnu
> make[1]: Leaving directory '/home/rrt/Desktop/gforth/engine'
> ln -s -f engine/libgforth-itc libgforth-itc
> chcon -t unconfined_execmem_exec_t libgforth-itc || true
> chcon: can't apply partial context to unlabelled file 'libgforth-itc'
Any || true rule simply can't fail. If it fails, true gets its chance.
Therefore, if your build fails, just send me the entire log. It's a lot of
stuff, and I know what's a real error and what not.
Note that I have a gitlab-ee continuous integration setup that builds every
time I check in something, and it works. I also have a travic-ci setup on
github, and that fails on their old Ubuntu every time, because the make they
use has a bug I just don't want to work around.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o id: kQusJzA;address@hidden(dQ*
https://net2o.de/
signature.asc
Description: This is a digitally signed message part.
Re: [Bug-gforth] [bug #55675] Cannot build from git commit d505b1be, Bernd Paysan, 2019/02/08