Bug report: p11-kit build failure on Solaris 11.4

Sad Clouds cryintothebluesky at gmail.com
Mon Nov 2 13:26:43 UTC 2020


Which is exactly what I've done. I took the time to identify the issue
and contacted the maintainers about a potential fix. It is unfortunate
that platforms like Github prevent you from submitting bug reports,
unless you explicitly sign up for their social media account. There are
valid reasons why people may not want to do that, e.g. I'm not
interested in Github, I have no use for it and I don't want to be
receiving spam about their products and services. Same goes for other
open source collaboration platforms, that eventually get sold to large
commercial entities like Microsoft. Not because they generate much
revenue, but because of the millions of users registered on that
platform. They use your registration details as a commercial asset.
Thanks, but I think I'll pass on that opportunity.

I had a very simple agenda, submit a quick bug report and then get on
with my daily life. If you don't like my approach (and maybe people
don't even care about Solaris any more), then please ignore this and my
other emails.

Cheers.

On Mon, 2 Nov 2020 12:56:10 +0100
Stef Walter <swalter at redhat.com> wrote:

> Open Source is powered by folks getting involved ... but perhaps with
> some luck someone else will choose to do these (registration) tasks
> for you.
> 
> Fingers crossed,
> 
> Stef
> 
> On 02.11.20 12:25, Sad Clouds wrote:
> > Hello, as you've already included the relevant mailing list in your
> > reply, I'm hoping someone there will make a note of the issue.
> > 
> > I've tried to submit a bug on Github, unfortunately it doesn't
> > allow me to do that unless I go through a registration process,
> > which is not something that I want to do, there are too many of
> > them - Github, Gitlab, Bugzilla, etc.
> > 
> > On Mon, 2 Nov 2020 11:11:07 +0100
> > Stef Walter <swalter at redhat.com> wrote:
> > 
> >> Hi Sad Clouds,
> >>
> >> Thanks for the email. I would suggest sending this email to the
> >> p11-glue at lists.freedesktop.org mailing list, as described here:
> >>
> >> https://p11-glue.github.io/p11-glue/p11-kit.html
> >>
> >> Or you can file a issue or pull request in github:
> >>
> >> https://github.com/p11-glue/p11-kit/issues
> >>
> >> Cheers,
> >>
> >> Stef
> >>
> >> On Sun, Nov 1, 2020 at 4:16 PM Sad Clouds
> >> <cryintothebluesky at gmail.com> wrote:
> >>
> >>> There are some issues with -std=gnu99 in CFLAGS and defining
> >>> _XOPEN_SOURCE macro
> >>>
> >>> This line needs removal in common/compat.c
> >>>
> >>> /*
> >>>  * This is needed to expose pthread_mutexattr_settype and
> >>> PTHREAD_MUTEX_DEFAULT
> >>>  * on older pthreads implementations
> >>>  */
> >>> #define _XOPEN_SOURCE 700
> >>>
> >>> as it results in the following error:
> >>>
> >>>   CC       common/compat.lo
> >>> In file included from /usr/include/sys/types.h:12,
> >>>                  from common/compat.h:40,
> >>>                  from common/compat.c:43:
> >>> /opt/gcc-10.2.0-sparc64/lib/gcc/sparc64-sun-solaris2.11/10.2.0/include-fixed/sys/feature_tests.h:
> >>> 363:2: error: #error "Compiler or options invalid for pre-UNIX 03
> >>> X/Open applications  and pre-2001 POSIX applications"
> >>>   363 | #error "Compiler or options invalid for pre-UNIX 03 X/Open
> >>> applications \
> >>>       |  ^~~~~
> >>> *** [common/compat.lo] Error code 1
> >>>
> >>> bmake[2]: stopped in
> >>> /opt/pkgbuild/objects/security/p11-kit/work/p11-kit-0.23.21
> >>> 1 error
> >>>
> >>>
> >>
> >> -- 
> >> Stef Walter (he / his)
> >> Linux Engineering
> >> Red Hat
> > 
> 
> 
> -- 
> Stef Walter (he / his)
> Linux Engineering
> Red Hat
> 


More information about the p11-glue mailing list