All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4718] New: python (built for powerpc) distutils has paths to host compiler toolchain
Date: Sat, 21 Jan 2012 23:13:03 +0000 (UTC)	[thread overview]
Message-ID: <bug-4718-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=4718

           Summary: python (built for powerpc) distutils has paths to host
                    compiler toolchain
           Product: buildroot
           Version: 2011.11
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: bvwelch at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


I suspect that I probably missed somewhere that I could have set this up, and I
think I can workaround it using distutil.cfg, but I was surprised that when I
ran "python setup.py build_ext --inplace", the errors were showing path names
from the host where I ran buildroot, rather than my native powerpc toolchain.

Otherwise, buildroot is working great, thank you!

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-01-21 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 23:13 bugzilla at busybox.net [this message]
2012-01-31 19:43 ` [Buildroot] [Bug 4718] python (built for powerpc) distutils has paths to host compiler toolchain bugzilla at busybox.net
2012-02-01 17:23 ` bugzilla at busybox.net
2013-05-26 10:55 ` bugzilla at busybox.net
2013-07-10 13:19 ` bugzilla at busybox.net

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=bug-4718-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.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.