Re: Building libstdc++

[Brent Verner <brent at rcfile dot org>]

On 26 Dec 2000 at 07:25 (-0500), Richard Kenner wrote:
|     Kenner, could you try Brent's patch and let us know if it works for you?
| 
| I didn't see a complete patch with the proper conditionalization, so there's
| nothing to try yet.  Obviously, if I'm getting complaints about certain
| lines, deleting them will "fix" the problem.  I believe I'm also getting
| errors on "/*" style comment lines, too.

The patch I sent (only to you) was indeed not production-ready, as I
don't know what macro protection (if any) is available to detect the
assembler being used. anyone know this magic?

I believe the /* comments */ in inlined asm are ok, at least the
assembler on the DEC Alpha I have access to accepted them.

| I'd like to understand what those psuedo-ops are there for, though,
| before we just delete them.  As to the comment lines, they clearly needn't
| be in the generated assembler code.

I, too, would like to see analogous asm directives for DEC's assembler,
but I definitely don't know either assembler well enough to provide
those on-the-spot, however you can read all about DEC asm at:
  
  http://tru64unix.compaq.com/faqs/publications/base_doc/DOCUMENTATION/V40D_HTML/APS31DTE/TITLE.HTM

perhaps some GNU as guru could help out by perusing that documentation
and finding the analogs to GNU as' .subsection and .previous directives :)

| Just for the heck of it, I temporarily deleted those pseudos and comment
| lines and tried again.  This time I got:
[snip]
| ../include/bits/ctype_inline.h:40: `__OBJ_DATA' undeclared (first use this
|    function)

for some reason configure is picking up config/os/aix/bits/ctype_inline.h
for your system. I'm going to try a build on the Alpha box sometime 
today, maybe I'll see where this problem is happening. 

cheers.
  brent