1 |
On 5/2/16 5:27 PM, waltdnes@××××××××.org wrote: |
2 |
> On Mon, May 02, 2016 at 04:04:46PM -0400, Anthony G. Basile wrote |
3 |
>> On 5/2/16 2:37 PM, waltdnes@××××××××.org wrote: |
4 |
>>> On Mon, May 02, 2016 at 10:37:45AM -0400, Ian Stakenvicius wrote |
5 |
>>>> On 29/04/16 09:34 PM, waltdnes@××××××××.org wrote: |
6 |
>>>>> On Fri, Apr 29, 2016 at 08:19:53PM -0400, Anthony G. Basile wrote |
7 |
>>>>> |
8 |
>>>>>> 1) i support uclibc across many arches. see |
9 |
>>>>>> |
10 |
>>>>>> https://wiki.gentoo.org/wiki/Project:Hardened_uClibc |
11 |
>>>>>> |
12 |
>>>>>> |
13 |
>>>>>> 2) you can file uclibc bugs and i will look at them. i know about that |
14 |
>>>>>> one and i've got the fix upstream. its going slowly because the bug was |
15 |
>>>>>> in libcheck which is bundled with gstreamer and so there's layers of |
16 |
>>>>>> backporting. see |
17 |
>>>>>> |
18 |
>>>>>> https://bugs.gentoo.org/show_bug.cgi?id=577312 |
19 |
>>>>> |
20 |
>>>>> Thanks. For the time-being, I'll try building Pale Moon without HTML5 |
21 |
>>>>> video support. It may turn up other problems. |
22 |
>>>>> |
23 |
>>>> |
24 |
>>>> |
25 |
>>>> If you needed this for Firefox, grab 45.x or 46.0 since you can get |
26 |
>>>> HTML5 support from ffmpeg directly without needing gstreamer. |
27 |
>>> |
28 |
>>> Firefox's "Australis" can best be described as "the systemd of GUI's". |
29 |
>>> It's what drove me away from Firefox to Pale moon, in the first place, |
30 |
>>> and I'm not going back. |
31 |
>>> |
32 |
>>> I understand that Anthony is frustrated with uclibc, and is working on |
33 |
>>> replacing it with the uclibc-ng fork in the uclibc stage 3. I've run |
34 |
>>> into other issues, besides gstreamer, in uclibc. Hopefully, uclibc-ng |
35 |
>>> will have fewer issues. For now, I'll simply wait until the uclibc-ng |
36 |
>>> stage 3 comes out. |
37 |
>>> |
38 |
>> |
39 |
>> Yes, I am frustrated with uClibc and I'm just one package and a few |
40 |
>> stabilizations away from switching to uclibc-ng. The problem is that |
41 |
>> upstream is very far behind in patches, and even further behind in |
42 |
>> releases. So you submit a patch and you don't even know if it will |
43 |
>> apply cleanly because its in a queue of submissions that have not even |
44 |
>> hit git master/HEAD. Or you want to back port a fix to the 0.9.33 |
45 |
>> branch and there's a dozen other intermediate patches that have to be |
46 |
>> applied first. Since these patches really address other issues, you're |
47 |
>> cutting and pasting code. Its a mess. |
48 |
> |
49 |
> Let me know offline if/when you need a beta tester. I have QEMU and |
50 |
> an ancient 32-bit-only Atom netbook that could really use a smaller |
51 |
> libc. |
52 |
> |
53 |
|
54 |
well at some point i'll start throwing stages up in |
55 |
distfiles.gentoo.org/experimental/<arch>/uclibc-ng. I'll let the list |
56 |
know and it'll be open season on those tarballs. I'll give them about 6 |
57 |
months or so and then drop the older uclibc ones. |
58 |
|
59 |
Beta testing is always welcome, but building stage3's consistently and |
60 |
repeatedly is usually a good indicator that they're good to go. |
61 |
|
62 |
The big problem is going to be the migration. You can't just unmerge |
63 |
uclibc and emerge uclibc-ng. The two hard block one another for that |
64 |
reason. The migration path I took is really really dirty but works: |
65 |
|
66 |
1. ebuild uclibc-ng-<version>.ebuild clean install |
67 |
3. Copy .so files from /var/tmp/portage/.../image/lib to /lib |
68 |
Since the .so versions are different they won't overwrite. |
69 |
4. Use a static binary to switch over the sym links to the new .so's |
70 |
5. emerge uclibc-ng properly |
71 |
6. re-emerge world |
72 |
|
73 |
I can automate some of that with scripts, but it will take care on the |
74 |
part of the user who should be ready to boot off of rescue media. I'm |
75 |
going to recommend that people really avoid that if possible and start anew. |
76 |
|
77 |
-- |
78 |
Anthony G. Basile, Ph.D. |
79 |
Gentoo Linux Developer [Hardened] |
80 |
E-Mail : blueness@g.o |
81 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
82 |
GnuPG ID : F52D4BBA |