Re: [oi-dev] inkscape calls gcc7 and 10

2023-07-04 Thread Udo Grabowski (IMK)
On 04/07/2023 11:08, Udo Grabowski (IMK) wrote: On 04/07/2023 10:53, Marcel Telka wrote: On Tue, Jul 04, 2023 at 10:20:32AM +0200, Udo Grabowski (IMK) wrote: Hi, the story with the mixup continues, this time inkscape. Crashes, shows both gcc/7 and gcc/10 The inkscape's problems are basically

Re: [oi-dev] inkscape calls gcc7 and 10

2023-07-04 Thread Udo Grabowski (IMK)
On 04/07/2023 10:53, Marcel Telka wrote: On Tue, Jul 04, 2023 at 10:20:32AM +0200, Udo Grabowski (IMK) wrote: Hi, the story with the mixup continues, this time inkscape. Crashes, shows both gcc/7 and gcc/10 The inkscape's problems are basically these: $ ldd $(which inkscape) | egrep 'not

Re: [oi-dev] inkscape calls gcc7 and 10

2023-07-04 Thread Udo Grabowski (IMK)
On 04/07/2023 10:20, Udo Grabowski (IMK) wrote: Hi, the story with the mixup continues, this time inkscape. Crashes, shows both gcc/7 and gcc/10 But trying to fix this with LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 /usr/bin/inkscape still crashes somewhere in gcc, so possible other indirect

Re: [oi-dev] inkscape calls gcc7 and 10

2023-07-04 Thread Marcel Telka
On Tue, Jul 04, 2023 at 10:20:32AM +0200, Udo Grabowski (IMK) wrote: > Hi, > the story with the mixup continues, this time inkscape. > Crashes, shows both gcc/7 and gcc/10 The inkscape's problems are basically these: $ ldd $(which inkscape) | egrep 'not found|gcc' libstdc++.so.6 =>

[oi-dev] inkscape calls gcc7 and 10

2023-07-04 Thread Udo Grabowski (IMK)
Hi, the story with the mixup continues, this time inkscape. Crashes, shows both gcc/7 and gcc/10 But trying to fix this with LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 /usr/bin/inkscape still crashes somewhere in gcc, so possible other indirect calls: (dbx) run Running: inkscape (process id 9798)