public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kbalk@pobox.com
To: gcc-gnats@gcc.gnu.org
Subject: c/7237: HP/UX 10.20 compile problems, e.g, STAGE1_CFLAGS not overriden
Date: Mon, 08 Jul 2002 13:16:00 -0000	[thread overview]
Message-ID: <20020708200604.20707.qmail@sources.redhat.com> (raw)


>Number:         7237
>Category:       c
>Synopsis:       HP/UX 10.20 compile problems, e.g, STAGE1_CFLAGS not overriden
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 08 13:16:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Karri Balk
>Release:        gcc version 3.1
>Organization:
>Environment:
Reading specs from /usr/local/lib/gcc-lib/hppa1.1-hp-hpux10.20/3.1/specs
Configured with: ../gcc-3.1/configure --enable-languages=c
Thread model: single
>Description:
I originally attempted to build the C and C++ compiler on 10.20, but due to the following problems and insufficient disk space, I finally built just the C compiler.  There are three problems I noted with what I did try:

1.  When building the C compiler, the STAGE1_CFLAGS was 
    not being overridden with the value of CFLAGS, and 
    the compilation would fail:

    Build cmd: gmake CFLAGS='-O -Ae' LIBCFLAGS='-g -O' \
               bootstrap

    Snippet of error (linefeeds added for clarity):
    ranlib libbackend.a
    cc -DIN_GCC    -g    -DHAVE_CONFIG_H  -o cc1 \
      c-parse.o c-lang.o attribs.o c-errors.o c-lex.o 
      c-pragma.o c-decl.o c-typeck.o c-convert.o 
      c-aux-info.o c-common.o c-format.o c-semantics.o 
      c-objc-common.o libcpp.a  main.o 
      libbackend.a ./intl/libintl.a ../libiberty/libiberty.a
    cc -c -DIN_GCC    -g    -DHAVE_CONFIG_H    -I. -I. 
      -I../../gcc-3.1/gcc -I../../gcc-3.1/gcc/. 
      -I../../gcc-3.1/gcc/config 
      -I../../gcc-3.1/gcc/../include 
      ../../gcc-3.1/gcc/tradcpp.c -o tradcpp.o
    cc: "../../gcc-3.1/gcc/tradcpp.c", line 2598: 
       error  1000: Unexpected symbol: "*".
    cc: "../../gcc-3.1/gcc/tradcpp.c", line 2607: 
       error 1000: Unexpected symbol: ")".
     :: 
     [KB: other errors related to finding a prototype]
     ::
    gmake[2]: *** [tradcpp.o] Error 1
    gmake[2]: Leaving directory `/usr/gcc-objdir/gcc'
    gmake[1]: *** [stage1_build] Error 2
   
    If I changed STAGE1_CFLAGS to match the value specified
    for CFLAGS (i.e., to specify an extended ANSI 
    compilation), the build would complete.

2.  If building both the C and C++ compiler, setting
    STAGE1_CFLAGS for extended ANSI compilation caused 
    the compilation to fail at a later stage:

    Build cmd: gmake CFLAGS='-O -Ae' LIBCFLAGS='-g -O' \
               LIBCXXFLAGS='-g -O -fno-implicit-templates' \
               bootstrap-lean

               Note:  gcc/Makefile was edited to set
               STAGE1_CFLAGS to "-O -Ae" due to problem #1.

    Snippet of error (linefeeds added for clarity):
    checking for BSD-compatible nm... /usr/ccs/bin/nm
    checking how to recognise dependant libraries... 
       file_magic (s[0-9][0-9][0-9]|PA-RISC[0-9].[0-9]) 
       shared library
    checking for object suffix... configure: 
       error: installation or configuration problem; 
       compiler does not work
    gmake[1]: *** [configure-target-libstdc++-v3] Error 1

  gcc-objdir/hppa1.1-hp-hpux10.20/libstdc++v3/configure/log:

    configure:2143: /usr/gcc-objdir/gcc/xgcc 
       -B/usr/gcc-objdir/gcc/ 
       -B/usr/local/hppa1.1-hp-hpux10.20/bin/ 
       -B/usr/local/hppa1.1-hp-hpux10.20/lib/ 
       -isystem /usr/local/hppa1.1-hp-hpux10.20/include 
       -c -O -Ae  conftest.c 1>&5
    <command line>:1:2: missing '(' after predicate

    The error refers to the "-0 -Ae" options.  If I
    manually edit the Makefile to set STAGE1_CFLAGS 
    back to its original value, the make would continue
    and I would not see this error.

3.  When building the C and C++ compiler, I used the
    "bootstrap-lean" option as I have very little disk space
    to work with.  I'm not positive, but I believe this 
    was what caused my following link error.  I did not get
    this error when I built just the C compiler specifying
    "bootstrap" instead of "bootstrap-lean".

    Build cmd: gmake CFLAGS='-O -Ae' LIBCFLAGS='-g -O' \
               LIBCXXFLAGS='-g -O -fno-implicit-templates' \
               bootstrap-lean

    Snippet of error (linefeeds added for clarity):
    ar rc libbackend.a alias.o bb-reorder.o bitmap.o
       builtins.o caller-save.o calls.o 
       ... [KB: object files snipped here] ... vmsdbgout.o  
       xcoffout.o ggc-page.o pa.o
    true libbackend.a
    cc -DIN_GCC    -O -Ae   -DHAVE_CONFIG_H  -o cc1 \
       c-parse.o c-lang.o attribs.o c-errors.o c-lex.o 
       c-pragma.o c-decl.o c-typeck.o c-convert.o 
       c-aux-info.o c-common.o c-format.o c-semantics.o 
       c-objc-common.o libcpp.a  main.o libbackend.a 
      ./intl/libintl.a   ../libiberty/libiberty.a
    /usr/ccs/bin/ld: Unsatisfied symbols:
   __ashrdi3 (code)
   __umoddi3 (code)
   __udivdi3 (code)
   __main (code)
   __lshrdi3 (code)
   __moddi3 (code)
   __ashldi3 (code)
   __divdi3 (code)
   gmake[2]: *** [cc1] Error 1
   gmake[2]: Leaving directory `/usr/gcc-objdir/gcc'
   gmake[1]: *** [all-gcc] Error 2
   gmake[1]: Leaving directory `/usr/gcc-objdir'
   gmake: *** [bootstrap-lean] Error 2

I was finally able to build just the C compiler, but it would not generate symbol tables when I compile a file using gcc and the -g option.  I have not determined why this is so, and have left that problem for another day!
>How-To-Repeat:
The gmake options and steps taken are noted above in "description".
>Fix:
I apologize, but I have none to offer ... I was so frustrated with my lack of disk space and limited ability to print files, that I did not attempt to resolve the problem.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-07-08 20:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020708200604.20707.qmail@sources.redhat.com \
    --to=kbalk@pobox.com \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).