Binhost

BlueKnight

The Information on how to set up your environment for utilizing the Gentoo binhost repository is below. You will need to have ability to modify your “/etc/portage/make.conf” file to make the following changes.

The setup is here for the following Binhost systems:

  • Arm v6
  • Arm v7
  • Gentoo x86
  • Gentoo x86 with KDE
  • Gentoo amd64
  • Gentoo amd64 with KDE
  • KVM with QEMU

Armv6 Binhost

The Armv6 Binhost is compiled on the Raspberry Pi’s, it can be set up by editing the “/etc/portage/make.conf” file and adding the following line:

PORTAGE_BINHOST=”http://tscbinhost.technologysecure.com/packages-arm6/”

This will reference the binhost location. Also please be aware that the Binary host was set up with the default profile list. To get the profile list to see what you are set up as use the following:

root# eselect profile list

Everything was compiled for the following profile:

[23] default/linux/arm/13.0/armv6j *

That means if you want to use another profile, these binary files might not apply. Also the default CPU settings for this were:

SETTINGS FOR CPU 

CHOST=”armv6j-hardfloat-linux-gnueabi”
CFLAGS=”-O2 -pipe -march=armv6j -mfpu=vfp -mfloat-abi=hard”
CXXFLAGS=”${CFLAGS}”

You also need to modification to the USE flag line to contain the following USE Flags. We try not to use USE flags but sometimes they are needed like the one for the binary distribution. In /etc/portage/make.conf modify the following line to say this.

USE="alsa fbdev evdev tslib lirc"

Sometimes instead of adding a global use flags a specific use flag is added to the following files. For this Binary host the following has been added to the package.use file

Link to the Package Use for Arm 6

 

 

 Armv7 Binhost

The Armv7 Binhost can be set up by editing the “/etc/portage/make.conf” file and adding the following line:

PORTAGE_BINHOST=”http://tscbinhost.technologysecure.com/packages-armv7/”

This will reference the binhost location. Also please be aware that the Binary host was set up with the default profile list. To get the profile list to see what you are set up as use the following:

root # eselect profile list

Everything was compiled for the following profile:

[23] default/linux/arm/13.0/armv6j *

That means if you want to use another profile, these binary files might not apply. Also the default CPU settings for this were:

SETTINGS FOR CPU

CHOST=”armv7a-hardfloat-linux-gnueabi”
CFLAGS=”-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard”
CXXFLAGS=”${CFLAGS}”

You also need to modification to the USE flag line to contain the following USE Flags. We try not to use USE flags but sometimes they are needed like the one for the binary distribution. In /etc/portage/make.conf modify the following line to say this.

USE="threads -X"

Sometimes instead of adding a global use flags a specific use flag is added to the following files. For this Binary host the following has been added to the package.use file:

 

Link to the Package Use file for Arm7

 


Gentoo X86 Binhost

The 32 Bit Binhost can be set up by editing the “/etc/portage/make.conf” file and adding the following line:

PORTAGE_BINHOST=”http://tscbinhost.technologysecure.com/packages-x86/”

This will reference the binhost location. Also please be aware that the Binary host was set up with the default profile list. To get the profile list to see what you are set up as use the following:

root # eselect profile list

Everything was compiled for the following profile:

[1] default/linux/x86/13.0 *

That means if you want to use another profile, these binary files might not apply. Also the default CPU settings for this were:

SETTINGS FOR CPU

CHOST=”i686-pc-linux-gnu”
CFLAGS=”-O2 -march=core2 -pipe”
CXXFLAGS=”${CFLAGS}”

You also need to modification to the USE flag line to contain the following USE Flags. We try not to use USE flags but sometimes they are needed like the one for the binary distribution. In /etc/portage/make.conf modify the following line to say this.

USE=" "

Sometimes instead of adding a global use flags a specific use flag is added to the following files. For this Binary host the following has been added to the package.use file:

 

Link to x86 (32 Bit) Package use File

 


Gentoo X86-kde Binhost

The 32 Bit KDE Binhost can be set up by editing the “/etc/portage/make.conf” file and adding the following line:

PORTAGE_BINHOST=”http://tscbinhost.technologysecure.com/packages-x86-kde/”

This will reference the binhost location. Also please be aware that the Binary host was set up with the default profile list. To get the profile list to see what you are set up as use the following:

root # eselect profile list

Everything was compiled for the following profile:

[8]   default/linux/x86/13.0/desktop/plasma *

That means if you want to use another profile, these binary files might not apply. Also the default CPU settings for this were:

SETTINGS FOR CPU
CHOST=”i686-pc-linux-gnu”
CFLAGS=”-O2 -march=core2 -pipe”
CXXFLAGS=”${CFLAGS}”

You also need to modification to the USE flag line to contain the following USE Flags. We try not to use USE flags but sometimes they are needed like the one for the binary distribution. In /etc/portage/make.conf modify the following line to say this.

USE="X udev"

Sometimes instead of adding a global use flags a specific use flag is added to the following files. For this Binary host the following has been added to the package.use file:

Link to Package Use file for X86 (32 Bit) KDE

 


Gentoo 64 Bit Binhost

The 64 Bit Binhost can be set up by editing the “/etc/portage/make.conf” file and adding the following line:

PORTAGE_BINHOST=”http://tscbinhost.technologysecure.com/packages-amd64/”

This will reference the binhost location. Also please be aware that the Binary host was set up with the default profile list. To get the profile list to see what you are set up as use the following:

root # eselect profile list

Everything was compiled for the following profile:

[1] default/linux/amd64/13.0 *

That means if you want to use another profile, these binary files might not apply. Also the default CPU settings for this were:

SETTINGS FOR CPU

CHOST=”x86_64-pc-linux-gnu”
CFLAGS=”-march=corei7 -O2 -pipe”
CXXFLAGS=”${CFLAGS}”

You also need to modification to the USE flag line to contain the following USE Flags. We try not to use USE flags but sometimes they are needed like the one for the binary distribution. In /etc/portage/make.conf modify the following line to say this.

USE=" "

Sometimes instead of adding a global use flags a specific use flag is added to the following files. For this Binary host the following has been added to the package.use file:

 

Link to Package Use Content for amd64 (64 Bit) BInhost

 


Gentoo 64 KDE Bit Binhost

The 64 KDE Bit Binhost can be set up by editing the “/etc/portage/make.conf” file and adding the following line:

PORTAGE_BINHOST=”http://tscbinhost.technologysecure.com/packages-amd64-kde”

This will reference the binhost location. Also please be aware that the Binary host was set up with the default profile list. To get the profile list to see what you are set up as use the following:

root # eselect profile list

Everything was compiled for the following profile:

[8]   default/linux/x86/13.0/desktop/plasma *

That means if you want to use another profile, these binary files might not apply. Also the default CPU settings for this were:

SETTINGS FOR CPU
CHOST=”x86_64-pc-linux-gnu”
CFLAGS=”-march=corei7 -O2 -pipe”
CXXFLAGS=”${CFLAGS}”

You also need to modification to the USE flag line to contain the following USE Flags. We try not to use USE flags but sometimes they are needed like the one for the binary distribution. In /etc/portage/make.conf modify the following line to say this.

USE="X udev"

Sometimes instead of adding a global use flags a specific use flag is added to the following files. For this Binary host the following has been added to the package.use file:

 

Link to amd64 (64 Bit) Package Use File.