Skip to content

distcc image todo #158

Open
Open
distcc image todo#158
Assignees
danzeeeman

Description

@bakercp
bakercp
opened on Jun 19, 2013
  • have VM select the default interface (rather than hard code the wifi interface ... this a virtual box problem, not a linux config problem)
  • default username / password as RPI
  • Unmount VBoxGuestAdditions.iso (? I think it can be after it has been installed).
  • Fix keyboard layout (sudo apt-get install console-data and select us english for now)
  • Install avahi (sudo apt-get install avahi-daemon avahi-utils libavahi-compat-libdnssd-dev)
  • Add an easy way to switch the build toolchain to support armv7 architecture (pcduino, etc)
  • /etc/default/distcc -> set ZEROCONF="true"
  • Lots of alerts and warnings when starting up the VB image. (regarding mouse and keyboard control). Would be nice if these didn't pop up.
  • /etc/default/distcc -> set ALLOWEDNETS="127.0.0.1 192.168.0.0./8 10.0.0.0/8" for those of us working on the local host (non-bridged) and also on10...*` networks. We share our code ... and we share our compilers :)
  • move the PATH variable inside the /etc/init.d/distcc script to /etc/default/distcc (to keep it all in one place) (also make a note of this location with the other notes that mention allowed nets, etc). This path variable is all you need to change to get it compiling with armv7 (i.e. you change the path and restart the distcc daemon).
  • add simple script in the ubuntu home directory for changing the PATH variable, plus a README giving basic configuration instructions (mirrored from our wiki) for how to configure basic stuff.
  • init.d script for pi that allows it to optionally automatically locate an online distcc server via zeroconf and set the MAKEVARS appropriately. i.e. this
#!/bin/bash

avahi-browse _distcc._tcp -r -t -p -l | grep -Eo '([0-9]{1,3}\.){3}[0-9]{1,3}' | tr '\n' ' ' > $HOME/.distcc/hosts

And this

export MAKEFLAGS="-s -j 16 CXX=/usr/lib/distcc/g++ CC=/usr/lib/distcc/gcc"
  • clear bash history

Activity

  1. ghost assigned
    danzeeeman
    on Jun 19, 2013

  2. danzeeeman commented on Jun 19, 2013

    @danzeeeman
    danzeeeman
    on Jun 19, 2013

    Noted.

    Thanks!
    On Jun 19, 2013 12:27 PM, "Christopher Baker" notifications@github.com
    wrote:

    • Fix keyboard layout (sudo apt-get install console-data and select
      us english for now)
    • Install avahi (sudo apt-get install avahi-daemon avahi-utils
      libavahi-compat-libdnssd-dev)

    —
    Reply to this email directly or view it on GitHubhttps://github.com//issues/158
    .

  3. bakercp commented on Jun 19, 2013

    @bakercp
    bakercp
    on Jun 19, 2013
    MemberAuthor

    @jvcleave ping.

  4. bakercp commented on Jun 19, 2013

    @bakercp
    bakercp
    on Jun 19, 2013
    MemberAuthor

    Cross reference : openframeworks#2134

  5. bakercp commented on Jun 19, 2013

    @bakercp
    bakercp
    on Jun 19, 2013
    MemberAuthor

    Just edited allowed nets to be less restrictive.

    ALLOWEDNETS="127.0.0.1 192.168.0.0/8 10.0.0.0/8"

    We need to make a note of this ... we should really be restricting things a bit ... but ...

  6. bakercp commented on Jun 19, 2013

    @bakercp
    bakercp
    on Jun 19, 2013
    MemberAuthor

    Perhaps ALLOWEDNETS should just be set to any with a note that anybody will be able to use the distcc server ... :)

  7. bakercp commented on Jun 19, 2013

    @bakercp
    bakercp
    on Jun 19, 2013
    MemberAuthor

    OK. So this is all working very well when the VM is bridged to the same network that the pi is connected to. When (for instance) you share internet with the PI (on os x) via ethernet, it puts the pi on a different subnet, which causes zeroconf to not recognize the distcc server. BUT as long as your ALLOWEDNETS include the PI's subnet (assigned by OSX networksharing) AND you manually add the ip of the server to the ~/.distcc/hosts file, it will connect with the server and all work just fine.

    I would really like to figure out a way to allow this VM to plug and play with a PI plugged into the ethernet port of a mac by just addressing everything by the *.local addresses and without the requirement of the computer being on an active internet connection or bridged to an outside net .... i think it's possible, but haven't had time to really push it yet (I have it all set up on parallels that way and it works nicely, but parallels has the option to bridge to the host computer's default network interface, which makes things a little more automagical)

  8. danzeeeman commented on Jun 19, 2013

    @danzeeeman
    danzeeeman
    on Jun 19, 2013

    I'll bug some of my VM masters on how to do that.
    On Jun 19, 2013 1:28 PM, "Christopher Baker" notifications@github.com
    wrote:

    OK. So this is all working very well when the VM is bridged to the same
    network that the pi is connected to. When (for instance) you share internet
    with the PI (on os x) via ethernet, it puts the pi on a different subnet,
    which causes zeroconf to not recognize the distcc server. BUT as long as
    your ALLOWEDNETS include the PI's subnet (assigned by OSX networksharing)
    AND you manually add the ip of the server to the ~/.distcc/hosts file, it
    will connect with the server and all work just fine.

    I would really like to figure out a way to allow this VM to plug and play
    with a PI plugged into the ethernet port of a mac by just addressing
    everything by the *.local addresses and without the requirement of the
    computer being on an active internet connection or bridged to an outside
    net .... i think it's possible, but haven't had time to really push it yet
    (I have it all set up on parallels that way and it works nicely, but
    parallels has the option to bridge to the host computer's default network
    interface, which makes things a little more automagical)

    —
    Reply to this email directly or view it on GitHubhttps://github.com//issues/158#issuecomment-19699586
    .

  9. jvcleave commented on Jun 21, 2013

    @jvcleave
    jvcleave
    on Jun 21, 2013
    Member

    ran into an issue last night that required gcc 4.7 - is it dangerous or rocket surgery to have our configuration use 4.7?

  10. danzeeeman commented on Jun 21, 2013

    @danzeeeman
    danzeeeman
    on Jun 21, 2013

    I'm not sure what did you need 4.7 for?
    On Jun 21, 2013 11:42 AM, "Jason Van Cleave" notifications@github.com
    wrote:

    ran into an issue last night that required gcc 4.7 - is it dangerous or
    rocket surgery to have our configuration use 4.7?

    —
    Reply to this email directly or view it on GitHubhttps://github.com//issues/158#issuecomment-19823502
    .

  11. jvcleave commented on Jun 21, 2013

    @jvcleave
    jvcleave
    on Jun 21, 2013
    Member

    it wasn't OF related but I was trying to compile a newer version of omxplayer - it was a vague error

  12. jvcleave commented on Jun 21, 2013

    @jvcleave
    jvcleave
    on Jun 21, 2013
    Member

    reading more into this - nevermind - I think it's best to keep it the way it is

  13. danzeeeman commented on Aug 10, 2013

    @danzeeeman
    danzeeeman
    on Aug 10, 2013

    @bakercp if you have admin rights let me make a new repo for the scripts in the VM image. updating stuff now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions