Re: Bug#1121530: libreoffice: Please build with -fPIE on sparc64 to fix FTBFS

John Paul Adrian Glaubitz <[email protected]>
Newsgroups gmane.linux.debian.ports.sparc,gmane.linux.debian.devel.openoffice
Message-ID <6b2ede231bea77a8ab6c2d3c20474557947e59dd.camel@physik.fu-berlin.de>
Hi,

On Fri, 2025-11-28 at 12:02 +0100, John Paul Adrian Glaubitz wrote:
> On Fri, 2025-11-28 at 09:46 +0100, John Paul Adrian Glaubitz wrote:
> > On Fri, 2025-11-28 at 09:34 +0100, Rene Engelhard wrote:
> > > Upstream patches related to/for lp-solve I mean:
> > > 
> > > <https://git.libreoffice.org/core/+/refs/heads/master/external/lpsolve/>
> > 
> > Yes, I'm aware of this.
> > 
> > > In any way you need to teach ccc -fPIE. But then I'd wonder why lp-solve in
> > > Debian built... That one has "just" -fPIC.
> > 
> > Please see my other mail. I said, I'm going to replace "-fpic" with "-fPIC".
> > 
> > -fpic/-fPIC is for libraries, -fpie/-fPIE for executables.
> > 
> > > See salsa.debian.org/math-team/lp-solve
> > 
> > Which confirms my theory ;-).
> 
> The attached patch replaces "-fpic" with "-fPIC" in the lp-solve build script which
> seems to be enough to fix this particular build issue on sparc64.

So, it gets beyond the previous linker problem now but fails while linking Rust code:

[LNK] ExtensionLibrary/rust_uno-example.uno.so
/usr/bin/ld: cannot find -lrust_uno: No such file or directory
collect2: error: ld returned 1 exit status
make[1]: *** [/home/glaubitz/loffice/libreoffice-26.2.0~alpha1/solenv/gbuild/LinkTarget.mk:869: /home/glaubitz/loffice/libreoffice-26.2.0~alpha1/workdir/LinkTarget/ExtensionLibrary/rust_uno-
example.uno.so] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:301: build] Error 2

I assume that this is unrelated to sparc64.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.