Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Unable to find module location
Date: Sat, 18 Mar 2023 05:49:37 -0700	[thread overview]
Message-ID: <20230318124937.GA39892@sumitra.com> (raw)
In-Reply-To: <64997a6c-24f1-d551-1b87-735a699e4a8e@gmail.com>

On Sat, Mar 18, 2023 at 07:34:25PM +0700, Bagas Sanjaya wrote:
> On 3/18/23 19:15, Sumitra Sharma wrote:
> > HI,
> > 
> > I tried your way. Build and Install aarch64-linux-gnu-gcc, added the
> > path and run the command 'make -j2 ARCH=arm
> > CROSS_COMPILE=aarch64-linux-gnu-'
> > 
> 
> The ARCH is wrong. In this case it should have been `ARCH=arm64`.
>

Sorry, for such a silly mistake.

However I run the command "make -j2 ./drARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-" and got 
make[3]: Nothing to be done for 'drivers/staging/nvec/'.

I think  this is because it is not yet created as a module.

This was my initial issue.

Regards,

Sumitra

> 
> -- 
> An old man doll... just what I always wanted! - Clara
> 

  reply	other threads:[~2023-03-18 12:49 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 [this message]
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
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=20230318124937.GA39892@sumitra.com \
    --to=sumitraartsy@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=outreachy@lists.linux.dev \
    /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