cURL / Mailing Lists / curl-library / Single Mail


RE: Curl Embedded Linux

From: Chris Brown <>
Date: Fri, 29 Jun 2007 17:31:00 +1200

Thanks for your quick reply.

Based on your advice and the comments you made I have tried again to run
configure and cross compile for the MIPS system (I also installed OpenSSL).
I have run configure as follows:

[root_at_localhost curl-7.16.2]# ./configure --with-ssl=/usr/local/ssl
--enable-cookies --enable-http --prefix=/chris/curlmv
--host=/opt/hardhat/devkit/mips/fp_le/bin/mips_fp_le --build=mips_fp_le

I am getting the output below.

checking whether to enable maintainer-specific portions of Makefiles... no
checking for sed... /bin/sed
checking for /opt/hardhat/devkit/mips/fp_le/bin/mips_fp_le-ar... no
checking for ar... ar
configure: WARNING: In the future, Autoconf will not detect cross-tools
whose name does not start with the host triplet. If you think this
configuration is useful to you, please write to
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for /opt/hardhat/devkit/mips/fp_le/bin/mips_fp_le-strip... no
checking for strip... strip
checking curl version... 7.16.2
checking build system type... Invalid configuration `mips_fp_le': machine
`mips_fp_le' not recognized
configure: error: /bin/sh ./config.sub mips_fp_le failed
[root_at_localhost curl-7.16.2]#

Aside from the obvious error I notice that it doesn't seem to be finding
'mips_fp_le-ar' or 'mips_fp_le-strip' in the directory specified, both of
which are present.

Can you offer any further help?



-----Original Message-----
[] On Behalf Of Daniel Stenberg
Sent: Thursday, 21 June 2007 7:37 p.m.
To: libcurl development
Subject: Re: Curl Embedded Linux

On Thu, 21 Jun 2007, Chris Brown wrote:

> I then successfully referenced this library in the makefile for my own
> test application based on simple.c. The problem I have is that I am
> attempting to repeat this process on my MIPS embedded MontaVista Linux
> system which uses mips_fp_le-gcc. When I run ./configure I get the
following output:

Well, I trust you used some options to configure as well?

> sed: invalid command

The curl build requires 'sed' to exist, so you should get that installed.

> checking whether to enable maintainer-specific portions of
> Makefiles... no checking for sed... /bin/sed checking for ar... no

Really 'ar' ? I would think that you'd want a 'mips_fp_le-ar' or similar?

> checking build system type... mkdir: Cannot create directory
> `/tmp/cg678-5572': No such file or directory

This sounds like your build system is crazy or too limited for a normal
Check the config.log file for details but it has to be able to create
temporary files (and directories) for configure to work.

> Can anyone offer any suggestions or point me in the right direction?
> My ultimate intention is to use https posts so I will also need to
> ensure that SSL is working. Please excuse my naivity- as I mentioned
> above I'm new to Linux and its a steep learning curve at the moment.

Well, I happen to work with an ARM linux at the moment. I use a gcc setup
named arm-softfloat-linux-gnu-gcc. To cross-compile curl for my system, I
just have to do this:

  $ ./configure --host=arm-softfloat-linux-gnu
  $ make
  $ make DESTDIR=/rootdir/for/my/target install

This should be pretty much the same for whatever linux target you have, but
it assumes that you have a certain level of tools installed on the build

Hm, I reread your mail. Are you saying you *build* on the embedded target? I
find that a very odd idea since embedded targets are usually way way waaaaay
slower and have less memory etc than even your average several years old PC.
I suggest you go the cross-compile route.

Of course, building *on* the target is just like how you build on any Linux,
you just need to make sure you have all the tools and the correct build
environment setup and present.

  Commercial curl and libcurl Technical Support:
__________ NOD32 2342 (20070621) Information __________
This message was checked by NOD32 antivirus system.
Received on 2007-06-29