Gentoo Archives: gentoo-amd64

From: Beso <givemesugarr@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] madwifi-ng not compile in amd64
Date: Wed, 30 Jan 2008 08:18:54
Message-Id: d257c3560801300018t4c91a689ncdad88116c7dfe39@mail.gmail.com
In Reply to: Re: [gentoo-amd64] madwifi-ng not compile in amd64 by Volker Armin Hemmann
1 2008/1/30, Volker Armin Hemmann <volker.armin.hemmann@××××××××××××.de>:
2 >
3 > On Mittwoch, 30. Januar 2008, Beso wrote:
4 > > the real problem stands in the keyword.... the amd64 would downgrade a
5 > lot
6 > > of stuff.... before doing it it's better to identify the normal
7 > programs,
8 > > like kde, gnome, and similar and let them be for the moment as
9 > ~amd64....
10 > > but at least stuff like, gcc, glibc, baselayout, kernel and some other
11 > base
12 > > stuff should stay on the amd64 branch.... you won't be able to downgrade
13 > > glibc so that one for the moment would stay on the unstable branch....
14 > but
15 > > if you don't feel in the mood to downgrade cause the ~amd64 being to
16 > > amd64, then just update the profile and you should see something like
17 > 100
18 > > packages....
19 > > also adding --as-needed as LDFLAGS should help you save some time in
20 > > recompiling stuff....
21 >
22 > yeah - no. Don't do it. It breaks stuff.
23
24
25 it doesn't anymore. it works very well.
26
27
28 > the 2gb of ccache would help, but not a lot.... 400+ packages would mean
29 > > about 3-4 days on a amd64 2ghz single core, so prepare for a looong time
30 > of
31 > > compile time.... also the 5 blockers are not good and should be fixed in
32 > > some way before proceeding to the recompile....
33 >
34 > no, it would mean something around 12h. Depending on the packages.
35
36
37 400 packages of which gcc and gnome ones is more than 12h....
38
39 > if you decide to modify the use flags when changing profile it's the best
40 > > time....
41 >
42 > yeah, check which flags changed, and which ones you really need. That way
43 > you
44 > might be able to cut down the amount of packages.
45 >
46 > > so my advice is the following:
47 > > 1. take some time to look at the use flags (emerge ufed and see a
48 > > description of them and also add/remove them from the ufed gui in
49 > > make.conf)
50 > > 2. add LDFLAGS="--as-needed" into make.conf
51 >
52 > really, don't do it.
53
54
55 really do it!!!! the flag works very well and doesn't give any breakage
56 anymore.... the packages that are broken by this flags have all ldflags
57 removed in the ebuild so there's no reason to not use it.
58
59 > > Total: 478 packages (1 upgrade, 396 downgrades, 14 new, 1 in new slot,
60 > > > 66 reinstalls, 5 blocks), Size of downloads: 480,074 kB
61 >
62 > check your keywords - and blockers are easily solved. Usually you need to
63 > unmerge something. And the blocking ebuild tells you what.
64 >
65 >
66 > And agtdino and Beso:
67 >
68 > DO NOT TOP POST.
69 >
70 > This is not a Windows mailing list.
71
72
73 this is how web gmail works when replying.
74
75 --
76 > gentoo-amd64@l.g.o mailing list
77 >
78 >
79
80
81 --
82 dott. ing. beso

Replies

Subject Author
Re: [gentoo-amd64] madwifi-ng not compile in amd64 agtdino <agtdino@××××××××.es>