On Mon, Nov 7, 2011 at 2:05 PM, Venkatesh Srinivas
wrote:
> kaffe (from pkgsrc) seems to need gcc 4.1 to build correctly...
>
> -- vs;
>
I would like to second to that. gcc 4.1 is needed to build wip/jdk16
since kaffe can be built only by using gcc 4.1 at the moment. (Many
thanks to Francois Tig
On Tue, Mar 25, 2008 at 3:05 PM, Justin C. Sherrill
<[EMAIL PROTECTED]> wrote:
> On Tue, March 25, 2008 8:14 am, Chris Turner wrote:
>
> > I noticed it wasn't available from pkgbox in the 1.12 area..
>
> The build isn't done yet. (3847 packages built so far) However,
> python24-2.4.4 did fail
On Thu, Feb 28, 2008 at 6:52 PM, Justin C. Sherrill
<[EMAIL PROTECTED]> wrote:
> On Thu, February 28, 2008 1:50 pm, mustkaru wrote:
>
> > Thanks, am looking forward to 1.12 bin packages! Could you possibly
> > send an announcement to the list too?
>
> I will -
On Thu, Feb 28, 2008 at 6:38 PM, Justin C. Sherrill
<[EMAIL PROTECTED]> wrote:
> On Thu, February 28, 2008 12:23 pm, mustkaru wrote:
> > Hi,
> >
> > I installed 1.12.0 on my laptop along with 1.10.1 packages (should the
> > packages really be recompiled or can
Hi,
I installed 1.12.0 on my laptop along with 1.10.1 packages (should the
packages really be recompiled or can I use 1.10.1 binary packages?). I
use an external lcd panel since laptop screen is too small. Now when
booting, I switch the screen output to go to the external lcd panel
only (ie laptop
On Jan 26, 2008 10:11 PM, walt <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, 26 Jan 2008, mustkaru wrote:
>
> ..
>
> > I just wanted to compile the new kernel to slim it down and throw out
> > debugging stuff.
> >
> > I attach the custom kernel config
On Jan 26, 2008 3:24 PM, walt <[EMAIL PROTECTED]> wrote:
>
> On Sat, 26 Jan 2008, mustkaru wrote:
>
> > Hi,
> >
> > I successfully installed Dragonfly on my laptop and compiled a new
> > kernel. However, when booting the new kernel panics: can't find
Hi,
I successfully installed Dragonfly on my laptop and compiled a new
kernel. However, when booting the new kernel panics: can't find boot
device 'ad' (root is on /dev/ad0s1a). There is no 'ad' in the list of
devices recognized by kernel. ata0 appears in the boot messages
though. The nata devices
