From: Julia Lawall <julia.lawall@inria.fr>
To: Sumitra Sharma <sumitraartsy@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, outreachy@lists.linux.dev
Subject: Re: Unable to find module location
Date: Mon, 20 Mar 2023 14:04:30 +0100 (CET) [thread overview]
Message-ID: <e13532cc-d9da-5090-7731-5d3945d7564c@inria.fr> (raw)
In-Reply-To: <20230320095314.GC126429@sumitra.com>
On Mon, 20 Mar 2023, Sumitra Sharma wrote:
> >>On Mon, 20 Mar 2023, Bagas Sanjaya wrote:
>
> > On 3/20/23 15:46, Sumitra Sharma wrote:
> > > Hi julia,
> > >
> > > This did worked.
> > >
> > > But the main issue of creating NVEC_PAZ00 a module using make menuconfig still persist.
> > >
> >
> >> Oh dear, you don't know how to use menuconfig...
> >>
> >> When you execute `make menuconfig`, you'll be presented with menu when
> >> you can choose what config you want to enable. To find the desired config
> >> (NVEC_PAZ00 in this case), press `/` and type in the config name. If
> >> found, you will see menu location for config symbols that match. Then
> >> follow the shown path.
>
> > Actually, this isn't the issue. You have to have the ARCH=arm as well.
> > Otherwise, / provides instructions, but there is no way to follow them.
>
> Yes you are correct locating the mocule in menuconfig is my issue. Do you mean 'make menuconfig ARCH=arm'.
I have never tried that order. make ARCH=arm tegra_defconfig menuconfig
should work. Maybe other options work also. Arm has a lot of specific
configurations.
julia
>
> Sorry for such a long thread. :(
>
> Regards,
> Sumitra
>
>
>
>
>
next prev parent reply other threads:[~2023-03-20 13:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 8:40 Unable to find module location Sumitra Sharma
2023-03-18 9:13 ` Deepak R Varma
2023-03-18 13:02 ` Sumitra Sharma
2023-03-18 16:08 ` Deepak R Varma
2023-03-19 8:45 ` Sumitra Sharma
2023-03-20 9:19 ` Deepak R Varma
2023-03-20 10:02 ` Sumitra Sharma
2023-03-20 10:16 ` Deepak R Varma
2023-03-20 10:21 ` Deepak R Varma
2023-03-22 4:12 ` Sumitra Sharma
2023-03-18 9:14 ` Bagas Sanjaya
2023-03-18 12:15 ` Sumitra Sharma
2023-03-18 12:34 ` Bagas Sanjaya
2023-03-18 12:49 ` Sumitra Sharma
2023-03-18 13:01 ` Bagas Sanjaya
2023-03-18 17:57 ` Sumitra Sharma
2023-03-19 2:08 ` Bagas Sanjaya
2023-03-19 8:32 ` Sumitra Sharma
2023-03-19 8:40 ` Julia Lawall
2023-03-19 8:56 ` Julia Lawall
2023-03-19 12:10 ` Sumitra Sharma
2023-03-19 12:36 ` Julia Lawall
2023-03-20 8:46 ` Sumitra Sharma
2023-03-20 8:56 ` Julia Lawall
2023-03-20 8:59 ` Bagas Sanjaya
2023-03-20 9:04 ` Julia Lawall
2023-03-20 9:03 ` Julia Lawall
2023-03-20 9:53 ` Sumitra Sharma
2023-03-20 13:04 ` Julia Lawall [this message]
2023-03-22 4:10 ` Sumitra Sharma
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=e13532cc-d9da-5090-7731-5d3945d7564c@inria.fr \
--to=julia.lawall@inria.fr \
--cc=bagasdotme@gmail.com \
--cc=outreachy@lists.linux.dev \
--cc=sumitraartsy@gmail.com \
/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).