Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carsten Langgaard <carstenl@mips.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Jun Sun <jsun@mvista.com>,
	ralf@oss.sgi.com, vhouten@kpn.com, linux-mips@oss.sgi.com
Subject: Re: Updates on RedHat 7.1/mips
Date: Wed, 18 Jul 2001 09:13:20 +0200	[thread overview]
Message-ID: <3B553710.8B7A4CDE@mips.com> (raw)
In-Reply-To: 20010717122902.B24048@lucon.org

"H . J . Lu" wrote:

> On Tue, Jul 17, 2001 at 09:16:05PM +0200, Carsten Langgaard wrote:
> > Could you add a Perl rpm to you distribution, this also seems to be needed to
> > build the RPMs natively.
>
> Perl has to be built natively. I uploaded mysql-3.23.36-1.1.src.rpm,
> perl-5.6.0-12.1.src.rpm, apache-1.3.19-5.src.rpm,
> mod_perl-1.24_01-2.src.rpm, tcsh-6.10-5.src.rpm and
> zsh-3.0.8-8.src.rpm. Just installed my RedHat 7.1. Then you can build
> perl yourself. You may need to build/install the tcsh rpm first.

It look like there is a cross dependence, the build of tcsh failed with the
following message:

/var/tmp/rpm-tmp.7250: /usr/bin/perl: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.7250 (%build)

So tcsh is needed to build perl and perl is needed to build tcsh :-(

>
> >
> > I also would like to do a cross build, but how do I do that ?
> > Do I have to change all the spec files, to set the target arch to MIPS, or is
> > there a easier and better way to do that ?
> > I guess if I just install the SRPMs and the cross toolchain, and try to build
> > out of that I will simply build for the build platform, which is i386.
>
> You need my patched `rpm' to do cross build. You also need some
> specicial set up. I am enclosng a message of mine. I will see if
> I can cleanup my cross build environment and upload it.
>
> H.J.
> -----
> > they work great! Thanks for all your hard work. Now, I would like
> > to be able to build some RPMs as well. I have never cross-built
> > RPMs before. I took the SRPMS for make and tried:
> >
> >    rpm -ba make.spec --target=mipsel
> >
> > This did not do anything and built nothing. Is there a FAQ that
> > I can read on cross building RPMS in addition to the documentation
> > on http://www.rpm.org/ ? Do you have any quick pointers? Thanks
> > again.
>
> Although my source rpms do support cross compile, FYI, all my
> mips/mipsel rpms are cross compiled from ia32 machines, the
> unpatched rpm, that is /bin/rpm, doesn't support cross compile.
> In my RedHat 7.1, there are i386 rpm binaries which support
> cross compile. I have a setup to cross build rpms to mips/mipsel.
> Make sure your rpm sees
>
> %__ar                   %{_target_prefix}-linux-ar
> %__as                   %{_target_prefix}-linux-as
> %__cc                   %{_target_prefix}-linux-gcc
> %__cxx                  %{_target_prefix}-linux-c++
> %__ld                   %{_target_prefix}-linux-ld
> %__nm                   %{_target_prefix}-linux-nm
> %__objcopy              %{_target_prefix}-linux-objcopy
> %__objdump              %{_target_prefix}-linux-objdump
> %__ranlib               %{_target_prefix}-linux-ranlib
> %__strip                %{_target_prefix}-linux-strip
>

How do I do that ?

>
> and do
>
> # rpm --target=mips --define '_target_prefix mips'
>
> or
>
> # rpm --target=mipsel --define '_target_prefix mipsel'
>
> BTW, you alao need to rebuild binutils with
>
> # rpm --define 'ENABLE_ALL_TARGETS 1' -ta binutils-2.11.90.0.23.tar.gz
>
> H.J.

--
_    _ ____  ___   Carsten Langgaard   Mailto:carstenl@mips.com
|\  /|||___)(___   MIPS Denmark        Direct: +45 4486 5527
| \/ |||    ____)  Lautrupvang 4B      Switch: +45 4486 5555
  TECHNOLOGIES     2750 Ballerup       Fax...: +45 4486 5556
                   Denmark             http://www.mips.com

  parent reply	other threads:[~2001-07-18  7:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06  8:15 Illegal instruction Carsten Langgaard
2001-07-06  9:27 ` Houten K.H.C. van (Karel)
2001-07-06 11:42   ` Maciej W. Rozycki
2001-07-06 13:26 ` Dan Aizenstros
2001-07-06 22:04 ` Jun Sun
2001-07-10 11:14   ` Carsten Langgaard
2001-07-10 17:31     ` H . J . Lu
2001-07-16 11:26       ` Carsten Langgaard
2001-07-16 21:28         ` Updates on RedHat 7.1/mips H . J . Lu
2001-07-17 19:16           ` Carsten Langgaard
2001-07-17 19:29             ` H . J . Lu
2001-07-17 19:50               ` Daniel Jacobowitz
2001-07-17 19:57                 ` H . J . Lu
2001-07-17 20:09                   ` Ilya Volynets
2001-07-17 20:11                     ` H . J . Lu
2001-07-18  3:52                       ` Arnaldo Carvalho de Melo
2001-07-18  4:01                         ` Ilya Volynets
2001-07-18  7:13               ` Carsten Langgaard [this message]
2001-07-18 15:11                 ` H . J . Lu
2001-07-18 15:23                   ` Carsten Langgaard
2001-07-18 20:53                     ` Seth Mos
2001-07-19  0:36                       ` H . J . Lu
2001-07-19 21:03                         ` Seth Mos
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 12:07 Gleb O. Raiko
2001-07-18 13:26 Ralf Baechle
2001-07-18 16:48 ` Daniel Jacobowitz
2001-07-18 22:23   ` Ralf Baechle
2001-07-19 13:29     ` Florian Lohoff

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=3B553710.8B7A4CDE@mips.com \
    --to=carstenl@mips.com \
    --cc=hjl@lucon.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=vhouten@kpn.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox