🚀 go-pugleaf

A copy of this text has been sent to bug-glibc@prep.ai.mit.edu 


I'm installing glibc-1.05 on a sun4c running SunOS 4.1.1
I'm using gcc-2.2.2 and make-3.62

> How to Install the GNU C Library
>    Installation of the GNU C library is relatively simple.

I configured like:
    $ ./configure sparc-sun-sunos4.1.1 --with-gnu-ld \
    --prefix=/usr/local --exec_prefix=/usr/local

I make'd successfully.  But I'm curious.  I don't have gas, and I don't
know how to read this configure option explanation in file INSTALL:

> `--with-gnu-as'
>      Use this option if you plan to use the GNU assembler, `gas', when
>      building the GNU C Library.  On some systems, the library may not
>      build properly if you do *not* use `gas'.

"not build properly" -- does this mean the make will fail, or that the
make will succeed but produce flawed libraries?

> `tests'
>      The names of test programs for this section of the library.  These
>      should be simple names, such as `tester' (rather than complete file
>      names, such as `tester.c').  `make tests' will build and run all
>      the test programs.  If a test program needs input, put the test
>      data in a file called `TEST-PROGRAM.input'; it will be given to
>      the test program on its standard input.  If a test program wants
>      to be run with arguments, put the arguments (all on a single line)
>      in a file called `TEST-PROGRAM.args'.

So I test like:
    $ make test

and get errors (ouch):
    Make[1]: *** [test_ctype.out] Error 139
    Make[1]: *** [test-math.out] Error 139
    Make[1]: *** [tst-setjmp.out] Error 139
    Make[1]: *** [tst-signal.out] Error 139
    Make[1]: *** [tst-printf.out] Error 139
    Make[1]: *** [tst-strtol.out] Error 139
    Make[1]: *** [tester.out] Error 139
    Make[1]: *** [test_time.out] Error 139
    Make[1]: *** [list.out] Error 139
    Make[1]: *** [testgrp.out] Error 139
    Make[1]: *** [tstgetopt.out] Error 139
    Make[1]: *** [speeds.out] Error 139
    Make: *** [tests] Error 1
with the dozen accompanying coredumps.

Sigh.
So do the tests fail because the tests are broken?
Or did I build flawed libs?
And if I built flawed libs, then what's the cure -- gas?


I think this can easily be better documented, so I submit this as a
documentation bug.


By the way,

> `--with-gnu-ld'
>      Use this option if you plan to use GNU `ld' to link programs with
>      the GNU C Library.  (We strongly recommend that you do.)

I have GNU ld because I have gcc-2.2.2, right?  That's the link editor
in .../lib/gcc-lib/sparc-sun-sunos4.1.1/2.2.2/ld
which gcc will automatically use.
So if the user always uses gcc, this condition is satisfied.
I don't have the GNU ld from the binutils package installed, so the user
should always do the link-editing by running gcc instead of ld, or
actually specify the one in .../lib/gcc-lib/sparc-sun-sunos4.1.1/2.2.2/ld .

Please confirm or correct my logic.

Thanks for your help.
Best regards,
ruck

John R. Ruckstuhl, Jr.                  ruck@alpha.ee.ufl.edu
Dept of Electrical Engineering          ruck@cis.ufl.edu, uflorida!ruck
University of Florida                   ruck%sphere@cis.ufl.edu, sphere!ruck
-- 
John R. Ruckstuhl, Jr.                  ruck@alpha.ee.ufl.edu
Dept of Electrical Engineering          ruck@cis.ufl.edu, uflorida!ruck
University of Florida                   ruck%sphere@cis.ufl.edu, sphere!ruck