All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: sparclinux@vger.kernel.org
Subject: crosstool-0.28-rc13: add sparc64 support
Date: Mon, 10 May 2004 05:01:54 +0000	[thread overview]
Message-ID: <409F0CC2.1040002@kegel.com> (raw)

Thanks to some quick help from H.J.Lu and patient
testing by M.H.VanLeeuwen, the 0.28-rc13 snapshot of crosstool now builds
gcc-3.4.0-glibc-2.3.2 cross-compilers targeting sparc64-linux.

Please give it a try and report any problems here or
on the crossgcc mailing list.
You can download it from
   http://kegel.com/crosstool/

Changelog:

0.28-rc13:
      arm:
      * Thanks to mroehner@gmx dot de for his crossgcc post of 9 May 2004,
        which suggested the following changes:
        - got rid of symlinks in patches/glibc-2.3.2 to avoid Windows problems
        - use 2.4 kernel headers until arm can build with 2.6 headers
        - moved contrib/glibc-vfp.patch to patches/glibc-2.3.2,
          as it seems to solve problems even when using hard float

      sparc64:
      * H.J.Lu and M.H.VanLeeuwen helped with http://gcc.gnu.org/PR15345;
        see patches/glibc-2.3.2/glibc-2.3.2-sparc64-dl-machine.patch

      misc:
      * fixed typo in chrootshell.c's die() macro that suppressed error text

0.28-rc12:
      x86_64:
      * added x86_64.config, generated by linux-2.6.5's "make allnoconfig"; seems
        to be needed for glibc-2.3.2 on x86_64 + gcc-3.4.0
      * added patches/linux-2.6.5/linux-2.6.5-x86_64-unistd.patch
        to fix x86_64 build with kernel 2.6.5
...

-- 
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

                 reply	other threads:[~2004-05-10  5:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=409F0CC2.1040002@kegel.com \
    --to=dank@kegel.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.