Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failure if PPP and mbed trace or L3IPInterface is enabled #12486

Closed
kivaisan opened this issue Feb 21, 2020 · 2 comments · Fixed by #12506
Closed

Build failure if PPP and mbed trace or L3IPInterface is enabled #12486

kivaisan opened this issue Feb 21, 2020 · 2 comments · Fixed by #12506

Comments

@kivaisan
Copy link
Contributor

kivaisan commented Feb 21, 2020

Description of defect

Build will fail if mbed traces and PPP, or L3IPInterface is enabled due to missing intergration to #11942

Cellular trace needs to be fixed to use SocketAddress:
https://github.com/ARMmbed/mbed-os/blob/master/features/cellular/framework/AT/AT_CellularContext.cpp#L988

L3IPInterface: This method needs to be changed to use new SocketAddress:
https://github.com/ARMmbed/mbed-os/blob/master/features/netsocket/L3IPInterface.cpp#L42-L54

Target(s) affected by this defect ?

All

Toolchain(s) (name and version) displaying this defect ?

All

What version of Mbed-os are you using (tag or sha) ?

mbed-os-99.99.99 (8f1bf96)

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Mbed-cli

How is this defect reproduced ?

Enable mbed-trace and PPP, or L3IPInterface

cc: @michalpasztamobica

@ciarmcom
Copy link
Member

Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2556

@ciarmcom
Copy link
Member

ciarmcom commented Oct 2, 2020

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2220

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants