From: Michael Burghart <mb@michaelburghart.de>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling Apache
Date: Tue, 22 Mar 2011 20:33:15 +0100 [thread overview]
Message-ID: <4D88F97B.4060605@michaelburghart.de> (raw)
In-Reply-To: <4D88C6B3.5010103@free.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Am 22.03.2011 16:56, schrieb Eric BENARD:
>> thanks for your info. Seems pretty weird and more complex than I
>> thought. But how do you integrate those rules into buildroot? I only saw
>> the "standard" autoconf and cmake Makefiles.in the documentation..
>>
> well for that part you will need to ask on the mailing list.
>
what I do not understand: I get the following error:
make[4]: Entering directory
`/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre'
./dftables
/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c
make[4]: ./dftables: Kommando nicht gefunden
So I tried it manually and did a cd into the directory:
cd /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/
then I invoked the dftables command manually:
./dftables
/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c
got "File not found":
- -bash: ./dftables: Datei oder Verzeichnis nicht gefunden
Did a ls on that file and it exists! So why did it produce an "File not
foound" error
mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> ls
- -l ./dftables
- -rwxr-xr-x 1 mb users 8015 22. M?r 15:18 ./dftables
How can that be? I am really puzzled now...
> Regard,
> Eric
>
- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNiPl7AAoJEEMkp/gkis19EbcIAKi6tbjQAzNbf5OLqNh3Js2d
9DSDhnCiGG1DfYkxTKDPEkdiPDXjxQMX4DtKivlnKs8n0MqW84jkbFV1yauFS8x4
zkQ/zWTCRSrToMmCzhnMOpxPibB318hWseAEGECR7XrjdoRKSZiZQKGKzkVJECEM
c2hzJOt0RyxTOqs1ZdmUmxZ/ui6O5w5bjb7tqPFh44GNH5JDigG7ghkJrtIuojEE
tpL3MI7ZEi2LRQ8CGRvRejuxqiGL+U1gYJqpQ/dO1CmwbUMX7bQNzanN0OB+gqII
YO1qbdG0kaONxScDn96qe2WVH98C7dfK4UOw+K2ordjmR98aunrlv7pmCvGAx4A=
=kA5n
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-22 19:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 21:39 [Buildroot] Compiling Apache Michael Burghart
2011-03-22 14:59 ` Eric BENARD
[not found] ` <4D88BD19.7070901@michaelburghart.de>
[not found] ` <4D88C6B3.5010103@free.fr>
2011-03-22 16:07 ` Michael Burghart
2011-03-22 19:33 ` Michael Burghart [this message]
2011-03-22 19:55 ` Baruch Siach
2011-03-22 20:00 ` Michael Burghart
2011-03-22 20:03 ` Baruch Siach
2011-03-22 20:21 ` Michael Burghart
2011-03-23 6:12 ` Michael Burghart
2011-03-23 17:16 ` Baruch Siach
2011-03-23 19:02 ` [Buildroot] proc not mouning Heyendal, Carl
2011-03-23 19:27 ` bruce bushby
2011-03-23 19:32 ` ANDY KENNEDY
2011-03-23 19:35 ` Heyendal, Carl
2011-03-23 19:43 ` ANDY KENNEDY
2011-03-23 19:46 ` Heyendal, Carl
2011-03-23 19:36 ` bruce bushby
2011-03-23 20:35 ` Heyendal, Carl
2011-03-23 21:14 ` ANDY KENNEDY
2011-03-24 18:58 ` Thomas Petazzoni
2011-03-24 19:04 ` Heyendal, Carl
2011-10-21 16:29 ` vbr vbr
2011-10-28 12:50 ` Peter Korsgaard
2011-03-24 6:42 ` [Buildroot] Compiling Apache Michael Burghart
2011-03-22 19:35 ` Michael Burghart
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=4D88F97B.4060605@michaelburghart.de \
--to=mb@michaelburghart.de \
--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