public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k
@ 2004-04-22 15:57 Dan Kegel
  2004-04-26 22:00 ` Jim Wilson
  2004-04-27 13:17 ` Andreas Schwab
  0 siblings, 2 replies; 4+ messages in thread
From: Dan Kegel @ 2004-04-22 15:57 UTC (permalink / raw)
  To: Binutils, GCC Mailing List

While testing all the targets crosstool supports with the new combination of tools
(gcc-3.4.0 and binutils-2.15.90.0.3),
I ran into an error with --host=x86-linux --target m68k-linux:

localealias.s:544: Error: junk at end of line, first unrecognized character is `,'

Here are lines 544 to 546 of localealias.s:
     544         .local  lock
     545         .comm   lock,24,2
     546         .section        __libc_freeres_ptrs
So I guess it didn't like the ,24,2 on the .comm line.

Since I changed both gcc and binutils versions at once,
I have no idea which of the two changes triggered the problem.

This reminds me a bit of the problem I had compiling
that combination for --host=x86-cygwin --target=x86-linux,
maybe some configury bit is screwed up somewhere in gcc-3.4.0.

I'll leave demo-m68k.sh at gcc-3.3.3 for the moment.  One of
these days I'll try to track this down, maybe.
- Dan

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

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

* Re: problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k
  2004-04-22 15:57 problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k Dan Kegel
@ 2004-04-26 22:00 ` Jim Wilson
  2004-04-27 13:17 ` Andreas Schwab
  1 sibling, 0 replies; 4+ messages in thread
From: Jim Wilson @ 2004-04-26 22:00 UTC (permalink / raw)
  To: Dan Kegel; +Cc: binutils, gcc

Dan Kegel wrote:
> Here are lines 544 to 546 of localealias.s:
>     544         .local  lock
>     545         .comm   lock,24,2
>     546         .section        __libc_freeres_ptrs
> So I guess it didn't like the ,24,2 on the .comm line.

This assembler syntax is fairly common, and has been supported for a 
long time.  It works fine if I build a cross assembler to m68k-linux 
from current FSF development sources.

Perhaps gas was miscompiled.  It is also possible gas was misconfigured, 
but if so this would have to be pretty a pretty obvious error which 
should be easy to spot.

The flow in gas should be obj_elf_common, s_comm_internal, 
elf_common_parse, parse_align, and when parse_align returns, 
input_line_pointer should be pointing at the end of the input line (or 
perhaps pointing as whitespace).
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

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

* Re: problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k
  2004-04-22 15:57 problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k Dan Kegel
  2004-04-26 22:00 ` Jim Wilson
@ 2004-04-27 13:17 ` Andreas Schwab
  2004-04-27 13:51   ` Dan Kegel
  1 sibling, 1 reply; 4+ messages in thread
From: Andreas Schwab @ 2004-04-27 13:17 UTC (permalink / raw)
  To: Dan Kegel; +Cc: Binutils, GCC Mailing List

Dan Kegel <dank@kegel.com> writes:

> While testing all the targets crosstool supports with the new combination of tools
> (gcc-3.4.0 and binutils-2.15.90.0.3),
> I ran into an error with --host=x86-linux --target m68k-linux:
>
> localealias.s:544: Error: junk at end of line, first unrecognized character is `,'
>
> Here are lines 544 to 546 of localealias.s:
>      544         .local  lock
>      545         .comm   lock,24,2
>      546         .section        __libc_freeres_ptrs
> So I guess it didn't like the ,24,2 on the .comm line.

No, gas is actually complaining about line 547 (it does not properly count
lines in #APP/#NO_APP sections).  See the thread starting at
<http://sources.redhat.com/ml/binutils/2004-04/msg00646.html>.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

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

* Re: problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k
  2004-04-27 13:17 ` Andreas Schwab
@ 2004-04-27 13:51   ` Dan Kegel
  0 siblings, 0 replies; 4+ messages in thread
From: Dan Kegel @ 2004-04-27 13:51 UTC (permalink / raw)
  To: Andreas Schwab; +Cc: Binutils, GCC Mailing List

Andreas Schwab wrote:
> Dan Kegel <dank@kegel.com> writes:
> 
> 
>>While testing all the targets crosstool supports with the new combination of tools
>>(gcc-3.4.0 and binutils-2.15.90.0.3),
>>I ran into an error with --host=x86-linux --target m68k-linux:
>>
>>localealias.s:544: Error: junk at end of line, first unrecognized character is `,'
>>
>>Here are lines 544 to 546 of localealias.s:
>>     544         .local  lock
>>     545         .comm   lock,24,2
>>     546         .section        __libc_freeres_ptrs
>>So I guess it didn't like the ,24,2 on the .comm line.
> 
> No, gas is actually complaining about line 547 (it does not properly count
> lines in #APP/#NO_APP sections).  See the thread starting at
> <http://sources.redhat.com/ml/binutils/2004-04/msg00646.html>.

Thanks, Andreas!  I'll apply that patch to binutils-2.15.90.0.3 in the next release of crosstool.
- Dan

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

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

end of thread, other threads:[~2004-04-27 13:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-22 15:57 problem building glibc-2.3.2 with gcc-3.4.0 and binutils-2.15.90.0.3 for m68k Dan Kegel
2004-04-26 22:00 ` Jim Wilson
2004-04-27 13:17 ` Andreas Schwab
2004-04-27 13:51   ` Dan Kegel

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