Difference between revisions of "GenLink to SabLink for ARM9"

From NAS-Central Buffalo - The Linkstation Wiki
Jump to: navigation, search
Line 1: Line 1:
−
 
 
'''''Site under construction'''''
 
'''''Site under construction'''''
  
Line 6: Line 5:
  
 
== Get The Genlink up to date ==
 
== Get The Genlink up to date ==
 +
 +
First you need to update your gentoo that way you can use the sabayon tools
 +
 +
change the used BINHOST in /etc/make.conf to
 +
 +
PORTAGE_BINHOST="http://pkgs.sablink.nas-central.org/genlink/"                                           
 +
 +
This Binhost contains the needed updates for sablink
 +
 +
now update the packages to the right version because the new packages are eapi masked we have to trick the install
 +
 +
  emerge --getbinpkgonly --usepkgonly -O python:2.7
 +
 +
then add the add the eselct-python
 +
 +
  emerge --getbinpkgonly --usepkgonly -O eselect-python
 +
 +
now select python 2.7
 +
 +
eselect python list
 +
eselect python set x
 +
 +
now force the right version of portage
 +
 +
  emerge --getbinpkgonly --usepkgonly -O portage
 +
 +
now install the tools used by equo
 +
 +
  emerge --getbinpkgonly --usepkgonly shadow
 +
 +
and now get the sablink tools installed
 +
 +
  emerge --getbinpkgonly --usepkgonly equo
 +
 +
and get the core files for sablink
 +
 +
  emerge --getbinpkgonly --usepkgonly -O sablink-core
 +
 +
now your system is prepared for sablink system
 +
 +
 +
== Change the CHOST and force entropy Arch ==
 +
now you system is still aof type armv5tejl
 +
it needs to be changed to armv5tel (the j is standing for Arm Jazzel but no linux version is supporting it native so no need for it; arm also removed proper Jazzel support in newer processors)
 +
 +
change the /etc/make.conf from
 +
 +
CHOST="armv5tejl-softfloat-linux-gnueabi"
 +
 +
to
 +
 +
CHOST="armv5tel-softfloat-linux-gnueabi"
 +
 +
now force the proper arch also for the entropy package manager (if you type uname -a its still armv5tejl)
 +
 +
echo "armv5tel" > /etc/entropy/.arch
 +
 +
now your system is prepared for the migration to SabLink
 +
  
  

Revision as of 10:27, 9 November 2012

Site under construction

Converting a GenLink Installation to an Sablink system is a tricky process becuase the gcc from the genlink is unable to compile new packages without errors so a new genlink was created with a proper gcc to compile all the required apdates to move to SabLink


Get The Genlink up to date

First you need to update your gentoo that way you can use the sabayon tools

change the used BINHOST in /etc/make.conf to 

PORTAGE_BINHOST="http://pkgs.sablink.nas-central.org/genlink/"

This Binhost contains the needed updates for sablink

now update the packages to the right version because the new packages are eapi masked we have to trick the install 

 emerge --getbinpkgonly --usepkgonly -O python:2.7

then add the add the eselct-python 

 emerge --getbinpkgonly --usepkgonly -O eselect-python

now select python 2.7 

eselect python list
eselect python set x

now force the right version of portage 

 emerge --getbinpkgonly --usepkgonly -O portage

now install the tools used by equo 

 emerge --getbinpkgonly --usepkgonly shadow

and now get the sablink tools installed 

 emerge --getbinpkgonly --usepkgonly equo

and get the core files for sablink 

 emerge --getbinpkgonly --usepkgonly -O sablink-core

now your system is prepared for sablink system


Change the CHOST and force entropy Arch

now you system is still aof type armv5tejl it needs to be changed to armv5tel (the j is standing for Arm Jazzel but no linux version is supporting it native so no need for it; arm also removed proper Jazzel support in newer processors)

change the /etc/make.conf from 

CHOST="armv5tejl-softfloat-linux-gnueabi"

to 

CHOST="armv5tel-softfloat-linux-gnueabi"

now force the proper arch also for the entropy package manager (if you type uname -a its still armv5tejl) 

echo "armv5tel" > /etc/entropy/.arch

now your system is prepared for the migration to SabLink

Retrieved from "http://buffalo.nas-central.org/w/index.php?title=GenLink_to_SabLink_for_ARM9&oldid=32013"