New Gentoo/FreeBSD 9.0 stages for x86 and amd64

Hi,

I've (finally) made new fbsd stages. They are available at:
http://dev.gentoo.org/~aballier/fbsd9.0/
in their respective directories.
(at the time of writing this email, there's only amd64 but x86 will
appear soon)

I'll make some more testing and would appreciate any feedback. If
everything goes well I'll push them to the mirrors, in the usual
experimental directory.

I would like to thank especially Yuta SATOH and Richard Yao for their
work on making new stages for Gentoo/FreeBSD which made the task much
easier.

Regards,

Alexis.

New x86-fbsd stage3

Dear Everyone,

I made an unofficial x86-fbsd stage3. It is available at the following
address:

http://www.cs.stonybrook.edu/~ryao/stage3-i686-freebsd-9.0.tar.bz2

Yours truly,
Richard Yao

Gentoo/FBSD Install

I'd like to set up a Gentoo/FBSD install to test some packages, but the
docs are out of date and I can't figure it out myself. Has anyone set
one up recently? If so, can it be explained relatively painlessly?

G/FreeBSD: 8.0, (almost) new stages and removal of old versions

Hi all,

I am going to remove all the freebsd ebuilds that are not 7.2; the 6.2
profiles have been gone for a while and ebuilds are really not
maintained, 7.1 profiles have been deprecated for a while too (2
months). If anyone has objections, speak up now!

For those of you who have not updated yet, it is probably simpler to
start a fresh install from the 7.2 stages that I've pushed some months
ago (see experimental/x86/freebsd/7.2/stages/ in the mirrors). I have
not received rants against those stages so I'll assume they're fine :)
About sparc-fbsd, I have (thanks to Monkeh) access to a sparc-fbsd box
where I've put a 7.2 but the port is more surviving than anything else.
The box doesn't have enough disk space to build stages for example,
thus I am nowhere near to be able to push new stages.

As for 8.0, I'll start playing with it now; if any of you have started
to play with it and wanna share the experience, please poke me.

Regards,

Alexis.

New profile.bashrc.

Hello everybody.

I'm back, sort of, job's workload went a bit down thanks to a change
freeze during holidays.

