From: David Marchand <david.marchand@6wind.com>
To: Mats Liljegren <liljegren.mats2@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Error building using 1.6.0r1
Date: Fri, 28 Feb 2014 09:11:45 +0100 [thread overview]
Message-ID: <CALwxeUvLSjtSCcTo67P4x0X5yaeLvR19rKtxwo4PKMMakxxF1Q@mail.gmail.com> (raw)
In-Reply-To: <CA+xJJ18cBxsmD=UC2uE_Hw_7fE9LmKdu+ViUJ_hVqYJ1m4w4cQ@mail.gmail.com>
Hello Mats,
I reproduced the problem (and another one).
I will send two patches in a few minutes, can you try them ?
Thank you.
--
David Marchand
On Thu, Feb 27, 2014 at 3:08 PM, Mats Liljegren
<liljegren.mats2@gmail.com>wrote:
> I run a 64-bit host building for 32-bit DPDK, which fails with:
>
> dpdk/i686-default-linuxapp-gcc$ make
> == Build scripts
> == Build scripts/testhost
> == Build lib
> == Build lib/librte_eal
> == Build lib/librte_eal/common
> == Build lib/librte_eal/linuxapp
> == Build lib/librte_eal/linuxapp/igb_uio
> Building modules, stage 2.
> MODPOST 1 modules
> == Build lib/librte_eal/linuxapp/eal
> CC eal.o
> In file included from
> /home/lwrt/build/dpdk/lib/librte_eal/linuxapp/eal/eal.c:55:0:
> /home/lwrt/build/dpdk/lib/librte_eal/linuxapp/eal/eal.c: In function
> 'eal_parse_base_virtaddr':
>
> /home/lwrt/build/dpdk/i686-default-linuxapp-gcc/include/rte_common.h:133:22:
> error: cast from pointer to integer of different size
> [-Werror=pointer-to-int-cast]
> RTE_PTR_ALIGN_FLOOR((typeof(ptr))RTE_PTR_ADD(ptr, (align) - 1), align)
> ^
>
> /home/lwrt/build/dpdk/i686-default-linuxapp-gcc/include/rte_common.h:115:10:
> note: in definition of macro 'RTE_PTR_ALIGN_FLOOR'
> (typeof(ptr))rte_align_floor_int((uintptr_t)ptr, align)
> ^
> /home/lwrt/build/dpdk/lib/librte_eal/linuxapp/eal/eal.c:566:9: note:
> in expansion of macro 'RTE_PTR_ALIGN_CEIL'
> addr = RTE_PTR_ALIGN_CEIL(addr, RTE_PGSIZE_2M);
> ^
>
> /home/lwrt/build/dpdk/i686-default-linuxapp-gcc/include/rte_common.h:133:22:
> error: cast from pointer to integer of different size
> [-Werror=pointer-to-int-cast]
> RTE_PTR_ALIGN_FLOOR((typeof(ptr))RTE_PTR_ADD(ptr, (align) - 1), align)
> ^
>
> /home/lwrt/build/dpdk/i686-default-linuxapp-gcc/include/rte_common.h:115:46:
> note: in definition of macro 'RTE_PTR_ALIGN_FLOOR'
> (typeof(ptr))rte_align_floor_int((uintptr_t)ptr, align)
> ^
> /home/lwrt/build/dpdk/lib/librte_eal/linuxapp/eal/eal.c:566:9: note:
> in expansion of macro 'RTE_PTR_ALIGN_CEIL'
> addr = RTE_PTR_ALIGN_CEIL(addr, RTE_PGSIZE_2M);
> ^
> cc1: all warnings being treated as errors
> make[6]: *** [eal.o] Error 1
> make[5]: *** [eal] Error 2
> make[4]: *** [linuxapp] Error 2
> make[3]: *** [librte_eal] Error 2
> make[2]: *** [lib] Error 2
> make[1]: *** [all] Error 2
> make: *** [all] Error 2
>
> Is this a known problem?
>
> Best regards
> Mats Liljegren
>
next prev parent reply other threads:[~2014-02-28 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 14:08 Mats Liljegren
2014-02-28 8:11 ` David Marchand [this message]
2014-02-28 8:47 ` Mats Liljegren
2014-02-28 10:20 ` Mats Liljegren
2014-03-06 11:16 ` Mats Liljegren
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=CALwxeUvLSjtSCcTo67P4x0X5yaeLvR19rKtxwo4PKMMakxxF1Q@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=liljegren.mats2@gmail.com \
/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).