Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] br-2009.08 X11 problem
Date: Fri, 13 Nov 2009 10:24:09 -0800	[thread overview]
Message-ID: <4AFDA449.6020005@cs.ucsb.edu> (raw)

Hello,

I am using br-2009.08 and I am trying to build x-org server.  X11
compilation fails because openssl/sha.h is not found:

glyph.c:30:25: error: openssl/sha.h: No such file or directory
glyph.c: In function 'HashGlyph':
glyph.c:207: error: 'SHA_CTX' undeclared (first use in this function)

I checked that the openssl package is chosen and is present in my
package directory.  Also, xserver_xorg-server.mk located in
<br_dir>/package/x11r7/xserver_xorg-server lists openssl as the
dependency.  However, during the build process there is no include flag
that points to the openssl/include directory.  What is the quick and
dirty way to fix this?  If I modify the x11 Makefile, it gets over
written during the buildroot make.

Thanks,

Roman

             reply	other threads:[~2009-11-13 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 18:24 Roman Chertov [this message]
2009-11-15 13:27 ` [Buildroot] br-2009.08 X11 problem Peter Korsgaard

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=4AFDA449.6020005@cs.ucsb.edu \
    --to=rchertov@cs.ucsb.edu \
    --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