public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: 'Ken Bass' <daytooner@gmail.com>,
	"crossgcc@sourceware.org"	<crossgcc@sourceware.org>
Subject: RE: cross-compile gstreamer: can't find "glibconfig.h"
Date: Mon, 15 Aug 2016 15:08:00 -0000	[thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C6EE88E25B@ex-mb1.corp.adtran.com> (raw)
In-Reply-To: <CAH5g0274Kp99o6105LgCg53dJ=Ksis1RXPQzOGsGF_8wkDu7Tg@mail.gmail.com>

> Here is the configure command:
> 
> ./configure --host=armv6-rpi-linux-gnueabihf --includedir=<toolchain
> path>/x-tools/ib/glib2.0/include CFLAGS="-g -pg" CXXFLAGS="-g -pg"
> --with-pkg-config-path=<toolchain
> path>/x-tools/armv6-rpi-linux-gnueabihf/lib/pkgconfig
> --with-sysroot=/<toolchain
> path>x-tools/armv6-rpi-linux-gnueabihf/armv6-rpi-linux-gnueabihf/sysroot
> 
> This runs ok. When I run make, for the first CC I get an error like
> "glibconfig.h: No such file or directory".

Ken,

Have you installed glib into your sysroot?  If not, then
you would need to provide the location of the glib for
building gstream.

Depending on your setup, you may wish to build many of the
external libraries into your toolchain (assuming that you
won't be the only one using your toolchain), so that you
can easily distribute the toolchain throughout your
organization.

If this sounds promising to you, send me private mail
and I'll send you a patch against BuildRoot that will
allow you to build external libraries into your toolchain.

HTH,
Andy

> 
> I have glib(1 and 2.0) installed on the build system. But if I use
> that, the compiler thinks the host is also a 64 bit system (which it
> isn't).
> 
> Any ideas? Any and all help greatly appreciated.
> 
> TIA
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq


  reply	other threads:[~2016-08-15 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 12:42 Ken Bass
2016-08-15 15:08 ` ANDY KENNEDY [this message]
2016-08-18  3:48 ` Ken Bass

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=F9C551623D2CBB4C9488801D14F864C6EE88E25B@ex-mb1.corp.adtran.com \
    --to=andy.kennedy@adtran.com \
    --cc=crossgcc@sourceware.org \
    --cc=daytooner@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).