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

FS#1454 - argp-standalone: option ARGP_NO_ERRS is not honoured #6418

Open
openwrt-bot opened this issue Mar 24, 2018 · 0 comments
Open

FS#1454 - argp-standalone: option ARGP_NO_ERRS is not honoured #6418

openwrt-bot opened this issue Mar 24, 2018 · 0 comments
Labels
core packages pull request/issue for core (in-tree) packages flyspray

Comments

@openwrt-bot
Copy link

tru7:

Symptom: error message is written for invalid option even with ARGP_NO_ERRS set in function argp_parse

Verified on ar71xx / mips_24kc / wndr3700 and mpc85xx / powerpc_8540 / tl-wdr4900
OpenWrt / LEDE trunk OpenWrt SNAPSHOT, r6548-8e1065d681

Found a problem when working with a software project where the LEDE / OpenWrt binary issues an error message for an invalid option when starting the binary while the debian / ubuntu linux version does not. I tracked it down to the fact that it must be a bug in the argp-standalone library of OpenWrt / LEDE where the option ARGP_NO_ERRS in function argp_parse is not honoured.

To reproduce I wrote a little demo program which works fine on debian and ubuntu but shows the invalid behaviour on OpenWrt / LEDE.

The demo program is hosted on https://github.com/tru7/argp-demo where I have also provided a feed named Makefile.lede to build the package on OpenWrt / LEDE.

I have no skills in coding and absolutely no skills in debugging, so this is about all I can do about this.

@aparcar aparcar added the core packages pull request/issue for core (in-tree) packages label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core packages pull request/issue for core (in-tree) packages flyspray
Projects
None yet
Development

No branches or pull requests

2 participants