Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
To: ezannoni@redhat.com
Cc: ac131313@cygnus.com, aoliva@redhat.com, gdb@sources.redhat.com
Subject: Re: GDB cvs won't build on AIX 4.1
Date: Mon, 04 Feb 2002 12:59:00 -0000	[thread overview]
Message-ID: <200202042059.VAA27761@reaktor.regent.e-technik.tu-muenchen.de> (raw)
In-Reply-To: <15454.51522.720684.688328@localhost.redhat.com>; from "Elena Zannoni" at Feb 4, 102 6:48 pm

-mminimal-toc is only available with gcc, so we might loose again, if someone
tries to build GDB with the native compiler.  It might be worthwile to add
-mminimal-toc if we are using gcc though, for performance reasons.

I have not been suggesting to revert the patch, but I was thinking along the
lines of (completely untested):

            # Do this only for native AIX builds

            # The GNU linker does not understand the -bbigtoc switch, which the
	    # native linker needs.
            hold_ldflags=$LDFLAGS
            AC_MSG_CHECKING(for the ld -bbigtoc flag)
            LDFLAGS="${LDFLAGS} -Wl,-bbigtoc"
            AC_TRY_LINK(, [int i;], nativeld=yes, nativeld=no)
            LDFLAGS=$hold_ldflags
            AC_MSG_RESULT($nativeld)
            if test $nativeld = yes; then
               CONFIG_LDFLAGS="${CONFIG_LDFLAGS} -Wl,-bbigtoc"
            fi

in gdb/configure.in, adapted from a similar Solaris test, which should work
for all compiler/linker combinations.

> Andrew Cagney writes:
>  > > On Feb  4, 2002, Andrew Cagney <ac131313@cygnus.com> wrote:
>  > > 
>  > > 
>  > >>> Perhaps we should hard-code the link option -bbigtoc for gdb to
>  > >>> link properly on AIX?
>  > > 
>  > > 
>  > >> That was the problem.  See gdb/294.
>  > >> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=294
>  > > 
>  > > 
>  > > Thanks for the pointer.  Would it be pointless then to post a patch
>  > > that detected which version of GCC is in use, and whether the linker
>  > > it uses accepts -bbigtoc?
>  > 
>  > 
>  > The oposite!  See Peter Schauer's comment - it would solve the problem.
>  > 
>  > Andrew
> 
> Sorry for the late reply, but there is another way to solve that
> problem which is to compile gdb passing the -mminimal-toc option to
> gcc. This should be uniformly OK independently of the linker used.
> 
> There are also these options available, but I haven't tried them.
> 
> -mfull-toc 
> -mno-fp-in-toc 
> -mno-sum-in-toc 
> 
> 
> FWIW, using the GNU linker and reverting that patch I get this
> error: ../../powerpc-ibm-aix4.3.3.0/bin/ld: invalid BFD target
> `bigtoc'collect2: ld returned 1 exit status
> 
> Elena

-- 
Peter Schauer			pes@regent.e-technik.tu-muenchen.de


  reply	other threads:[~2002-02-04 20:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02 18:45 Alexandre Oliva
2002-02-03 18:40 ` Andrew Cagney
2002-02-04  4:15   ` Alexandre Oliva
2002-02-04  8:06     ` Andrew Cagney
2002-02-04  9:47       ` Elena Zannoni
2002-02-04 12:59         ` Peter.Schauer [this message]
2002-02-24  5:10           ` Alexandre Oliva
2002-03-01 15:51             ` Peter.Schauer

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=200202042059.VAA27761@reaktor.regent.e-technik.tu-muenchen.de \
    --to=peter.schauer@regent.e-technik.tu-muenchen.de \
    --cc=ac131313@cygnus.com \
    --cc=aoliva@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    /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