[gentoo-dev] The dreaded debug use flag/eclass

[gentoo-dev] The dreaded debug use flag/eclass

[Alec Warner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Oh yeah, it's back, for the 6th time :)

I've provided links to all the other discussions I could find on
theaimsgroup in case you want to take a trip down memory lane.
Hopefully I'll summarize the previous discussion well enough that you
don't have to torture yourself..too much.

The latest discussion ( [4], [5] ) was brought up by SpanKY about how
the debug use flag and eclass are used differently depending on the
situation.  Some used the flag for turning on internal debugging
routines ( think verbose library output ).  Some used the flag to change
 CFLAGS and turn off stripping so that the debug symbols would remain
intact.

- From use.desc we gather:
skyfw@kyoto /usr/portage/profiles $ cat use.desc | grep debug
debug - Tells configure and the makefiles to build for debugging.
Effects vary across packages, but generally it will at least add -g to
CFLAGS. Remember to set FEATURES=nostrip too

Many people do not like the fact that a USE flag changes CFLAGS.
Although there are other USE flags that do this too ( pic comes to mind
in a couple ebuilds, checkpassword fex ) they are a minority compared to
debug.  People want to be able to debug things in a simple manner, and
this is not easily possible with the current portage system.  It
requires per-package FEATURES ( which is bottled with a host of other
things, see [6] ).

So, for future versions of portage ( not stable, unless per-package
features makes it in...somehow ) we add a FEATURE called "debug".  This
FEATURE will:
1. Set CFLAGS to a gentoo standard set ( perhaps user configurable ) of
flags.
2. Will turn on FEATURES="nostrip".
3. Anything else it should do? ( Redhat's moving debug info to a
seperate location perhaps? [3]

The debug.eclass will be depreciated.  The DEBUG use flag will change
names to an agreed upon name that specifies the addition of debuging
output.  Foser's debuginfo change seemed appropriately named ( although
thanks for changing it back :) ).

No more eclass, no more packages inheriting from the debug but not even
using the USE flag, just one per-package feature.

[1] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=8&s=debug&q=b
[2] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=7&s=debug&q=b
[3] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=4&s=debug&q=b
[4] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=2&s=debug&q=b
[5] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=1&s=debug&q=b
[6] http://bugs.gentoo.org/show_bug.cgi?id=44796
[7] http://bugs.gentoo.org/show_bug.cgi?id=55708
[8] http://bugs.gentoo.org/show_bug.cgi?id=55977

- -Alec Warner ( Antarus )
warnera6@egr.msu.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQu7KxmzglR5RwbyYAQIXjg//VjprL1CML8ZfYvSNLI/AujugOs1p3M4X
zFomIdqklIlzYNYet6qKe8esi3TQe59/UwYvQBTsIg7gXYI3ij6oq81CbU7MQUY5
DK1YKlAdsW75EKwhc8Bo47m7X9medC55m6XcoiweRPoEcsF9B1Aw1qfRm5B9WT8J
hYtRmp0vHvdF9Viw0t5ekpX3VvYrqffheClUs9i0VraDikZ3ycKk8cKGpxPDUxE1
CwcnaPMN2HKNNW2jieH4rrTVRNCaZ2ZIf/x5QlaU1i8W20KzoT5JUAkMQVcsQtby
FTfN35xgK1BFGblPHpb4taRGgwa2oaQwXUV+aux8nZy9jYXPBQcEXFRSoGKpHlNp
uAftITo93MDC06PqcstVBCsJJTTiiP6MGIyfn+U0ghopPBpF7/Cn9RLQxrTbBJVC
M2yEIZ+mb+3Nneii5kUe9ErH2EgEt/K2UkPLNXZBS6kiFI9AGSQZK/3bVE3QUbFM
hN5hP0IGgS7WU3qFO8PluOOoIm/uDhG9XyWoCqW0rO5rLv2eCeqpNhIhZANs2Plw
xjZuGnPkMLA1TxF2OZoc5T3+/gUHX/2Y/aAItYTZra+lvQBEZMXz3Kxoz4vmWjWs
rWsbTejZMUUUfd8XVXxBLw4WFt2V2pDdla1LzAx9lF+aSMm15NhdwmfCV7nHblaU
bB+LTL4QH9g=
=3iaR
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Mike Frysinger]

On Monday 01 August 2005 09:22 pm, Alec Warner wrote:
> Many people do not like the fact that a USE flag changes CFLAGS.
> Although there are other USE flags that do this too ( pic comes to mind
> in a couple ebuilds, checkpassword fex ) they are a minority compared to
> debug.

your USE=pic example is wrong, it does not change CFLAGS (and if your package 
does, it is broken)
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Mike Frysinger]

On Monday 01 August 2005 10:07 pm, Mike Frysinger wrote:
> On Monday 01 August 2005 09:22 pm, Alec Warner wrote:
> > Many people do not like the fact that a USE flag changes CFLAGS.
> > Although there are other USE flags that do this too ( pic comes to mind
> > in a couple ebuilds, checkpassword fex ) they are a minority compared to
> > debug.
>
> your USE=pic example is wrong, it does not change CFLAGS (and if your
> package does, it is broken)

and i just reviewed all packages which declare IUSE=pic and they were pretty 
much all wrong:
amanda
tvtime
sil-plugin
c-client
uw-imap
checkpassword
chillispot
cherokee
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Danny van Dyk]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger schrieb:
|>your USE=pic example is wrong, it does not change CFLAGS (and if your
|>package does, it is broken)
|
|
| and i just reviewed all packages which declare IUSE=pic and they were
pretty
| much all wrong:
[...]
| chillispot
chillispot at least is not wrong. If USE="pic" is set, it compiles _only
with_ -fPIC, ommiting to compile files twice and effectivly telling
libtool not to produce a normal static library.

Danny
- --
Danny van Dyk <kugelfang@gentoo.org>
Gentoo/AMD64 Project, Gentoo Scientific Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC7t3NaVNL8NrtU6IRAu2CAJ0WSnKRYbI4HPAWgZVJFO/1yOsOjgCeOIaC
ck3L6XbX2GcDbwdukzQfZto=
=rX06
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Mike Frysinger]

On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
> chillispot at least is not wrong. If USE="pic" is set, it compiles _only
> with_ -fPIC, ommiting to compile files twice and effectivly telling
> libtool not to produce a normal static library.

not really

chillispot doesnt build/install any libraries
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Danny van Dyk]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger schrieb:
| On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
|
|>chillispot at least is not wrong. If USE="pic" is set, it compiles _only
|>with_ -fPIC, ommiting to compile files twice and effectivly telling
|>libtool not to produce a normal static library.
|
|
| not really
|
| chillispot doesnt build/install any libraries
| -mike
Heh, in this case the --with-pic option for configure is useless and has
no effect :-/

Danny
- --
Danny van Dyk <kugelfang@gentoo.org>
Gentoo/AMD64 Project, Gentoo Scientific Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC71SuaVNL8NrtU6IRAoLuAJ9Iq7OjfP20V1cnmYyHhlgSJnUxuQCdE61f
UdWn3jR83wmZftVQIBrmSCQ=
=25Q6
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Mike Frysinger]

On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
> Mike Frysinger schrieb:
> |>your USE=pic example is wrong, it does not change CFLAGS (and if your
> |>package does, it is broken)
>
> chillispot at least is not wrong. If USE="pic" is set, it compiles _only
> with_ -fPIC, ommiting to compile files twice and effectivly telling
> libtool not to produce a normal static library.

just to review ... `use_with pic` should never be used because if you dont 
have 'pic' in your USE flags, the ebuild will run `./configure 
--without-pic` ... that means libtool will try to produce shared and static 
libraries with object files which were built without PIC ... on many arches 
(like amd64), the linker will abort

btw, where do you get this information ?  my tests show that libtool still 
compiles all files twice even though --with-pic was used ...
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Martin Schlemmer]

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

On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote:
> On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
> > Mike Frysinger schrieb:
> > |>your USE=pic example is wrong, it does not change CFLAGS (and if your
> > |>package does, it is broken)
> >
> > chillispot at least is not wrong. If USE="pic" is set, it compiles _only
> > with_ -fPIC, ommiting to compile files twice and effectivly telling
> > libtool not to produce a normal static library.
> 
> just to review ... `use_with pic` should never be used because if you dont 
> have 'pic' in your USE flags, the ebuild will run `./configure 
> --without-pic` ... that means libtool will try to produce shared and static 
> libraries with object files which were built without PIC ... on many arches 
> (like amd64), the linker will abort
> 
> btw, where do you get this information ?  my tests show that libtool still 
> compiles all files twice even though --with-pic was used ...

Last time I checked, only --without-pic or --disable-static disable
compiling twice.


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Mike Frysinger]

