From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] can't create own package
Date: Mon, 7 May 2018 13:11:15 +0200 [thread overview]
Message-ID: <20180507131115.179c0405@windsurf> (raw)
In-Reply-To: <CANMfZMgxMC2jf26FfKJ7gX6zyLfg0bj2nePxWKc1hh0yrrNbyQ@mail.gmail.com>
Hello,
On Mon, 7 May 2018 16:35:08 +0530, s.vineeth amalraj wrote:
> I followed your comments and created a folder and TAMIL_SITE points to a
> folder now. I am able to build without any error. But am not able to view
> that in my newly built OS. Or couldn't use that package in my OS. I am not
> able to sort where the issue is? Kindly help. Thank you!
Please don't create a new thread, but instead reply to the existing
e-mail.
Also, you don't provide enough details: if you don't provide your .mk
file, and the build log, we can't guess what you have done and provide
some help and guidance.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-07 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 11:05 [Buildroot] can't create own package s.vineeth amalraj
2018-05-07 11:11 ` Thomas Petazzoni [this message]
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=20180507131115.179c0405@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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