From: eric.van.der.velde@nl.fortisbank.com
To: gsl-discuss@sources.redhat.com
Subject: Build problem on ABM AIX + solution
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <OF43E4997C.EFC1381A-ON41256AD4.00299FCF@nl.fortisbank.com> (raw)
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
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__...?
Eric
___________________________________________________________________________
This e-mail is sent for the sole attention of the identified addressee and its
contents are provided for information purposes only. Fortis Bank makes no
warranty or representation as to the accuracy and completeness of any
information and does not assume whatever commitment hereby. Legally binding
obligation can only arise for, or be entered into on behalf of, Fortis Bank by
means of a written instrument, signed by two duly authorised representatives of
Fortis Bank. Fortis Bank excludes any liability whatsoever for any direct or
consequential loss arising from the use, or reliance on, this e-mail or its
contents.
___________________________________________________________________________
next 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 [this message]
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
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 ` Build problem on ABM AIX + solution Brian Gough
2001-12-19 13:20 ` gsl-discuss
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 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=OF43E4997C.EFC1381A-ON41256AD4.00299FCF@nl.fortisbank.com \
--to=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).