This is a discussion on Error after Upgrade from RH 7.3 to Fedora within the alt.comp.mail.qmail forums, part of the Mail Servers and Related category; I've had qmail on my RH 7.3 box and it's been trouble-free for a couple of ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I've had qmail on my RH 7.3 box and it's been trouble-free for a
couple of year. It's installed per the instructions in LWQ. I just upgraded, and now I'm getting the following error message: "Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed" I did a Google search but the only thing I found was a reference to the wrong version of Daemontools. I am using 0.76. Anybody know how to fix this? Thanks. Jack |
|
|||
|
On 22 Feb 2004 11:16:11 -0800, JR <jr@despammed.com> may have written:
> I've had qmail on my RH 7.3 box and it's been trouble-free for a > couple of year. It's installed per the instructions in LWQ. > > I just upgraded, and now I'm getting the following error message: > "Incorrectly built binary which accesses errno or h_errno directly. > Needs to be fixed" > > I did a Google search but the only thing I found was a reference to > the wrong version of Daemontools. I am using 0.76. > > Anybody know how to fix this? Google for qmail and errno. Without getting into a religious war over it, the basics are, that starting in glibc 2.3.x, errno was turned into a macro instead of an integer, most likely to make it thread-safe. In any package that djb has written, do the following: open "error.h" replace the line: extern int errno; with: #include <errno.h> HTH, -- Brian T Glenn delink.net Internet Services |
|
|||
|
Brian T Glenn <glenn-nntp@this.delink.is.net.invalid> wrote in message news:<slrnc3idvn.20a.glenn-nntp@ziege.delink.net>...
> On 22 Feb 2004 11:16:11 -0800, JR <jr@despammed.com> may have written: > > I've had qmail on my RH 7.3 box and it's been trouble-free for a > > couple of year. It's installed per the instructions in LWQ. > > > > I just upgraded, and now I'm getting the following error message: > > "Incorrectly built binary which accesses errno or h_errno directly. > > Needs to be fixed" > > > > I did a Google search but the only thing I found was a reference to > > the wrong version of Daemontools. I am using 0.76. > > > > Anybody know how to fix this? > > Google for qmail and errno. Without getting into a religious war over > it, the basics are, that starting in glibc 2.3.x, errno was turned into > a macro instead of an integer, most likely to make it thread-safe. > > In any package that djb has written, do the following: > > open "error.h" > > replace the line: extern int errno; > with: #include <errno.h> > > HTH, Brian, Thanks, I was Googling for the entire string, and that limited the results. I found several relevant posts this time. I see there's a patch, but Dave Sill says you can do the same as you recommended. Will I need to recompile the affected apps? Thanks. Jack |
|
|||
|
On 23 Feb 2004 08:14:03 -0800, JR <jr@despammed.com> may have written:
> Brian T Glenn <glenn-nntp@this.delink.is.net.invalid> wrote in message news:<slrnc3idvn.20a.glenn-nntp@ziege.delink.net>... >> Google for qmail and errno. Without getting into a religious war over >> it, the basics are, that starting in glibc 2.3.x, errno was turned into >> a macro instead of an integer, most likely to make it thread-safe. >> >> In any package that djb has written, do the following: >> >> open "error.h" >> >> replace the line: extern int errno; >> with: #include <errno.h> > > Thanks, I was Googling for the entire string, and that limited the > results. I found several relevant posts this time. I see there's a > patch, but Dave Sill says you can do the same as you recommended. Well the patch does exactly what i said, that's all :) > Will I need to recompile the affected apps? Patches tend to be for source code in the UNIX world as opposed to binary patches. You will have to recompile. Just do the patch, run make, then shutdown the service and run "make setup check", then restart the service. the annoying warning from ld.so should go away then. Cheers, -- Brian T Glenn delink.net Internet Services |