So I went on a emerge rampage that got me bitching and moaning about the
parallel make install problems. Here's the profile.bashrc that I came up
with (charset.alias stuff taken from the Gentoo/Prefix profile.bashrc,
I'm in doubt here, was this fixed already?).
Please review/test/etc. Right now my G/FBSD install survives an emerge
-e @system with MAKEOPTS=-j6 which it didn't survive before...
Except for sys-apps/ed, which is using a bare /usr/bin/install from it's
Makefile.

By the way, anybody working on 8.0 ebuilds? ^_^

if [[ ${EBUILD_PHASE} == compile ]] ; then
	if grep -q "Assume that mode_t is passed compatibly" ${S} -r --include openat.c; then
		eerror "The source code contains a faulty openat.c unit from gnulib."
		eerror "Please report this on Gentoo Bugzilla in Gentoo/Alt product for component FreeBSD."
		eerror "http://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt&component=FreeBSD&op_sys=FreeBSD"
		die "Broken openat.c gnulib unit."
	fi
        if grep -q "test .*==" "${S}" -r --include configure; then
                eerror "Found a non POSIX test construction in a configure script"
                eerror "The configure checks of this package may not function properly"
                eerror "Please report this on Gentoo Bugzilla in Gentoo/Alt product for component FreeBSD."
                eerror "http://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt&component=FreeBSD&op_sys=FreeBSD"

[SoC 2009] Gentoo/NetBSD important stuff (!)

Hello everybody,

I've been quiet since 1 month, sorry for the delay but it's maily because of
my studies.

Thanks to Alexis Ballier, I've been able to upload my files somewhere on the
web; actually it's hosted on a Gentoo webserver, waiting for somewhere else..

Here is the URL [1]. You'll find:
- A stage3 Gentoo/NetBSD tarball. To install it, you'll have to download NetBSD
  [2] and perform a minimal installation. If you have troubles during
installation, I advise you to read Chapter 3 of NetBSD handbook, "Example
installation", which describes how to do, step by step [3].

- A QEMU image, archived using lzma. This is the quickest way to test my work,
  without performing an installation. To proceed, QEMU has to be installed on
your machine. I let you read documentation on how to proceed to let your VM
surf the web (hint: you must use tun/tap(4) driver), in order to download
ebuilds from it.

Please, feel free to ask questions or to make suggestions, I'll be glad to
answer. I'm currently applying to become a Gentoo developer, to continue
working on that project, I don't want it to die !

Cheers,

Patrice

[1] http://dev.gentoo.org/~aballier/gnbsd/
[2] ftp://ftp4.fr.netbsd.org/pub/NetBSD/NetBSD-5.0/i386/installation/cdrom/

[SoC 2009] End of SoC 2009: Gentoo/NetBSD project final report

Hello everyone,

Today is the end of Summer of Code. As soon as I can (= when it'll be possible
to upload this stuff somewhere), I'll release 3 important things to the
Gentoo/BSD community:

- Gentoo/NetBSD ebuilds: as I said, these ebuilds need to be polished, reworked and
  tested. I didn't get a lot of feedbacks on them so please, be soft with me. :P
- gentoo-netbsd-5.0-stage3.tar.bz2: the famous tarball in question. I'll write
  a little wiki to explain installation steps but it should be very easy: perform
a minimal NetBSD install, download the tarball, extract, and enjoy !
- QEMU VM image: for people who don't want to mess with the install, an image
  will be available. I really need to wait for Google to give us a place to
upload our stuff because of the size of the VM (3 GB). Please, be patient. I'm
sorry but currently, I don't have enough place on my VPS. (perhaps Gentoo guys
can provide me some .. ? :D)

I've made some screenshots of this VM during boot process via OpenRC, login,
emerging of an ebuild (nano), .. Take a look at this url to see them:
http://omani.ac/4ap

This project won't die after GSoC; I'd like to continue working on this in
order to make something as mature as Gentoo/FreeBSD project. Yeah, there is a
big amount of work. :)

As usual, don't hesitate to comment my work, I'll be glad to hear you. :)

I'd like to thank Luca Barbato for his support during the half my GSoC; I
probably wouldn't have finished this project without him. I also like to thank
gentoo-bsd mailing list guys for their precious answers. Even if their has been

[SoC 2009] Gentoo/NetBSD ? Of course it runs !

Heya people,

This is the final GSoC week and we are near from the end: I'll soon release my
work. Yesterday, I've tried to boot a NetBSD machine under QEMU, where my stage
has been extracted and guess what? It boots, I can login into, and even emerge ebuilds!

I've planned to release 3 things to the community:
- my ebuilds: they need to be reworked and to be heavily tested. The only
  feedbacks I get has been from Davide and Luca. Don't hesitate to make
suggestions and comments on my work.
- a stage: currently, the stage contains everything you'll need to run the
  system. Fetch NetBSD 5.0, perform a minimal install and untar the stage on /,
as a normal Gentoo/Linux install.
- a QEMU image: to quickly test my work, without losing time of an
  installation, you can try this image. Simply boot the image and enjoy.

I'm 5% from the end. What are the 5% left ?
A very weird behavior has appeared: on my NetBSD box, when I emerge an ebuild
in the ROOT, as example: nano, ebuild is emerged, chrooting inside the ROOT and
running the binary works fine. No problem with that. So where is the error ?
When I emerge the same ebuild inside the ROOT, it works but each time you
execute this binary, it produces a gmon.out file. Even without using emerge
(downloading sources, ./configure & make), it also produces a gmon.out after
beeing executed. I don't think the problem comes from emerge. But from where ?
GCC comes from NetBSD sources, as same as binutils.
I can read in GCC man page that gmon.out is produced when -pg flag is used.
Here are my CFLAGS & CXXFLAGS variables from /etc/make.conf, in my ROOT directory:
  CFLAGS="-march=i386 -pipe -O2"
  CXXFLAGS=${CFLAGS}
