1 |
On 12/14/2012 05:31 AM, Ed W wrote: |
2 |
> Hey, cool! |
3 |
> |
4 |
> Sorry, bit slow keeping up with the list. Great work though! I have been |
5 |
> using x86 uclibc for a year now on an embedded router distro, so |
6 |
> completely behind this. With new uclibc+nptl there are generally very |
7 |
> few build problems. Main problem is builds which exclude iconv and |
8 |
> gettext... (eg glib needs some hacking) |
9 |
|
10 |
Recent >glib-2.30.3 + uclibc is a real pita and breaking everything that |
11 |
links against glib. I'm busy with other stuff but glib is the major |
12 |
stumbling block now. I think the problem is in pthreads. I haven't had |
13 |
time to git bisect it down to the breaking commit. |
14 |
|
15 |
> |
16 |
> Just a couple of random thoughts: |
17 |
> |
18 |
> - You pull in libiconv as a required package? Wasn't the complaint that |
19 |
> this could cause problems with GCC upgrades later? Note I have some |
20 |
> patches that I submitted in the past which allow uclibc to build a |
21 |
> partly working iconv (almost certainly got bugs, but seems to pass the |
22 |
> obvious tests) |
23 |
|
24 |
In cross compiling with CHOST= a glibc system, uclibc iconv code builds |
25 |
fine. But it does not build fine on a native uclibc system. Lots of |
26 |
things need iconv now, even coreutils. See bug #445716. |
27 |
|
28 |
> |
29 |
> - You have -iconv as a git use, but I think most git ebuilds are forcing |
30 |
> it back on again no matter what you say? |
31 |
|
32 |
That's an old workaround. It should work now. Let me know. |
33 |
|
34 |
> |
35 |
> - You appear to mask nls? How about defaulting it to off rather than |
36 |
> forcing it off? I'm still unclear what problems are actually caused by |
37 |
> installing gettext? Seems like it can cause a permanent dep with gcc |
38 |
> linking to it, but for some situations that is probably not the end of |
39 |
> the world? Surely some people want nls on... (not me) |
40 |
|
41 |
Okay but please test and open a bug. Tell me what arch you tested on, |
42 |
exactly what change was made to the profiles etc. |
43 |
|
44 |
> |
45 |
> |
46 |
> It would definitely be good to try and get people building uclibc with |
47 |
> iconv - as in, hopefully people will file bugs and fix them and quickly |
48 |
> we might end up with a proper working iconv in uclibc. Also canvasing |
49 |
> for a mini gettext implementation for runtime use... |
50 |
> |
51 |
> |
52 |
> Thanks for your work on this! |
53 |
|
54 |
Pay me in beer or patches :) |
55 |
|
56 |
|
57 |
> |
58 |
> Ed W |
59 |
> |
60 |
> |
61 |
> On 02/11/2012 11:24, Anthony G. Basile wrote: |
62 |
>> Hi everyone, |
63 |
>> |
64 |
>> Can I get feedback regarding the subproject page at |
65 |
>> |
66 |
>> http://www.gentoo.org/proj/en/hardened/uclibc/ |
67 |
>> |
68 |
>> before I link it up and announce it to the rest of the world. |
69 |
>> |
70 |
>> BTW, newer stage3's for amd64 and x86 uclibc are on the tree now under |
71 |
>> experimental. |
72 |
>> |
73 |
>> --Tony |
74 |
>> |
75 |
>> |
76 |
>> On 10/27/2012 06:17 AM, Anthony G. Basile wrote: |
77 |
>>> Hi everyone, |
78 |
>>> |
79 |
>>> Either today or tomorrow, there will be two new experimental hardened |
80 |
>>> profiles, one on amd64 and the other x86. These will be: |
81 |
>>> |
82 |
>>> hardened/linux/uclibc/amd64 |
83 |
>>> |
84 |
>>> and |
85 |
>>> |
86 |
>>> hardened/linux/uclibc/x86 |
87 |
>>> |
88 |
>>> Please be careful with them! Do not try to switch to these profiles from |
89 |
>>> a glibc system. portage will complain about blocking and not let you |
90 |
>>> proceed, but for the truly stubborn who will hack away until it does |
91 |
>>> work, trust me, it will not work. It will utterly break everything. |
92 |
>>> |
93 |
>>> Aside: while this is an extreme case, switching profiles is never to be |
94 |
>>> taken lightly. Eg. hardened <-> non-hardened or selinux <-> non-selinux. |
95 |
>>> |
96 |
>>> For the curious, you can play with these using the stage3's at |
97 |
>>> |
98 |
>>> http://http://67.151.215.237/ |
99 |
>>> |
100 |
>>> Notice there are 4 combinations |
101 |
>>> |
102 |
>>> amd64 hardened |
103 |
>>> amd64 vanilla |
104 |
>>> |
105 |
>>> i686 hardened |
106 |
>>> i686 vanilla |
107 |
>>> |
108 |
>>> The amd64 are completely done. I'm working on i686 now so you may want |
109 |
>>> to wait on those. Any stage marked on or later than oct 25 should be |
110 |
>>> good. |
111 |
>>> |
112 |
>>> Note: the vanilla is just hardened with USE="-hardened" set in |
113 |
>>> make.conf. They are being built as a comparison to the hardened. |
114 |
>>> |
115 |
>>> |
116 |
>>> |
117 |
>> |
118 |
>> |
119 |
> |
120 |
|
121 |
|
122 |
-- |
123 |
Anthony G. Basile, Ph. D. |
124 |
Chair of Information Technology |
125 |
D'Youville College |
126 |
Buffalo, NY 14201 |
127 |
(716) 829-8197 |