Path: csiph.com!usenet.pasdenom.info!news.etla.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.025 X-Spam-Evidence: '*H*': 0.95; '*S*': 0.00; 'irc': 0.05; 'output': 0.05; 'bootstrap': 0.07; 'linux,': 0.07; "subject:' ": 0.07; 'hooks': 0.09; 'run,': 0.09; 'subject:test': 0.09; 'developer': 0.10; 'python': 0.11; '"in': 0.16; 'grep': 0.16; 'processor,': 0.16; 'subject:install': 0.16; 'subject:make': 0.16; 'subject:python3': 0.16; 'basically': 0.19; 'ownership': 0.19; 'things.': 0.19; '(in': 0.22; 'tests': 0.22; 'to:name:python- list@python.org': 0.22; 'install': 0.23; 'aspect': 0.24; 'guys': 0.24; "i've": 0.25; 'source': 0.25; 'post': 0.26; 'world,': 0.26; 'developing': 0.27; 'topic': 0.29; 'errors': 0.30; 'along': 0.30; "i'm": 0.30; 'arm': 0.31; 'install,': 0.31; 'though.': 0.31; 'there.': 0.32; 'probably': 0.32; 'running': 0.33; '(e.g.': 0.33; 'guess': 0.33; 'subject:from': 0.34; 'subject: (': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'building': 0.35; 'there': 0.35; 'version': 0.36; 'really': 0.36; 'curious': 0.36; 'next': 0.36; 'charset:us-ascii': 0.36; 'thanks': 0.36; 'experience,': 0.37; 'too': 0.37; 'list': 0.37; 'clear': 0.37; 'message- id:@gmail.com': 0.38; 'to:addr:python-list': 0.38; 'that,': 0.38; 'expect': 0.39; 'bad': 0.39; 'channel': 0.39; 'embedded': 0.39; 'to:addr:python.org': 0.39; 'mailing': 0.39; 'called': 0.40; 'how': 0.40; 'most': 0.60; 'forum': 0.61; 'making': 0.63; 'header :Message-Id:1': 0.63; 'kind': 0.63; 'provide': 0.64; 'more': 0.64; 'different': 0.65; 'account': 0.65; 'here': 0.66; 'anything.': 0.68; 'hints': 0.68; 'helping': 0.70; 'fat': 0.84; 'python-dev': 0.84; 'subject:source': 0.84; 'tricky': 0.84; 'way)': 0.84; 'capture': 0.91; 'concluded': 0.91 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=LmdoNfUo6xLkVGG9O+aTGONzReMrya86SqLHsLwGt4g=; b=cJZXfZqlc3/FbFBi8NcT/ZozmNFuzuX1/7/sgaemuENLt2ztH2zpkY233Oi8VWH09s 0UpsBuvOdwn3DXj/9/XAuGSP/Z8R1hqnB7ONpIyvx1d2UnxDw9jMHrAJpMbzWiz/uZ11 upYrhrv7CIIX03dDuOhQC7xegIbuXFZteQAVU5oP3HT7kr7+x/8quNz4jBLcVOz3wVFD fXmD+hH+0d0x5RbP+4GjIfUVW7Tw7upwQYmIPLGZQn+CNi5gMKDHfyxpkFMTHezrdvGp gue2yG1NlRrTL4ICRL2Q/9oumCZM/0dDJqCaChMVIHdm/yw4oC6FwkyGYmWArN0+ueyD LUzQ== X-Received: by 10.69.0.228 with SMTP id bb4mr12397166pbd.66.1383878354289; Thu, 07 Nov 2013 18:39:14 -0800 (PST) From: Travis Griggs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: What to make of 'make test' for python3 install from source (beaglebone angstrom install). Date: Thu, 7 Nov 2013 18:39:11 -0800 To: "python-list@python.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 32 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1383878363 news.xs4all.nl 15931 [2001:888:2000:d::a6]:33876 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:58738 After hints here and there from different channels, and a pretty good = StackOverflow post on the subject, I've concluded that "out of the box", = the install from source utilities don't really provide many hooks for = making a "custom/minimal" install. Best bet is basically to do the = standard install, and then go trim off the fat that wasn't called for. = If not that, you really have to take ownership of the whole build = process (e.g. as Debian and others do). Thanks to Ned and others for = helping along the way. One part of the recommended install is to 'make test'. In a perfect = world, I guess everything would pass. Since I'm running an embedded = linux, on an arm processor, I kind of expect some issues. As the tests = run, I see that there are indeed some errors here and there. But I don't = see where they get summarized or anything. I guess I can try to capture = the output and grep through it. I'm curious how people use the make = install. Looking to bootstrap off of other's experience, if any has some = willing to share. --Travis Griggs "I multiply all estimates by pi to account for running around in = circles"=