Re: LLVM exit code 139 building git master on Xubuntu 22.04

2023-10-20 Thread Eike Rathke
Hi David,

On Thursday, 2023-10-19 19:35:37 +0100, David Gerard wrote:

> So rather than file a bug and wait, I first tried a newer version of
> clang, and clang-15 worked. Hooray!

Smells somewhat like one of these
https://github.com/llvm/llvm-project/issues/62362
https://github.com/llvm/llvm-project/issues/55567
https://github.com/llvm/llvm-project/issues/57142

  Eike

-- 
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A


signature.asc
Description: PGP signature


Re: LLVM exit code 139 building git master on Xubuntu 22.04

2023-10-19 Thread David Gerard
On Thu, 19 Oct 2023 at 07:26, Stephan Bergmann  wrote:
> On 10/18/23 23:08, David Gerard wrote:

> > I just tried again from a completely fresh git clone, and it's still
> > happening. Any ideas? Is there anything in the new C++20 conf that's
> > too new for llvm 14.0.0 Ubuntu version?

> Smells like a bug in that particular version of Clang.  I'd follow the
> printed instructions to report it, either directly upstream at LLVM or
> (presumably better) at Ubuntu first.


So rather than file a bug and wait, I first tried a newer version of
clang, and clang-15 worked. Hooray!

Here's what I did:

# Become root

sudo -s

# install clang-15

apt remove llvm-14 clang-14 libclang-cpp14 libclang1-14
apt autoremove
apt install clang-15 llvm-15 libclang-cpp15 libclang1-15

# put its binaries in the path - no, there doesn't seem to be a more elegant way

cd /usr/lib/llvm-15/bin
for f in *; do rm -f /usr/bin/$f; ln -s ../lib/llvm-15/bin/$f /usr/bin/$f; done

and then get out of root and ./autogen.sh


- d.


Re: LLVM exit code 139 building git master on Xubuntu 22.04

2023-10-19 Thread Stephan Bergmann

On 10/18/23 23:08, David Gerard wrote:

I just tried again from a completely fresh git clone, and it's still
happening. Any ideas? Is there anything in the new C++20 conf that's
too new for llvm 14.0.0 Ubuntu version?


Smells like a bug in that particular version of Clang.  I'd follow the 
printed instructions to report it, either directly upstream at LLVM or 
(presumably better) at Ubuntu first.




Re: LLVM exit code 139 building git master on Xubuntu 22.04

2023-10-18 Thread David Gerard
On Tue, 17 Oct 2023 at 21:33, David Gerard  wrote:

> I pulled from git master today to build LO and got LLVM exit code 139
> - an error code I can't find the meaning of, but it's apparently an
> internal error.

I just tried again from a completely fresh git clone, and it's still
happening. Any ideas? Is there anything in the new C++20 conf that's
too new for llvm 14.0.0 Ubuntu version?


- d.


LLVM exit code 139 building git master on Xubuntu 22.04

2023-10-17 Thread David Gerard
I pulled from git master today to build LO and got LLVM exit code 139
- an error code I can't find the meaning of, but it's apparently an
internal error.

The build ends like this, even after a make clean (I've cut the stack dump):

...
[CXX] sal/osl/unx/tempfile.cxx
[CXX] sal/osl/unx/thread.cxx
[CXX] sal/osl/unx/time.cxx
[CXX] sal/osl/unx/uunxapi.cxx
[CXX] sal/osl/unx/system.cxx
PLEASE submit a bug report to
https://github.com/llvm/llvm-project/issues/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0.Program arguments: /usr/bin/c++ -DBOOST_ERROR_CODE_HEADER_ONLY
-DBOOST_SYSTEM_NO_DEPRECATED -DCPPU_ENV=gcc3 -DLINUX -DNDEBUG
-DOSL_DEBUG_LEVEL=0 -DUNIX -DUNX -DX86_64 -D_PTHREADS -D_REENTRANT
-DSAL_DLLIMPLEMENTATION -DRTL_OS=\"Linux\" -DRTL_ARCH=\"X86_64\"
-DSRCDIR=\"/home/fun/libreoffice\" -DCOND_LIB_SAL_TEXTENC
-DSYSTEM_ZLIB -DZLIB_CONST -fvisibility=hidden -Wall
-Wno-missing-braces -Wendif-labels -Wextra -Wundef -Wunreachable-code
-Wshadow -Wunused-macros -Wembedded-directive -finput-charset=UTF-8
-fmessage-length=0 -fno-common -pipe -fstack-protector-strong
-Wdeprecated-copy-dtor -Wimplicit-fallthrough
-Wunused-exception-parameter -Wrange-loop-analysis
-fvisibility-inlines-hidden -fPIC -Wshadow -Woverloaded-virtual
-std=c++20 -pthread -O2 -fexceptions -DLIBO_INTERNAL_ONLY -c
/home/fun/libreoffice/sal/osl/all/debugbase.cxx -o
/home/fun/libreoffice/workdir/CxxObject/sal/osl/all/debugbase.o -MMD
-MT /home/fun/libreoffice/workdir/CxxObject/sal/osl/all/debugbase.o
-MP -MF /home/fun/libreoffice/workdir/Dep/CxxObject/sal/osl/all/debugbase.d_
-I/home/fun/libreoffice/workdir/UnpackedTarball/dtoa/include/
-I/home/fun/libreoffice/workdir/UnpackedTarball/dragonbox/include/
-I/home/fun/libreoffice/include
-I/usr/lib/jvm/java-17-openjdk-amd64/include
-I/usr/lib/jvm/java-17-openjdk-amd64/include/linux
-I/home/fun/libreoffice/config_host -I/home/fun/libreoffice/sal/inc
-fcolor-diagnostics
1./home/fun/libreoffice/sal/osl/all/debugbase.cxx:52:8: current
parser token ';'
2./home/fun/libreoffice/sal/osl/all/debugbase.cxx:30:1: parsing
namespace '(anonymous)'
3./home/fun/libreoffice/sal/osl/all/debugbase.cxx:33:1: parsing
function body '(anonymous namespace)::StaticDebugBaseAddressFilter'
4./home/fun/libreoffice/sal/osl/all/debugbase.cxx:33:1: in
compound statement ('{}')
Stack dump without symbol names (ensure you have llvm-symbolizer in
your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point
to it):

[...]

clang: error: clang frontend command failed with exit code 139 (use -v
to see invocation)
Ubuntu clang version 14.0.0-1ubuntu1.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin


I don't see everyone else complaining about this, so I expect it's
something special in my setup. Does anyone have any idea?


- thanks, David.