Guys,

   I was working with hylafax in Arch updating the package from 6.0.4 to 6.0.5
and I ran into a strange error related to "throws different exceptions":

<snip>
86-64 -mtune=generic -O2 -pipe  -c Dispatcher.c++
In file included from Sys.h:34:0,
                  from Dispatcher.c++:27:
/usr/include/sys/stat.h:299:47: error: declaration of ‘int fchmod(int, __mode_t)
throw ()’ throws different exceptions
./port.h:32:12: error: from previous declaration ‘int fchmod(int, mode_t)’
make[3]: *** [Dispatcher.o] Error 1
make[3]: Leaving directory
`/home/david/arch/pkg/bld/hylafax/src/hylafax-6.0.5/libhylafax'
make[2]: *** [default] Error 2
make[2]: Leaving directory
`/home/david/arch/pkg/bld/hylafax/src/hylafax-6.0.5/libhylafax'
make[1]: *** [dirs] Error 2
make[1]: Leaving directory `/home/david/arch/pkg/bld/hylafax/src/hylafax-6.0.5'
make: *** [default] Error 2
==> ERROR: A failure occurred in build().
     Aborting...

   I'm getting better at sorting this stuff out, but exception handling problems
are the exception... no pun intended. What says the experts. I wanted a clean
install to look at permissions again on the bin/notify.php and bin/faxrcvd.php
issue and thought I might as well try 6.0.5.

   What say the experts? What is the probable cause of throwing different
exceptions? The stat.h file on Arch is available on my server here:

http://www.3111skyline.com/dl/bugs/hylafax/stat.h

--
David C. Rankin, J.D.,P.E.

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-requ...@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*

You'll want to apply this:
    http://git.hylafax.org/HylaFAX?a=commitdiff;h=b0d873c950a72aa568d2fcf...

I still believe this is a bug in GCC 4.5+, where they turned something
every other compiler handles a fatal error, causing configure not to
find the declaration for fchmod (and thus declare it's own in port.h).
 I doubt anyone will be able to convince GCC of this ;-)  See:
    http://bugs.hylafax.org/show_bug.cgi?id=924

configure has been changed in HylaFAX to not tickle that particular
property of GCC.

That fix was applied to the 6.0 branch after 6.0.5 was released, but
no distros were based on GCC 4.5+ yet at that time.

I guess it's time for 6.0.6 release...
a.

On Thu, Mar 31, 2011 at 10:24 PM, David C. Rankin

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-requ...@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*

On 04/01/2011 07:52 AM, Aidan Van Dyk wrote:

Thanks Aidan - gcc 4.5 has bitten me more than once with contructor handling,
etc. Arch went to gcc 4.5 a couple of months ago and it has been an interesting
ride. I'll pass this info along to the Arch packager for Hylafax. Thanks Again.

--
David C. Rankin, J.D.,P.E.

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-requ...@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*