On Wednesday 03 August 2005 07:16 am, Martin Schlemmer wrote:
> On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote:
> > On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
> > > Mike Frysinger schrieb:
> > > |>your USE=pic example is wrong, it does not change CFLAGS (and if your
> > > |>package does, it is broken)
> > >
> > > chillispot at least is not wrong. If USE="pic" is set, it compiles
> > > _only with_ -fPIC, ommiting to compile files twice and effectivly
> > > telling libtool not to produce a normal static library.
> >
> > just to review ... `use_with pic` should never be used because if you
> > dont have 'pic' in your USE flags, the ebuild will run `./configure
> > --without-pic` ... that means libtool will try to produce shared and
> > static libraries with object files which were built without PIC ... on
> > many arches (like amd64), the linker will abort
> >
> > btw, where do you get this information ?  my tests show that libtool
> > still compiles all files twice even though --with-pic was used ...
>
> Last time I checked, only --without-pic or --disable-static disable
> compiling twice.

my tests show that with libtool 1.5.18 --without-pic doesnt change 
anything ... obviously --disable-static changes things same as 
--disable-shared would :P

maybe i just did it wrong ... i used imlib2-1.2.0 as a reference
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Danny van Dyk]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger schrieb:
| On Wednesday 03 August 2005 07:16 am, Martin Schlemmer wrote:
|
|>On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote:
|>
|>>On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
|>Last time I checked, only --without-pic or --disable-static disable
|>compiling twice.
|
|
| my tests show that with libtool 1.5.18 --without-pic doesnt change
| anything ... obviously --disable-static changes things same as
| --disable-shared would :P
|
| maybe i just did it wrong ... i used imlib2-1.2.0 as a reference
| -mike
According to libtool's source, it only compiles things twice if it shall
build 'old-libs' ($build_old_libs=yes) _and_ shared libraries. If it
builds 'libtool-libs' ($build_libtool_libs=yes) it uses the same object
files for both the static and the shared library.

But I might be comletely wrong... libtool's internals are sometimes so
confusing :-/

Danny
- --
Danny van Dyk <kugelfang@gentoo.org>
Gentoo/AMD64 Project, Gentoo Scientific Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC8MJ7aVNL8NrtU6IRAh5OAKCLThNfuQH+vq8hCKZUxZZhz/8zuwCcD61l
rBB/S+0uH0MiRt5lNZj3eMo=
=gBww
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Paul de Vrieze]

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

On Wednesday 03 August 2005 15:11, Danny van Dyk wrote:
> Mike Frysinger schrieb:
> | On Wednesday 03 August 2005 07:16 am, Martin Schlemmer wrote:
> |>On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote:
> |>>On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
> |>
> |>Last time I checked, only --without-pic or --disable-static disable
> |>compiling twice.
> |
> | my tests show that with libtool 1.5.18 --without-pic doesnt change
> | anything ... obviously --disable-static changes things same as
> | --disable-shared would :P
> |
> | maybe i just did it wrong ... i used imlib2-1.2.0 as a reference
> | -mike
>
> According to libtool's source, it only compiles things twice if it
> shall build 'old-libs' ($build_old_libs=yes) _and_ shared libraries. If
> it builds 'libtool-libs' ($build_libtool_libs=yes) it uses the same
> object files for both the static and the shared library.
>
> But I might be comletely wrong... libtool's internals are sometimes so
> confusing :-/

It shouldn't, and I believe it doesn't. Static libraries should be built 
without -pic, and shared with. Of course static libraries with pic do 
work, but it is a suboptimal solution. (Unless you want to include said 
static library into a shared library). Just see a static library as 
nothing more or less than a system archive of object files that 
applications can include.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] The dreaded debug use flag/eclass

[Alec Warner]

Mike Frysinger wrote:

>On Monday 01 August 2005 09:22 pm, Alec Warner wrote:
>  
>
>>Many people do not like the fact that a USE flag changes CFLAGS.
>>Although there are other USE flags that do this too ( pic comes to mind
>>in a couple ebuilds, checkpassword fex ) they are a minority compared to
>>debug.
>>    
>>
>
>your USE=pic example is wrong, it does not change CFLAGS (and if your package 
>does, it is broken)
>-mike
>  
>
I know what it is supposed to be used for, pointing it out for the fact 
that many packages use it incorrectly, just as debug is used incorrectly :P
-- 
gentoo-dev@gentoo.org mailing list