All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: Sparc-32 debian wheezy package repository at http://developer.gaisler.net/debian/
Date: Wed, 04 Apr 2012 07:30:42 +0000	[thread overview]
Message-ID: <4F7BF8A2.9010106@gaisler.com> (raw)
In-Reply-To: <4F7BF320.1040506@gaisler.com>

Julian Calaby wrote:
> Hi Konrad,
>
> On Wed, Apr 4, 2012 at 17:07, Konrad Eisele<konrad@gaisler.com>  wrote:
>> Debian wheezy sparc-32 package repository:
>> http://developer.gaisler.net/debian/
>
> Awesome work!
>
>> For cross compilation of debian packages there is a
>> sparc-linux-gnu crosscompiler with many libraries preinstalled:
>> http://developer.gaisler.net/debian/cross-compiler/sparc-linux-gnu-cross_1.0.0-1_amd64.deb
>> This package is for a 64-bit machine.
>
> crosstool-ng (which Sam has contributed Sparc support to) is another
> way to easily build a cross compiler. buildroot is another
> alternative.

The one above has a lot of headers and libxxx-dev-sparc-cross.dev  packages installed by default.
It is a multiarch compiler for debian-64-wheezy. You can build new cross package by:
$apt-get source <name>
$cd <dir>
$dpkg-buildpackage -asparc -us -uc -rfakeroot -b
Then you convert  the .deb to multiarch:
$export CC=sparc-linux-gnu-gcc
and install the "dev" deb oackages:
$dpkg-cross -A -M -a sparc -b <dev-name>.deb
$sudo dpkg -i <dev-name-sparc-cross>.deb
Most of the time you have to fiddle with he buildscripts though.
You need to be in a debian-64 wheezy distribution. (I use a 64-bit virtual virtualbox
and netinst from http://www.debian.org/devel/debian-installer/).

-- Konrad

>
> Thanks,
>


      parent reply	other threads:[~2012-04-04  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  7:07 Sparc-32 debian wheezy package repository at http://developer.gaisler.net/debian/ Konrad Eisele
2012-04-04  7:25 ` Julian Calaby
2012-04-04  7:30 ` Konrad Eisele [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F7BF8A2.9010106@gaisler.com \
    --to=konrad@gaisler.com \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.