public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* "make check" failure with sh-linux
@ 2001-05-27  0:02 H . J . Lu
  2001-05-27  4:49 ` kaz Kojima
  0 siblings, 1 reply; 4+ messages in thread
From: H . J . Lu @ 2001-05-27  0:02 UTC (permalink / raw)
  To: binutils; +Cc: kkojima

I got one "make check" failure in ld with sh-linux:

FAIL: SH relaxing to S-records


H.J.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: "make check" failure with sh-linux
  2001-05-27  0:02 "make check" failure with sh-linux H . J . Lu
@ 2001-05-27  4:49 ` kaz Kojima
  2001-05-28  3:56   ` Nick Clifton
  0 siblings, 1 reply; 4+ messages in thread
From: kaz Kojima @ 2001-05-27  4:49 UTC (permalink / raw)
  To: binutils

Hi,

"H . J . Lu" <hjl@lucon.org> wrote:
> I got one "make check" failure in ld with sh-linux:
> 
> FAIL: SH relaxing to S-records

This error comes from the defaulting entry addresses. It's set to
0x400000 with --oformat srec and 0x400080 for he ELF output format
in sh-linux case. How about the following patch to the test?

	kaz

Index: sh.exp
===================================================================
RCS file: /cvs/src/src/ld/testsuite/ld-sh/sh.exp,v
retrieving revision 1.3
diff -u -r1.3 sh.exp
--- sh.exp	2001/03/13 06:14:28	1.3
+++ sh.exp	2001/05/27 11:35:12
@@ -56,7 +56,14 @@
 
 set testsrec "SH relaxing to S-records"
 
-if ![ld_simple_link $ld tmpdir/sh1.s1 "-relax --oformat srec tmpdir/sh1.o"] {
+if [istarget sh*-linux-gnu] {
+    # This target needs the explicit entry address.
+    catch "exec $objdump -x tmpdir/sh1 | grep start\\ address | sed s/start\\ address//" entry_addr
+    set srec_relax_arg "-Ttext $entry_addr -relax --oformat srec tmpdir/sh1.o"
+} else {
+    set srec_relax_arg "-relax --oformat srec tmpdir/sh1.o"
+}
+if ![ld_simple_link $ld tmpdir/sh1.s1 $srec_relax_arg ] {
     fail $testsrec
 } else {
     # The file name is embedded in the S-records, so create both


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: "make check" failure with sh-linux
  2001-05-27  4:49 ` kaz Kojima
@ 2001-05-28  3:56   ` Nick Clifton
  2001-05-28  4:59     ` kaz Kojima
  0 siblings, 1 reply; 4+ messages in thread
From: Nick Clifton @ 2001-05-28  3:56 UTC (permalink / raw)
  To: kaz Kojima; +Cc: binutils

Hi Kaz,

Thanks very much for submitting this patch.

> > FAIL: SH relaxing to S-records
> 
> This error comes from the defaulting entry addresses. It's set to
> 0x400000 with --oformat srec and 0x400080 for he ELF output format
> in sh-linux case. How about the following patch to the test?

I have applied your patch to the sources.

In the future, please could you enclose a suitable ChangeLog entry (in
plain text) along with the patch itself.

Cheers
        Nick

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: "make check" failure with sh-linux
  2001-05-28  3:56   ` Nick Clifton
@ 2001-05-28  4:59     ` kaz Kojima
  0 siblings, 0 replies; 4+ messages in thread
From: kaz Kojima @ 2001-05-28  4:59 UTC (permalink / raw)
  To: binutils

Hi,

Nick Clifton <nickc@cambridge.redhat.com> wrote:
>>> FAIL: SH relaxing to S-records
>> 
>> This error comes from the defaulting entry addresses. It's set to
>> 0x400000 with --oformat srec and 0x400080 for he ELF output format
>> in sh-linux case. How about the following patch to the test?
>
> I have applied your patch to the sources.

Thanks!

> In the future, please could you enclose a suitable ChangeLog entry (in
> plain text) along with the patch itself.

My bad. Sorry for the inconvenience.

	kaz

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2001-05-28  4:59 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-27  0:02 "make check" failure with sh-linux H . J . Lu
2001-05-27  4:49 ` kaz Kojima
2001-05-28  3:56   ` Nick Clifton
2001-05-28  4:59     ` kaz Kojima

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).