[arch-general] Fwd: Re: [hylafax-users] Error building 6.0.5 on Arch Linux /sys/stat.h:299:47: error: declaration of ‘int fchmod(int, __mode_t) throw ()’ throws different exceptions
Just FYI Arch Devs - Hylafax needs a patch to build with gcc 4.5. You may want to wait for 6.0.6 for the next version update. Details from the ifax devs below: -------- Original Message -------- Subject: Re: [hylafax-users] Error building 6.0.5 on Arch Linux /sys/stat.h:299:47: error: declaration of ‘int fchmod(int, __mode_t) throw ()’ throws different exceptions Date: Fri, 1 Apr 2011 08:52:50 -0400 From: Aidan Van Dyk <aidan@ifax.com> To: David C. Rankin <drankinatty@suddenlinkmail.com> CC: hfax <hylafax-users@hylafax.org> You'll want to apply this: http://git.hylafax.org/HylaFAX?a=commitdiff;h=b0d873c950a72aa568d2fcfe7dbc8b... 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 <drankinatty@suddenlinkmail.com> wrote:
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-request@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@ifax.com.*
-- David C. Rankin, J.D.,P.E.
On Fri, 2011-04-01 at 08:40 -0500, David C. Rankin wrote:
Just FYI Arch Devs - Hylafax needs a patch to build with gcc 4.5. You may want to wait for 6.0.6 for the next version update. Details from the ifax devs below:
-------- Original Message -------- Subject: Re: [hylafax-users] Error building 6.0.5 on Arch Linux /sys/stat.h:299:47: error: declaration of ‘int fchmod(int, __mode_t) throw ()’ throws different exceptions Date: Fri, 1 Apr 2011 08:52:50 -0400 From: Aidan Van Dyk <aidan@ifax.com> To: David C. Rankin <drankinatty@suddenlinkmail.com> CC: hfax <hylafax-users@hylafax.org>
You'll want to apply this:
http://git.hylafax.org/HylaFAX?a=commitdiff;h=b0d873c950a72aa568d2fcfe7dbc8b...
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 <drankinatty@suddenlinkmail.com> wrote:
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-request@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@ifax.com.*
It's probably going to be build with gcc4.6 ;) -- Jelle van der Waa
On 04/01/2011 09:13 AM, Jelle van der Waa wrote:
It's probably going to be build with gcc4.6 ;)
Jelle, When the next version is built, we need to take a look at the file ownership for the files under /var/spool/hylafax. Currently the files are owned by root or uucp. However, we have a 'fax' user. There have been a few issues on Arch with trouble getting the faxrcvd and notify executables to work with avantfax, etc. Looking at other distros, the ownership of the files under /var/spool/hylafax is fax:uucp. Seeing that the files are world executable -- it shouldn't make a difference, but I can't help but wondering if something is checking ownership expecting to find the files owned by the 'fax' user and then not executing the faxrcvd or notify commands as a result. Dunno -- just food for thought on the next rebuild :p -- David C. Rankin, J.D.,P.E.
On 04/07/2011 11:41 AM, David C. Rankin wrote:
but I can't help but wondering if something is checking ownership expecting to find the files owned by the 'fax' user and then not executing the faxrcvd or notify commands as a result.
It's not just ownership of the executables, but also the files in /var/spool/hylafax/recvq, /var/spool/hylafax/doneq, .... It may present a read permission problem if owned by uucp:uucp, especially where ../hylafax/etc/config.ttyS1 has "RecvFileMode: 0640" or 0600. Again, just food for thought... I'll try and learn more about what user hylafx is running under for the various tasks. Right now, I just don't know. -- David C. Rankin, J.D.,P.E.
participants (2)
-
David C. Rankin
-
Jelle van der Waa