From: Michael Burghart <mb@michaelburghart.de>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling Apache
Date: Tue, 22 Mar 2011 20:35:25 +0100 [thread overview]
Message-ID: <4D88F9FD.104@michaelburghart.de> (raw)
In-Reply-To: <4D88C6B3.5010103@free.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
I forgot. I did an strace on that non existing file:
mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> strace
./dftables
execve("./dftables", ["./dftables"], [/* 73 vars */]) = -1 ENOENT (No
such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7f8fa10dc000
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such
file or directory
) = 40
close(3) = 0
munmap(0x7f8fa10dc000, 4096) = 0
exit_group(1) = ?
Does anybody understand whats happening here?!
- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNiPn9AAoJEEMkp/gkis191/EH/j7MqbQNNrHWim7ZmKfaEHFm
hR0nBTurG/9xt19Tjg0zW9BdPnWAgIjP2ao+p2VRoaIwPGqj3rLdfLzHgfsg959K
kKYoYprcABEGDDPLMiVDK7PeXCyHbLH6v6oWFf6l6tyStRVvhIlDAUPro5bYAeQD
oBnMiq5u/PXRX5SI3P7/d3qnU+2N8fBWx8XM9Qjn+LRWh8RIxyYtMwvYNg3q7bb7
3zSbVxBtxgNHogHCrtt9bl6+eosXAiHnwaA0EH+pimEkMJohchb8Gntq3/2Gm1TF
92a0dEBCLIjpM7WwyCJ1VmYrVyKxs/hGDw2+WHzJWgr49DTdKygfT/FdVAFm3+Q=
=zzIK
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-03-22 19:35 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
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 [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=4D88F9FD.104@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 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.