| Re: [proaudio] Museseq won't re-emerge after emerge --sync |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] Museseq won't re-emerge after emerge --sync
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Date: Tue, 5 Jun 2007 20:25:15 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Sun, 3 Jun 2007 22:48:43 +0000,
"Krzysztof Polikowski" <polikowski@xxxxxxxxx> a écrit :
> So, tell me, what i should change? My system is very stable and fast.
> I can setup Cflags & Ldflags in /etc/portage/env/ for jackd and museseq.
> What is wrong in ldflags & cflags?
>
> Greetings.
>
The problem with custom cflags is at you are on your own because ANY custom
cflags need profiling for EACH SINGLE package in the box.
Cflags and ldflags are a very sensitive issue. It is even worst because
each gcc version can (and will) behave differently with the same combination of
custom cflags. I was experimenting with such flags it was some time ago, and at
the end, the only solution was to reformat and reinstall all with safe cflags.
Custom cflags can introduce very subtle bugs that only a profiling can find.
(profiling is a process where you begin to compile a software with same cflags,
make test to be sure at it behave as wanted, and recompile the software
with other cflags and compare the result with the result of the first reference
compilation.)
And now one have the time to do profiling for each single package in the box,
and that after each gcc upgrade.
On gentoo, you have a 3 level cflags strategy:
system cflags in /etc/make.conf, just use safe flags here;
ebuild cflags, just trust the gentoo developers here,
and package cflags, just trust the package maker here.
Ciao,
Dominique
> 2007/6/3, Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx>:
> >
> > On So, 03.06.07 21:39 "Krzysztof Polikowski" <polikowski@xxxxxxxxx>
> > wrote:
> >
> > > ok, here it is,
> > >
> > > [..]
> > > CFLAGS="-march=nocona -O2 -s -pipe -fomit-frame-pointer -msse3 -mmmx
> > > -mfpmath=sse -funswitch-loops -ftree-vectorize -fprefetch-loop-arrays
> > > -frerun-cse-after-loop -momit-leaf-frame-pointer -DNDEBUG
> > > -DG_DISABLE_ASSERT -DNO_DEBUG"
> > > CHOST="x86_64-pc-linux-gnu"
> > > [..]
> > > LDFLAGS="-Wl,-O1,--enable-new-dtags,--sort-common,--as-needed
> > > -Bdirect -s"
> > > MAKEOPTS="-j3 -s"
> >
> > Wicked!
> >
> > Well, you're on your own.
> > We can't and never will support something like this.
> >
> > T.
> >
> >
>
>
--
Dominique Michel
--
N.B.: Tous les emails que je reçois sont filtrés par spamassassin avant de me
parvenir.