[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20060103: Building ldm-6.4.4 under HP-UX 11.23 using gcc

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20060103: Building ldm-6.4.4 under HP-UX 11.23 using gcc
  • Date: Wed, 04 Jan 2006 12:19:17 -0700
Jayne,

>Date: Tue, 03 Jan 2006 14:42:34 -1000
>From: "Jayne Hirakawa" <address@hidden>
>Organization: NOAA
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20060103: Building ldm-6.4.4 under HP-UX 11.23 using gcc

The above message contained the following:

> Attached config.log.
> jayne
[snip]

> configure:2143: checking if the system supports _XBS5_LPBIG_OFFBIG
> configure:2160: result: yes
> configure:2216: -U_MAPRGNS
> configure:2218: cflags="+DA2.0W"
> configure:2220: ldflags=""
> configure:2222: libs=""
> configure:2224: ARFLAGS="-cru"
> configure:2226: checking the C compiler (again)
> configure:2232: gcc -c -O +DA2.0W  conftest.c >&5
> gcc: +DA2.0W: No such file or directory
> configure:2238: $? = 1
> configure: failed program was:
> | int foo;
> configure:2259: error: gcc failed to compile test code

Yup.  Your getconf(1) utility is incompatible with your gcc(1) compiler:
getconf(1) is returning the options necessary for compiling in a large
programming environment using the native HP compiler.

I suggest telling the configure(1) script that you don't want a
programming environment that supports large product-queues.  This will
limit your product-queue to about 4 gigabytes and is the price of not
being able to use the native HP compiler.

Try the following:

    1.  Go to the top-level source-directory.

    2.  Execute the command "make distclean".

    3.  Execute the configure(1) script with the "--disable-max-size"
        option, e.g.,

            ./configure --disable-max-size >configure.log 2>&1

Regards,
Steve Emmerson