[gentoo-user] custom-cxxflags not supported but on anyway

[gentoo-user] custom-cxxflags not supported but on anyway

[Dale]

Hi,

I'm in the process of installing KDE 4 and noticed something new to me. 
I generally check my USE flags and make sure I am getting what I want
and not getting what I don't.  I noticed this tho:

> [ebuild   R   ] x11-libs/qt-core-4.4.2  USE="qt3support ssl
> -custom-cxxflags% -debug -doc -glib -pch" 0 kB
> [ebuild   R   ] x11-libs/qt-test-4.4.2  USE="-custom-cxxflags% -debug
> -pch" 0 kB
> [ebuild   R   ] x11-libs/qt-script-4.4.2  USE="-custom-cxxflags%
> -debug -pch" 0 kB
> [ebuild  NS   ] app-crypt/qca-2.0.0-r2 [1.0-r3] USE="-debug -doc
> -examples" 0 kB
> [ebuild   R   ] x11-libs/qt-sql-4.4.2  USE="qt3support sqlite
> -custom-cxxflags% -debug -firebird -mysql -odbc -pch -postgres" 0 kB
> [ebuild  N    ] net-libs/libvncserver-0.9.1  USE="jpeg zlib -no24bpp
> -nobackchannel" 0 kB
> [ebuild  N    ] media-libs/xvid-1.1.3  USE="(-altivec) -examples" 0 kB
> [ebuild  N    ] media-libs/libmodplug-0.8.4-r2  0 kB
> [ebuild  N    ] sys-libs/libieee1284-0.2.8  USE="-doc" 0 kB
> [ebuild  N    ] dev-libs/libpthread-stubs-0.1  USE="-debug" 0 kB
> [ebuild   R   ] x11-libs/qt-dbus-4.4.2  USE="-custom-cxxflags% -debug
> -pch" 0 kB
> [ebuild   R   ] x11-libs/qt-gui-4.4.2-r1  USE="accessibility cups dbus
> qt3support tiff -custom-cxxflags% -debug -glib -mng -nas -nis -pch
> -xinerama" INPUT_DEVICES="-wacom" 0 kB
> [ebuild   R   ] x11-libs/qt-qt3support-4.4.2  USE="accessibility
> -custom-cxxflags% -debug -pch" 0 kB
> [ebuild   R   ] x11-libs/qt-svg-4.4.2  USE="-custom-cxxflags% -debug
> -pch" 0 kB
> [ebuild   R   ] x11-libs/qt-webkit-4.4.2  USE="-custom-cxxflags%
> -debug -pch" 0 kB
> [ebuild   R   ] x11-libs/qt-opengl-4.4.2  USE="qt3support
> -custom-cxxflags% -debug -pch" 0 kB

This is just a few that are clumped together.  There are quite a few
others as well.  After checking I find out this:

> root@smoker / # euse -i custom-cxxflags
> global use flags (searching: custom-cxxflags)
> ************************************************************
> [-    ] custom-cxxflags - Build with user-specified CXXFLAGS (unsupported)
>
> local use flags (searching: custom-cxxflags)
> ************************************************************
> no matching entries found
> root@smoker / #

I notice it says unsupported.  So I thought maybe I added this at some
point but didn't remember it.  Here is my related make.conf info:

> root@smoker / # cat /etc/make.conf | grep USE=
> USE="-a52 acl acpi alsa amd arts artswrappersuid automount -bluetooth
> -branding bzip2 cddb cdr chroot crypt curl dbus -doc -dts dvd dvdr
> dvdread esd exif fdftk -fftw -firefox  -gcj gif gimp gkrellm -gnome
> gphoto2 gtk hal hbci htmlhandbook ipv6 java javascript jbig jpeg
> jpeg2k justify kde kdeprefix libwww logrotate loop-aes mmx mplayer mp3
> -musepack -mysql -nls nsplugin ofx offensive opengl -oss parport pdf
> ppds qt3  qt3support qt4 realmedia seamonkey sqlite sse syslog tcl
> -theora tiff tk truetype usb -v4l webkit win32codecs wma wmf wmp X xml
> xprint yahoo -xulrunner zeroconf 3dnow "
> root@smoker / # cat /etc/make.conf | grep FLAG
> CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
> CXXFLAGS="${CFLAGS}"
> root@smoker / #

I try to keep my USE line in alphabetical order but I just don't see
that flag in there.  I know KDE 4 is not stable but some of the packages
are being recompiled because of the USE flag being changed.  This is my
profile info:

> root@smoker / # eselect profile list
> Available profile symlink targets:
>   [1]   hardened/x86/2.6
>   [2]   selinux/2007.0/x86
>   [3]   selinux/2007.0/x86/hardened
>   [4]   default/linux/x86/2008.0
>   [5]   default/linux/x86/2008.0/desktop *
>   [6]   default/linux/x86/2008.0/developer
>   [7]   default/linux/x86/2008.0/server
>   [8]   hardened/linux/x86
> root@smoker / # 


I also checked the profile USE but don't see the change in there
either.  So, why is this enabled but not supported?  Is this safe to
have enabled?  Does it even matter anyway?  What is making it even
change to begin with? 

Thanks.

Dale

:-)  :-) 

P. S.  I bet this will be simple too.  o_O

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Daniel Pielmeier]

>> [ebuild   R   ] x11-libs/qt-core-4.4.2  USE="qt3support ssl
>> -custom-cxxflags% -debug -doc -glib -pch" 0 kB

