From ArchWiki
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start Template:Article summary text Template:Article summary end

Note: Currently there is no SPArch installation media so you must follow steps along the lines of Install from Existing Linux. Note also that there are not many repositories currently, and they do not have many packages.

Installing pacman on your host system

First you need to get pacman:

$ wget

If you do not mind littering your root, you can install pacman this way:

# cd /
# tar xzf /where/put/pacman-3.4.1-1-sparc64.pkg.tar.gz

Once you have pacman on your host system, you will need to edit pacman.conf. Tell pacman to use one of the SPArch package repositories.

# vim /etc/pacman.conf
Server =$repo/os/$arch/
Server =$repo/os/$arch/

In order for pacman to work, you may also need to first install some other packages. In Debian testing, I had to install xz-utils and libarchive-dev. I then had to install libfetch and openssl from the SPArch repository

$ wget
$ wget
$ cd /
# tar xzf /path/to/openssl
# tar xzf /path/to/libfetch

Setting up a chroot

For this section follow the directions on Install_from_Existing_Linux.

Building a bootable base system

Since packages are missing from the SPArch repository, you will have to build some yourself to get a working system. To do this, you will want to either install abs into your chroot or on your host (depending on whether your chroot has enough to compile what you need) and then modify makepkg.conf for building sparc packages.

# vim /etc/makepkg.conf
CFLAGS="-O2 -pipe -mcpu=v9"
CXXFLAGS="-O2 -pipe -mcpu=v9"
Note: If you want to create 64 bit binaries, you must use the -m64 flag. Otherwise, on a v9 system you will get 32 bit v8+ binaries. Most of the time you probably do not want 64 bit binaries: they will use more memory and be slower unless processing large data.

If you plan to share the packages you build, please also set the PACKAGER variable and make sure PKGEXT is '.pkg.tar.xz'

To update a PKGBUILD for building for sparc64:

sed -i.old "s/arch=(/arch=('sparc64' /" PKGBUILD

Sharing your packages with others

We need to figure out how to maintain the sparc repositories so that we can spread out the work of keeping a working set packages available to others. --DaveKong 01:47, 8 November 2010 (EST)

Packages needed for a base system (sparc64)


  • attr
  • bash
  • binutils
  • bzip2
  • coreutils
  • cryptsetup
  • dash
  • dcron
  • device-mapper
  • dhcpcd
  • diffutils
  • e2fsprogs
  • file
  • filesystem
  • findutils
  • gawk
  • gcc-libs
  • gen-init-cpio
  • gettext
  • glibc
  • grep
  • grub
  • gzip
  • initscripts
  • iputils
  • jfsutils
  • kernel26
  • less
  • libusb
  • licenses
  • logrotate
  • lzo2
  • mailx
  • man-db
  • man-pages
  • mdadm
  • net
  • pacman
  • pam
  • pciutils
  • pcmciautils
  • perl
  • ppp
  • procps
  • psmisc
  • reiserfsprogs
  • rp-pppoe
  • sed
  • shadow
  • sysfsutils
  • syslog-ng
  • sysvinit
  • tar
  • tcp_wrappers
  • texinfo
  • udev
  • usbutils
  • util-linux-ng
  • vi
  • wget
  • which
  • wpa_supplicant
  • xfsprogs


  • autoconf
  • automake
  • bison
  • fakeroot
  • flex
  • gcc
  • libtool
  • m4
  • make
  • patch
  • pkg-config