Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6374] New: gnutls package broken if linux cryptodev module selected
Date: Wed, 10 Jul 2013 17:42:37 +0000 (UTC)	[thread overview]
Message-ID: <bug-6374-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6374

           Summary: gnutls package broken if linux cryptodev module
                    selected
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: rjbarnet at rockwellcollins.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


With the latest version of buildroot from the git repository as of 7/10/2013 -
2013.08-git-00452-gcca5538 - if the BR2_PACKAGE_CRYPTODEV_LINUX is selected the
package BR2_PACKAGE_GNUTLS will not build successfully as the following error
occurs during a build:

  CC     ocsp_output.lo
  CCLD   libgnutls_x509.la
make[4]: Leaving directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/lib/x509'
Making all in accelerated
make[4]: Entering directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/lib/accelerated'
make[5]: Entering directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/lib/accelerated'
  CC     accelerated.lo
  CC     cryptodev.lo
  CC     cryptodev-gcm.lo
cryptodev.c:359:3: error: unknown field 'reset' specified in initializer
cryptodev.c:361:1: warning: initialization from incompatible pointer type
[enabled by default]
cryptodev.c:361:1: warning: (near initialization for 'mac_struct.fast')
[enabled by default]
cryptodev.c:410:3: error: unknown field 'reset' specified in initializer
make[5]: *** [cryptodev.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
make[5]: Leaving directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/lib/accelerated'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/lib/accelerated'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1'
make: ***
[/home/rjbarnet/projects/eicu/selinux/buildroot/output/build/gnutls-3.2.1/.stamp_built]
Error 2

This worked with the 2013.05 official release version of buildroot.

Thanks,
-Ryan

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-07-10 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 17:42 bugzilla at busybox.net [this message]
2013-07-19  0:40 ` [Buildroot] [Bug 6374] gnutls package broken if linux cryptodev module selected bugzilla at busybox.net

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-all 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=bug-6374-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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