[BUG] sim/module: ar output the warning message from ci

Open
#2,754 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
build-system

Research direction

Start by rerunning the linked CI job for the sim/module configuration and inspect the build output around the ar warning. Trace which build step invokes ar with no archive members, then verify that the configuration builds without the warning and usage text.

Written by the indexing model from the issue text.

Description

Description / Steps to reproduce the issue

please see https://github.com/apache/nuttx-apps/actions/runs/11381576984/job/31663367795?pr=2737:

====================================================================================
Configuration/Tool: sim/module
2024-10-17 10:15:50
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Building NuttX...
ar: no archive members specified
usage:  ar -d [-TLsv] archive file ...
	ar -m [-TLsv] archive file ...
	ar -m [-abiTLsv] position archive file ...
	ar -p [-TLsv] archive [file ...]
	ar -q [-cTLsv] archive file ...
	ar -r [-cuTLsv] archive file ...
	ar -r [-abciuTLsv] position archive file ...
	ar -t [-TLsv] archive [file ...]
	ar -x [-ouTLsv] archive [file ...]
  Normalize sim/module
On which OS does this issue occur?

[OS: Linux]

What is the version of your OS?

Ubuntu

NuttX Version

master

Issue Architecture

[Arch: all]

Issue Area

[Area: Binfmt]

Verification
  • I have verified before submitting the report.
Dominant language
C
Stars
465
Forks
782
Avg merge
3d 11h
Merged PRs (30d)
44

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/nuttx-apps

All issues in apache/nuttx-apps

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.