On Wed, 2010-05-05 at 10:42 -0700, H.J. Lu wrote:
> On Wed, May 5, 2010 at 10:18 AM, Steve Ellcey wrote:
> >
> > I was wondering if anyone has built GCC using a CFLAGS (and CXXFLAGS)
> > setting
> > that causes GCC to generate code that is not compatibile with the default
> > GCC output. Basical
Steve Ellcey writes:
> HJ seems to have the way to make it work, set CC to 'gcc -mlp64' instead
> of setting CC to 'gcc' and CFLAGS to '-mlp64' but that seems a bit
> counter-intuitive to the meaning of the flags.
'-mlp64' is an ABI-changing flag, so it is better to put it in CC, since
you are,
On Thu, 2010-05-06 at 00:36 +0100, Dave Korn wrote:
> On 05/05/2010 18:18, Steve Ellcey wrote:
>
> > During the build libiberty is built in 64 bit mode
>
> But *which* libiberty? Host, build, or target?
That is a good question. I am building in obj and I have:
obj/libiberty/libiberty.a
On 05/05/2010 18:18, Steve Ellcey wrote:
> During the build libiberty is built in 64 bit mode
But *which* libiberty? Host, build, or target?
> if I use --disable-bootstrap and build all-gcc then I don't have this problem.
This could be an interaction with the cross-compile mechanism, may
On Wed, May 5, 2010 at 12:41 PM, Basile Starynkevitch
wrote:
> On 05/05/2010 07:42 PM, H.J. Lu wrote:
>>
>> On Wed, May 5, 2010 at 10:18 AM, Steve Ellcey wrote:
>>>
>>> I was wondering if anyone has built GCC using a CFLAGS (and CXXFLAGS)
>>> setting
>>> that causes GCC to generate code that is n
On 05/05/2010 07:42 PM, H.J. Lu wrote:
On Wed, May 5, 2010 at 10:18 AM, Steve Ellcey wrote:
I was wondering if anyone has built GCC using a CFLAGS (and CXXFLAGS) setting
that causes GCC to generate code that is not compatibile with the default
GCC output.
I am using
# CC="gcc -m32" CXX="g++
On Wed, May 5, 2010 at 10:18 AM, Steve Ellcey wrote:
>
> I was wondering if anyone has built GCC using a CFLAGS (and CXXFLAGS) setting
> that causes GCC to generate code that is not compatibile with the default
> GCC output. Basically, I am building GCC on ia64-hp-hpux11.31 where I set
> CFLAGS a
I was wondering if anyone has built GCC using a CFLAGS (and CXXFLAGS) setting
that causes GCC to generate code that is not compatibile with the default
GCC output. Basically, I am building GCC on ia64-hp-hpux11.31 where I set
CFLAGS and CXXFLAGS to "-mlp64" to generate 64 bit code instead of the
