DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dirk-Holger Lenz <dirk.lenz@ng4t.com>
To: dev@dpdk.org
Subject: [dpdk-dev] g++ applications doesn't compile anymore when dpdk header files are included
Date: Wed, 01 Jul 2015 18:34:00 +0200	[thread overview]
Message-ID: <55941678.3000806@ng4t.com> (raw)

Hello,
the g++ complains the following problems when rte_xxxx.h header files 
are included:
   ....x86_64-native-linuxapp-gcc/include/rte_common.h:95:59: warning: 
invalid conversion from ‘void*’ to ‘rte_mempool_objhdr*’.... this 
appears in multiple flavours
   -as a workaround the '-fpermissive' option of the g++ may be used but 
that's not nice.
....x86_64-native-linuxapp-gcc/include/generic/rte_cpuflags.h:50:6: 
error: use of enum ‘rte_cpu_flag_t’ without previous declaration enum 
rte_cpu_flag_t;
   ....x86_64-native-linuxapp-gcc/include/generic/rte_cpuflags.h:55:6: 
error: use of enum ‘cpu_register_t’ without previous declaration
  enum cpu_register_t;
....x86_64-native-linuxapp-gcc/include/generic/rte_cpuflags.h:104:31: 
error: use of enum ‘rte_cpu_flag_t’ without previous declaration 
rte_cpu_get_flag_enabled(enum rte_cpu_flag_t feature);
   -as a workaround the file 
'lib/librte_eal/common/include/generic/rte_cpuflags.h' may be modified:
   remove or uncomment the following lines:
    line 50: //enum rte_cpu_flag_t;
    line 55: //enum cpu_register_t;
    lines 103/104: //static inline int
                           //rte_cpu_get_flag_enabled(enum 
rte_cpu_flag_t feature);

Best regards
Dirk
-- 
Dirk-Holger Lenz
+49 157 848 09099
dirk.lenz@ng4t.com
	ng 4 T 	Telecommunication
Technology
Testing
Tools


ng4T GmbH
Siemensdamm 50
13629 Berlin
Germany
www.ng4t.com <http://www.ng4t.com/>
+49 30 65218530

Berlin-Charlottenburg, HRB 123546
CEO Dr. Andreas Kallmann

             reply	other threads:[~2015-07-01 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 16:34 Dirk-Holger Lenz [this message]
2015-07-01 17:32 ` Sanford, Robert

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=55941678.3000806@ng4t.com \
    --to=dirk.lenz@ng4t.com \
    --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).