Hello,
I am currently applying the lwIP TCP/IP stack to the S32K314 product and encountered a "multiple definition" error, so I am leaving a question.
When I add the TCP/IP stack to the peripherals and build, the following error occurs:
However, when I remove the multiple definition issue using linker options, the build succeeds as follows:
Using linker options to bypass the multiple definition issue does not seem like a proper solution, so I want to address the root cause of the problem.
Thank you.
Thank you!
Hi @malove
In the actual example, fsdata.c is not included for the compilation. only fs.c included.
You can exclude the fsdata.c from build to avoid fsdata.o generation. which will help you to solve the problem without modifying the linker options.
Thanks,
Sathish.
Thank you @PavelL
Hello @malove ,
I see your point now. Please check this:
- Re: linker error:multiple definition of `_start' - NXP Community
- Solved: Multiple definitions of
functions 'isprintf' etc - NXP Community - Link Order: Using Multiple Definitions with ARM GNU Linker and Eclipse.
Best regards,
Pavel
Hello @PavelL
What I want to clarify is that I am not trying to have two static IP addresses.
Instead, I am trying to resolve the issue where certain elements in the fsdata.c source file are being defined multiple times.
However, this file is not something I wrote myself; it is part of the TCP/IP stack that I am using as is. I am not sure how to modify or resolve this issue.
Hello @malove ,
what is your goal? To have two static IP addresses? As far as I know, dual stack IPv4 and IPv6 should work on lwip. However, I did a web search but I didn't find a solution - all questions like this one mapping multiple * IP addresses to one Ethernet interface (LWIP) - NXP Community stayed unanswered or the solution didn't work. So, it looks like not feasible.
As David already replied to here S32K3 Lwip iperf test issue - NXP Community, LWIP is an open source and we do not have resources to support.
Best regards,
Pavel