Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Several issues with building multiple "projects"	for same architecture
Date: Mon, 29 Oct 2007 18:33:13 +0100	[thread overview]
Message-ID: <20071029173313.GA29762@aon.at> (raw)
In-Reply-To: <d83696340710290855s5e4e4f44y7b5777bfeacf4ec2@mail.gmail.com>

On Mon, Oct 29, 2007 at 10:55:49AM -0500, Jonathan Nalley wrote:
>I am using the buildroot to build for several different boards, some of them
>have the same CPU architecture (PPC405GP/EP).  I have noticed some issues
>with the "project" concept in the buildroot.  Since the builds are for the
>same architecture the toolchain is created under "build_powerpc".
>Everything works fine for the first board, but for subsequent builds for
>different "project" names things are missing under
>"project_build_powerpc/PROJECT_NAME/root".  Specifically:
>
>/root/lib/libgcc_s.so
>/root/usr/lib/libstdc++.so
>/root/usr/sbin/ethtool
>
>This is because the make files that install those files check for:
>
>$(GCC_BUILD_DIR2)/.libs_installed
>
>and
>
>$(ETHTOOL_DIR)/.installed

I've fixed at least the ethtool case several weeks ago in
f93f6bf4f9ae7c8c248fba2fc72ab42325975b63

As you can see, the project idea was never really integrated properly
:-/

  reply	other threads:[~2007-10-29 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 15:55 [Buildroot] Several issues with building multiple "projects" for same architecture Jonathan Nalley
2007-10-29 17:33 ` Bernhard Fischer [this message]
2007-10-29 18:22 ` [Buildroot] Several issues with building multiple "projects" forsame architecture Ulf Samuelsson
2007-10-29 22:50 ` [Buildroot] Several issues with building multiple "projects" for same architecture Ulf Samuelsson
2007-10-30  0:10   ` Hamish Moffatt
2007-10-30  7:41     ` [Buildroot] Several issues with building multiple"projects" " Ulf Samuelsson

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=20071029173313.GA29762@aon.at \
    --to=rep.dot.nop@gmail.com \
    --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