[Top][All Lists]

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

Re: openexr: FTBFS on hurd-i386: duplicated case in switch

From: Michael Banck
Subject: Re: openexr: FTBFS on hurd-i386: duplicated case in switch
Date: Wed, 6 Dec 2006 13:51:40 +0100

reassign 396135 libc0.3-dev
retitle 396135 libc0.3-dev: Hurd errno 118 assigned twice (ECANCELED and 


Cyril wrote:
> since ECANCELED and ENOTSUP have the same value on hurd-i386, the
> build fails with:
> > IexThrowErrnoExc.cpp: In function 'void Iex::throwErrnoExc(const
> > std::string&, int)':
> > IexThrowErrnoExc.cpp:720: error: duplicate case value
> > IexThrowErrnoExc.cpp:679: error: previously used here

This is a bug in the Hurd-specific parts of glibc and should get fixed
upstream, rather.

See http://lists.gnu.org/archive/html/help-hurd/2003-06/msg00088.html
for further discussion:

|From: Roland McGrath
|Subject: Re: Why is ENOTSUP == ECANCELED?
|Date: Mon, 23 Jun 2003 19:44:19 -0400 (EDT)
|> On Mon, Jun 23, 2003 at 10:35:56PM +0200, Andreas Voegele wrote:
|> > In /include/bits/errno.h both ENOTSUP and ECANCELED get the value
|> > _HURD_ERRNO(118).  Is this intended?
|> I don't think so.  Roland can you fix this if it is wrong?
|They certainly should not have the same number.  The Hurd numbers are
|determined by magic comments in libc/manual/errno.texi; it appears that
|someone added some codes to errno.texi with magic comments and picked
|some random numbers for them (probably Linux numbers) instead of 
|omitting them.  That needs to be fixed.  Can you compare all the 
|numbers in errno.texi with those that existing Hurd binaries were 
|really using, and assign unused numbers to any excess errno codes the 
|Hurd didn't previously have?

(Note that AFAICT Linux doesn't use 118 for ENOTSUP or ECANCELED either)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]