Seems normal, as long as you build a ethernet netif (I suppose there is a typo 
problem, and you talk about ethernetif.c) use ARP. The solution is just to not 
build this file. But even with LWIP_ARP=1, I'm not sure this file can be 
builded.
 
 
 
  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : [EMAIL PROTECTED] 
Web Site : http://www.hymatom.fr <http://www.hymatom.fr/>  
====================================
P Avant d'imprimer, penser à l'environnement
 

        -----Message d'origine-----
        De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de embed9527
        Envoyé : lundi 26 novembre 2007 10:49
        À : [email protected]
        Objet : [lwip-users] Can lwip1.3.0 support LWIP_ARP = 0 ?
        
        
         
         
        Hi,
         
            In my test, when I set LWIP_ARP = 0 and ARP_QUEUEING = 0, 
lwip\netif\enthernet.c has a lot of errors like:
         
            ETHARP_HWADDR_LEN does not define;
            struct eth_hdr does not define;
            ......
         
            So, I want to ask that I set LWIP_ARP = 0 is right? if it is right, 
what can I do?
            
        Thanks.

<<image001.jpg>>

<<image002.jpg>>

BEGIN:VCARD
VERSION:2.1
N:BERNON;Frédéric;;M.
FN:Frédéric BERNON
ORG:HYMATOM SA;Recherche et Développement
TITLE:Chef de projet informatique
TEL;WORK;VOICE:04-67-87-61-10
TEL;WORK;FAX:04-67-70-85-44
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;23;Zone Industrielle=0D=0A175 rue de Massacan;VENDARGUES;;34740;FRANCE;
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:23=0D=0AZone Industrielle=0D=0A175 rue de Massacan=0D=0AVENDARGUES 34740=0D=
=0AFrance
URL;WORK:http://www.hymatom.fr
ROLE:Chef de projet informatique
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20020404T083210Z
END:VCARD
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to