Bug in installation instructions.

Thread View: gnu.g++.bug

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by pardo Thu, 11 May 1989 00:06

#1971

Author: pardo
Date: Thu, 11 May 1989 00:06

31 lines
1548 bytes

The file .../g++-include/stdio.h must be updated on a
machine-by-machine basis.  On *some* machines, the directive at line
55 of 1.35.2's stdio.h is simply wrong.

    #define SPRINTF_RETURNS_INT

It should be commented out.

I did not see particular warnings about this in the installation
guide.  In general, the preferred practice is that when no machine is
provided for machine-dependent code, the code will fail to compile.
IMHO, stdio's willingness to compile incorrectly is a bug.

The installation scripts could take care of patching up the .h files
to match the machine type, or the .h files should barf when they are
used the first time, or there should be a big red WARNING label in the
instructions (there might be one and I just missed it).

I can immagine a machine-dependent `profile':

    stdio.h:#define HAVE_BUFSIZE
    stdio.h:/* #define SPRINTF_RETURNS_INT */

and a magic comment in the .h file

    /*! patch */

and finally a `patchincludes' script that applies the correct
(machine-dependent) profile to each .h file at installation.

	;-D on  ( Soon: instructions for bug installation )  Pardo

Re: Bug in installation instructions.

#1972

Author: Doug Schmidt
Date: Thu, 11 May 1989 02:11

24 lines
1514 bytes

In article <8905110006.AA18733@june.cs.washington.edu> pardo@JUNE.CS.WASHINGTON.EDU writes:
++ I can immagine a machine-dependent `profile':
++ 
++     stdio.h:#define HAVE_BUFSIZE
++     stdio.h:/* #define SPRINTF_RETURNS_INT */
++ 
++ and a magic comment in the .h file
++ 
++     /*! patch */
++ 
++ and finally a `patchincludes' script that applies the correct
++ (machine-dependent) profile to each .h file at installation.

What we really need is a super-duper config program like the one that
Larry Wall supplies with PERL.  Any body out there know how to use
meta-config?  Anyone want to volunteer to supply this for g++ and
libg++?!

   Doug        
--
On a clear day, under blue skies, there is no need to seek.
And asking about Buddha                +------------------------+
Is like proclaiming innocence,         | schmidt@ics.uci.edu    |
With loot in your pocket.              | office: (714) 856-4043 |

bad crt1+.o

#1973

Author: Youda He
Date: Thu, 11 May 1989 05:04

9 lines
1066 bytes

after spend a day tried to install g++ 1.35.0- 7may + patches, I keep getting
bad crt1+.o on libg++(1.34 and 1.35), I get g++.xtar.Z and patches from 
yahi.stanford.edu after applied patches, I just do:
make maketest; config.g++ sun4-os4; make install; g++ compiled ok after
patched bison using README from g++, a test on libg++ test0 show crt1+.o
bad, I have bring up g++ before, (too bad I don't have them any more).
Bison is the current one (the one with -version option (1.01)). Is there any 
one have g++ (7may) working on sun4-os4, could you check the size of crt1+.o
I get 1793 us ls -l crt1+;  Thanks !

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads