Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 348673 - sparc64-freebsd bootstrap profile support
Summary: sparc64-freebsd bootstrap profile support
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: Sparc64 FreeBSD
: High enhancement
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-14 05:28 UTC by Lucas Yamanishi
Modified: 2011-04-06 17:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Yamanishi 2010-12-14 05:28:46 UTC
I successfully bootstrapped gentoo-prefix on my sparc64/freebsd8.1 machine.  I request the requisite profile is added to the tree at portage/profiles/prefix/bsd/freebsd/8.1/sparc64

Reproducible: Didn't try

Steps to Reproduce:
1. Install FreeBSD 8.1 on sparc64 Sun Fire V100

2. Make requiste profile based on freebsd/8.0/x86
2a.  modify ARCH, CHOST and ACCEPT_KEYWORD variables
2b.  set freebsd/8.1/package.provided to include sys-freebsd/libc-8.1
2c.  mask >sys-devel/binutils-2.20.1-r1 and >sys-devel/gcc-4.2.4-r1
2d.  link the created profile tree to your an installed portage tree using the parent file from /freebsd/8.1/



3. Follow prefix bootstrap guide for FreeBSD at http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml
3a.  Add ACCEPT_KEYWORDS="~sparc-solaris" to $EPRFIX/etc/make.conf
3b.  after step 'emerge --sync', remove all but ARCH, CHOST and ACCEPT_KEYWORDS from the custom make.defaults and redirect the parent file to the new $EPREFIX/usr/portage tree
Actual Results:  
Gentoo-Prefix bootstraps successfully

Expected Results:  
Gentoo-Prefix bootstraps successfully

Since portage doesn't include support for KEYWORD ~sparc64-freebsd, and the prefix tree doesn't include ~sparc-fbsd I was forced to use ~sparc64-solaris.  I imagine it would work with most other prefix keywords, but I didn't try anything else.  My logic was simple: arch was most important, followed by testing outside of linux.

Also, root's default shell is /bin/csh, so the startprefix script wouldn't work until I changed SHELL to /bin/tcsh.
Comment 1 Fabian Groffen gentoo-dev 2010-12-14 20:14:09 UTC
Hi!

I added a csh -> tcsh hack in the bootstrap startscript target, like we do for sh -> bash

what CHOST do you have in use?  I assumed sparc64-unknown-freebsd8.1 for now

I added the profile to the tree.
Comment 2 Lucas Yamanishi 2010-12-15 05:52:51 UTC
Yes.

ARCH="sparc-fbsd"
CHOST="sparc64-unknown-freebsd8.1"
ACCEPT_KEYWORDS="sparc-fbsd ~sparc-fbsd sparc64-freebsd ~sparc64-freebsd"

In the official prefix tree, I don't think (~)sparc-fbsd is desirable, or even meaningful since it's not included as a keyword in any of the ebuilds.  However, cross referencing it to the main tree serves as a good reference point.
Comment 4 Fabian Groffen gentoo-dev 2011-04-06 17:06:48 UTC
everything here looks done to me, closing