[Top][All Lists]

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

RE: BUG while running the make file

From: Raheja, Himanshu
Subject: RE: BUG while running the make file
Date: Wed, 7 Feb 2007 16:02:01 -0500

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

2007-02-07-15:28:15.682 sbkdgdbdev1 Init_tempfile: bad tempdir
2007-02-07-15:28:15.683 sbkdgdbdev1 Init_tempfile: bad tempdir
2007-02-07-15:28:15.684 sbkdgdbdev1 Init_tempfile: bad tempdir

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

-----Original Message-----
From: Dave Korn [mailto:address@hidden 
Sent: Wednesday, February 07, 2007 1:48 PM
To: Raheja, Himanshu; 'Eli Zaretskii'
Cc: address@hidden
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
64-bit code, but your binutils are slightly out of date and have bugs
to assemble the 64-bit code.  The -m32 flag that you have found out to
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,
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
the old one if something went wrong.)

Can't think of a witty .sigline today....

reply via email to

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