Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please provide a PPC32 Build #71

Closed
3 tasks done
mterron opened this issue Jun 10, 2017 · 8 comments
Closed
3 tasks done

Please provide a PPC32 Build #71

mterron opened this issue Jun 10, 2017 · 8 comments

Comments

@mterron
Copy link
Contributor

mterron commented Jun 10, 2017

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

  • I have read and understood the contributors guide.
  • The issue I am reporting can be replicated
  • The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1


[BUG | ISSUE] Expected Behaviour:
FTL runs

[BUG | ISSUE] Actual Behaviour:
No binary available for CPU arch ppc as per lscpu output
Architecture: ppc
CPU op-mode(s): 32-bit
Byte Order: Big Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Model: amcc,apollo3g
BogoMIPS: 1600.00
L1d cache: 32K
L1i cache: 32K
L2d cache: unknown size
L2i cache: unknown size

[BUG | ISSUE] Steps to reproduce:
Install pi-hole on a PPC based device.

Device specifics

Hardware Type: MyBook Live
OS: Linux

@technicalpyro
Copy link
Contributor

looking at what i can find regarding your hardware i am unsure it would be supported. however you can start here: https://github.com/pi-hole/FTL#how-to-compile-ftl-from-source and once DL6ER is awake (he wrote the FTL backend) he may have a better answer

@dschaper
Copy link
Member

We'll check and see if our builder is capable of producing binaries for that platform. We use Travis to build out our binaries and it may not be possible to get something on that processor, but we will try.

@DL6ER
Copy link
Member

DL6ER commented Jun 13, 2017

I haven't had much luck trying to get a ready-to-use cross compiler. Have you tried to compile FTL from source as suggested by @technicalpyro ?

@mterron
Copy link
Contributor Author

mterron commented Jun 13, 2017 via email

@mterron
Copy link
Contributor Author

mterron commented Jun 14, 2017

I was able to cross-compile by doing this as root on a fresh Debian Jessie install:

apt update && apt install curl git
echo 'deb http://emdebian.org/tools/debian/ jessie main' >> /etc/apt/sources.list
curl http://emdebian.org/tools/debian/emdebian-toolchain-archive.key | apt-key add -
dpkg --add-architecture powerpc
apt update
apt install crossbuild-essential-powerpc
git clone https://github.com/pi-hole/FTL
cd FTL
sed -i.bak 's/^CC=gcc/CC=powerpc-linux-gnu-gcc/' Makefile
export ARCH=powerpc
make

@DL6ER
Copy link
Member

DL6ER commented Jun 16, 2017

@dschaper We have no sudo capabilities on Travis CI, do you think we can do still what @mterron is suggesting?

@mterron
Copy link
Contributor Author

mterron commented Jun 18, 2017

Seems using 'sudo: required' in your Travis config file will provide the sudo capabilities needed to install crosscompilers? I'm not familiar with Travis though.

Also adding this to .travis.yml should work I guess:

- env:
    - BUILD_CC="powerpc-linux-gnu-gcc"
    - BIN_NAME="pihole-FTL-powerpc-linux-gnu"
    addons:
      apt:
        packages:
        - gcc-powerpc-linux-gnu
        - binutils-powerpc-linux-gnu
        - libc6-dev-powerpc-cross

@dschaper
Copy link
Member

dschaper commented Jun 18, 2017

We use the container based Trusty build environment, which precludes the use of sudo in the containers. I'm looking at other options to build our binaries, but that's not too high on the priority list for back end operations. We may be able to add your snippet to the matrix to build out that binary, it does look like those packages are available in Trusty's repository.

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

No branches or pull requests

5 participants