From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to add PHP
Date: Sun, 17 Nov 2013 18:33:01 +0000 [thread overview]
Message-ID: <52890BDD.8070709@communistcode.co.uk> (raw)
In-Reply-To: <5837624278552957107@unknownmsgid>
Hi Scott,
Bitbake will point you to the log file in the output (it will be a
fairly long filepath). If there isn't a link to a file in the output and
the output is short then paste that in an email, or pastebin.
If you're still struggling with what to send or where to find it, I
would suggest dropping by the IRC channels and someone will be about to
help further.
Cheers,
Jack.
On 17/11/13 16:23, Scott Penner wrote:
> Hi Jack, thanks for the reply!
> I am looking for modphp, which is in the webserver directory and I
> have tried adding that package but the build fails. I've added the
> apache webserver with success and took the same approach for adding
> modphp. Which log files can I send? My learning is still curving :/
>
> Thanks,
>
> Scott Penner
>
> Goodwell Inc.
> c. 4033761977
> a. Box 906 Brooks, Ab T1R1B8
>
>> On Nov 15, 2013, at 2:52 AM, Jack Mitchell <ml@communistcode.co.uk> wrote:
>>
>>> On 15/11/13 05:58, Scott Penner wrote:
>>> Hi and thanks for this resource,
>>>
>>> I am trying to add PHP to my image and cannot!
>>> I've tried a few different attempts, sort of documented
>>> here<https://community.freescale.com/message/359851#359851>
>>> Its for a imx6sabrelite board and I'm trying to modify the fsl-image-test
>>> image.
>>> I can add the apache server, and it works, but get errors during the bake
>>> when adding PHP.
>>> Should I be using the PHP packages in the webserver directory or devtools
>>> directory?
>>> Do you have any working examples of a lamp install or just apache/PHP
>>> install procedure?
>>>
>>> Thanks for any insight,
>>>
>>> Scott Penner
>>
>> Hi Scott,
>>
>> There should only be one location for PHP, or are you getting PHP and
>> mod-php mixed up? If so, you should read up on what the differences are
>> and decide which one you need.
>>
>> Secondly, we can't help without error logs :)
>>
>> Cheers,
>>
>> --
>> Jack Mitchell (jack@embed.me.uk)
>> Embedded Systems Engineer
>> Cambridgeshire, UK
>> http://www.embed.me.uk
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
next prev parent reply other threads:[~2013-11-17 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 5:58 How to add PHP Scott Penner
2013-11-15 9:52 ` Jack Mitchell
2013-11-17 16:23 ` Scott Penner
2013-11-17 18:33 ` Jack Mitchell [this message]
2013-11-17 19:16 ` Scott Penner
2013-11-17 19:30 ` Jack Mitchell
2013-11-17 19:39 ` Scott Penner
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=52890BDD.8070709@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.