public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Azreen Bin Ahmad <azreena@starhub.com.sg>
To: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Help on gcc compiler option
Date: Sun, 21 Jan 2001 19:29:00 -0000	[thread overview]
Message-ID: <8BFDED98FB97D41185BE009027C3BFBAAD163F@hawaii.starhub.com.sg> (raw)

Hi,

Being new to gcc, need help on this:

I am having problems installing perl DB_File module with each time it gives
a specific error.  The notes pointed to the need to configure Berkeley DB
with the "CFLAGS=+z" option (for HP-UX platform).  However, this +z is only
for the native C compiler, while I specified env "CC=gcc" to use gcc.  

I tried looking up (to no avail) for info on the equivalent of C's +z option
in gcc.  Being new to this, i really appreciate any help.  Thanks in
advance.  below are some extracts of the notes from README  for  DB_File
(1.73) .

HP-UX Notes
-----------

Some people running HP-UX 10 have reported getting an error like this
when building DB_File with the native HP-UX compiler.

    ld: (Warning) At least one PA 2.0 object file (DB_File.o) was detected.
    The linked output may not run on a PA 1.x system.
    ld: Invalid loader fixup for symbol "$000000A5".

If this is the case for you, Berkeley DB needs to be recompiled with
the +z or +Z option and the resulting library placed in a .sl file. The
following steps should do the trick:

  1: Configure the Berkeley DB distribution with the +z or +Z C compiler
     flag:

        env "CFLAGS=+z" ../dist/configure ...

  2: Edit the Berkeley DB Makefile and change:

        "libdb= libdb.a" to "libdb= libdb.sl".

   3: Build and install the Berkeley DB distribution as usual.

warm regards
azreen
S'pore

             reply	other threads:[~2001-01-21 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-21 19:29 Azreen Bin Ahmad [this message]
2001-01-21 19:48 ` Alexandre Oliva

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=8BFDED98FB97D41185BE009027C3BFBAAD163F@hawaii.starhub.com.sg \
    --to=azreena@starhub.com.sg \
    --cc=gcc-help@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).