From: Dan Pattison <dan.pattison@ethertek.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Web Server
Date: Wed, 04 Feb 2009 15:07:21 -0800 [thread overview]
Message-ID: <498A1FA9.1070306@ethertek.ca> (raw)
Hello List:
We are using buildroot v2009.02 on a Fedora 10 linux distro. Our
architecture is for Atmel AT91SAM9G20-EK development board. We want a
more robust web server than the BOA or Busybox HTTPD. Our main
requirement is to have the web server make a web browser (IE6, IE7,
Firefox etc.) display a login/password box. It seems the two mentioned
web servers do not support this.
Apache seems overkill for our needs, so we wanted to try
Cherokee-0.98.1: http://www.cherokee-project.com/
Using /buildroot/scripts/add_new_package.wizard we are able to make our
package show up in the make menuconfig configurator utility. When we do
a make from the top level directory we can see Cherokee gets downloaded
and starts to compile, but it errors out with these errors below:
spawn-fcgi.o: In function
`fcgi_spawn_connection':
spawn-fcgi.c:(.text+0x340): undefined reference to `rpl_malloc'
collect2: ld returned 1 exit status
make[3]: *** [spawn-fcgi] Error 1
make[3]: Leaving directory
`/home/ethertek/rms200/buildroot/build_arm/cherokee-0.98.1/contrib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/ethertek/rms200/buildroot/build_arm/cherokee-0.98.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/ethertek/rms200/buildroot/build_arm/cherokee-0.98.1'
make: ***
[/home/ethertek/rms200/buildroot/build_arm/cherokee-0.98.1/.stamp_built]
Error 2
We can see the error: undefined reference to `rpl_malloc', but being new
to cross compiling, we do not know how to fix it.
Can someone please help us get cherokee to compile for our architecture?
Also, when using the add_new_package.wizard, how do you know when to
select "Does autoreconf need to be run first?". It did not seem to
matter in the case of cross compiling Cherokee-0.98.1
Lastly, does anyone know of a different web server for Buildroot that
will make the most common web browsers (IE6, IE7, Firefox etc) pop up
the username/password box?
Thank you, and Best Regards,
Dan Pattison
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.233 / Virus Database: 270.10.17/1934 - Release Date: 01/29/09 17:57:00
next reply other threads:[~2009-02-04 23:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 23:07 Dan Pattison [this message]
2009-02-04 23:21 ` [Buildroot] Web Server Peter Korsgaard
2009-02-05 6:19 ` [Buildroot] at91rm9200 toolchain Sandeep Kumar
2009-02-05 13:25 ` Peter Korsgaard
2009-02-06 11:48 ` [Buildroot] Urgent : at91rm9200 root file system Sandeep Kumar
2009-02-06 11:53 ` Peter Korsgaard
[not found] ` <1233924549.4559.17.camel@linux-l8en.site>
[not found] ` <87zlgz91gc.fsf@macbook.be.48ers.dk>
2009-02-06 13:54 ` Sandeep Kumar
2009-02-06 15:21 ` Dan Pattison
2009-02-06 15:50 ` Sandeep Kumar
2009-02-06 16:02 ` Dan Pattison
2009-02-06 16:25 ` Sandeep Kumar
2009-02-06 17:09 ` Dan Pattison
2009-02-09 9:18 ` Sandeep Kumar
2009-02-09 9:26 ` Peter Korsgaard
2009-02-09 12:00 ` Sandeep Kumar
2009-02-09 13:05 ` Peter Korsgaard
2009-02-10 12:30 ` Sandeep Kumar
2009-02-10 12:30 ` Peter Korsgaard
2009-02-05 18:18 ` [Buildroot] Web Server Dan Pattison
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=498A1FA9.1070306@ethertek.ca \
--to=dan.pattison@ethertek.ca \
--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