From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
Rebecca Cran <rebecca@bluestop.org>
Cc: Ting Ye <ting.ye@intel.com>, Jian Wang <jian.j.wang@intel.com>
Subject: Re: [edk2-devel] [PATCH] CryptoPkg: add issetugid declaration to fix openssl build on FreeBSD
Date: Sat, 20 Apr 2019 13:30:17 +0200 [thread overview]
Message-ID: <CAKv+Gu99RbtfTk7mix_eHuQBxftJgM_QvKXRO1iukriWZg603w@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu-YeMjpuKCCMLDwypbqB5MMNc6g1zcmdvqeWqV2fAydbQ@mail.gmail.com>
On Sat, 20 Apr 2019 at 13:28, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> On Sat, 20 Apr 2019 at 00:38, rebecca via Groups.Io
> <rebecca=bluestop.org@groups.io> wrote:
> >
> > When building OpenSSL, the OpenBSD/FreeBSD/DFBSD code in crypto/uid.c
> > calls issetugid(). Add the declaration of this function to
> > CrtLibSupport.h to avoid the need to patch the openssl code on these
> > platforms.
> >
> > Signed-off-by: Rebecca Cran <rebecca@bluestop.org>
>
> This is slightly odd. The host architecture shouldn't really matter,
> and so if we end up calling different code in UEFI when built on *BSD,
> there is differently something wrong. Or am I missing something?
>
*definitely
> > ---
> > CryptoPkg/Library/Include/CrtLibSupport.h | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/CryptoPkg/Library/Include/CrtLibSupport.h b/CryptoPkg/Library/Include/CrtLibSupport.h
> > index a241fb96fb..b05c5d908c 100644
> > --- a/CryptoPkg/Library/Include/CrtLibSupport.h
> > +++ b/CryptoPkg/Library/Include/CrtLibSupport.h
> > @@ -155,6 +155,7 @@ uid_t getuid (void);
> > uid_t geteuid (void);
> > gid_t getgid (void);
> > gid_t getegid (void);
> > +int issetugid (void);
> > void qsort (void *, size_t, size_t, int (*)(const void *, const void *));
> > char *getenv (const char *);
> > char *secure_getenv (const char *);
> > --
> > 2.21.0
> >
> >
> > ------------
> > Groups.io Links: You receive all messages sent to this group.
> >
> > View/Reply Online (#39338): https://edk2.groups.io/g/devel/message/39338
> > Mute This Topic: https://groups.io/mt/31250604/1761188
> > Group Owner: devel+owner@edk2.groups.io
> > Unsubscribe: https://edk2.groups.io/g/devel/unsub [ard.biesheuvel@linaro.org]
> > ------------
> >
next prev parent reply other threads:[~2019-04-20 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 22:38 [PATCH] CryptoPkg: add issetugid declaration to fix openssl build on FreeBSD rebecca
2019-04-20 11:28 ` [edk2-devel] " Ard Biesheuvel
2019-04-20 11:30 ` Ard Biesheuvel [this message]
2019-04-20 17:18 ` rebecca
2019-04-22 13:46 ` Wang, Jian J
2019-04-24 9:25 ` Philippe Mathieu-Daudé
2019-04-24 19:17 ` Laszlo Ersek
2019-04-24 19:29 ` rebecca
2019-04-24 19:36 ` rebecca
2019-04-25 1:06 ` Wang, Jian J
2019-04-26 13:55 ` rebecca
2019-04-26 13:56 ` Andrew Fish
2019-04-26 14:07 ` rebecca
2019-04-26 20:19 ` Laszlo Ersek
2019-04-27 0:06 ` rebecca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKv+Gu99RbtfTk7mix_eHuQBxftJgM_QvKXRO1iukriWZg603w@mail.gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox