From: Nicholas Mc Guire <der.herr@hofr.at>
To: kernelnewbies@kernelnewbies.org
Subject: building .lst files for a subdirectory
Date: Wed, 20 Feb 2019 11:23:49 +0100 [thread overview]
Message-ID: <20190220102349.GA1905@osadl.at> (raw)
Hi !
Probably I´m just overlooking something obvious but trying
to build .lst files in directories that have no Makefile
is causing problems. For "normal" files its simply
$ make path/file.lst
but that seems to assume that there always is a Makefile in each
directory. For some drivers this is not the case e.g.
drivers/staging/rtlwifi/Makefile covers all the subdirectories
directly and there are no Makefiles or Kbuild files in the
respective subdirs. So building .lst fails:
hofrat@threadripper:~/git/linux-next$ make drivers/staging/rtlwifi/phydm/rtl_phydm.lst
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
scripts/Makefile.build:42: drivers/staging/rtlwifi/phydm/Makefile: No such file or directory
And not too surprising the build instructions from Documentation/kbuild/modules.txt
will not do the trick either:
hofrat@threadripper:~/git/linux-next/drivers/staging/rtlwifi/phydm$ make -C ~/git/linux-next M=$PWD rtl_phydm.lst
make: Entering directory '/home/hofrat/git/linux-next'
scripts/Makefile.build:42: /home/hofrat/git/linux-next/drivers/staging/rtlwifi/phydm/Makefile: No such file or directory
make[1]: *** No rule to make target '/home/hofrat/git/linux-next/drivers/staging/rtlwifi/phydm/Makefile'. Stop.
Makefile:1704: recipe for target 'rtl_phydm.lst' failed
make: *** [rtl_phydm.lst] Error 2
make: Leaving directory '/home/hofrat/git/linux-next'
Any hint how to build those .lst files ?
thx!
hofrat
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2019-02-20 10:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190220102349.GA1905@osadl.at \
--to=der.herr@hofr.at \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).