Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jay Carlson" <nop@nop.com>
To: "Joe deBlaquiere" <jadb@redhat.com>, "Florian Lohoff" <flo@rfc822.org>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
	"MIPS/Linux List \(SGI\)" <linux-mips@oss.sgi.com>
Subject: RE: Dumb Question on Cross-Development
Date: Wed, 4 Apr 2001 11:17:39 -0400	[thread overview]
Message-ID: <KEEOIBGCMINLAHMMNDJNIEHHCAAA.nop@nop.com> (raw)
In-Reply-To: <3AC93C0B.5020102@redhat.com>

> Perfect it is not, but it's not nearly _that_ bad either. I would
> say 40% of the RPMs I've tried will configure out of the box for
> a cross build. Another 40% or so require a few "export
> ac_cv_sizeof_long=4" kind of settings to configure for a cross
> build. The remaining 20% are painful.

Yeah, and it's not so bad once you start building up a config.site file you
can reuse across builds.  I got this idea from the debian dpkg-cross
package.  For people who aren't debian-y, the idea is that you set
CONFIG_SITE to point at a file like
http://www.csee.umbc.edu/~acedil1/agenda/files/agenda-config.site and run
configure as normal.  (I don't think I like that particular file but it
should give you ideas.)

BTW dpkg-cross comes with a tool that does ldd via grepping through objdump
output.

Jay

WARNING: multiple messages have this Message-ID (diff)
From: "Jay Carlson" <nop@nop.com>
To: Joe deBlaquiere <jadb@redhat.com>, Florian Lohoff <flo@rfc822.org>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
	"MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
Subject: RE: Dumb Question on Cross-Development
Date: Wed, 4 Apr 2001 11:17:39 -0400	[thread overview]
Message-ID: <KEEOIBGCMINLAHMMNDJNIEHHCAAA.nop@nop.com> (raw)
Message-ID: <20010404151739.8DMobed5WH5ODaYaYpMwi0jBNeoc5O_D_gr1YSKysrU@z> (raw)
In-Reply-To: <3AC93C0B.5020102@redhat.com>

> Perfect it is not, but it's not nearly _that_ bad either. I would
> say 40% of the RPMs I've tried will configure out of the box for
> a cross build. Another 40% or so require a few "export
> ac_cv_sizeof_long=4" kind of settings to configure for a cross
> build. The remaining 20% are painful.

Yeah, and it's not so bad once you start building up a config.site file you
can reuse across builds.  I got this idea from the debian dpkg-cross
package.  For people who aren't debian-y, the idea is that you set
CONFIG_SITE to point at a file like
http://www.csee.umbc.edu/~acedil1/agenda/files/agenda-config.site and run
configure as normal.  (I don't think I like that particular file but it
should give you ideas.)

BTW dpkg-cross comes with a tool that does ldd via grepping through objdump
output.

Jay

  reply	other threads:[~2001-04-04 15:18 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 12:24 Dumb Question on Cross-Development Kevin D. Kissell
2001-04-02 12:24 ` Kevin D. Kissell
2001-04-02 13:14 ` Ralf Baechle
2001-04-02 13:14   ` Ralf Baechle
2001-04-02 19:20   ` Kevin D. Kissell
2001-04-02 19:20     ` Kevin D. Kissell
2001-04-02 21:48     ` Florian Lohoff
2001-04-02 22:22       ` Kevin D. Kissell
2001-04-02 22:22         ` Kevin D. Kissell
2001-04-02 22:30         ` Florian Lohoff
2001-04-03  2:57           ` Joe deBlaquiere
2001-04-04 15:17             ` Jay Carlson [this message]
2001-04-04 15:17               ` Jay Carlson
2001-04-03  6:11           ` Geert Uytterhoeven
2001-04-03  9:52             ` Maciej W. Rozycki
2001-04-03  9:50           ` Maciej W. Rozycki
2001-04-03 17:34           ` Jun Sun
2001-04-04 10:02             ` Florian Lohoff
2001-04-04 10:15               ` Geert Uytterhoeven
2001-04-04 11:02                 ` Florian Lohoff
2001-04-04 12:15                 ` Maciej W. Rozycki
2001-04-04 11:22               ` Alan Cox
2001-04-04 11:22                 ` Alan Cox
2001-04-04 16:05                 ` Florian Lohoff
2001-04-04 18:06               ` Jun Sun
2001-04-04 18:45                 ` Florian Lohoff
2001-04-06  9:37           ` Wichert Akkerman
2001-04-03  9:26       ` Maciej W. Rozycki
2001-04-03 15:10         ` Ralf Baechle
2001-04-04 12:06           ` Maciej W. Rozycki
2001-04-04 12:29             ` Ralf Baechle
2001-04-04 13:39               ` Maciej W. Rozycki
2001-04-04 14:23                 ` Carsten Langgaard
2001-04-04 15:37                   ` Maciej W. Rozycki
2001-04-05 10:54                     ` Carsten Langgaard
2001-04-05 12:05                       ` Maciej W. Rozycki
2001-04-05 14:35                         ` Carsten Langgaard
2001-04-05 16:50                           ` Maciej W. Rozycki
2001-04-05 12:32                       ` Ralf Baechle
2001-04-06 15:30                         ` Maciej W. Rozycki
2001-04-07 15:29                 ` Joe deBlaquiere
2001-04-09 12:16                   ` Maciej W. Rozycki
2001-04-02 21:56     ` Thiemo Seufer
2001-04-02 23:41 ` Binutils fixed to deal with 'insmod' issue and discussion Steven J. Hill
2001-04-03  2:17   ` Thiemo Seufer
2001-04-03  8:26     ` Ralf Baechle
2001-04-03 17:27       ` Steven J. Hill
2001-04-04  5:57         ` Andreas Jaeger
2001-04-04 16:12       ` Thiemo Seufer
2001-04-03 15:46     ` Steven J. Hill
2001-04-03 16:59   ` Maciej W. Rozycki
2001-04-03 16:56     ` Steven J. Hill
2001-04-04 11:35       ` Maciej W. Rozycki

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=KEEOIBGCMINLAHMMNDJNIEHHCAAA.nop@nop.com \
    --to=nop@nop.com \
    --cc=flo@rfc822.org \
    --cc=jadb@redhat.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@oss.sgi.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