Bug#978040: [Pkg-pascal-devel] Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2022-01-13 Thread Abou Al Montacir
Hi Paul, On Sun, 2022-01-02 at 17:06 +0100, Paul Gevers wrote: > I'm not sure your allowed to run dpkg-reconfigure on a trigger as that > requires admin interaction. That sounds weird. As an admin I wouldn't > expect my configuration to get updated (when installing an "unrelated" > package). 

Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2022-01-02 Thread Paul Gevers
Hi, On 02-01-2022 14:29, Abou Al Montacir wrote: If you check on a porter box for ARM or power PC, you will find only arm or ppc related ifdefs. So it works for all architectures, but not multiarch. Isn't multiarch only properly working on some combinations anyways? E.g. i386 can be

Bug#978040: [Pkg-pascal-devel] Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2022-01-02 Thread Abou Al Montacir
Hi Paul, On Sun, 2022-01-02 at 08:19 +0100, Paul Gevers wrote: > Hi, > > On 29-12-2021 23:47, Abou Al Montacir wrote: > > So it should work correctly on all targets. > > Does this work correctly on all multiarch architectures too? I inspected > only my own installation and there it only has

Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2022-01-01 Thread Paul Gevers
Hi, On 29-12-2021 23:47, Abou Al Montacir wrote: So it should work correctly on all targets. Does this work correctly on all multiarch architectures too? I inspected only my own installation and there it only has cpui386 and cpux86_64. However, it is true that if a new gcc version is

Bug#978040: [Pkg-pascal-devel] Bug#978040: Bug#978040: Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2021-12-29 Thread Abou Al Montacir
I have just checked on a new installation of FPC 3.2.2 on ARM and it looks like the detection of GCC library path is correct. # path to the gcclib #ifdef cpuaarch64 -Fl/usr/lib/gcc/arm-linux-gnueabi/11 #endif The code, internally uses; gcc --print-libgcc-file-name So it should work correctly on

Bug#978040: [Pkg-pascal-devel] Bug#978040: Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2020-12-29 Thread Abou Al Montacir
Hi Matija, On Tue, 2020-12-29 at 18:50 +0100, Matija Nalis wrote: > As for hard coding, those paths are ALREADY hard-coded at least forIntel > architectures (amd64, i386), for example: ... > That hard-coded paths seem to already be auto-generated on build somehow. The file names

Bug#978040: [Pkg-pascal-devel] Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2020-12-29 Thread Matija Nalis
On Tue, Dec 29, 2020 at 03:20:14PM +0100, Abou Al Montacir wrote: > Why gcc10 and not gcc8? I assume you are using sid.But then we need a way to > avoid hard coding the gcc version. Yes, gcc-10 is what build-essential installs on Sid (and Bullseye), which is what I am using there (as I'm trying

Bug#978040: [Pkg-pascal-devel] Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2020-12-29 Thread Abou Al Montacir
Why gcc10 and not gcc8? I assume you are using sid.But then we need a way to avoid hard coding the gcc version. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part

Bug#978040: Warning: (9034) "crtbeginS.o" not found (on non-intel architectures)

2020-12-24 Thread Matija Nalis
Package: fpc Version: 3.2.0+dfsg-8 Severity: normal X-Debbugs-Cc: mnalis-debian...@voyager.hr Dear Maintainer, * What led up to the situation? trying to compile my source throws warnings (which subsequently causes failure to build due to "-Sewnh". I can of course remove that option and