[oi-dev] slim_source rebuild

2022-11-04 Thread Marcel Telka
Hi Andreas, I noticed we do miss the slim_source rebuild after the PR #70 (Switch to Python 3.9) merge: https://github.com/OpenIndiana/slim_source/pull/70 It was merged on 2022-09-24, but the latest (re)build of slim_source is from 2022-09-17: # pkg list -afv system/install FMRI

Re: [oi-dev] slim_source rebuild

2022-11-04 Thread Klaus Ziegler
On 11/4/22 14:24, Marcel Telka wrote: Hi Andreas, I noticed we do miss the slim_source rebuild after the PR #70 (Switch to Python 3.9) merge: https://github.com/OpenIndiana/slim_source/pull/70 It was merged on 2022-09-24, but the latest (re)build of slim_source is from 2022-09-17: # pkg lis

Re: [oi-dev] slim_source rebuild

2022-11-04 Thread Andreas Wacknitz
I have manually re-run gmake publish for it and after the next jenkins build had finished (thunderbird update) the new packages should also be available now. Regards, Andreas Am 04.11.22 um 14:24 schrieb Marcel Telka: Hi Andreas, I noticed we do miss the slim_source rebuild after the PR #70 (S

[oi-dev] strange compiler error

2022-11-04 Thread Friedrich Kink via oi-dev
Hi all, I try to compile the newest asterisk version, but I get the following linker error: /usr/gcc/7/bin/gcc -g -nostartfiles -nodefaultlibs -nostdlib -r -Wl,-b binary -o res_geolocation/pidf_lo_test.o res_geolocation/pidf_lo_test.xml ld: fatal: file binary: open failed: No such file or di

Re: [oi-dev] strange compiler error

2022-11-04 Thread Toomas Soome via oi-dev
You pass -b ( to linker) but not “binary”. Sent from my iPhone > On 4. Nov 2022, at 22:14, Friedrich Kink via oi-dev > wrote: > > Hi all, > > I try to compile the newest asterisk version, but I get the following linker > error: > > /usr/gcc/7/bin/gcc -g -nostartfiles -nodefaultlibs -nostdl

Re: [oi-dev] strange compiler error

2022-11-04 Thread Friedrich Kink via oi-dev
hmm but I understand the manpage that -b is the linker switch and binary the input format key word, which is valid see below. And even I use it like '-Wl,-b,binary` it gives the same error. objdump -i BFD header file version (GNU Binutils) 2.39 elf32-i386-sol2  (header little endian, data littl

Re: [oi-dev] strange compiler error

2022-11-04 Thread Peter Tribble
Hi, You're passing an option that's only valid for gnu ld, but the ld in use is the illumos one. Presumably you're picking up the gnu ld manual page because of the way your PATH is set, but gcc is explicitly configured to use a particular ld (and as - see the output of 'gcc -v' for how it's confi

Re: [oi-dev] strange compiler error

2022-11-04 Thread Toomas Soome via oi-dev
> On 4. Nov 2022, at 22:47, Friedrich Kink wrote: > > hmm but I understand the manpage that -b is the linker switch and binary the > input format key word, which is valid see below. And even I use it like > '-Wl,-b,binary` it gives the same error. > how about -Wl,-b -Wl,binary ? rgds, too

Re: [oi-dev] strange compiler error

2022-11-04 Thread Friedrich Kink via oi-dev
Hi, thank you very much for this explanation (also all others). Indeed I used the wrong man page. Reading the right man page it seems that this mimic is not easily transferable to Solaris/illumos. Now I need to check the intention and how this can be achieved in the Solaris/illumos world. At