From: Jun Sun <jsun@mvista.com>
To: 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: Tue, 03 Apr 2001 10:34:55 -0700 [thread overview]
Message-ID: <3ACA09BF.C8EF0D6C@mvista.com> (raw)
In-Reply-To: 20010403003059.E25228@paradigm.rfc822.org
Florian Lohoff wrote:
>
> On Tue, Apr 03, 2001 at 12:22:48AM +0200, Kevin D. Kissell wrote:
> >
> > I'm not sure exactly what you mean here. That no one would
> > consider using your Debian cross environment? That no one
>
> I am not building cross, i am not building the debian cross
> toolchain. Just for completeness.
>
> > would consider doing cross-development? What part of it
> > seems to you to be a show-stopper?
>
> A major problem get the thing in which the configure try to
> begin to build executables and guess on the behaviour of the
> OS to run on. This ends to be a hack and reminds me on
> "pre gnu configure" times where one had to deal
> with hundrets of "config.h" or "os.h" files.
>
While it is a pain for some packages, it is actually not too bad for most of
them. I think we (mvista) are rolling out cross-compiled 250+ packages for 5
major CPU architectures and 21 sub-architectures - where most of them are
based on debian sources. :-)
> If you are going to use anything like a package format
> might it be "rpm" or "deb" the dependencies tend to be
> utterly broken as the dependcies are guessed by stuff like
> "ldd" output and friends.
>
There are some tools which make it work right. mvista has one. I think
Merceij has one too.
Jun
next prev parent reply other threads:[~2001-04-03 17:39 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
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 [this message]
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=3ACA09BF.C8EF0D6C@mvista.com \
--to=jsun@mvista.com \
--cc=flo@rfc822.org \
--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 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.