* RE: Problem with linking a.out-i386 files on a solaris host
@ 2003-03-05 18:51 Carl Petersen
0 siblings, 0 replies; 3+ messages in thread
From: Carl Petersen @ 2003-03-05 18:51 UTC (permalink / raw)
To: Nick Clifton; +Cc: binutils
That worked.
Thanks
-----Original Message-----
From: Nick Clifton [mailto:nickc@redhat.com]
Sent: Wednesday, March 05, 2003 7:47 AM
To: Carl Petersen
Cc: binutils@sources.redhat.com
Subject: Re: Problem with linking a.out-i386 files on a solaris host
Hi Carl,
> I have built the most recent binutils with support for all possible
> targets.
>
> When I execute:
>
> ld -b a.out-i386 file1.o file2.o file3.o file4.o --oformat a.out-i386 -o outfile
>
> I get warnings like
>
> 'ld: warning: i386 architecture of input file `file1.o' is incompatible with sparc output'
These warnings can be suppressed with the "--no-warn-mismatch" switch,
but I guess that this is not what you really want.
> But I am not trying to generate a sparc output file. I am in fact trying to generate a
> a.out-i386 output file.
Indeed - it seems that the --oformat functionality of the linker is
severely broken. If the specified output format is not a variation of
the default output format the linker does not behave very well at
all. I would recommend, for now, that you build an a.out-i386
targeted, sparc hosted linker instead and use that to create your
'outfile' binary.
Cheers
Nick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Problem with linking a.out-i386 files on a solaris host
2003-03-03 22:59 Carl Petersen
@ 2003-03-05 13:45 ` Nick Clifton
0 siblings, 0 replies; 3+ messages in thread
From: Nick Clifton @ 2003-03-05 13:45 UTC (permalink / raw)
To: Carl Petersen; +Cc: binutils
Hi Carl,
> I have built the most recent binutils with support for all possible
> targets.
>
> When I execute:
>
> ld -b a.out-i386 file1.o file2.o file3.o file4.o --oformat a.out-i386 -o outfile
>
> I get warnings like
>
> 'ld: warning: i386 architecture of input file `file1.o' is incompatible with sparc output'
These warnings can be suppressed with the "--no-warn-mismatch" switch,
but I guess that this is not what you really want.
> But I am not trying to generate a sparc output file. I am in fact trying to generate a
> a.out-i386 output file.
Indeed - it seems that the --oformat functionality of the linker is
severely broken. If the specified output format is not a variation of
the default output format the linker does not behave very well at
all. I would recommend, for now, that you build an a.out-i386
targeted, sparc hosted linker instead and use that to create your
'outfile' binary.
Cheers
Nick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Problem with linking a.out-i386 files on a solaris host
@ 2003-03-03 22:59 Carl Petersen
2003-03-05 13:45 ` Nick Clifton
0 siblings, 1 reply; 3+ messages in thread
From: Carl Petersen @ 2003-03-03 22:59 UTC (permalink / raw)
To: binutils
I have built the most recent binutils with support for all possible targets.
When I execute:
ld -b a.out-i386 file1.o file2.o file3.o file4.o --oformat a.out-i386 -o outfile
I get warnings like
'ld: warning: i386 architecture of input file `file1.o' is incompatible with sparc output'
But I am not trying to generate a sparc output file. I am in fact trying to generate a
a.out-i386 output file.
Thanks
Carl Petersen
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-03-05 18:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-05 18:51 Problem with linking a.out-i386 files on a solaris host Carl Petersen
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 22:59 Carl Petersen
2003-03-05 13:45 ` Nick Clifton
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).