I use the same outside the ROOT (on my NetBSD devel box). I've never used this

Help wanted?

[SoC 2009] What's new ?

Hello everyone,

Here are the lastest news about the project.

What have been done ?
- I coded the lastet ebuild needed to complete my "collection": NetBSD 5.0 kernel compilation & installation.
- I've made changes in my ebuilds, in order to make them use bsdmk eclass. It
  is much painless to write NetBSD ebuilds using this eclass.
- I've added new functions to my NetBSD eclass. These functions use bsdmk
  eclass sub-functions.
- Thanks to Javier comment, I've created patches for Makefiles in order to
  remove some binaries / libraries compilation & installation. Here is the list
of what I've removed and what I'll need to emerge to install what have been
removed:
http://projects.boulz.org/trac/gentoo-nbsd/attachment/wiki/WikiStart/netbsd-gentoo-ebuilds.txt

What needs to be done ?
- OpenRC integration: We will stop to use NetBSD rc services management in
  favor of OpenRC services management. I've successfuly compiled OpenRC (which
seems to work out-of-the-box on NetBSD). I've also read
http://www.gentoo.org/doc/en/openrc-migration.xml but I would like to write a
checklist concerning NetBSD before moving forward. I'm very new to this stage
so any help would be appreciated.
- Profile creation: Currently, I've made a crappy copy/paste from "x86-fbsd"
  profile but I would like to create a new profile. Same as above, I'm new to
this stage and any help would be much appreciated.
- Ebuilds testing/patching: Portage tools rely on Perl and Python and I'll
  sureley have to patch these ebuilds. I should plan a bulk build to test which
ebuilds work/fail during compilation process.

As usual, any comments/suggestions are welcome, so please don't hesitate!

Cheers,

Patrice

[SoC 2009] News & progress about porting Portage on NetBSD/x86

Hello everyone,

I've been busy and quiet since my last email; indeed, I had busy times due to
school related things to do (mostly exams). You surely know what it means.. :)

Let's talk about my GSoC project and things I've done since the last time I
gave you information.

I wrote many ebuilds, in order to emerge some specific parts of NetBSD. There
is one eclass, which is used to fetch sources using CVS. This eclass is also
used to specify where sources are downloaded on the system. End-user can
specify a personnal path and a special CVS tag to fetch sources.

As I said on my Trac wiki, you can build-up a NetBSD system using my ebuilds.
Actually, using ROOT option, I've been able to setup a working NetBSD system,
chroot inside the ROOT directory and been able to compile some C source code
with GCC: just a simple "hello world!". But it proves that GNU as and GNU ld
work with GCC, as well as include headers. So, I think the toolchain fully
works.
2 or 3 ebuilds are missing: /usr/share, /rescue and maybe /usr/games. Not to
mention an important ebuild: NetBSD kernel!

Now, my work will focus on bulk build Portage tree, and determine which ebuilds
work/fail during compilation process. After some tests, I have to install
Portage packages into a 3rd party directory, something like /usr/pkg (default
location using pkgsrc) or /usr/local. Why ? I've tried to emerge bash: bash
depends on ncurses, so I emerged ncurses before bash. ncurses compiled fine
(yes!) but while installing it, a lot of files conflicted with existing files
(mainly /usr/lib and /usr/include). My searches, to set up a different prefix
than the default one used in ebuild.sh (/usr) lead me to an interesting Gentoo
project: Gentoo Prefix. I'll dig on this to see if I can use it or not. But it
seems clear to me that I MUST use a different prefix to install packages.

Any comments/suggestions are welcome, please don't hesitate!

Thanks for reading and have a nice day.

Patrice