Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-embedded
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
To: Ed W <lists@...>
From: Jude Pereira <judebpereira@...>
Subject: Re: stages for x86 uclibc
Date: Thu, 1 Sep 2011 11:17:47 +0530
<meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Hey Ed,<div>I bumped the ebuild to the snapshot of 20110831 last evening, I&#39;ve successfully compiled it, but then python goes crazy.</div>

<div><br></div><div>It says that it cant find, but it is actually in the correct lib dir. I&#39;m going to look into this even more now.<br clear="all"><font color="#888888"><div><br></div></font></div></span><br>

--Jude Pereira<br>(<a href="" target="_blank"></a>)<br>
<br><br><div class="gmail_quote">On Wed, Aug 31, 2011 at 8:49 PM, Ed W <span dir="ltr">&lt;<a href="mailto:lists@...">lists@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class="im">On 31/08/2011 13:16, Jude Pereira wrote:<br>
&gt; I do have the time to give the uclibc profile in portage a good kick.<br>
&gt; I&#39;m very much into this as I&#39;m working with uclibc toolchains under<br>
&gt; the x86 mainly.<br>
&gt; I&#39;ll make an ebuild for the new one, and test it out.<br>
</div>I didn&#39;t need to do much more than trim out all the old patches and bump<br>
the ebuild. �Just to give a heads up, here are my main changes for<br>
--- /usr/portage/sys-libs/uclibc/uclibc-<br>
2011-04-20 19:31:26.000000000 +0100<br>
+++ /usr/local/portage/sys-libs/uclibc/uclibc-0.9.33_pre20110617.ebuild<br>
2011-06-23 19:43:24.000000000 +0100<br>
@@ -170,6 +173,10 @@<br>
 � � � � � � � �epatch &quot;${WORKDIR}&quot;/patch<br>
 � � � �fi<br>
+ � � � epatch &quot;${FILESDIR}&quot;/${PN}-${PV}-clean.patch<br>
+ � � � epatch &quot;${FILESDIR}&quot;/gen_wc8bit.patch<br>
+ � � � epatch &quot;${FILESDIR}&quot;/gen_wctype.patch<br>
 � � � �sed -i &#39;s:getline:get_line:&#39; extra/scripts/unifdef.c #277186<br>
 � � � �########## CPU SELECTION ##########<br>
@@ -305,6 +312,14 @@<br>
 � � � �cp .config myconfig<br>
 � � � �emake -s clean &gt; /dev/null || die &quot;could not clean&quot;<br>
+ � � � # TODO: These should depend on some useflag, eg iconv<br>
+ � � � # Run after make clean, otherwise files removed<br>
+ � � � find ./extra/locale/charmaps -name &quot;*.pairs&quot; &gt;<br>
+ � � � #cp ./extra/locale/LOCALES ./extra/locale/locales.txt<br>
+ � � � cp &quot;${FILESDIR}&quot;/locales.txt ./extra/locale/locales.txt<br>
+ � � � # TODO: Now edit locales as appropriate...<br>
+ � � � # FIXME: ...<br>
Also, not sure I remember why, but I have this change...<br>
-IUSE=&quot;build uclibc-compat debug hardened ssp ipv6 minimal wordexp<br>
+IUSE=&quot;build elibc_uclibc uclibc-compat debug hardened ssp ipv6 minimal<br>
wordexp crosscompile_opts_headers-only&quot;<br>
The missing patch files are attached (note the _clean_ is not needed on<br>
recent git). �Note the gen_wc patches should be credited/copyrighted to<br>
the chap whos name I forget on the uclibc list who posted them about Feb<br>
this year?<br>
Bit of a mess, but hopefully helpful?<br>
<font color="#888888"><br>
Ed W<br>
stages for x86 uclibc
-- Jude Pereira
Re: stages for x86 uclibc
-- Ed W
Re: stages for x86 uclibc
-- Jude Pereira
Re: stages for x86 uclibc
-- Ed W
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: stages for x86 uclibc
Next by thread:
Re: stages for x86 uclibc
Previous by date:
Re: ARM summit at Plumbers 2011
Next by date:
arm/ac100: /sys doesn't get mounted since baselayout2/openrc

Updated Jun 25, 2012

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.