Dustin J. Mitchell wrote:
> Very true. And, in this case at least, the user does not have access
> to the ANSI version of the compiler (-Ae) -- apparently that's a
> value-add feature.
That's why several sites provide pre-built binaries of GCC for HP-UX.
You find them by typing the words
hp-ux
Dustin J. Mitchell zmanda.com> writes:
>
> It was my impression that #xxx directives should always start in
> column 0. Apparently that impression is as "dated" as C89 :)
Per C89 section 3.8,
A preprocessing directive consists of a sequence of preprocessing
tokens that begins with a # preproc
On Wed, Apr 9, 2008 at 5:45 PM, Bruno Haible <[EMAIL PROTECTED]> wrote:
> It's not only the indented #include which fails. The compiler message
> "error 1705: Function prototypes are an ANSI feature." clearly indicates
> that many more errors are to be expected, because the compiler is not even
Hello,
Dustin J. Mitchell wrote:
> A user is building Amanda on HPUX, and ran into a compiler error:
>
> | /* end confdefs.h. */
> | #include
> | #include
> |
> | int getpeername (int, void *, long int *);
> | int
> | main ()
> | {
> | long int len;
> | getp
A user is building Amanda on HPUX, and ran into a compiler error:
| /* end confdefs.h. */
| #include
| #include
|
| int getpeername (int, void *, long int *);
| int
| main ()
| {
| long int len;
| getpeername (0, 0, &len);
| ;
| return 0;
| }
config
