[gentoo-bsd] UNSUBSCRIBE Re: Subject: Digest of gentoo-bsd@lists.gentoo.org issue 64 (157-158)

[gentoo-bsd] UNSUBSCRIBE Re: Subject: Digest of gentoo-bsd@lists.gentoo.org issue 64 (157-158)

[Pawel Kilian]

[-- Attachment #1: Type: text/plain, Size: 9959 bytes --]

UNSUBSCRIBE 


On Saturday, January 19, 2013 at 5:02 AM, gentoo-bsd+help@lists.gentoo.org wrote:

> Topics (messages 157 through 158):
> 
> [gentoo-bsd] Two issues.
> 157 - Yuta SATOH <nigoro@gentoo.gr.jp (mailto:nigoro@gentoo.gr.jp)>
> 
> [gentoo-bsd] Two issues.
> 158 - Robert Raitz <pappy_mcfae@yahoo.com (mailto:pappy_mcfae@yahoo.com)>
> 
> Forwarded message:
> > From: Yuta SATOH <nigoro@gentoo.gr.jp>
> > Reply To: gentoo-bsd@lists.gentoo.org
> > To: gentoo-bsd@lists.gentoo.org
> > Date: Tuesday, January 15, 2013 7:02:23 AM
> > Subject: Re: [gentoo-bsd] Two issues.
> > 
> > Hi,
> > 
> > On Wed, 9 Jan 2013 02:28:37 -0800 (PST)
> > Robert Raitz <pappy_mcfae@yahoo.com (mailto:pappy_mcfae@yahoo.com)> wrote:
> > 
> > > The first issue is a segfault when issuing startx. 
> > > It looks like the segfault happens as dri2 is initializing. 
> > > 
> > 
> > 
> > Does this bug will not be helpful to you ?
> > https://bugs.gentoo.org/435648
> > 
> > > I'm thinking I'm going to backtrack to xorg-server-1.7.7-r1, as I have a
> > > backup from this machine when it was running that version of xorg-server
> > > as well as KDE3. Considering that FreeBSD 9.0 is using that version, or
> > > close to it, it should work for me as well. Sure, I'll have to re-enable
> > > the hal USE flag, but I've done that before.
> > > 
> > > The second problem is a bit more perplexing. When trying to setup the
> > > cross-compiler for using distcc with the Gentoo/FBSD hybrid, things fail
> > > with freebsd-libs dying over lack of libutil.h. Here's the snippet from
> > > the log:
> > > 
> > > /var/tmp/portage/cross-i686-gentoo-freebsd9.0/freebsd-lib-8.2-r1/work/lib/libc/posix1e/extattr.c:37:21: fatal error: libutil.h: No such file or directory
> > > compilation terminated.
> > > *** Error code 1
> > > 
> > > Stop.
> > > pmake: stopped in /var/tmp/portage/cross-i686-gentoo-freebsd9.0/freebsd-lib-8.2-r1/work/lib/libc
> > > ?* ERROR: cross-i686-gentoo-freebsd9.0/freebsd-lib-8.2-r1 failed (compile phase):
> > > ?*?? make libc failed
> > > ?* 
> > > ?* Call stack:
> > > ?*???? ebuild.sh (http://ebuild.sh), line? 93:? Called src_compile
> > > ?*?? environment, line 2765:? Called die
> > > ?* The specific snippet of code:
> > > ?*?????????? $(freebsd_get_bmake) ${mymakeopts} || die "make libc failed";
> > > 
> > > When trying to get any freebsd-lib package to take, I run into them all
> > > NOT including the amd64 or ~amd-64 keywords. In other words, they are
> > > all keyword masked. I'd like to unmask, but I worry that I'll break the
> > > machine I'm using to cross-compile. I'd really rather not do that if at
> > > all possible. If I am to use the freebsd-lib version that goes with my
> > > hybrid, that version is keyword masked. As a matter of fact, it seems
> > > the only one I can get to take is freebsd-lib-8.2-r1, and that's not the
> > > version I am running. 
> > > 
> > > So, my question is, how to set up the cross-compiler such that it works,
> > > and doesn't break anything else? Do I have to redo the ebuilds to force
> > > things to work? 
> > > 
> > 
> > 
> > Are you using crossdev ?
> > cross-*-freebsd-lib should automatically be unmasked by crossdev.
> > 
> > I have confirmed that cross compiler is completed on Gentoo/Linux amd64
> > in the next step.
> > 
> > 1. emerge sys-devel/crossdev
> > 2. cd /usr/portage/sys-freebsd/freebsd-lib
> > 3. wget -O freebsd-lib-9.1_rc3-r1.ebuild \
> > "http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-bsd.git;a=blob_plain;f=sys-freebsd/freebsd-lib/freebsd-lib-9.1_rc3-r1.ebuild;h=d4f4b85f9a07aa502b36678a756ca759def52d2a;hb=d92895be6230221821bc177e251139b5cad05155"
> > 4. ebuild freebsd-lib-9.1_rc3-r1.ebuild digest
> > 5. mkdir /etc/portage/package.keywords
> > 6. echo 'sys-freebsd/freebsd-mk-defs ~amd64' >> /etc/portage/package.keywords/local
> > 7. echo 'sys-apps/mtree ~amd64' >> /etc/portage/package.keywords/local
> > 8. crossdev --g '>4.7' i686-gentoo-freebsd9.1
> > 
> > > 
> > > The xorg-server issue I'll deal with on my own. I just have to find the
> > > DVD with the last stage-4 I did with this machine in the older
> > > configuration, unless there are other suggestions for getting this
> > > version of xorg-server (1.13) to work..
> > > 
> > > Cheers,
> > > Pappy
> > > 
> > 
> > 
> > 
> > 
> > Regards,
> > -- 
> > Yuta SATOH
> > 
> > 
> 
> Forwarded message:
> > From: Robert Raitz <pappy_mcfae@yahoo.com>
> > Reply To: gentoo-bsd@lists.gentoo.org
> > To: gentoo-bsd@lists.gentoo.org <gentoo-bsd@lists.gentoo.org>
> > Date: Tuesday, January 15, 2013 11:36:34 PM
> > Subject: Re: [gentoo-bsd] Two issues.
> > 
> > As an update, I did get X to work. Yes, that was the bug. I am at xorg-server-1.11.4-ish, and I do have X. The problem is, I want xfce4, which means pango, which will not finish compilation. 
> > 
> > Let me be a bit more specific. If I compile pango without the 'X' or 'introspection' USE flags, it will compile. As soon as either one is turned on, the compilation fails. That means no mousepad or leafpad, no thunar, not even my xscreensaver hacks. I have fvwm with xterm, lots of fonts, but nothing beyond having multiple terminal screens. Because it's currently a bit dumb, and on a hard drive that isn't this one, getting exact output is rough. I am most likely going to be putting it back into a chroot session.
> > 
> > I've seen that there are some freebsd bugs in bugzilla. Can I report that pango issue there, or should I post it somewhere else? Basically, what can be done to get me to a point where I can get my beastly penguin as usable as it's straight-up non-hybrid counterparts residing on this drive? Now that X is running, I find it a beastly tease to not allow xfce4, or anything other than fvwm or twm. Anyone who has gotten beyond that issue, please let me know what to do. I'm really hooked on getting it going fully. Apparently, KMS is coming soon for FreeBSD, and that's good for hybrid users, too. Probably even better for us.
> > 
> > Cheers,
> > Pappy
> > 
> > 
> > From: Yuta SATOH <nigoro@gentoo.gr.jp (mailto:nigoro@gentoo.gr.jp)>
> > To: gentoo-bsd@lists.gentoo.org (mailto:gentoo-bsd@lists.gentoo.org) 
> > Sent: Tuesday, January 15, 2013 4:02 AM
> > Subject: Re: [gentoo-bsd] Two issues.
> > 
> > Hi,
> > 
> > On Wed, 9 Jan 2013 02:28:37 -0800 (PST)
> > Robert Raitz <pappy_mcfae@yahoo.com (mailto:pappy_mcfae@yahoo.com)> wrote:
> > 
> > > The first issue is a segfault when issuing startx. 
> > > It looks like the segfault happens as dri2 is initializing. 
> > 
> > Does this bug will not be helpful to you ?
> > https://bugs.gentoo.org/435648
> > 
> > > I'm thinking I'm going to backtrack to xorg-server-1.7.7-r1, as I have a
> > > backup from this machine when it was running that version of xorg-server
> > > as well as KDE3. Considering that FreeBSD 9.0 is using that version, or
> > > close to it, it should work for me as well. Sure, I'll have to re-enable
> > > the hal USE flag, but I've done that before.
> > > 
> > > The second problem is a bit more perplexing. When trying to setup the
> > > cross-compiler for using distcc with the Gentoo/FBSD hybrid, things fail
> > > with freebsd-libs dying over lack of libutil.h. Here's the snippet from
> > > the log:
> > > 
> > > /var/tmp/portage/cross-i686-gentoo-freebsd9.0/freebsd-lib-8.2-r1/work/lib/libc/posix1e/extattr.c:37:21: fatal error: libutil.h: No such file or directory
> > > compilation terminated.
> > > *** Error code 1
> > > 
> > > Stop.
> > > pmake: stopped in /var/tmp/portage/cross-i686-gentoo-freebsd9.0/freebsd-lib-8.2-r1/work/lib/libc
> > > ?* ERROR: cross-i686-gentoo-freebsd9.0/freebsd-lib-8.2-r1 failed (compile phase):
> > > ?*?? make libc failed
> > > ?* 
> > > ?* Call stack:
> > > ?*???? ebuild.sh (http://ebuild.sh), line? 93:? Called src_compile
> > > ?*?? environment, line 2765:? Called die
> > > ?* The specific snippet of code:
> > > ?*?????????? $(freebsd_get_bmake) ${mymakeopts} || die "make libc failed";
> > > 
> > > When trying to get any freebsd-lib package to take, I run into them all
> > > NOT including the amd64 or ~amd-64 keywords. In other words, they are
> > > all keyword masked. I'd like to unmask, but I worry that I'll break the
> > > machine I'm using to cross-compile. I'd really rather not do that if at
> > > all possible. If I am to use the freebsd-lib version that goes with my
> > > hybrid, that version is keyword masked. As a matter of fact, it seems
> > > the only one I can get to take is freebsd-lib-8.2-r1, and that's not the
> > > version I am running. 
> > > 
> > > So, my question is, how to set up the cross-compiler such that it works,
> > > and doesn't break anything else? Do I have to redo the ebuilds to force
> > > things to work? 
> > 
> > Are you using crossdev ?
> > cross-*-freebsd-lib should automatically be unmasked by crossdev.
> > 
> > I have confirmed that cross compiler is completed on Gentoo/Linux amd64
> > in the next step.
> > 
> > 1. emerge sys-devel/crossdev
> > 2. cd /usr/portage/sys-freebsd/freebsd-lib
> > 3. wget -O freebsd-lib-9.1_rc3-r1.ebuild \
> > "http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-bsd.git;a=blob_plain;f=sys-freebsd/freebsd-lib/freebsd-lib-9.1_rc3-r1.ebuild;h=d4f4b85f9a07aa502b36678a756ca759def52d2a;hb=d92895be6230221821bc177e251139b5cad05155"
> > 4. ebuild freebsd-lib-9.1_rc3-r1.ebuild digest
> > 5. mkdir /etc/portage/package.keywords
> > 6. echo 'sys-freebsd/freebsd-mk-defs ~amd64' >> /etc/portage/package.keywords/local
> > 7. echo 'sys-apps/mtree ~amd64' >> /etc/portage/package.keywords/local
> > 8. crossdev --g '>4.7' i686-gentoo-freebsd9.1
> > 
> > > 
> > > The xorg-server issue I'll deal with on my own. I just have to find the
> > > DVD with the last stage-4 I did with this machine in the older
> > > configuration, unless there are other suggestions for getting this
> > > version of xorg-server (1.13) to work..
> > > 
> > > Cheers,
> > > Pappy
> > 
> > 
> > 
> > Regards,
> > -- 
> > Yuta SATOH
> > 
> > 
> > 
> > 


[-- Attachment #2: Type: text/html, Size: 13476 bytes --]