On Donnerstag, 20. Mai 2021, 08:11:31 CEST Mathias Homann wrote:

Hi guys,

I am having an extremely weird problem with two packages that I'm building.

I have been packaging the apps in question for years now, but now I'm trying to get OBS to produce a working rpm on Tumbleweed and it just DOES NOT WORK.

The build on OBS succeeds just fine, but if I install the package the application crashes on start.

The packages for Leap 15.2 and 15.3 built from the same spec and sources work just fine, even to the point that right now I'm using the 15.3 package on tumbleweed.

and here is the REALLY weird part: If I take the whole content of the package directory from my obs project and copy it to rpmbuild/SOURCES on a Tumbleweed machine,. and build it locally with rpmbuild, the package I get works just fine. If I build locally with "obs build" the resulting binary crashes.

I have NO idea where to begin looking - all I know right now is that a backtrace in gdb wasn't really helpful either... the crash happens somewhere in libstdc++ o.0

Anyone got any ideas? the packages in question are in home:lemmy04:snowglobe/ phoenix-firestorm-lgpl and home:lemmy04:phoenix-firestorm-release ...

beside package differences of the build environment, one of the first things would be the most likely different compile and linker flags. Check the prjconf for the Optflags and try to apply them in your local build to verify if it crashes then as well. -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer

Citeren Mathias Homann :

Hi guys,

I am having an extremely weird problem with two packages that I'm building.

I have been packaging the apps in question for years now, but now I'm trying to get OBS to produce a working rpm on Tumbleweed and it just DOES NOT WORK.

The build on OBS succeeds just fine, but if I install the package the application crashes on start.

The packages for Leap 15.2 and 15.3 built from the same spec and sources work just fine, even to the point that right now I'm using the 15.3 package on tumbleweed.

and here is the REALLY weird part: If I take the whole content of the package directory from my obs project and copy it to rpmbuild/SOURCES on a Tumbleweed machine,. and build it locally with rpmbuild, the package I get works just fine. If I build locally with "obs build" the resulting binary crashes.

I have NO idea where to begin looking - all I know right now is that a backtrace in gdb wasn't really helpful either... the crash happens somewhere in libstdc++ o.0

Anyone got any ideas? the packages in question are in home:lemmy04:snowglobe/ phoenix-firestorm-lgpl and home:lemmy04:phoenix-firestorm-release ...

You seem to be using an outdated package for libidn in your OBS build. Unless you've configured you TW system to prefer/use all the packages you build in OBS, this might cause differences between the packages used for build/test and when installed.

Am Donnerstag, 20. Mai 2021, 08:28:44 CEST schrieb John Paul Adrian Glaubitz:

On 5/20/21 8:17 AM, Adrian Schröter wrote:

...

...

Anyone got any ideas? the packages in question are in home:lemmy04:snowglobe/ phoenix-firestorm-lgpl and home:lemmy04:phoenix-firestorm-release ...> beside package differences of the build environment, one of the first things would be the most likely different compile and linker flags.

Check the prjconf for the Optflags and try to apply them in your local build to verify if it crashes then as well.

I would probably try to turn off LTO as a first guess:

%define _lto_cflags %{nil}

would that go in the spec file or in the project config? cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

Am Donnerstag, 20. Mai 2021, 08:28:02 CEST schrieb Arjen de Korte:

Citeren Mathias Homann :

...

Hi guys,

I am having an extremely weird problem with two packages that I'm building.

I have been packaging the apps in question for years now, but now I'm trying to get OBS to produce a working rpm on Tumbleweed and it just DOES NOT WORK.

The build on OBS succeeds just fine, but if I install the package the application crashes on start.

The packages for Leap 15.2 and 15.3 built from the same spec and sources work just fine, even to the point that right now I'm using the 15.3 package on tumbleweed.

and here is the REALLY weird part: If I take the whole content of the package directory from my obs project and copy it to rpmbuild/SOURCES on a Tumbleweed machine,. and build it locally with rpmbuild, the package I get works just fine. If I build locally with "obs build" the resulting binary crashes.

I have NO idea where to begin looking - all I know right now is that a backtrace in gdb wasn't really helpful either... the crash happens somewhere in libstdc++ o.0

Anyone got any ideas? the packages in question are in home:lemmy04:snowglobe/ phoenix-firestorm-lgpl and home:lemmy04:phoenix-firestorm-release ... You seem to be using an outdated package for libidn in your OBS build. Unless you've configured you TW system to prefer/use all the packages you build in OBS, this might cause differences between the packages used for build/test and when installed.

I have to - some of the prebuilt binaries that are part of the finished product rely on that old version 0.o besides, that was one of the first things I tried - building with the normal libidn and ignoring the dependency issues produces the same crashes. cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

On 5/20/21 8:32 AM, Mathias Homann wrote:

...

I would probably try to turn off LTO as a first guess:

%define _lto_cflags %{nil}

would that go in the spec file or in the project config?

Just at the top of the spec file. Adrian

Hi, On Thu, May 20, 2021 at 5:50 PM Mathias Homann wrote:

Am Donnerstag, 20. Mai 2021, 08:28:44 CEST schrieb John Paul Adrian Glaubitz:

...

I would probably try to turn off LTO as a first guess:

%define _lto_cflags %{nil}

Adrian

that did it - thank you!

now I'd like to know what that LTO stuff is - to me LTO is a type of backup tape...

https://gcc.gnu.org/wiki/LinkTimeOptimization ismail