public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: binutils@sourceware.cygnus.com
Cc: Richard Henderson <rth@cygnus.com>, "David S. Miller" <davem@redhat.com>
Subject: [PATCH] HOSTING_* definitions for sparc*-*linux-gnu*
Date: Sun, 08 Aug 1999 04:28:00 -0000	[thread overview]
Message-ID: <19990808132932.F545@mff.cuni.cz> (raw)

Hi!

When trying to check ld testsuite I found out sparc*linux does not have any
entries in configure.host, so bootstrap checks all failed.
But after applying this patch, the testsuite passed completely, so I will
have to dig more deeply into the shared libs on Solaris problem.
I recall davem's patch was written exactly because SparcLinux had major
problems with running non-PIC code linked into shared libraries.

1999-08-08  Jakub Jelinek  <jj@ultra.linux.cz>

	* configure.host: Set up HOSTING_CRT0 and HOSTING_LIBS for
	sparc*-*linux-gnu*.

--- ./configure.host.jj	Fri Jul 23 15:31:49 1999
+++ ./configure.host	Sun Aug  8 10:41:53 1999
@@ -173,4 +173,14 @@ sparc*-*-solaris2*)
   NATIVE_LIB_DIRS=/usr/ccs/lib
   ;;
 
+sparc-*-linux-gnu*)
+  HOSTING_CRT0='-dynamic-linker /lib/ld-linux.so.2 `gcc --print-file-name=crt1.o` `gcc --print-file-name=crti.o` `if [ -f ../gcc/crtbegin.o ]; then echo ../gcc/crtbegin.o; else gcc --print-file-name=crtbegin.o; fi`'
+  HOSTING_LIBS='`if [ -f ../gcc/libgcc.a ] ; then echo ../gcc/libgcc.a ; else gcc -print-libgcc-file-name; fi` -L`dirname \`gcc --print-file-name=libc.so\`` -lc `if [ -f ../gcc/libgcc.a ] ; then echo ../gcc/libgcc.a ; else gcc -print-libgcc-file-name; fi` `if [ -f ../gcc/crtend.o ]; then echo ../gcc/crtend.o; else gcc --print-file-name=crtend.o; fi` `gcc --print-file-name=crtn.o`'
+  ;;
+
+sparc64-*-linux-gnu*)
+  HOSTING_CRT0='-dynamic-linker /lib64/ld-linux.so.2 `gcc --print-file-name=crt1.o` `gcc --print-file-name=crti.o` `if [ -f ../gcc/crtbegin.o ]; then echo ../gcc/crtbegin.o; else gcc --print-file-name=crtbegin.o; fi`'
+  HOSTING_LIBS='`if [ -f ../gcc/libgcc.a ] ; then echo ../gcc/libgcc.a ; else gcc -print-libgcc-file-name; fi` -L`dirname \`gcc --print-file-name=libc.so\`` -lc `if [ -f ../gcc/libgcc.a ] ; then echo ../gcc/libgcc.a ; else gcc -print-libgcc-file-name; fi` `if [ -f ../gcc/crtend.o ]; then echo ../gcc/crtend.o; else gcc --print-file-name=crtend.o; fi` `gcc --print-file-name=crtn.o`'
+  ;;
+
 esac

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux  |  http://ultra.linux.cz/  |  http://ultra.penguin.cz/
Linux version 2.3.13 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________

             reply	other threads:[~1999-08-08  4:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-08  4:28 Jakub Jelinek [this message]
1999-08-08  9:05 ` H.J. Lu

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=19990808132932.F545@mff.cuni.cz \
    --to=jj@sunsite.ms.mff.cuni.cz \
    --cc=binutils@sourceware.cygnus.com \
    --cc=davem@redhat.com \
    --cc=rth@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).