From: gianluca <gianlucarenzi@eurek.it>
To: Dinesh Velayudham <Dinesh.Velayutham@LnTtechservices.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: J1939 Linux
Date: Fri, 8 Apr 2016 13:20:22 +0200 [thread overview]
Message-ID: <570793F6.7080808@eurek.it> (raw)
In-Reply-To: <20160408090444.GA5485@airbook.vandijck-laurijssen.be>
On 04/08/2016 11:04 AM, Kurt Van Dijck wrote:
> Hey,
>
>> Kurt,
>> I am facing deb-pkg error while building the kernel. Need your guidance on that.
>>
>> Steps below.
>> 1. I cloned the kernel from "http://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu-vivid.git/commit/?id=32ac5b4aae56cf9446c30463663c8ae2226069da" with tag name "Ubuntu-3.19.0-56.62"
>> 2. Then I added "git remote add j1939 git://github.com/kurt-vd/linux"
>> 3. git remote update j1939
>> 4. git merge j1939/j1939d-v3.15
>> 5. Merge was successful without any issues.
>> 6. cp /boot/config-3.19.0.56-generic .config
>> 7. yes ' ' | make oldconfig
>> 8. make menuconfig -> added SAE J1939 support and debugging support for J1939 and CAN messages
>> 9. make -j 3 deb-pkg LOCALVERSION=-custome
>
> I think you did everything well up to step 9.
> My knowledge on building kernels specific for debian/Ubuntu is limited.
> Yet, the command you issue seems strange.
> Shouldn't you just do:
>
> $ make -j 3 LOCALVERSION=-custome
>
> and then
>
> $ sudo make install
>
Nope. Eventually you have to compile the drivers too with a make modules.
make deb-pkg will:
1. compile the kernel and the static drivers
2. compile the modules
3. install the modules
4. it will create the initrd for next boot.
> Kind regards,
> Kurt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
Eurek s.r.l. |
Electronic Engineering | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212
next prev parent reply other threads:[~2016-04-08 11:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 15:43 J1939 Linux Dinesh
2016-04-06 7:46 ` Kurt Van Dijck
2016-04-06 14:33 ` Dinesh Velayudham
2016-04-06 19:40 ` Kurt Van Dijck
2016-04-07 22:28 ` Dinesh Velayudham
2016-04-08 9:04 ` Kurt Van Dijck
2016-04-08 11:20 ` gianluca [this message]
2016-04-08 11:58 ` Kurt Van Dijck
2016-04-08 14:29 ` Dinesh Velayudham
2016-04-09 11:40 ` Kurt Van Dijck
[not found] ` <03B271BE48E2554EB34508DAB79DBABA8709986A@POCITMSEXMB05.LntUniverse.com>
[not found] ` <20160412082020.GA19875@airbook.vandijck-laurijssen.be>
[not found] ` <03B271BE48E2554EB34508DAB79DBABA8709A50F@POCITMSEXMB05.LntUniverse.com>
2016-04-12 18:15 ` Kurt Van Dijck
2016-04-12 18:28 ` Dinesh Velayudham
2016-04-13 16:08 ` Dinesh Velayudham
2016-04-13 18:33 ` Kurt Van Dijck
2016-04-14 10:03 ` Kurt Van Dijck
2016-04-14 10:49 ` Marc Kleine-Budde
2016-04-14 12:22 ` Kurt Van Dijck
2016-04-14 12:31 ` Marc Kleine-Budde
2016-04-14 15:51 ` Kurt Van Dijck
2016-04-14 17:52 ` Dinesh Velayudham
2016-04-14 23:10 ` Kurt Van Dijck
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=570793F6.7080808@eurek.it \
--to=gianlucarenzi@eurek.it \
--cc=Dinesh.Velayutham@LnTtechservices.com \
--cc=linux-can@vger.kernel.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