> 2007-02-07-15:28:15.682 sbkdgdbdev1 Init_tempfile: bad tempdir '/var/spool/lpd/%P' ... > *** glibc detected *** double free or corruption (fasttop): 0x080a0bc8 ***
Now those are definite lprng issues. Suggest googling or taking that to an lprng list. This list is only for bugs in make. We try to be helpful but you're talking to the wrong guys. ------------------------------------- Martin's Outlook, BlueArc Engineering -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raheja, Himanshu Sent: Wednesday, February 07, 2007 13:02 To: Dave Korn; Eli Zaretskii Cc: bug-make@gnu.org Subject: RE: BUG while running the make file One more help needed from you guys. I have two LPRng versions installed on my Linux box. I have binaries for LPRng 3.6.9 under /usr/local/bin. I have installed the latest LPRng 3.8.28 and I was successfully able to compile in 32 bit mode. Binaries for this are kept in /usr/local/sbin. While I am running LPRng 3.8.28 (/usr/local/sbin.) I get following errors: 2007-02-07-15:28:15.682 sbkdgdbdev1 Init_tempfile: bad tempdir '/var/spool/lpd/%P' 2007-02-07-15:28:15.683 sbkdgdbdev1 Init_tempfile: bad tempdir '/var/spool/lpd/%P' 2007-02-07-15:28:15.684 sbkdgdbdev1 Init_tempfile: bad tempdir /var/spool/lpd/%P' If I am running LPRng 3.6.9 I get following errors: *** glibc detected *** double free or corruption (fasttop): 0x080a0bc8 *** *** glibc detected *** double free or corruption (fasttop): 0x080a0bc8 *** Kindly help and suggest what could be done. Thanks and Regards Himanshu. -----Original Message----- From: Dave Korn [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 1:48 PM To: Raheja, Himanshu; 'Eli Zaretskii' Cc: bug-make@gnu.org Subject: RE: BUG while running the make file On 07 February 2007 18:44, Raheja, Himanshu wrote: > Hi Folks, > > I was able to resolve that issue by googling: > > When I ran ./configure CFLAGS=-m32 LDFLAGS=-m32 > > And after that make install was working fine. > But I am not sure why this was happening. Probably because your compiler is a recent one, and defaults to compiling 64-bit code, but your binutils are slightly out of date and have bugs trying to assemble the 64-bit code. The -m32 flag that you have found out to use makes sure the compiler still generates 32-bit code, which the binutils do not have any problem with. So you end up with a 32-bit executable. (It might be possible to upgrade your binutils and get the build to work for 64 bits, and the resulting executable might run faster, but it's not something to try unless you were confident with upgrading packages and knew how to revert to the old one if something went wrong.) cheers, DaveK -- Can't think of a witty .sigline today.... _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make