Friday 14 Aug 2009 13:15:07 (+0200), Alexis Ballier wrote :
> I didn't know you were left alone; if you need some help you can
> contact me too; unfortunately I'm way too busy these days to be able to
> be a full mentor but I'm interested in seeing a g/netbsd port so I can
> give a high priority in helping you towards that goal :)
Shit happens. But thanks for your help. :)
I'm gonna ping you on IRC.
>
> I've a couple of remarks wrt
> http://projects.boulz.org/trac/gentoo-nbsd/attachment/wiki/WikiStart/netbsd-gentoo-ebuilds.txt
>
> netbsd-bin
> | sh -> app-shells/bash = OK
>
> This doesn't sound optimal; I'd rather keep netbsd sh which is probably
> a POSIX compliant sh and leave bash as /bin/bash; while in practice this
> is not always the case, all gentoo packages should be fine with /bin/sh
> not being bash. Esp. openrc works very well with a more
> lightweight /bin/sh than bash and thus makes booting faster.
Ok, I'll correct that.
>
> netbsd-sbin
> | rcorder -> nothing = OK
>
> rcorder is the thing that does a topological sort on init script
> dependencies, right? In that case, with openrc it's very unlikely to be
> needed but IMHO it would be nice to have it available (an useflag?).
Using OpenRC makes rcorder useless: it's used in /etc/rc script.
>
> netbsd-ubin
> 14 | m4 -> sys-devel/m4 = OK
> 15 | patch -> sys-devel/patch = OK
> 22 | sed -> sys-apps/sed = OK
>
> Be careful there: all of them prepend the binaries names with a g when
> userland isn't gnu. On FreeBSD, with portage we use the GNU versions
> (see profiles/default/bsd/fbsd which aliases them) but BSD versions have
> been preferred as, respectively, m4, patch and sed. This raises the
> question: what userland do you want to have? IMHO it is better to have
> a full BSD userland while stuff that require GNU tools can use the g
> prefixed tools; with that idea you can see portage as a pkgsrc
> replacement (or ports replacement in case of fbsd) instead of a
> different system with a netbsd kernel & libc but with the rest of it
> being GNU.
I didn't know that, and it's great if "g" suffix is added.
But Portage needs some GNU tools like GNU sed: some scripts/patches
don't work if you don't use it. Same thing about awk:
I read ebuild.sh source code and "gawk" command is used. I'll correct this but
I'll still install them in my stage.
>
> 17 | yacc -> sys-devel/bison = OK
>
> Here too: On FreeBSD we use yacc from freebsd-ubin. bison ebuild should
> be fine with that and won't install the yacc symlink.
On my "correct" list.
>
> 24 | uuidgen -> sys-apps/e2fsprogs = FAIL
>
> Keep it there and don't worry about the e2fsprogs version. The e2fsprogs
> version uses libuuid which shouldn't be needed on BSD. I'm not sure
> about netbsd, but freebsd has uuid functions in the libc; they come
> with a different interface but do the same thing. See eg
> https://bugs.gentoo.org/show_bug.cgi?id=270003
> Otherwise you'll need libuuid from util-linux, and good luck getting
> something working on BSD out of it.
Yes, NetBSD has also his own version of uuidgen and libuuid. On my list.
>
> netbsd-usbin
> 42 | lp,lpc,lpd,lpq,lpr,lprm,lptest,pac->net-print/cups=FAIL
> 43 | postfix (MKPOSTFIX) -> mail-mta/postfix = FAIL
> 44 | wpa_* -> net-wireless/wpa_supplicant = FAIL
>
> We should probably address these. What's the failure there?
>
*
> netbsd-libs
> 49 | libss -> sys-libs/ss = OK
>
> sys-libs/ss shouldn't be used, take the one from e2fsprogs-libs.
>
> 54 | libpcap -> net-libs/libpcap = FAIL
>
> What's the problem here?
>
*
> 55 | libcom_err -> sys-libs/e2fsprogs-libs with
> "--disable-tls" ./configure flag = OK
>
> What's the problem with tls?
>
*,
which means: we should talk about this on IRC. I'll give you errors logs. It's
mainly compilation errors.
>
> About the ebuilds in the overlay:
>
> netbsd-kernel -> usually we name kernel as -sources: gentoo-sources,
> freebsd-sources, etc.
I'm gonna rename it.
>
> netbsd-binutils, netbsd-gcc: what's the point of these wrt
> sys-devel/{binutils,gcc} ?
>
NetBSD devs seem to have patched GCC sources to suit to NetBSD. I maybe writing
a big mistake. But I have tried every GCC's ebuilds and none of them have
worked. Even by downloading GCC sources on gcc.gnu.org website, ./configure and
make, it simply doesn't work. That's why I've created an ebuild..
>
> wrt the way you disable bundled libs (eg in netbsd-libs): can't this be
> done on a more generic way than patching, like the way freebsd.eclass
> does with REMOVE_SUBDIRS ? Doesn't dummy-mk from bsdmk.eclass work on
> netbsd makefiles?
>
Yes, it should work. In fact, it's because I haven't yes packaged my ebuilds
that I've used patches. To compile and install one of my ebuilds, you'll need
to download sources via CVS. My ebuilds are just a frontend to /usr/src. I know
it's not the right way to do: Davide seemed to be fine with that, but Luca
explained me how to proceed. For the moment, I'll stay with this configuration
because it "works". But, of course, I'll correct this after GSoC.
>
> > Another problem I face is Kerberos libraries compilation. It fails to
> > compile with this error:
> > http://pastebin.org/8892
>
> Sounds like openssl related; what provides /usr/include/openssl/evp.h ?
>
~ grep "EVP_PKEY_decrypt" /usr/include/openssl/evp.h
int EVP_PKEY_decrypt(EVP_PKEY_CTX *ctx, unsigned char *out, size_t *outlen, const unsigned char *in, size_t inlen);
> > I also have to change two ./configure args which are "--without-et"
> > and "--without-ss" to pass configure script. According to ./configure
> > help: --with-system-et use system compile_et and -lcom_err [default:
> > build and install a local version]
> > --with-system-ss use system -lss and mk_cmds [private version]
>
> Why do you need this? e2fsprogs-libs should provide libcomm_err and
> libss and we should seriously avoid using bundled libs in packages.
>
I've tried to compile Kerberos 5 1.7 this morning and it works without changing
any ./configure flags. The only error comes from PKINIT: it is an extension
to Kerberos that adds public key cryptography. Do we really need it ?
Thus, if I remove it from Makefile, compilation works fine.
>
>> I'm currently facing PAM
>> problems. I remember Johan Hattne sending me an email about PAM
>> patches especially for NetBSD. Johan, if you read me, your help would
>> be much appreciated !
>
> Just in case, you're using sys-auth/openpam, right?
>
> Alexis.
>
Yes. The problem comes from "passwd" program which segfaults. I need to dig on
this more. I can provide a .core if you want.
Anyway, thanks again for your help. :)
Cheers!
Patrice
|
