FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Alt

 
 
LinkBack Thread Tools
 
Old 12-21-2010, 11:33 PM
Perry Smith
 
Default prefix installer, AIX 5.3 gcc failed to build

Hi,

Sorry if I'm becoming a thorn that won't go away.

I started over from scratch and died here. This sounds similar to what the emails were describing. The files listed, like ebuild, egencache, emerge, etc are not in prefix/usr/bin so I can't see what they look like. The path to python appears to be valid but it is from my prefix-launcher directory.

make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/usr/dumps/myself/gpx/portage/sys-apps/portage-2.2.01.17409/work/prefix-portage-2.2.01.17409'
make[1]: Leaving directory `/usr/dumps/myself/gpx/portage/sys-apps/portage-2.2.01.17409/work/prefix-portage-2.2.01.17409'
>>> Completed installing portage-2.2.01.17409 into /usr/dumps/myself/gpx/portage/sys-apps/portage-2.2.01.17409/image/gsa/ausgsa-p12/04/prefix/

ecompressdir: bzip2 -9 /gsa/ausgsa-p12/04/prefix/usr/share/man
QA Notice: the following files use invalid (possible non-prefixed) shebangs:
gsa/ausgsa-p12/04/prefix/usr/bin/ebuild:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/bin/egencache:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/bin/emerge:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/bin/portageq:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/bin/quickpkg:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/bin/repoman:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/sbin/archive-conf:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/sbin/dispatch-conf:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/sbin/emaint:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/sbin/env-update:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/sbin/fixpackages:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
gsa/ausgsa-p12/04/prefix/usr/sbin/regenworld:/usr/dumps/prefix-launcher-2.1.0/powerpc-ibm-aix5.3.0.0/usr/bin/python (in PATH but target not found)
ERROR: sys-apps/portage-2.2.01.17409 failed:
Aborting due to QA concerns: invalid shebangs found

Call stack:
misc-functions.sh, line 1699: Called install_qa_check
misc-functions.sh, line 210: Called install_qa_check_prefix
misc-functions.sh, line 857: Called die
The specific snippet of code:
die "Aborting due to QA concerns: invalid shebangs found"

If you need support, post the output of 'emerge --info =sys-apps/portage-2.2.01.17409',
the complete build log and the output of 'emerge -pqv =sys-apps/portage-2.2.01.17409'.
The complete build log is located at '/usr/dumps/myself/gpx/portage/sys-apps/portage-2.2.01.17409/temp/build.log'.
The ebuild environment file is located at '/usr/dumps/myself/gpx/portage/sys-apps/portage-2.2.01.17409/temp/environment'.
S: '/usr/dumps/myself/gpx/portage/sys-apps/portage-2.2.01.17409/work/prefix-portage-2.2.01.17409'
 
Old 12-22-2010, 07:05 AM
Michael Haubenwallner
 
Default prefix installer, AIX 5.3 gcc failed to build

On 12/22/2010 01:33 AM, Perry Smith wrote:
> Hi,
>
> Sorry if I'm becoming a thorn that won't go away.
>
> I started over from scratch and died here.
> This sounds similar to what the emails were describing.
> The files listed, like ebuild, egencache, emerge, etc are not in prefix/usr/bin so I can't see what they look like.
> The path to python appears to be valid but it is from my prefix-launcher directory.

Recently I've been able to do a successfull bootstrap on Linux,
because I've added a workaround for the missing python-symlink
to eprefix-bootstrap.

So you will have to update eprefix-bootstrap/eprefix-bootstrap.build
in prefix-launcher from svn trunk, and then do:
$ gmake config
$ rm -rf buildroot/eprefix-bootstrap/*
$ gmake eprefix-bootstrap

However, on AIX, I still have to fix gcc-4.5.1 which is upgraded to
later in the bootstrap process.

/haubi/
--
Michael Haubenwallner
Gentoo on a different level
 
Old 12-22-2010, 04:11 PM
Perry Smith
 
Default prefix installer, AIX 5.3 gcc failed to build

On Dec 22, 2010, at 2:05 AM, Michael Haubenwallner wrote:

>
> On 12/22/2010 01:33 AM, Perry Smith wrote:
>> Hi,
>>
>> Sorry if I'm becoming a thorn that won't go away.
>>
>> I started over from scratch and died here.
>> This sounds similar to what the emails were describing.
>> The files listed, like ebuild, egencache, emerge, etc are not in prefix/usr/bin so I can't see what they look like.
>> The path to python appears to be valid but it is from my prefix-launcher directory.
>
> Recently I've been able to do a successfull bootstrap on Linux,
> because I've added a workaround for the missing python-symlink
> to eprefix-bootstrap.
>
> So you will have to update eprefix-bootstrap/eprefix-bootstrap.build
> in prefix-launcher from svn trunk, and then do:
> $ gmake config
> $ rm -rf buildroot/eprefix-bootstrap/*
> $ gmake eprefix-bootstrap

Did you mistype this? I'm getting '*** No rule to make target'
 
Old 12-22-2010, 04:35 PM
Perry Smith
 
Default prefix installer, AIX 5.3 gcc failed to build

On Dec 22, 2010, at 2:05 AM, Michael Haubenwallner wrote:

> $ rm -rf buildroot/eprefix-bootstrap/*

I screwed this up. Sorry.

I didn't put the /* at the end.
 
Old 12-22-2010, 04:55 PM
Perry Smith
 
Default prefix installer, AIX 5.3 gcc failed to build

On Dec 22, 2010, at 2:05 AM, Michael Haubenwallner wrote:

>
> On 12/22/2010 01:33 AM, Perry Smith wrote:
>> Hi,
>>
>> Sorry if I'm becoming a thorn that won't go away.
>>
>> I started over from scratch and died here.
>> This sounds similar to what the emails were describing.
>> The files listed, like ebuild, egencache, emerge, etc are not in prefix/usr/bin so I can't see what they look like.
>> The path to python appears to be valid but it is from my prefix-launcher directory.
>
> Recently I've been able to do a successfull bootstrap on Linux,
> because I've added a workaround for the missing python-symlink
> to eprefix-bootstrap.
>
> So you will have to update eprefix-bootstrap/eprefix-bootstrap.build
> in prefix-launcher from svn trunk, and then do:
> $ gmake config
> $ rm -rf buildroot/eprefix-bootstrap/*
> $ gmake eprefix-bootstrap

So I did:

make /usr/dumps/src/prefix-launcher-2.1.0/buildroot/eprefix-bootstrap/eprefix_bootstrap.fetched

to refetch it and then the

make eprefix-bootsrap

worked.
 
Old 12-22-2010, 06:33 PM
Michael Haubenwallner
 
Default prefix installer, AIX 5.3 gcc failed to build

On 12/22/10 18:11, Perry Smith wrote:
>> So you will have to update eprefix-bootstrap/eprefix-bootstrap.build
>> in prefix-launcher from svn trunk, and then do:
>> $ gmake config
>> $ rm -rf buildroot/eprefix-bootstrap/*
>> $ gmake eprefix-bootstrap
>
> Did you mistype this? I'm getting '*** No rule to make target'

Ohw, forgot you do have the prefetched config already - most likely the target
without rule is "buildroot/eprefix-bootstrap/eprefix_bootstrap.fetched.done"

So you should make config again with:
$ gmake config eprefix_bootstrap_BUILDFROM=SCRATCH

This should also recreate the buildroot/eprefix-bootstrap/ directory and tell
'gmake eprefix-bootstrap' to fetch eprefix-bootstrap script first.

Please ensure you have http_proxy set if necessary, or the downloaded
eprefix-bootstrap script might contain some html-error only.

FWIW, the snapshots-from-scratch here now tell that I have to upgrade automake
and autoconf in prefix-launcher to create some local libtool for ncurses...

But as you already have some ncurses bootstrapped, you might be able to continue
with updated eprefix-bootstrap until gcc-4.5.1 - anything >= gcc-4.3 seems to break...

So before continuing you also might want to do this for now:
$ echo '>=sys-devel/gcc-4.3' >> EPREFIX/etc/portage/package.mask

/haubi/
--
Michael Haubenwallner
Gentoo on a different level
 
Old 12-23-2010, 12:17 AM
Perry Smith
 
Default prefix installer, AIX 5.3 gcc failed to build

My bootstrap saga continues:
+ powerpc-ibm-aix5.3.0.0-gcc -DZLIB -DOPENSSL_THREADS -pthread -DDSO_DLFCN -DHAVE_DLFCN_H -O -DB_ENDIAN -DSHA1_ASM -DSHA256_ASM -DAES_ASM -fno-strict-aliasing -shared -Wl,-G -L/gsa/ausgsa-p12/04/prefix/lib -L/gsa/ausgsa-p12/04/prefix/usr/lib -shared -Wl,-bexpall,-bnolibpath,-G,-bernotok,-bsymbolic,-bexpall -o libssl.so.1.0.0 link_tmp.336100/bio_ssl.o link_tmp.336100/d1_both.o link_tmp.336100/d1_clnt.o link_tmp.336100/d1_enc.o link_tmp.336100/d1_lib.o link_tmp.336100/d1_meth.o link_tmp.336100/d1_pkt.o link_tmp.336100/d1_srvr.o link_tmp.336100/kssl.o link_tmp.336100/s23_clnt.o link_tmp.336100/s23_lib.o link_tmp.336100/s23_meth.o link_tmp.336100/s23_pkt.o link_tmp.336100/s23_srvr.o link_tmp.336100/s2_clnt.o link_tmp.336100/s2_enc.o link_tmp.336100/s2_lib.o link_tmp.336100/s2_meth.o link_tmp.336100/s2_pkt.o link_tmp.336100/s2_srvr.o link_tmp.336100/s3_both.o link_tmp.336100/s3_clnt.o link_tmp.336100/s3_enc.o link_tmp.336100/s3_lib.o link_tmp.336100/s3_meth.o link_tmp.336100/s3_pkt.o link_tmp.336100/s3_srvr.o link_tmp.336100/ssl_algs.o link_tmp.336100/ssl_asn1.o link_tmp.336100/ssl_cert.o link_tmp.336100/ssl_ciph.o link_tmp.336100/ssl_err.o link_tmp.336100/ssl_err2.o link_tmp.336100/ssl_lib.o link_tmp.336100/ssl_rsa.o link_tmp.336100/ssl_sess.o link_tmp.336100/ssl_stat.o link_tmp.336100/ssl_txt.o link_tmp.336100/t1_clnt.o link_tmp.336100/t1_enc.o link_tmp.336100/t1_lib.o link_tmp.336100/t1_meth.o link_tmp.336100/t1_reneg.o link_tmp.336100/t1_srvr.o -L. -lcrypto -lzld: 0711-317 ERROR: Undefined symbol: .OPENSSL_cleanse
OPENSSL_cleanse is defined in crypto/mem_clr.c but there is no .o file and no mention of mem_clr in the log files.
I pulled down the source and put it in a stand alone build, made my patch (previous email), and it config'ed and made without incident.
Thanks,pedz
 
Old 12-23-2010, 05:53 AM
Michael Haubenwallner
 
Default prefix installer, AIX 5.3 gcc failed to build

On 12/23/10 02:17, Perry Smith wrote:
> My bootstrap saga continues:
>
>> ld: 0711-317 ERROR: Undefined symbol: .OPENSSL_cleanse
>
> OPENSSL_cleanse is defined in crypto/mem_clr.c but there is no .o file and no mention of mem_clr in the log files.

This is fixed already[1], you might have to get an updated tree,
or take the problematic packages via an svn-checkout of prefix-overlay.
But do not start over, ncurses will break when bootstrapping from
scratch due to [2], but it works when autotools are merged.

> I pulled down the source and put it in a stand alone build, made my patch (previous email), and it config'ed and made without incident.

The problem is that we have to configure with 'no-asm' on aix too.

[1] http://overlays.gentoo.org/proj/alt/changeset/59039
[2] http://overlays.gentoo.org/proj/alt/changeset/59038

/haubi/
--
Michael Haubenwallner
Gentoo on a different level
 

Thread Tools




All times are GMT. The time now is 12:14 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org