DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 37] DPAA / FSLMC do not compile on the musl libc
Date: Thu, 03 May 2018 10:54:05 +0000	[thread overview]
Message-ID: <bug-37-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=37

            Bug ID: 37
           Summary: DPAA / FSLMC do not compile on the musl libc
           Product: DPDK
           Version: 18.05
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: dpdk@stormmq.com
  Target Milestone: ---

Various files assume that `error.h` is part of the c library (it isn't). These
files include at least:-

```
drivers/bus/fslmc/qbman/include/compat.h
drivers/bus/dpaa/include/compat.h
bus/dpaa/base/fman/netcfg_layer.c
```

`drivers/bus/fslmc/qbman/include/compat.h` needs `#include <stdio.h>`

`drivers/bus/dpaa/include/fsl_qman.h` assumes uses the privately namespaced
`__WORDSIZE` is defined.

There are probably other defects.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-05-03 10:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-37-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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;
as well as URLs for NNTP newsgroup(s).