public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: rebecca@bluestop.org
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Jian Wang <jian.j.wang@intel.com>, Ting Ye <ting.ye@intel.com>
Subject: Build error in CryptoPkg on FreeBSD
Date: Tue, 4 Jun 2019 19:52:22 -0600	[thread overview]
Message-ID: <d5aca3be-44e1-8108-6184-92752f510560@bluestop.org> (raw)

I know it's not an officially supported platform, but a recent update
has broken building CryptoPkg under FreeBSD. I've tried building both
Armada80x0McBin (shown below) and OvmfPkg, and both fail.


"/usr/local/bin/aarch64-unknown-freebsd13.0-gcc" 
@/home/bcran/workspace/Build/Armada80x0McBin-AARCH64/DEBUG_GCC5/AARCH64/CryptoPkg/Library/OpensslLib/OpensslLib/OUTPUT/cc_resp.txt 
-c -o
/home/bcran/workspace/Build/Armada80x0McBin-AARCH64/DEBUG_GCC5/AARCH64/CryptoPkg/Library/OpensslLib/OpensslLib/OUTPUT/openssl/crypto/rand/rand_unix.obj 
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/crypto/rand/rand_unix.c
In file included from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/crypto/rand/rand_unix.c:26:0:
/usr/include/sys/sysctl.h:1120:25: error: unknown type name 'u_int'
 int sysctl(const int *, u_int, void *, size_t *, const void *, size_t);
                         ^~~~~
In file included from /usr/include/sys/signal.h:53:0,
                 from /usr/include/sys/param.h:139,
                 from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/crypto/rand/rand_unix.c:27:
/usr/include/sys/_timespec.h:42:18: error: conflicting types for 'time_t'
 typedef __time_t time_t;
                  ^~~~~~
In file included from
/home/bcran/workspace/edk2/CryptoPkg/Library/Include/limits.h:9:0,
                 from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/e_os.h:13,
                 from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/crypto/rand/rand_unix.c:13:
/home/bcran/workspace/edk2/CryptoPkg/Library/Include/CrtLibSupport.h:88:24:
note: previous declaration of 'time_t' was here
 typedef INT32          time_t;
                        ^~~~~~
In file included from /usr/include/sys/param.h:139:0,
                 from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/crypto/rand/rand_unix.c:27:
/usr/include/sys/signal.h:56:18: error: conflicting types for 'size_t'
 typedef __size_t size_t;
                  ^~~~~~
In file included from
/home/bcran/workspace/edk2/CryptoPkg/Library/Include/limits.h:9:0,
                 from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/e_os.h:13,
                 from
/home/bcran/workspace/edk2/CryptoPkg/Library/OpensslLib/openssl/crypto/rand/rand_unix.c:13:
/home/bcran/workspace/edk2/CryptoPkg/Library/Include/CrtLibSupport.h:86:24:
note: previous declaration of 'size_t' was here
 typedef UINTN          size_t;
                        ^~~~~~
make: *** [GNUmakefile:24956:
/home/bcran/workspace/Build/Armada80x0McBin-AARCH64/DEBUG_GCC5/AARCH64/CryptoPkg/Library/OpensslLib/OpensslLib/OUTPUT/openssl/crypto/rand/rand_unix.obj]
Error 1


-- 
Rebecca Cran


             reply	other threads:[~2019-06-05  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  1:52 rebecca [this message]
2019-06-05  5:35 ` [edk2-devel] Build error in CryptoPkg on FreeBSD Wang, Jian J

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=d5aca3be-44e1-8108-6184-92752f510560@bluestop.org \
    --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