From: gsl-discuss@lists.thewrittenword.com
To: eric.van.der.velde@nl.fortisbank.com
Cc: gsl-discuss@sources.redhat.com
Subject: Re: Build problem on ABM AIX + solution
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <20010927033816.A82941@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <OF43E4997C.EFC1381A-ON41256AD4.00299FCF@nl.fortisbank.com>
On Thu, Sep 27, 2001 at 08:36:36AM +0100, eric.van.der.velde@nl.fortisbank.com wrote:
> Trying to make gsl on an IBM AIX 4.3 (xlc) system failed in the file
> test/results.c (problems concerning the va_list)
>
> The problem is that __STDC__ is not defined on an AIX system (which should
> be), and the prepocessor takes the 'wrong' decision.
> To solve this problem I modified the test/results file all the occurences
> of
>
> #ifdef __STDC__
>
> to
>
> #if defined(__STDC__) || defined(AIX)
>
> Then I added -DAIX to the CFLAGS and ran ./configure again (followed by a
> make)
>
> I hope this can solve you build problems on AIX in the future
Ick! Please do *not* do this. Platform-specific stuff like this is
ugly. A more proper fix should be found.
> Here some info on the AIX compiler:
>
> the IBM C compiler doesn't define __STDC__ (despite the fact
> that its entirely ANSI compatible - actually it does define __STDC__ if
> you put it in "strict" mode, but then it treats an allocation of an "int"
> to an "unsigned int" as a severe error and stops. Thus nobody uses the
> strict mode, thus __STDC__ is rarely defined. In addition it generates an
> error message if you define __STDC__ manually....) Therefore could you put
> in a || defined (AIX) to all your #ifdef __STDC__...?
I have xlc 5.0.2.0. Without *any* options, __STDC__ == 1. What do you
consider "strict" mode? -qlanglvl=ansi?
We built gsl-0.9.2 with xlc and -qlanglvl=ansi and test/results.c
compiled fine.
--
albert chin (china@thewrittenword.com)
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 eric.van.der.velde
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` how do you build a 64-bit library on IRIX Charles Yee
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Charles Yee
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` William Brower
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 Build problem on ABM AIX + solution eric.van.der.velde
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=20010927033816.A82941@oolong.il.thewrittenword.com \
--to=gsl-discuss@lists.thewrittenword.com \
--cc=eric.van.der.velde@nl.fortisbank.com \
--cc=gsl-discuss@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).