Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] Undo [PATCH v2] Mark MIPS I, II, III and IV as deprecated
Date: Tue, 04 Feb 2014 22:39:46 -0500	[thread overview]
Message-ID: <52F1B282.1040106@gentoo.org> (raw)

Per this thread/patch here:
http://lists.busybox.net/pipermail/buildroot/2013-November/082976.html

I'd like to point out that these CPU ISAs are not completely "deprecated"
nor rare.  Well, MIPS-I and MIPS-II might be "rare", but MIPS-III and
MIPS-IV are the minimum required ISAs for old SGI systems, which are most
plentiful on eBay.  Gentoo and Debian support Indy, Indigo2, and O2-based
systems, most of which need MIPS-IV (the R4x00 Indy's and I2's need MIPS-III
at a minimum).

I've been looking at buildroot as a way to quickly generate a working root
filesystem for netboot images, but I ran into a side-effect of this patch
when building 'attr':

/usr/space/buildroot/buildroot-2013.11/output/host/usr/lib/gcc/mips-buildroot-linux-uclibc/4.8.2/../../../../mips-buildroot-linux-uclibc/bin/ld:
/tmp/ccHuCGCg.o: linking mips:8000 module with previous mips:isa32 modules

/usr/space/buildroot/buildroot-2013.11/output/host/usr/lib/gcc/mips-buildroot-linux-uclibc/4.8.2/../../../../mips-buildroot-linux-uclibc/bin/ld:
failed to merge target specific data of file /tmp/ccHuCGCg.o

I was passing '-march=mips4' to the build, which resulted in the error.
After finding this patch, activating BR2_DEPRECATED, and selecting "mips
iv", the build completed fine.

Does deprecation imply removal at some point in the future?  I'd argue in
favour of keeping them around, but either restricting them to a
machine-specific build (such as creating a sub-family for SGI systems and
setting them there), and keeping the new defaults for mips/mipsel at
mips32/mips64 ISAs.

Thanks!,

-- 
Joshua Kinard
Gentoo/MIPS
kumba at gentoo.org
4096R/D25D95E3 2011-03-28

"The past tempts us, the present confuses us, the future frightens us.  And
our lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140204/786b0989/attachment.asc>

             reply	other threads:[~2014-02-05  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  3:39 Joshua Kinard [this message]
2014-02-05 11:12 ` [Buildroot] Undo [PATCH v2] Mark MIPS I, II, III and IV as deprecated Markos Chandras
2014-02-05 20:52 ` Arnout Vandecappelle
2014-02-05 23:11   ` Joshua Kinard
2014-02-06 17:52     ` Arnout Vandecappelle

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=52F1B282.1040106@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=buildroot@busybox.net \
    /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