Re: [gentoo-catalyst] Generic stage1 and glibc

[John Eckhart]

Andrew Gaffney wrote:
> John Eckhart wrote:
>> I'm trying to build a generic stage1 using the
>> stage3-x86-2006.1.tar.bz2 as a seed and the 20070319 portage
>> snapshot. I can get all the way up to the building of glibc
>> (glibc-2.5 as per the portage snapshot), which fails with the
>> following error:
>>
>>  * i386 CHOSTs are no longer supported.
>>  * Chances are you don't actually want/need i386.
>>  * Please read http://www.gentoo.org/doc/en/change-chost.xml
>>
>> !!! ERROR: sys-libs/glibc-2.5 failed.
>>
>>
>> I wonder how the release team is producing the stage1's for 2007.0.
>> Are they masking glibc-2.5 or have they moved the sub-architecture
>> for stage1-x86 to something newer like i586?
>
> There is a build problem with glibc-2.5 for the i386 CHOST. Rather
> than fix it (which would be a lot of work for virtually no benefit),
> the minimum supported CHOST has been changed to i486. Just set 'chost:
> i486-pc-linux-gnu' in your stage1.spec. Unless you're planning on
> installing on an actual 386, this will work fine for 486 and up.
>

Andrew,
    Thanks, that helps. I am also seeing another build error when 
building nano for the stage 1. It appears that the stage2 and stage3 
seeds from 2006.1 are built without unicode support in ncurses, yet nano 
is trying to build with unicode.

I've attached my spec file, here is a summary:
   building: stage1-x86
   seed: stage2-x86-2006.1
   snapshot: 20070319
   catalyst: 2.0.3

I'm not sure if I did something wrong, or it's because I am using the 
latest portage snapshot, etc. If the problem has to do with the snapshot 
then I can think of a few ways to fix it: add -unicode to the nano use 
flags, pull the unicode nano requirement when USE="build", add a command 
in the stage1-chroot.sh to update the seed and rebuild curses with unicode.

Here is the excerpt from my build log:

...
configure: error:
*** UTF-8 support was requested, but insufficient UTF-8 support was
*** detected in your curses and/or C libraries.  Please verify that your
*** slang was built with UTF-8 support or your curses was built with
*** wide character support, and that your C library was built with wide
*** character support.

!!! Please attach the following file when filing a report to 
bugs.gentoo.org:
!!! /var/tmp/portage/app-editors/nano-2.0.3/work/nano-2.0.3/config.log

!!! ERROR: app-editors/nano-2.0.3 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 1238:   Called src_compile
  nano-2.0.3.ebuild, line 44:   Called econf '--bindir=/bin' 
'--enable-color' '--enable-multibuffer' '--enable-nanorc' '--disable-wr
apping-as-root' '--disable-spell' '--disable-justify' '--disable-debug' 
'--disable-nls' '--enable-utf8' '--disable-tiny' '--without-
slang'
  ebuild.sh, line 577:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call 
stack if relevant.
!!! A complete build log is located at 
'/var/tmp/portage/app-editors/nano-2.0.3/temp/build.log'.


!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1047, in run_local
    cmd("/bin/bash "+self.settings["controller_file"]+" run","run script 
failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 485, in cmd
    raise CatalystError,myexc
CatalystError: <unprintable instance object>
None

!!! catalyst: Stage build aborting due to error.


Catalyst aborting....