-custom-cxxflags

To me it looks like it is disabled!
This flag has been added recently to the qt packages and although it
is disabled the affected packages need a rebuild when newuse is
triggered.

-- 
Regards,
Daniel

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]

On Mon, 16 Feb 2009 12:38:25 +0100, Daniel Pielmeier wrote:

> This flag has been added recently to the qt packages and although it
> is disabled the affected packages need a rebuild when newuse is
> triggered.

Use --reinstall changed-use instead of --newuse. It saves on pointless
rebuilds.


-- 
Neil Bothwick

The trouble with life is that you are halfway through it before you
realize it's a "do it yourself" thing.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Daniel Pielmeier]

2009/2/16 Neil Bothwick <neil@digimed.co.uk>:
> On Mon, 16 Feb 2009 12:38:25 +0100, Daniel Pielmeier wrote:
>
>> This flag has been added recently to the qt packages and although it
>> is disabled the affected packages need a rebuild when newuse is
>> triggered.
>
> Use --reinstall changed-use instead of --newuse. It saves on pointless
> rebuilds.
>

Hm I must have missed this option somehow. Good to know there is such
feature. I guess in this case only the portage package database is
updated.

-- 
Regards,
Daniel

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Dale]

Daniel Pielmeier wrote:
>>> [ebuild   R   ] x11-libs/qt-core-4.4.2  USE="qt3support ssl
>>> -custom-cxxflags% -debug -doc -glib -pch" 0 kB
>>>       
>
> -custom-cxxflags
>
> To me it looks like it is disabled!
> This flag has been added recently to the qt packages and although it
> is disabled the affected packages need a rebuild when newuse is
> triggered.
>
>   

But since it is changing, I would assume it was on before?  If it was
off before then why would it rebuild it? 

I do have to say, I don't recall ever seeing this one before.

Dale

:-)  :-) 

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Daniel Pielmeier]

2009/2/16 Dale <rdalek1967@gmail.com>:
>
> But since it is changing, I would assume it was on before?  If it was
> off before then why would it rebuild it?
>
> I do have to say, I don't recall ever seeing this one before.
>

The use flag was intruduced to the stable version without a version
bump. So it is a new flag but if you don't enable it nothing will
change if you do a rebuild. Thus following the suggestion from Neil
would be the best solution. If I had known this option before it would
have saved me a useless rebuild.

-- 
Regards,
Daniel

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Dale]

Neil Bothwick wrote:
> On Mon, 16 Feb 2009 12:38:25 +0100, Daniel Pielmeier wrote:
>
>   
>> This flag has been added recently to the qt packages and although it
>> is disabled the affected packages need a rebuild when newuse is
>> triggered.
>>     
>
> Use --reinstall changed-use instead of --newuse. It saves on pointless
> rebuilds.
>
>
>   

Well, it is done now.  You know what would be nice, a mailing list that
announces these new "features".  Maybe one that only devs can post to
but anyone can receive.  Just a little note that something new is coming
and what it does would be really nice.

Dale

:-)  :-) 

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Alan McKinnon]

On Monday 16 February 2009 20:36:02 Dale wrote:
> Well, it is done now.  You know what would be nice, a mailing list that
> announces these new "features".  Maybe one that only devs can post to
> but anyone can receive.  Just a little note that something new is coming
> and what it does would be really nice.

Well, there sort-of is something like that already - the Changelog. The 
trouble with news-announce-change lists is that no-one can ever make up their 
mind as to what goes on it and what doesn't, so they end up sooner or later 
being a dump for the entire Changelog (which you already have :-) )

I've been caught out by this stuff too many times. Now I always read 
/var/portage/profiles/package.mask before an update. With a bit of practise 
anf doing it frequently, you get a good idea of what parts of the tree are 
active and where changes are being made. Helps with predicting stuff :-)

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 544 bytes --]

On Mon, 16 Feb 2009 14:50:37 +0100, Daniel Pielmeier wrote:

> >
> > Use --reinstall changed-use instead of --newuse. It saves on pointless
> > rebuilds.
 
> Hm I must have missed this option somehow. Good to know there is such
> feature. I guess in this case only the portage package database is
> updated.

It's fairly new, especially on stable. AFAIK it doesn't touch the package
database, so a subsequent --newuse will still want to rebuild the package.


-- 
Neil Bothwick

Check three friends. If they're OK, you're it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] custom-cxxflags not supported but on anyway

[Dale]

Alan McKinnon wrote:
> On Monday 16 February 2009 20:36:02 Dale wrote:
>   
>> Well, it is done now.  You know what would be nice, a mailing list that
>> announces these new "features".  Maybe one that only devs can post to
>> but anyone can receive.  Just a little note that something new is coming
>> and what it does would be really nice.
>>     
>
> Well, there sort-of is something like that already - the Changelog. The 
> trouble with news-announce-change lists is that no-one can ever make up their 
> mind as to what goes on it and what doesn't, so they end up sooner or later 
> being a dump for the entire Changelog (which you already have :-) )
>
> I've been caught out by this stuff too many times. Now I always read 
> /var/portage/profiles/package.mask before an update. With a bit of practise 
> anf doing it frequently, you get a good idea of what parts of the tree are 
> active and where changes are being made. Helps with predicting stuff :-)
>
>   

Yew a better guru than me tho.  ;-)

lol

Dale

:-)  :-)