* [gentoo-user] Qt-core-4.5.1 jamboree not optimised for i686
@ 2009-06-03 11:35 Mick
2009-06-03 11:41 ` Alan McKinnon
0 siblings, 1 reply; 3+ messages in thread
From: Mick @ 2009-06-03 11:35 UTC (permalink / raw
To: gentoo-user
Major build this morning of qt with a lot of blockers. Having
unmerged a lot of packages to remove the blockers I am now emerging
qt-core. I noticed this on my screen:
Determining system architecture... (Linux:2.6.29-gentoo-r5:i686)
32-bit Intel 80x86 (i386)
'i386' is supported
System architecture: 'i386'
Symbol visibility control enabled.
Symbolic function binding enabled.
This is the Qt/X11 Open Source Edition.
Since I have these in make.conf I would think that a package like qt
would compile optimised code for my architecture, not just i386?
ARCH="x86"
CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -msse -mmmx -pipe"
MAKEOPTS="-j2"
ACCEPT_KEYWORDS="x86"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
Just curious.
--
Regards,
Mick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] Qt-core-4.5.1 jamboree not optimised for i686
2009-06-03 11:35 [gentoo-user] Qt-core-4.5.1 jamboree not optimised for i686 Mick
@ 2009-06-03 11:41 ` Alan McKinnon
2009-06-03 12:23 ` Mick
0 siblings, 1 reply; 3+ messages in thread
From: Alan McKinnon @ 2009-06-03 11:41 UTC (permalink / raw
To: gentoo-user
On Wednesday 03 June 2009 13:35:04 Mick wrote:
> Major build this morning of qt with a lot of blockers. Having
> unmerged a lot of packages to remove the blockers I am now emerging
> qt-core. I noticed this on my screen:
>
> Determining system architecture... (Linux:2.6.29-gentoo-r5:i686)
> 32-bit Intel 80x86 (i386)
> 'i386' is supported
> System architecture: 'i386'
> Symbol visibility control enabled.
> Symbolic function binding enabled.
>
> This is the Qt/X11 Open Source Edition.
>
> Since I have these in make.conf I would think that a package like qt
> would compile optimised code for my architecture, not just i386?
>
> ARCH="x86"
> CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -msse -mmmx -pipe"
> MAKEOPTS="-j2"
> ACCEPT_KEYWORDS="x86"
> CHOST="i686-pc-linux-gnu"
> CXXFLAGS="${CFLAGS}"
>
> Just curious.
architecture != cpu type
in this case architecture is things like i386, sparc, mips, arm
--
alan dot mckinnon at gmail dot com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] Qt-core-4.5.1 jamboree not optimised for i686
2009-06-03 11:41 ` Alan McKinnon
@ 2009-06-03 12:23 ` Mick
0 siblings, 0 replies; 3+ messages in thread
From: Mick @ 2009-06-03 12:23 UTC (permalink / raw
To: gentoo-user
2009/6/3 Alan McKinnon <alan.mckinnon@gmail.com>:
> On Wednesday 03 June 2009 13:35:04 Mick wrote:
>> Major build this morning of qt with a lot of blockers. Having
>> unmerged a lot of packages to remove the blockers I am now emerging
>> qt-core. I noticed this on my screen:
>>
>> Determining system architecture... (Linux:2.6.29-gentoo-r5:i686)
>> 32-bit Intel 80x86 (i386)
>> 'i386' is supported
>> System architecture: 'i386'
>> Symbol visibility control enabled.
>> Symbolic function binding enabled.
>>
>> This is the Qt/X11 Open Source Edition.
>>
>> Since I have these in make.conf I would think that a package like qt
>> would compile optimised code for my architecture, not just i386?
>>
>> ARCH="x86"
>> CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -msse -mmmx -pipe"
>> MAKEOPTS="-j2"
>> ACCEPT_KEYWORDS="x86"
>> CHOST="i686-pc-linux-gnu"
>> CXXFLAGS="${CFLAGS}"
>>
>> Just curious.
>
> architecture != cpu type
>
> in this case architecture is things like i386, sparc, mips, arm
Hey! I knew that!
Thanks :)
--
Regards,
Mick
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-06-03 12:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-03 11:35 [gentoo-user] Qt-core-4.5.1 jamboree not optimised for i686 Mick
2009-06-03 11:41 ` Alan McKinnon
2009-06-03 12:23 ` Mick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox