Re: stdlib.h i386 and alpha differences! was: Bug#22650: xcircuit: nonmaintainer upload for Alpha patches
- To: James Troup <J.J.Troup@scm.brad.ac.uk>
- Cc: email@example.com, firstname.lastname@example.org
- Subject: Re: stdlib.h i386 and alpha differences! was: Bug#22650: xcircuit: nonmaintainer upload for Alpha patches
- From: Paul Slootman <email@example.com>
- Date: Wed, 20 May 1998 12:28:09 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <email@example.com> from "James Troup" on 1998/05/20 10:36 +0100
- References: <19980519225115.A23292@wurtel.demon.nl> <Pine.LNX.3.96.980519173318.4803Cfirstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
On Wed 20 May 1998, James Troup wrote:
> Paul Slootman <email@example.com> writes:
> > The malloc.h should never hurt, that's been available for as long as
> > I can remember (well, almost :-)
> Umm, why _are_ you #including <malloc.h>? Colour me stupid, but I was
> under the distinct impression one #includes <stdlib.h> for a malloc
> prototype, and this seems to be born out by both the manpage and the
> glibc info documentation. Surely something as basic as this doesn't
> vary on the alpha?
Apparently it _does_ :-( I also read the manpage for malloc, included
stdlib.h, and saw that the warnings didn't go away. I then looked into
/usr/include/stdlib.h and saw that there were no declarations for any
alloc routines. Not having an i386 available at home to compare, I
grepped for malloc in /usr/include and came up with malloc.h.
I've now looked at stdlib.h on i386, and that _does_ declare malloc...
The only difference I can imagine is that Alpha actually uses libc6.1
instead of plain libc6, but I still find it strange that stdlib.h
differs. Maybe I should consult libc6 gurus?
I've CC'ed the alpha mailing list, maybe someone there can shed some
light on this matter.
home: firstname.lastname@example.org | work: email@example.com
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com