All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Johnson <bradjohn263@comcast.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot openssl compile error
Date: Mon, 13 Apr 2009 22:10:39 -0500	[thread overview]
Message-ID: <49E3FEAF.7040705@comcast.net> (raw)
In-Reply-To: <20090413220823.210225fe@surf>

Hello Thomas,
I tried to build the latest (4/13/09) svn version of buildroot with my 
external buildroot toolchain (cross-compiler for arm). I assume the fix 
described in r25879 is in this version?
I still get an error compiling openssl:

/opt/arm-linux/usr/bin/arm-linux-gcc -I.. -I../.. -I../../include -fPIC 
-DOPENSS
L_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLF
CN_H -DTERMIO -O3 -fomit-frame-pointer -Wall   -c -o c_zlib.o c_zlib.c
c_zlib.c:25:18: error: zlib.h: No such file or directory

I do not see a --sysroot gcc argument. There is a 
build_arm/staging_dir/usr/include/zlib.h.
Please advise me as to how I can build openssl within buildroot using an 
external toolchain.

Thanks,
Brad

On 4/13/2009 3:08 PM, Thomas Petazzoni wrote:
> Le Mon, 13 Apr 2009 20:03:50 +0200,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>
>   
>> There's no -I$(STAGING_DIR)/usr/include in the gcc invocation, so that
>> probably fails with an external toolchain.
>>     
>
> There's no need for -I$(STAGING_DIR)/usr/include with an external
> toolchain if --sysroot $(STAGING_DIR) is passed (at least my
> experiments confirm this). See r25879.
>
> Thomas
>   
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.0.238 / Virus Database: 270.11.54/2056 - Release Date: 04/13/09 05:51:00
>
>   

  reply	other threads:[~2009-04-14  3:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-12  3:46 [Buildroot] buildroot openssl compile error Brad Johnson
2009-04-13 18:03 ` Peter Korsgaard
2009-04-13 20:08   ` Thomas Petazzoni
2009-04-14  3:10     ` Brad Johnson [this message]
2009-04-14  7:09       ` Thomas Petazzoni
2009-04-14  8:41         ` Thomas Petazzoni
2009-04-15  9:06           ` [Buildroot] OpenSSL build system knowledge somewhere ? Thomas Petazzoni
2009-04-15 12:57             ` Peter Korsgaard
2009-04-15 13:41               ` Thomas Petazzoni
2009-04-15 13:50                 ` Peter Korsgaard
2009-04-15 19:28                   ` Gustavo Zacarias
2009-04-15 13:59               ` Gustavo Zacarias
2009-04-14  2:00   ` [Buildroot] buildroot openssl compile error Brad Johnson
2009-04-28 21:06 ` Thomas Petazzoni

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=49E3FEAF.7040705@comcast.net \
    --to=bradjohn263@comcast.net \
    --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.