Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] install-to-staging OK but install-to-target fails
Date: Fri, 03 Feb 2012 08:00:03 +0100	[thread overview]
Message-ID: <871uqce70s.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <D921DC3114DE02419F1BFD413E98678E102B05F49F@VA3DIAXVS331.RED001.local> (Edward Endejan's message of "Thu, 2 Feb 2012 18:38:25 -0800")

>>>>> "Edward" == Endejan, Edward <Edward.Endejan@dmh-global.com> writes:

Hi,


 Edward> Thanks for the quick response. Our corporate internet
 Edward> connection went down this afternoon so we were pretty much dead
 Edward> in the water for the rest of the workday. Luckily we have a web
 Edward> interface to our cloud-hosted email so I saw your response
 Edward> tonight from home.

 Edward> Assuming our connection is restored by tomorrow, I'll get the
 Edward> defconfig to you. Is doing a 'make savedefconfig' any different
 Edward> than just sending the .config file from the base directory of
 Edward> buildroot?

Great. It contains the same info, but it's easier to look at as it only
shows the options you have changed from the details.

 Edward> A couple of other details in case they are relevant ...

 Edward> We were able to successfully build these GStreamer libraries
 Edward> with the original .mk files included with buildroot, but they
 Edward> were using .tar.gz snapshots rather than fetching the source
 Edward> using git. We want to convert to using the git approach so that
 Edward> we can easily push modifications to their source code back to
 Edward> that project.

Ok.

 Edward> We have cloned the GStreamer git repositories that we are using
 Edward> to a local git server so that we have them local and for
 Edward> faster, uninterrupted access. We have modified these .mk files
 Edward> to use git instead and to fetch from our local repository of
 Edward> clones. As another side-effect of this we added a pre-configure
 Edward> hook to run their autogen.sh script because the GStreamer
 Edward> project uses this approach rather than the standard buildroot
 Edward> autotools configuration approach. The .tar.gz snapshots include
 Edward> pre-built .configure files - the git clone versions do
 Edward> not. I'll send you the modified .mk files so that you have the
 Edward> whole picture, but they will have to be modified to point to
 Edward> the cgit.freedesktop.org git repositories before they will work
 Edward> for you.

It should be enough to just add a <foo>_AUTORECONF = YES line in the
affected packages. See connman for an example. If you ./autogen.sh with
your normal host libtool then that could explain the problem (we patch
up libtool output to work around cross compile issues). Could you try a
fresh rebuild with the AUTORECONF = YES lines added.


-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-02-03  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 20:04 [Buildroot] install-to-staging OK but install-to-target fails Endejan, Edward
2012-02-02 20:36 ` Peter Korsgaard
2012-02-03  2:38   ` Endejan, Edward
2012-02-03  7:00     ` Peter Korsgaard [this message]
2012-02-03 22:27       ` Endejan, Edward

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=871uqce70s.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