Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitrios Siganos <dimitris@siganos.org>
To: buildroot@busybox.net
Subject: [Buildroot] Running Packages
Date: Fri, 08 Feb 2013 06:18:38 +0000	[thread overview]
Message-ID: <511498BE.4030108@siganos.org> (raw)
In-Reply-To: <CAFzEKXETDCU8FTapwDLP1gpTOP=y9ETGjUfrDRxUxMGtkxi-+Q@mail.gmail.com>

On 08/02/13 00:55, Aditya Rawat wrote:
> Okay this my first attempt of adding custom packages to Buildroot where
> I added  the "Php" package along with all its extensions.
> After the build when I try the updated image it does seem to have the
> php package installed
> I tried "php -v" in shell and it could not find anything :(
> 
> Is there something I am missing the equation ?, maybe more any other
> configuration that is required.

Hi Aditya,

There are a lot of steps in between. You need to take it one step at a time.

First check that your package is integrated into the buildroot system.

Assuming you called your package php, run the command below to see if
your package is integrated into the buildroot system:

make php-dirclean php

You should see at least the following (and usually a lot lot more):
>>> php Configuring
>>> php Building
>>> php Installing to target

If the the package is being compiled, but just missing from the target,
then watch carefully what happens during the 'Installing to target' step.

By the way, buildroot has a php package. Which version of buildroot are
you using?

Regards,
Dimitris

  reply	other threads:[~2013-02-08  6:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08  0:55 [Buildroot] Running Packages Aditya Rawat
2013-02-08  6:18 ` Dimitrios Siganos [this message]
2013-02-08 15:21   ` Aditya Rawat
2013-02-08 19:59     ` Arnout Vandecappelle

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=511498BE.4030108@siganos.org \
    --to=dimitris@siganos.org \
    --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