bino-list
[Top][All Lists]
Advanced

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

Re: [Bino-list] configure failure of bino package


From: Krishna Kishore
Subject: Re: [Bino-list] configure failure of bino package
Date: Mon, 17 Dec 2012 17:48:45 +0530

Hi Martin,

  Yes. I set it correctly. 

        $ export CXXFLAGS="-march=i686"
        $ export CFLAGS="-march=i686"
        $ ./configure

   Also,
      $ ./configure CFLAGS="-march=i686" CXXFLAGS="-march=i686"

Regards,
Kishore.

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Martin Lambers
Sent: Friday, December 14, 2012 9:24 PM
To: address@hidden
Subject: Re: [Bino-list] configure failure of bino package

Hi, 

did you set it in the correct way, i.e.

$ ./configure CFLAGS="-march=i686" CXXFLAGS="-march=i686"

Martin

On Fri, 14 Dec 2012 20:38:17 +0530, Krishna Kishore wrote:
> Hi Martin,
> 
>   Thanks for your response.
> 
>   I am not setting any special options.
> 
>   I am just doing ./configure
> 
>   Even if I forcibly set -march=i686, this error is seen.
> 
> Regards,
> Kishore.
> 
> -----Original Message-----
> From: Martin Lambers [mailto:address@hidden
> Sent: Friday, December 14, 2012 8:28 PM
> To: address@hidden
> Cc: Krishna Kishore
> Subject: Re: [Bino-list] configure failure of bino package
> 
> On Fri, 14 Dec 2012 17:19:41 +0530, Krishna Kishore wrote:
> >    I am facing following error when I do configure. Version of gcc I 
> > have on my Ubuntu 12.04 is 4.6.3. Is there anything that I have to 
> > do to overcome this error?
> >
> > checking for GCC atomic builtins... no
> > configure: error: GCC atomic builtins not found. Please use a newer 
> > compiler.
> 
> Do you have any -march=... options in your CFLAGS or CXXFLAGS?
> 
> When building for 32bit x86, don't use -march=i386; use at least 
> -march=i686. Otherwise many features are not available, including the 
> atomic builtins.
> 
> Gcc on 12.04 should work out of the box unless you set some special 
> options.
> 
> Martin
> 
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential, 
> proprietary or legally privileged information. In case you are not the 
> original intended Recipient of the message, you must not, directly or 
> indirectly, use, disclose, distribute, print, or copy any part of this 
> message and you are requested to delete it and inform the sender. Any 
> views expressed in this message are those of the individual sender 
> unless otherwise stated. Nothing contained in this message shall be 
> construed as an offer or acceptance of any offer by Sasken 
> Communication Technologies Limited ("Sasken") unless sent with that 
> express intent and with due authority of Sasken. Sasken has taken 
> enough precautions to prevent the spread of viruses. However the 
> company accepts no liability for any damage caused by any virus 
> transmitted by this email. Read Disclaimer at 
> http://www.sasken.com/extras/mail_disclaimer.html





reply via email to

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