Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Web Server
Date: Thu, 05 Feb 2009 00:21:08 +0100	[thread overview]
Message-ID: <878woldc0r.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <498A1FA9.1070306@ethertek.ca> (Dan Pattison's message of "Wed\, 04 Feb 2009 15\:07\:21 -0800")

>>>>> "Dan" == Dan Pattison <dan.pattison@ethertek.ca> writes:

 Dan> Hello List:
 Dan> We are using buildroot v2009.02 on a Fedora 10 linux distro. Our
 Dan> architecture is for Atmel AT91SAM9G20-EK development board. We want a
 Dan> more robust web server than the BOA or Busybox HTTPD. Our main
 Dan> requirement is to have the web server make a web browser (IE6, IE7,
 Dan> Firefox etc.) display a login/password box. It seems the two mentioned
 Dan> web servers do not support this.

Standard http auth? Both busybox httpd and boa supports that.

 Dan> Apache seems overkill for our needs, so we wanted to try
 Dan> Cherokee-0.98.1:  http://www.cherokee-project.com/

We also have lighttpd in busybox, maybe take a look at that.

 Dan> Using /buildroot/scripts/add_new_package.wizard we are able to make
 Dan> our package show up in the make menuconfig configurator utility. When
 Dan> we do a make from the top level directory we can see Cherokee gets
 Dan> downloaded and starts to compile, but it errors out with these errors
 Dan> below:

 Dan> spawn-fcgi.o: In function `fcgi_spawn_connection':                                                                           

 Dan> spawn-fcgi.c:(.text+0x340): undefined reference to `rpl_malloc'
 Dan> collect2: ld returned 1 exit status                                                                                          

Check config.log, you normally have to set a *_cv_func_malloc_* (don't
remember the exact name offhand) variable to not get it to use this
malloc wrapper.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-02-04 23:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 23:07 [Buildroot] Web Server Dan Pattison
2009-02-04 23:21 ` Peter Korsgaard [this message]
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=878woldc0r.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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