From on2008nm at gmail.com  Thu May  1 01:18:49 2008
From: on2008nm at gmail.com (onkar mahajan)
Date: Thu, 1 May 2008 13:48:49 +0530
Subject: [belenix-dev] unionfs on Belenix
In-Reply-To: <46fe20470804302138u1265059fy4d33ac5bb033a191@mail.gmail.com>
References: <bf0ac4950804292146y70fc596y36d960a631a655f0@mail.gmail.com>
	<f5ff03920804300830j1e7494cfr6d8d79b9cf61eae8@mail.gmail.com>
	<bf0ac4950804301930p6e51e326m4fa327816e553e02@mail.gmail.com>
	<46fe20470804302138u1265059fy4d33ac5bb033a191@mail.gmail.com>
Message-ID: <bf0ac4950805010118n4bf86652o84cb61b93edaedc3@mail.gmail.com>

Yes, I can do that. Actually I would prefer to develop it from scratch ; but
then to save time porting from FreeBSD would be a better option.

regards,
Onkar




On 5/1/08, Moinak Ghosh <moinakg at gmail.com> wrote:
>
> On Thu, May 1, 2008 at 8:00 AM, onkar mahajan <on2008nm at gmail.com> wrote:
> > probably I will port it from Linux.
>
>   Um, you can't do that. The GPLv2 license does not permit mixing it with
>   CDDL code. A better option is to port FreeBSD UnionFS with the addition
>   of a bunch of external patches to fix bugs, performance issues and add
>   features.
>
> Regards,
> Moinak.
>
> >
> > Regards,
> > Onkar
> >
> >
> >
> >
> > On 4/30/08, Ananth Shrinivas <ananth.shrinivas at gmail.com> wrote:
> > >
> > >
> > >
> > >
> > > This is great news. What will be your reference implementation ? Or
> Will
> > you be porting UnionFS from another Operating System ?
> > >
> > > Cheers,
> > > Ananth
> > >
> > >
> > >
> > > On Wed, Apr 30, 2008 at 10:16 AM, onkar mahajan <on2008nm at gmail.com>
> > wrote:
> > >
> > > >
> > > > Hi all,
> > > >              I  am implementing unionfs on Belenix.
> > > >
> > > > This project builds a stackable unification file system, which can
> > appear to merge the contents of several directories (branches), while
> > keeping their physical content separate. Unionfs is useful for unified
> > source tree management, merged contents of split CD-ROM, merged separate
> > software package directories, data grids, and more. Unionfs allows any
> mix
> > of read-only and read-write branches, as well as insertion and deletion
> of
> > branches anywhere in the fan-out. To maintain unix semantics, Unionfs
> > handles elimination of duplicates, partial-error conditions, and more.
> > > >
> > > > for more info about FileSystem stacking and unionfs please visit :
> > > > http://www.filesystems.org/project-unionfs.html
> > > > and
> > > > http://www.linuxjournal.com/article/6485
> > > >
> > > >
> > > > Regards,
> > > > Onkar
> > >
> > >
> > > _______________________________________________
> > > belenix-dev mailing list
> > > belenix-dev at opensolaris.org
> > > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> > >
> > >
> >
> >
> > _______________________________________________
> >  belenix-dev mailing list
> >  belenix-dev at opensolaris.org
> >  http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080501/963030ca/attachment.html>

From sgpopuri at gmail.com  Thu May  1 03:51:13 2008
From: sgpopuri at gmail.com (Sriram Popuri)
Date: Thu, 1 May 2008 16:21:13 +0530
Subject: [belenix-dev] unionfs on Belenix
In-Reply-To: <bf0ac4950805010118n4bf86652o84cb61b93edaedc3@mail.gmail.com>
References: <bf0ac4950804292146y70fc596y36d960a631a655f0@mail.gmail.com>
	<f5ff03920804300830j1e7494cfr6d8d79b9cf61eae8@mail.gmail.com>
	<bf0ac4950804301930p6e51e326m4fa327816e553e02@mail.gmail.com>
	<46fe20470804302138u1265059fy4d33ac5bb033a191@mail.gmail.com>
	<bf0ac4950805010118n4bf86652o84cb61b93edaedc3@mail.gmail.com>
Message-ID: <72dedc000805010351u4628a80fwb27b67772ab46c23@mail.gmail.com>

Yes. FreeBSD is the best option to port from. Venkata Kishore (CC-ed) did
some work porting unionfs from FreeBSD.
He was struck at some point and you can probably continue that effort. You
can contact him for more pointers.

~Sriram

On Thu, May 1, 2008 at 1:48 PM, onkar mahajan <on2008nm at gmail.com> wrote:

> Yes, I can do that. Actually I would prefer to develop it from scratch ;
> but then to save time porting from FreeBSD would be a better option.
>
> regards,
> Onkar
>
>
>
>
> On 5/1/08, Moinak Ghosh <moinakg at gmail.com> wrote:
> >
> > On Thu, May 1, 2008 at 8:00 AM, onkar mahajan <on2008nm at gmail.com>
> > wrote:
> > > probably I will port it from Linux.
> >
> >   Um, you can't do that. The GPLv2 license does not permit mixing it
> > with
> >   CDDL code. A better option is to port FreeBSD UnionFS with the
> > addition
> >   of a bunch of external patches to fix bugs, performance issues and add
> >   features.
> >
> > Regards,
> > Moinak.
> >
> > >
> > > Regards,
> > > Onkar
> > >
> > >
> > >
> > >
> > > On 4/30/08, Ananth Shrinivas <ananth.shrinivas at gmail.com> wrote:
> > > >
> > > >
> > > >
> > > >
> > > > This is great news. What will be your reference implementation ? Or
> > Will
> > > you be porting UnionFS from another Operating System ?
> > > >
> > > > Cheers,
> > > > Ananth
> > > >
> > > >
> > > >
> > > > On Wed, Apr 30, 2008 at 10:16 AM, onkar mahajan <on2008nm at gmail.com>
> > > wrote:
> > > >
> > > > >
> > > > > Hi all,
> > > > >              I  am implementing unionfs on Belenix.
> > > > >
> > > > > This project builds a stackable unification file system, which can
> > > appear to merge the contents of several directories (branches), while
> > > keeping their physical content separate. Unionfs is useful for unified
> > > source tree management, merged contents of split CD-ROM, merged
> > separate
> > > software package directories, data grids, and more. Unionfs allows any
> > mix
> > > of read-only and read-write branches, as well as insertion and
> > deletion of
> > > branches anywhere in the fan-out. To maintain unix semantics, Unionfs
> > > handles elimination of duplicates, partial-error conditions, and more.
> > > > >
> > > > > for more info about FileSystem stacking and unionfs please visit :
> > > > > http://www.filesystems.org/project-unionfs.html
> > > > > and
> > > > > http://www.linuxjournal.com/article/6485
> > > > >
> > > > >
> > > > > Regards,
> > > > > Onkar
> > > >
> > > >
> > > > _______________________________________________
> > > > belenix-dev mailing list
> > > > belenix-dev at opensolaris.org
> > > > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > >  belenix-dev mailing list
> > >  belenix-dev at opensolaris.org
> > >  http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> > >
> > >
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080501/f433e4c0/attachment.html>

From on2008nm at gmail.com  Sat May  3 07:24:34 2008
From: on2008nm at gmail.com (onkar mahajan)
Date: Sat, 3 May 2008 19:54:34 +0530
Subject: [belenix-dev] compiling OpenSolaris kernel
Message-ID: <bf0ac4950805030724q5e71524wf3099352304a7498@mail.gmail.com>

Hi all,
             The following questions may be OT.
             I am a Linux kernel programmer. I want to know few things about
OpenSolaris :
(1) Is it possible to  tune the opensolaris( henceforth refered to as OS !
)  kernel as in the case of Linux ?
(2) is compiling as simple as in Linux ?
(3) Are there any turorials for tuning and upgrading the OS to bleeding edge
kernel ?

regards,
-Onkar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080503/07ac77ac/attachment.html>

From moinakg at gmail.com  Sat May  3 07:50:37 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sat, 3 May 2008 20:20:37 +0530
Subject: [belenix-dev] compiling OpenSolaris kernel
In-Reply-To: <bf0ac4950805030724q5e71524wf3099352304a7498@mail.gmail.com>
References: <bf0ac4950805030724q5e71524wf3099352304a7498@mail.gmail.com>
Message-ID: <46fe20470805030750p52f8ff5evfc806fca92f95f2@mail.gmail.com>

On Sat, May 3, 2008 at 7:54 PM, onkar mahajan <on2008nm at gmail.com> wrote:
> Hi all,
>              The following questions may be OT.
>              I am a Linux kernel programmer. I want to know few things about
> OpenSolaris :
> (1) Is it possible to  tune the opensolaris( henceforth refered to as OS ! )
> kernel as in the case of Linux ?

   By tuning do you mean "make menuconfig" ? if so then that is not possible.
   The build system currently uses a monolithic makefile system. Though it is
   possible to compile source subtrees separately you cannot yet exclude
   pieces from a full build.

>  (2) is compiling as simple as in Linux ?

   Once you have the compiler, tools and sources downloaded setting up your
   build environment just takes 5 minutes.

> (3) Are there any turorials for tuning and upgrading the OS to bleeding edge
> kernel ?

   Yes. You need to use BFU.

   See these for answers to the above questions:

   Getting started (Source, ISO, compilers etc.)
   http://www.opensolaris.org/os/downloads/on/

   OpenSolaris Developer Reference:
   http://opensolaris.org/os/community/on/devref_toc/

   Downloading source and tools as tarball:
   http://dlc.sun.com/osol/on/downloads/current/

Regards,
Moinak.

>
> regards,
> -Onkar
>
>
> _______________________________________________
>  belenix-dev mailing list
>  belenix-dev at opensolaris.org
>  http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From shampavman.cg at gmail.com  Sun May  4 03:00:27 2008
From: shampavman.cg at gmail.com (sham pavman)
Date: Sun, 4 May 2008 15:30:27 +0530
Subject: [belenix-dev] Belenix 0.7 can boot from RAM now :-)
Message-ID: <9f9ad12d0805040300s755153b1rb26be73114e4d1b5@mail.gmail.com>

Hi all,

Its done :-)
Belenix 0.7 can boot from ram now!!! :-)
Here's the inside story!!

The prime requirement for booting belenix from RAM was the presence of 2
files ,namely solaris.zlib and solarismisc.zlib .
Initially when i started off the cp of solaris.zilb was not happening,
reason being that the file was too big to be copied into RAM at once (561mb)
and that swap was completely not being mounted onto /tmp by the time this
script was executed...
The only option now was to explicitly mount swap and hope it works

Then next stage was to copy these 2 files to /tmp
and finally lofiadm it and later a mount to /usr and /mnt/misc
respectively...

Here are the codes

/sbin/mount -F tmpfs swap /tmp 2>/dev/msglog
if [ $? -eq 0 ];then
echo "successful mount" >/dev/msglog
else
echo "failure" >/dev/msglog
fi
/usr/bin/cp /.cdrom/solaris.zlib /tmp                       (copied the
binaries into /usr/bin first these executed this statement!!)
/usr/bin/cp /.cdrom/solarismisc.zlib /tmp

if [ $? -eq 0 ];then
echo "proceeding to final stage" >/dev/msglog
echo "failed to copy" >/dev/msglog
fi
/usr/sbin/lofiadm -a /dev/lofi/1 /usr 2>/dev/msglog
/usr/sbin/lofiadm -a /dev/lofi/2 /mnt/misc 2>/dev/msglog

Please visit www.blogs.sun.com/sham.
I will have a detailed post on this in my blog!!!!
Awaiting your replies.


Shampavman
CA,Jssate,
Bangalore, INDIA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080504/8d5ff0af/attachment.html>

From shivakumar.gn at gmail.com  Tue May  6 17:52:20 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Tue, 6 May 2008 17:52:20 -0700
Subject: [belenix-dev] [ug-bosug] blog entry on "ram based boot for
	belenix"
In-Reply-To: <9f9ad12d0805060831pf462a84y84b16cddc482a45b@mail.gmail.com>
References: <9f9ad12d0805060831pf462a84y84b16cddc482a45b@mail.gmail.com>
Message-ID: <319ee2b10805061752t73eb0127y27db318f270427d6@mail.gmail.com>

On Tue, May 6, 2008 at 8:31 AM, sham pavman <shampavman.cg at gmail.com> wrote:
> Hi all,
>
> I have posted a blog entry of my works.
> Here is the link: www.blogs.sun.com/sham/
> I also have some nice snapshots put up ,have a look at it :-)
>
> Awaiting your comments :)
>

Have commented :)
Cool work. Looking forward to some more measurements & data that makes
it more interesting.
Covering as many different user scenarios as possible would be
interesting to look at while noting measurements.
Installation would be only one of the scenarios. Others might be boot
up time, response times of the apps, any changes to min RAM
requirements, etc.
We can look at making it a boot up option for BeleniX. Lets discuss at
the next UG meeting.

-Shiv


From sriramnrn at gmail.com  Wed May  7 17:16:20 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Wed, 7 May 2008 17:16:20 -0700
Subject: [belenix-dev] We should include Intel's powertop in the next release
Message-ID: <49977f270805071716qa3850d2l22d04caaa19863c0@mail.gmail.com>

 I just learned of this from a podcast by Intel Dave
(http://softwareblogs.intel.com/2008/05/06/radio-free-software-intel-on-opensolaris/)

-- Sriram


From shivakumar.gn at gmail.com  Wed May  7 20:59:46 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 8 May 2008 11:59:46 +0800
Subject: [belenix-dev] OpenSolaris innovation awards program
Message-ID: <319ee2b10805072059k45763460p7ce9cd9c0d81ad9b@mail.gmail.com>

Hello All,

Have a look at http://opensolaris.org/os/project/awards

Lot of good amount of money to be won as awards. Also a good way to
get recognized.

There have been some good ideas being bounced on belenix and the user
group lists (bluetooth stack, port of unionfs, ruby bindings for
crossbow administration interfaces,....)

Go ahead and submit your ideas/work-in-progress as proposals.

Little time left

* Deadline to submit research grant proposals: May 15, 2008
* Research project due December 16, 2008
Above dates I believe are for the student research work.
For community project work submission
* The deadline to submit for the contest: June 14, 2008

Further details are available at
http://opensolaris.org/os/project/awards/awards_land

Any further queries maybe addressed to awards-program at opensolaris.org

-Shiv


From shivakumar.gn at gmail.com  Tue May 13 23:27:07 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Wed, 14 May 2008 11:57:07 +0530
Subject: [belenix-dev] sunstudio - redistributable ?
Message-ID: <319ee2b10805132327wf84b0ard027cd45d8882979@mail.gmail.com>

Hi,

At the OpenSolaris Developer Summit, I was informed by Kuldip Oberoi
that sunstudio is now redistributable. I would like a confirmation to
the same along with terms of distribution if any.
This definitely makes a difference while making the compiler choice
while porting applications for distros like BeleniX.

thanks & regards
Shiv


From pablomh at gmail.com  Wed May 14 00:44:47 2008
From: pablomh at gmail.com (=?ISO-8859-1?Q?Pablo_M=E9ndez_Hern=E1ndez?=)
Date: Wed, 14 May 2008 09:44:47 +0200
Subject: [belenix-dev] KDE4 and C++ projects
Message-ID: <59b875a00805140044n406099f7l16b8a97ea494cb4c@mail.gmail.com>

Hi:

I'd like to know if there any plans regarding the compiler/ABI chosen for
C++ programs/aplications (mainly with KDE4 in mind): SunStudio 12 if it gets
"freely distributable status" or GCC (with the ABI problems shown in the
KDE4 mailing lists).


Regards.

-- 
Pablo M?ndez Hern?ndez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080514/f26237d7/attachment.html>

From shivakumar.gn at gmail.com  Wed May 14 01:09:42 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Wed, 14 May 2008 13:39:42 +0530
Subject: [belenix-dev] KDE4 and C++ projects
In-Reply-To: <59b875a00805140044n406099f7l16b8a97ea494cb4c@mail.gmail.com>
References: <59b875a00805140044n406099f7l16b8a97ea494cb4c@mail.gmail.com>
Message-ID: <319ee2b10805140109m3ae58cd9n605caec7fdccb299@mail.gmail.com>

On Wed, May 14, 2008 at 1:14 PM, Pablo M?ndez Hern?ndez
<pablomh at gmail.com> wrote:
> Hi:
>
> I'd like to know if there any plans regarding the compiler/ABI chosen for
> C++ programs/aplications (mainly with KDE4 in mind): SunStudio 12 if it gets
> "freely distributable status" or GCC (with the ABI problems shown in the
> KDE4 mailing lists).
>

Till now we have been favouring gcc due to the absence of
re-distribution option with sun studio.
Latest unconfirmed news is that it is redistributable. With that the
odds will shift but the change won't happen overnight since there are
lot of spec-files/build scripts that work fine with gcc and moving
over will be good bit of effort.

-Shiv


From moinakg at gmail.com  Wed May 14 03:41:23 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 14 May 2008 16:11:23 +0530
Subject: [belenix-dev] KDE4 and C++ projects
In-Reply-To: <319ee2b10805140109m3ae58cd9n605caec7fdccb299@mail.gmail.com>
References: <59b875a00805140044n406099f7l16b8a97ea494cb4c@mail.gmail.com>
	<319ee2b10805140109m3ae58cd9n605caec7fdccb299@mail.gmail.com>
Message-ID: <46fe20470805140341v26aae3bfnfe7970a03c1aa0c3@mail.gmail.com>

On Wed, May 14, 2008 at 1:39 PM, S h i v <shivakumar.gn at gmail.com> wrote:
> On Wed, May 14, 2008 at 1:14 PM, Pablo M?ndez Hern?ndez
>  <pablomh at gmail.com> wrote:
>  > Hi:
>  >
>  > I'd like to know if there any plans regarding the compiler/ABI chosen for
>  > C++ programs/aplications (mainly with KDE4 in mind): SunStudio 12 if it gets
>  > "freely distributable status" or GCC (with the ABI problems shown in the
>  > KDE4 mailing lists).
>  >
>
>  Till now we have been favouring gcc due to the absence of
>  re-distribution option with sun studio.
>  Latest unconfirmed news is that it is redistributable. With that the
>  odds will shift but the change won't happen overnight since there are
>  lot of spec-files/build scripts that work fine with gcc and moving
>  over will be good bit of effort.

   Even with redistributability or not it is much less effort to get
the initial work
   done using Gcc and move to SS12 later on. At this point in time there are
   a large number of things to be done overall in BeleniX like getting our own
   IPS repository online. So we'd like to have as little
porting/compiling hassles
   as possible.

   SUN Studio is very much in the roadmap, just that we need to plan ahead
   for it. One more final consideration is when SUN Studio will become
   opensource. A FOSS distribution entails a FOSS toolchain as well.

   BeleniX today is using SUN Studio for building some things like ON Kernel
   and userland, JDS components, Firefox/Thinderbird etc.

Regards,
Moinak.

>
>  -Shiv
>  _______________________________________________
>  belenix-dev mailing list
>  belenix-dev at opensolaris.org
>  http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From swalker at opensolaris.org  Wed May 14 06:43:31 2008
From: swalker at opensolaris.org (Shawn Walker)
Date: Wed, 14 May 2008 08:43:31 -0500
Subject: [belenix-dev] [tools-compilers] sunstudio - redistributable ?
In-Reply-To: <319ee2b10805132327wf84b0ard027cd45d8882979@mail.gmail.com>
References: <319ee2b10805132327wf84b0ard027cd45d8882979@mail.gmail.com>
Message-ID: <b9c544f0805140643y1853eb46k4b3eb3735c40df55@mail.gmail.com>

On Wed, May 14, 2008 at 1:27 AM, S h i v <shivakumar.gn at gmail.com> wrote:
> Hi,
>
> At the OpenSolaris Developer Summit, I was informed by Kuldip Oberoi
> that sunstudio is now redistributable. I would like a confirmation to
> the same along with terms of distribution if any.
> This definitely makes a difference while making the compiler choice
> while porting applications for distros like BeleniX.

I was told that anything on pkg.opensolaris.org is redistributable by
its very nature.

However, I don't know what terms it falls under.

-- 
Shawn Walker

"To err is human -- and to blame it on a computer is even more so." -
Robert Orben


From koberoi at sun.com  Wed May 14 07:01:16 2008
From: koberoi at sun.com (Kuldip Oberoi)
Date: Wed, 14 May 2008 07:01:16 -0700
Subject: [belenix-dev] [tools-compilers] sunstudio - redistributable ?
In-Reply-To: <b9c544f0805140643y1853eb46k4b3eb3735c40df55@mail.gmail.com>
References: <319ee2b10805132327wf84b0ard027cd45d8882979@mail.gmail.com>
	<b9c544f0805140643y1853eb46k4b3eb3735c40df55@mail.gmail.com>
Message-ID: <482AF0AC.8010503@sun.com>

Here are the terms:

http://www.opensolaris.com/licensing/opensolaris_binary_license/

"(i)distribute the Software or Redistributables bundled as part of, and 
for the sole purpose of running, OpenSolaris code;"

I am currently confirming with our legal folks to see what, if any, 
restrictions exist for OpenSolaris-based distros.

/kso


Shawn Walker wrote:
> On Wed, May 14, 2008 at 1:27 AM, S h i v <shivakumar.gn at gmail.com> wrote:
>> Hi,
>>
>> At the OpenSolaris Developer Summit, I was informed by Kuldip Oberoi
>> that sunstudio is now redistributable. I would like a confirmation to
>> the same along with terms of distribution if any.
>> This definitely makes a difference while making the compiler choice
>> while porting applications for distros like BeleniX.
> 
> I was told that anything on pkg.opensolaris.org is redistributable by
> its very nature.
> 
> However, I don't know what terms it falls under.
> 


From shivakumar.gn at gmail.com  Wed May 14 17:03:44 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 15 May 2008 05:33:44 +0530
Subject: [belenix-dev] Codecs for BeleniX
Message-ID: <319ee2b10805141703y45b6cc5ei98a850308ddbcc87@mail.gmail.com>

Thanks to Mike, a few packages for codecs are now available at
http://eyes.satnet.if.ua/solaris/pkg/x86/SFE/index.php

There are few useful ones that are still missing, it would be great if
someone volunteered to build the missing ones (build failures in the
below list).
I can help trouble shoot when necessary.

regards
Shiv


---------- Forwarded message ----------
From: eyes watcher <201949 at rambler.ru>
Subject: Building the restricted softwares for Belenix


Hi mr. Shiv!
My name is Mike. I`m from Russia.
Alexander R. Eremin ask me to build the following restricted softwares
for Belenix:

Build with GCC "encumbered/SFElibdvdcss.spec:encumbered/SFElibdvdread.spec"
Build with SUNPRO
"encumbered/SFEdvdauthor.spec:encumbered/SFEliba52.spec:encumbered/SFElibdts.spec"
Build with GCC "encumbered/SFExvid.spec:encumbered/SFElame.spec"
Build with SUNPRO
"encumbered/SFEamrnb.spec:encumbered/SFEffmpeg.spec:encumbered/SFElibdv.spec:encumbered/SFElibdvbpsi.spec"
Build with SUNPRO
"encumbered/SFElibdvdnav.spec:encumbered/SFElibdvdplay.spec:encumbered/SFElibfame.spec"
Build with SUNPRO
"encumbered/SFElibid3tag-gnu.spec:encumbered/SFElibid3tag.spec"
Build with SUNPRO "encumbered/SFElibmpcdec.spec:encumbered/SFElibmpeg2.spec"
Build with SUNPRO
"encumbered/SFElibquicktime.spec:encumbered/SFEmpg321.spec:encumbered/SFEmpgtx.spec"
Build with SUNPRO "encumbered/SFEtwolame.spec"

The folwing packages are builded successfully with pkgtool, GCC and
SunStudioPro12 on x86 architecture, but some packages were not:
   Builded with GCC 3.4.3.:
SFElibdvdcss.spec - successful
SFElibdvdread - successful
SFExvid - successful
SFElame - failed

   Builded with SUNPRO
SFEdvdauthor - successful
SFEliba52 - failed
SFElibdts - failed
SFEamrnb - successful
SFEffmpeg - failed
SFElibdv - failed
SFElibdvbpsi - successful
SFElibdvdnav - successful
SFElibdvdplay - successful
SFElibfame - successful
SFElibid3tag-gnu - successful
SFElibid3tag - successful
SFElibmpcdec - failed
SFElibmpeg2 - successful
SFElibquicktime - failed
SFEmpg321 - failed
SFEmpgtx - successful
SFEtwolame - failed

All of succsessfully builded packages are here:
http://eyes.satnet.if.ua/solaris/pkg/x86/SFE/index.php

I hope I helped you a little bit.

Mike.


From sriramnrn at gmail.com  Wed May 14 19:08:01 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Thu, 15 May 2008 07:38:01 +0530
Subject: [belenix-dev] Becoming a Belenix developer - what should I use ?
Message-ID: <49977f270805141908le90d3c0j179ad93572a6a963@mail.gmail.com>

Hi:

I was about replace build 81 on my Mac with build 87, and was then
wondering, what exactly should I use as a base platform ?

After a conversation with Shiv on IM, I figured there are a variety of tasks:

- Build ON
- Build and update spec files for our SFE repository.
- Build and update packages for our upcoming IPS repository.

Given that we need spec file work at a priority, I'd rather focus on
points two and three above.

On a side note, I also want to use what ever I install as my primary
desktop (well, laptop) environment. This means I'll have to have the
following:
- Wine for Lotus Notes (builds and works fine on build 81)
-  VPNC (builds and works fine on build 81)

I know that the network drivers for Ethernet and Wifi would both work.
At present, oss does not work, and I'm OK with that.

I feel that using Belenix 0.7 is the best way to go to comply with the
wisdom of eating one's own dog food, etc.

What would the Belenix team recommend ?

-- Sriram


From shivakumar.gn at gmail.com  Wed May 14 20:57:19 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 15 May 2008 09:27:19 +0530
Subject: [belenix-dev] Becoming a Belenix developer - what should I use ?
In-Reply-To: <49977f270805141908le90d3c0j179ad93572a6a963@mail.gmail.com>
References: <49977f270805141908le90d3c0j179ad93572a6a963@mail.gmail.com>
Message-ID: <319ee2b10805142057m40de98e1w8e1c080cb5b657a5@mail.gmail.com>

Let me elaborate on the build ON part. There are 2 parts to it:
1. Making BeleniX self-hosting: ON currently doesn't build on BeleniX.
Identify changes required to make it build.
2. Automate rebasing of BeleniX from one ON build to another: Build ON
from source, create a chroot environment, build all application stack.
Create an ISO. => with these steps automated BeleniX will be able to
deliver a weekly developer build painlessly. Building ON can even be
optional in which case there can be regular developer builds using the
continuously integrated spec files but with a given ON bits.

In addition to the generic ones listed below depending on the specific
features/bug fixes going into a forth coming there are invariably
release specific work to be done.

These are posted time to time on the list as heads up, those
interested indicate so.

Another useful contribution would be to show case the work any person
is doing on his/her pet project by delivering it with BeleniX as the
target platform. This becomes much easier once we set the repo.

BeleniX is my default user and developer setup. The build environment
is easy to setup, check the last section "To have a pkgbuild
environment for building the spec files" in
http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html

You should be able to build wine and any of the apps that one can
build via spec files on SX.

Setting up an IPS is also possible on BeleniX. I am playing with IPS
*on BeleniX* so that I can work on providing IPS support to the
pkgbuild tools that we use.
Will post the details if interested. The IPS sources do not build
flawlessly though. Hadn't come around to fix it as yet.

regards
Shiv


On Thu, May 15, 2008 at 7:38 AM, Sriram Narayanan <sriramnrn at gmail.com> wrote:
> Hi:
>
> I was about replace build 81 on my Mac with build 87, and was then
> wondering, what exactly should I use as a base platform ?
>
> After a conversation with Shiv on IM, I figured there are a variety of tasks:
>
> - Build ON
> - Build and update spec files for our SFE repository.
> - Build and update packages for our upcoming IPS repository.
>
> Given that we need spec file work at a priority, I'd rather focus on
> points two and three above.
>
> On a side note, I also want to use what ever I install as my primary
> desktop (well, laptop) environment. This means I'll have to have the
> following:
> - Wine for Lotus Notes (builds and works fine on build 81)
> -  VPNC (builds and works fine on build 81)
>
> I know that the network drivers for Ethernet and Wifi would both work.
> At present, oss does not work, and I'm OK with that.
>
> I feel that using Belenix 0.7 is the best way to go to comply with the
> wisdom of eating one's own dog food, etc.
>
> What would the Belenix team recommend ?
>
> -- Sriram
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From shivakumar.gn at gmail.com  Thu May 15 03:11:39 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 15 May 2008 15:41:39 +0530
Subject: [belenix-dev] Fwd: [osol-announce] PowerTop v1.0 released !
In-Reply-To: <482B60F2.8090403@sun.com>
References: <482B60F2.8090403@sun.com>
Message-ID: <319ee2b10805150311k7ee4f2fexeb8d67a961ad5bf6@mail.gmail.com>

PowerTop release was announced today.


---------- Forwarded message ----------
From: Rafael Vanoni <Rafael.Vanoni at sun.com>
Date: Thu, May 15, 2008 at 3:30 AM
Subject: [osol-announce] PowerTop v1.0 released !
To: opensolaris-announce at opensolaris.org


The first release of the PowerTop tool for OpenSolaris is available at
the Tesla Project's page (http://opensolaris.org/os/project/tesla/).

PowerTOP is an observability tool that shows how effectively the system
is taking advantage of the CPU's power management features. The tool
allows the user to see how long the CPU is running at different power
states, and which events are causing the system to wakeup and
consequently consume more energy.

In order to run PowerTop, the user must have Solaris Nevada build 82 or
higher installed. It will also be possible to run the tool on Solaris 10
systems with Update 6 - once such update is released.

PowerTop is a community project developed on opensolaris.org. If you'd
like to get involved, join our alias (tesla-dev at opensolaris.org).

Rafael
_______________________________________________
opensolaris-announce mailing list
opensolaris-announce at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-announce


From moinakg at gmail.com  Thu May 15 09:03:25 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 15 May 2008 21:33:25 +0530
Subject: [belenix-dev] Becoming a Belenix developer - what should I use ?
In-Reply-To: <319ee2b10805142057m40de98e1w8e1c080cb5b657a5@mail.gmail.com>
References: <49977f270805141908le90d3c0j179ad93572a6a963@mail.gmail.com>
	<319ee2b10805142057m40de98e1w8e1c080cb5b657a5@mail.gmail.com>
Message-ID: <46fe20470805150903r66a499cdw34cad6fcfad656a1@mail.gmail.com>

On Thu, May 15, 2008 at 9:27 AM, S h i v <shivakumar.gn at gmail.com> wrote:
> Let me elaborate on the build ON part. There are 2 parts to it:
> 1. Making BeleniX self-hosting: ON currently doesn't build on BeleniX.
> Identify changes required to make it build.

   2 Things:

   * Add /usr/ccs/bin/as in the SUNWsprot package. This is already available
   in the SUNWsprot in pkg.opensolaris.org.

   * When building ON the /usr/gnu/bin has to be removed from PATH.

> 2. Automate rebasing of BeleniX from one ON build to another: Build ON
> from source, create a chroot environment, build all application stack.
> Create an ISO. => with these steps automated BeleniX will be able to
> deliver a weekly developer build painlessly. Building ON can even be
> optional in which case there can be regular developer builds using the
> continuously integrated spec files but with a given ON bits.
[...]>
> BeleniX is my default user and developer setup. The build environment
> is easy to setup, check the last section "To have a pkgbuild
> environment for building the spec files" in
> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
>

   I am gonna have to re-image by home system with BeleniX. Currently it
   it is SXDE B78. But that is a big task considering the amount of data I
   have on it. Right now it is backup, backup, backup ...

Regards,
Moinak.


From moinakg at gmail.com  Thu May 15 09:05:48 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Thu, 15 May 2008 21:35:48 +0530
Subject: [belenix-dev] Codecs for BeleniX
In-Reply-To: <319ee2b10805141703y45b6cc5ei98a850308ddbcc87@mail.gmail.com>
References: <319ee2b10805141703y45b6cc5ei98a850308ddbcc87@mail.gmail.com>
Message-ID: <46fe20470805150905nf8b2beclb099ab3fb2b0a706@mail.gmail.com>

On Thu, May 15, 2008 at 5:33 AM, S h i v <shivakumar.gn at gmail.com> wrote:
> Thanks to Mike, a few packages for codecs are now available at
> http://eyes.satnet.if.ua/solaris/pkg/x86/SFE/index.php
>
> There are few useful ones that are still missing, it would be great if
> someone volunteered to build the missing ones (build failures in the
> below list).
> I can help trouble shoot when necessary.

   Real cool. Where can I look at the logs ? I was able to build all of them
   myself.

Regards,
Moinak.

>
> regards
> Shiv
>
>
> ---------- Forwarded message ----------
> From: eyes watcher <201949 at rambler.ru>
> Subject: Building the restricted softwares for Belenix
>
>
> Hi mr. Shiv!
> My name is Mike. I`m from Russia.
> Alexander R. Eremin ask me to build the following restricted softwares
> for Belenix:
>
> Build with GCC "encumbered/SFElibdvdcss.spec:encumbered/SFElibdvdread.spec"
> Build with SUNPRO
> "encumbered/SFEdvdauthor.spec:encumbered/SFEliba52.spec:encumbered/SFElibdts.spec"
> Build with GCC "encumbered/SFExvid.spec:encumbered/SFElame.spec"
> Build with SUNPRO
> "encumbered/SFEamrnb.spec:encumbered/SFEffmpeg.spec:encumbered/SFElibdv.spec:encumbered/SFElibdvbpsi.spec"
> Build with SUNPRO
> "encumbered/SFElibdvdnav.spec:encumbered/SFElibdvdplay.spec:encumbered/SFElibfame.spec"
> Build with SUNPRO
> "encumbered/SFElibid3tag-gnu.spec:encumbered/SFElibid3tag.spec"
> Build with SUNPRO "encumbered/SFElibmpcdec.spec:encumbered/SFElibmpeg2.spec"
> Build with SUNPRO
> "encumbered/SFElibquicktime.spec:encumbered/SFEmpg321.spec:encumbered/SFEmpgtx.spec"
> Build with SUNPRO "encumbered/SFEtwolame.spec"
>
> The folwing packages are builded successfully with pkgtool, GCC and
> SunStudioPro12 on x86 architecture, but some packages were not:
>   Builded with GCC 3.4.3.:
> SFElibdvdcss.spec - successful
> SFElibdvdread - successful
> SFExvid - successful
> SFElame - failed
>
>   Builded with SUNPRO
> SFEdvdauthor - successful
> SFEliba52 - failed
> SFElibdts - failed
> SFEamrnb - successful
> SFEffmpeg - failed
> SFElibdv - failed
> SFElibdvbpsi - successful
> SFElibdvdnav - successful
> SFElibdvdplay - successful
> SFElibfame - successful
> SFElibid3tag-gnu - successful
> SFElibid3tag - successful
> SFElibmpcdec - failed
> SFElibmpeg2 - successful
> SFElibquicktime - failed
> SFEmpg321 - failed
> SFEmpgtx - successful
> SFEtwolame - failed
>
> All of succsessfully builded packages are here:
> http://eyes.satnet.if.ua/solaris/pkg/x86/SFE/index.php
>
> I hope I helped you a little bit.
>
> Mike.
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From shivakumar.gn at gmail.com  Thu May 15 20:05:41 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Fri, 16 May 2008 08:35:41 +0530
Subject: [belenix-dev] Codecs for BeleniX
In-Reply-To: <46fe20470805150905nf8b2beclb099ab3fb2b0a706@mail.gmail.com>
References: <319ee2b10805141703y45b6cc5ei98a850308ddbcc87@mail.gmail.com>
	<46fe20470805150905nf8b2beclb099ab3fb2b0a706@mail.gmail.com>
Message-ID: <319ee2b10805152005n4760fe8awe6b0b0226912f68d@mail.gmail.com>

On Thu, May 15, 2008 at 9:35 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>
>   Real cool. Where can I look at the logs ? I was able to build all of them
>   myself.
>

Build wasn't a problem in my environment as well. I do not yet have
access to the logs. I have requested for it.

-Shiv


From manishchaks at gmail.com  Sat May 17 11:08:45 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sat, 17 May 2008 23:38:45 +0530
Subject: [belenix-dev] How do I make sure BeleniX boots in command line mode
	everytime?
Message-ID: <b4dbee910805171108h819c39el8284d1b8f03f61ee@mail.gmail.com>

Hey all,

I am running BeleniX in a VBox VM. I plan to do run compilation on it [1]
How do I make sure the VM boots in cmd line mode everytime?
I want to SSH into the VM and work.

[1] - I am determined to have a KDE4/gcc build on it.
-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080517/b84c65c7/attachment.html>

From manishchaks at gmail.com  Sat May 17 12:20:36 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 00:50:36 +0530
Subject: [belenix-dev] How do i install gcc in belenix?
Message-ID: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>

Hi all,

It seems Belenix 0.7 does not come with gcc installed by default.
How do i install it?

-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/a10a1889/attachment.html>

From shivakumar.gn at gmail.com  Sat May 17 23:56:54 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 12:26:54 +0530
Subject: [belenix-dev] How do i install gcc in belenix?
In-Reply-To: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>
References: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>
Message-ID: <319ee2b10805172356l47f2f7acs6d6952dc2c5668de@mail.gmail.com>

On Sun, May 18, 2008 at 12:50 AM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Hi all,
>
> It seems Belenix 0.7 does not come with gcc installed by default.
> How do i install it?
>

Additional softwares can be installed using the "get-pkgs" command
For details see
http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html

$ get-pkgs devel
would install development headers, gcc and whole bunch of other
packages that are categorized as developer related.

-Shiv


From manishchaks at gmail.com  Sun May 18 00:08:19 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 12:38:19 +0530
Subject: [belenix-dev] How do i install gcc in belenix?
In-Reply-To: <319ee2b10805172356l47f2f7acs6d6952dc2c5668de@mail.gmail.com>
References: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>
	<319ee2b10805172356l47f2f7acs6d6952dc2c5668de@mail.gmail.com>
Message-ID: <b4dbee910805180008j25186ea1ue12b6147ba286f69@mail.gmail.com>

Hi Shiv,

Thanks for the pointers.
I was able to install gcc + dev libs.

I was watching while the install process was going on. Interestingly a lot
of libs required to build/run KDE4 are already present in BeleniX :)
(things like openexr, openssl-devel etc)

cmake is not present though.
How do i use the belenix spec file repo to install cmake?
(If it's not available, I am comfortable building it from scratch)

-- Manish

On Sun, May 18, 2008 at 12:26 PM, S h i v <shivakumar.gn at gmail.com> wrote:

> On Sun, May 18, 2008 at 12:50 AM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
> > Hi all,
> >
> > It seems Belenix 0.7 does not come with gcc installed by default.
> > How do i install it?
> >
>
> Additional softwares can be installed using the "get-pkgs" command
> For details see
> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
>
> $ get-pkgs devel
> would install development headers, gcc and whole bunch of other
> packages that are categorized as developer related.
>
> -Shiv
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/0f91321a/attachment.html>

From moinakg at gmail.com  Sun May 18 00:14:40 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sun, 18 May 2008 12:44:40 +0530
Subject: [belenix-dev] How do i install gcc in belenix?
In-Reply-To: <b4dbee910805180008j25186ea1ue12b6147ba286f69@mail.gmail.com>
References: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>
	<319ee2b10805172356l47f2f7acs6d6952dc2c5668de@mail.gmail.com>
	<b4dbee910805180008j25186ea1ue12b6147ba286f69@mail.gmail.com>
Message-ID: <46fe20470805180014u28135e63q567ce35ea493af74@mail.gmail.com>

On Sun, May 18, 2008 at 12:38 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Hi Shiv,
>
> Thanks for the pointers.
> I was able to install gcc + dev libs.
>
> I was watching while the install process was going on. Interestingly a lot
> of libs required to build/run KDE4 are already present in BeleniX :)
> (things like openexr, openssl-devel etc)
>
> cmake is not present though.
> How do i use the belenix spec file repo to install cmake?
> (If it's not available, I am comfortable building it from scratch)

   There is an SFEcmake in the BeleniX repo and included in the devel
   cluster.

Regards,
Moinak.

>
> -- Manish
>
> On Sun, May 18, 2008 at 12:26 PM, S h i v <shivakumar.gn at gmail.com> wrote:
>>
>> On Sun, May 18, 2008 at 12:50 AM, Manish Chakravarty
>> <manishchaks at gmail.com> wrote:
>> > Hi all,
>> >
>> > It seems Belenix 0.7 does not come with gcc installed by default.
>> > How do i install it?
>> >
>>
>> Additional softwares can be installed using the "get-pkgs" command
>> For details see
>>
>> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
>>
>> $ get-pkgs devel
>> would install development headers, gcc and whole bunch of other
>> packages that are categorized as developer related.
>>
>> -Shiv
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From manishchaks at gmail.com  Sun May 18 00:37:35 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 13:07:35 +0530
Subject: [belenix-dev] How do i install gcc in belenix?
In-Reply-To: <46fe20470805180014u28135e63q567ce35ea493af74@mail.gmail.com>
References: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>
	<319ee2b10805172356l47f2f7acs6d6952dc2c5668de@mail.gmail.com>
	<b4dbee910805180008j25186ea1ue12b6147ba286f69@mail.gmail.com>
	<46fe20470805180014u28135e63q567ce35ea493af74@mail.gmail.com>
Message-ID: <b4dbee910805180037h5e2b31fbrd93e5fbebf9a8066@mail.gmail.com>

On Sun, May 18, 2008 at 12:44 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

> [...snip...]
>    There is an SFEcmake in the BeleniX repo and included in the devel
>   cluster.
>
Is "pkginfo | grep <packagename>" a reliable way of telling which packages
are installed?
eg "pkginfo | grep shared-mime-info" ?


>
> Regards,
> Moinak.
>
> >
> > -- Manish
> >
> > On Sun, May 18, 2008 at 12:26 PM, S h i v <shivakumar.gn at gmail.com>
> wrote:
> >>
> >> On Sun, May 18, 2008 at 12:50 AM, Manish Chakravarty
> >> <manishchaks at gmail.com> wrote:
> >> > Hi all,
> >> >
> >> > It seems Belenix 0.7 does not come with gcc installed by default.
> >> > How do i install it?
> >> >
> >>
> >> Additional softwares can be installed using the "get-pkgs" command
> >> For details see
> >>
> >>
> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
> >>
> >> $ get-pkgs devel
> >> would install development headers, gcc and whole bunch of other
> >> packages that are categorized as developer related.
> >>
> >> -Shiv
> >
> >
> >
> > --
> > Manish Chakravarty
> > http://manish-chaks.livejournal.com/
> >
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/fd9b960d/attachment.html>

From shivakumar.gn at gmail.com  Sun May 18 00:38:16 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 13:08:16 +0530
Subject: [belenix-dev] How do I make sure BeleniX boots in command line
	mode everytime?
In-Reply-To: <b4dbee910805171108h819c39el8284d1b8f03f61ee@mail.gmail.com>
References: <b4dbee910805171108h819c39el8284d1b8f03f61ee@mail.gmail.com>
Message-ID: <319ee2b10805180038p6d8fc9a7v9b3601bcb6639de7@mail.gmail.com>

On Sat, May 17, 2008 at 11:38 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Hey all,
>
> I am running BeleniX in a VBox VM. I plan to do run compilation on it [1]
> How do I make sure the VM boots in cmd line mode everytime?
>

At the X server login prompt there is a drop to command line option.
(Alt+N is the shortcut if I remeber correctly).

> I want to SSH into the VM and work.
>

There is a bug in BeleniX07 due to which ssh access is not available
by default. The workaround is that
[1] As root, generate the ssh keys for the algo you use. Ex for dsa
     $ ssh-keygen -t dsa
[2] Move the files to /etc/ssh/ssh_host_dsa_key and
/etc/ssh/ssh_host_dsa_key.pub for private and public key files
respectively.
[3] Restart the /network/ssh service
     $ svcadm restart /network/ssh
The above steps are similar to rsa as well. If unsure about what is
supported by your client, install both.

Now you should be able to login via ssh.

-Shiv


From manishchaks at gmail.com  Sun May 18 00:41:18 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 13:11:18 +0530
Subject: [belenix-dev] How do I make sure BeleniX boots in command line
	mode everytime?
In-Reply-To: <319ee2b10805180038p6d8fc9a7v9b3601bcb6639de7@mail.gmail.com>
References: <b4dbee910805171108h819c39el8284d1b8f03f61ee@mail.gmail.com>
	<319ee2b10805180038p6d8fc9a7v9b3601bcb6639de7@mail.gmail.com>
Message-ID: <b4dbee910805180041t475e4f19s9e0f83c847ac15e1@mail.gmail.com>

Hi Shiv,
[..snip..]
>
> There is a bug in BeleniX07 due to which ssh access is not available
> by default. The workaround is that
> [1] As root, generate the ssh keys for the algo you use. Ex for dsa
>     $ ssh-keygen -t dsa
> [2] Move the files to /etc/ssh/ssh_host_dsa_key and
> /etc/ssh/ssh_host_dsa_key.pub for private and public key files
> respectively.

I assume you mean moving these to my home dir:

As in cp /etc/ssh/ssh_host_dsa_key.pub /home/manish/.ssh/id_dsa.pub?

>
> [..snip..]


> -Shiv
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/922b1862/attachment.html>

From shivakumar.gn at gmail.com  Sun May 18 00:44:08 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 13:14:08 +0530
Subject: [belenix-dev] How do I make sure BeleniX boots in command line
	mode everytime?
In-Reply-To: <b4dbee910805180041t475e4f19s9e0f83c847ac15e1@mail.gmail.com>
References: <b4dbee910805171108h819c39el8284d1b8f03f61ee@mail.gmail.com>
	<319ee2b10805180038p6d8fc9a7v9b3601bcb6639de7@mail.gmail.com>
	<b4dbee910805180041t475e4f19s9e0f83c847ac15e1@mail.gmail.com>
Message-ID: <319ee2b10805180044o7a9e71fdo604611bc9a9631a0@mail.gmail.com>

On Sun, May 18, 2008 at 1:11 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Hi Shiv,
> [..snip..]
>>
>> There is a bug in BeleniX07 due to which ssh access is not available
>> by default. The workaround is that
>> [1] As root, generate the ssh keys for the algo you use. Ex for dsa
>>     $ ssh-keygen -t dsa
>> [2] Move the files to /etc/ssh/ssh_host_dsa_key and
>> /etc/ssh/ssh_host_dsa_key.pub for private and public key files
>> respectively.
>
> I assume you mean moving these to my home dir:
>
> As in cp /etc/ssh/ssh_host_dsa_key.pub /home/manish/.ssh/id_dsa.pub?
>

No. I mean this:
$ mv id_dsa /etc/ssh/ssh_host_dsa_key
$ mv id_dsa.pub /etc/ssh/ssh_host_dsa_key.pub

Perform key generation as root user, otherwise make sure the file
permissions are right after moving.
These files are required by ssh daemon and need to be under /etc/ssh/

-Shiv


From moinakg at gmail.com  Sun May 18 00:54:58 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sun, 18 May 2008 13:24:58 +0530
Subject: [belenix-dev] How do i install gcc in belenix?
In-Reply-To: <b4dbee910805180037h5e2b31fbrd93e5fbebf9a8066@mail.gmail.com>
References: <b4dbee910805171220v4ff3016s27b9aa9b38d3603e@mail.gmail.com>
	<319ee2b10805172356l47f2f7acs6d6952dc2c5668de@mail.gmail.com>
	<b4dbee910805180008j25186ea1ue12b6147ba286f69@mail.gmail.com>
	<46fe20470805180014u28135e63q567ce35ea493af74@mail.gmail.com>
	<b4dbee910805180037h5e2b31fbrd93e5fbebf9a8066@mail.gmail.com>
Message-ID: <46fe20470805180054o55f4ab92od625e8c2c40a930e@mail.gmail.com>

On Sun, May 18, 2008 at 1:07 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>
>
> On Sun, May 18, 2008 at 12:44 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>>
>> [...snip...]
>>   There is an SFEcmake in the BeleniX repo and included in the devel
>>   cluster.
>
> Is "pkginfo | grep <packagename>" a reliable way of telling which packages
> are installed?
> eg "pkginfo | grep shared-mime-info" ?

   pkginfo 2>&1 | grep packagename

   pkginfo sends stdout to stderr!!

   To find out which package a file belongs to:

   pkginfo -lp <pathname>

Regards,
Moinak.

>
>>
>>
>> Regards,
>> Moinak.
>>
>> >
>> > -- Manish
>> >
>> > On Sun, May 18, 2008 at 12:26 PM, S h i v <shivakumar.gn at gmail.com>
>> > wrote:
>> >>
>> >> On Sun, May 18, 2008 at 12:50 AM, Manish Chakravarty
>> >> <manishchaks at gmail.com> wrote:
>> >> > Hi all,
>> >> >
>> >> > It seems Belenix 0.7 does not come with gcc installed by default.
>> >> > How do i install it?
>> >> >
>> >>
>> >> Additional softwares can be installed using the "get-pkgs" command
>> >> For details see
>> >>
>> >>
>> >> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
>> >>
>> >> $ get-pkgs devel
>> >> would install development headers, gcc and whole bunch of other
>> >> packages that are categorized as developer related.
>> >>
>> >> -Shiv
>> >
>> >
>> >
>> > --
>> > Manish Chakravarty
>> > http://manish-chaks.livejournal.com/
>> >
>> > _______________________________________________
>> > belenix-dev mailing list
>> > belenix-dev at opensolaris.org
>> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>> >
>> >
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>


From shivakumar.gn at gmail.com  Sun May 18 00:55:57 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 13:25:57 +0530
Subject: [belenix-dev] How do I make sure BeleniX boots in command line
	mode everytime?
In-Reply-To: <319ee2b10805180044o7a9e71fdo604611bc9a9631a0@mail.gmail.com>
References: <b4dbee910805171108h819c39el8284d1b8f03f61ee@mail.gmail.com>
	<319ee2b10805180038p6d8fc9a7v9b3601bcb6639de7@mail.gmail.com>
	<b4dbee910805180041t475e4f19s9e0f83c847ac15e1@mail.gmail.com>
	<319ee2b10805180044o7a9e71fdo604611bc9a9631a0@mail.gmail.com>
Message-ID: <319ee2b10805180055q56fbeb39ye67bb8b843a2546e@mail.gmail.com>

On Sun, May 18, 2008 at 1:14 PM, S h i v <shivakumar.gn at gmail.com> wrote:
> On Sun, May 18, 2008 at 1:11 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>> Hi Shiv,
>> [..snip..]
>>>
>>> There is a bug in BeleniX07 due to which ssh access is not available
>>> by default. The workaround is that
>>>

There is a easier 2 step method.
$ Create & install keys in a single step by executing "/lib/svc/method/sshd -c"
$ Restart /network/ssh

-Shiv


From moinakg at gmail.com  Sun May 18 02:23:05 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sun, 18 May 2008 14:53:05 +0530
Subject: [belenix-dev] Commit notifications for belenix repository
Message-ID: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>

I was thinking whether it will be good to have all belenix repository
commit notifications to come to belenix-dev list. That way everyone
interested belenix development will be aware of what changes are
going on.

Does anyone has objections ?

Regards,
Moinak.


From ketanpadegaonkar at gmail.com  Sun May 18 03:02:17 2008
From: ketanpadegaonkar at gmail.com (Ketan Padegaonkar)
Date: Sun, 18 May 2008 15:32:17 +0530
Subject: [belenix-dev] Commit notifications for belenix repository
In-Reply-To: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
References: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
Message-ID: <95F23ACD-4A05-4AC9-B3EB-36BAFF131BB0@gmail.com>

I don't think I'd mind if this is not too much noise in the midst of  
regular mails, if there's too much traffic, then a -commit list makes  
more sense.

Cheers,
Ketan Padegaonkar
I blog... therefore I am... http://ketan.padegaonkar.name
http://swtbot.org/ - a functional testing tool for SWT/Eclipse

On 18-May-08, at 2:53 PM, Moinak Ghosh wrote:

> I was thinking whether it will be good to have all belenix repository
> commit notifications to come to belenix-dev list. That way everyone
> interested belenix development will be aware of what changes are
> going on.
>
> Does anyone has objections ?
>
> Regards,
> Moinak.
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev




From manishchaks at gmail.com  Sun May 18 03:07:52 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 15:37:52 +0530
Subject: [belenix-dev] Commit notifications for belenix repository
In-Reply-To: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
References: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
Message-ID: <b4dbee910805180307r55e92e99mc523395cc27fee3e@mail.gmail.com>

On Sun, May 18, 2008 at 2:53 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

> I was thinking whether it will be good to have all belenix repository
> commit notifications to come to belenix-dev list. That way everyone
> interested belenix development will be aware of what changes are
> going on.

+1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/52121780/attachment.html>

From shivakumar.gn at gmail.com  Sun May 18 03:20:00 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 15:50:00 +0530
Subject: [belenix-dev] Commit notifications for belenix repository
In-Reply-To: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
References: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
Message-ID: <319ee2b10805180320w41842269w558a5b79f9ce206e@mail.gmail.com>

On Sun, May 18, 2008 at 2:53 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
> I was thinking whether it will be good to have all belenix repository
> commit notifications to come to belenix-dev list. That way everyone
> interested belenix development will be aware of what changes are
> going on.
>
> Does anyone has objections ?
>

Notification is a good idea but I am not keen for it to be on -dev
list. I have found the commit notifications on various opensolaris
lists as noise rather than being helpful, I have either unsubscribed
from those lists if I was a lurker there, or I have set rules in my
mail program if I have decided to stay on.
Of the hundreds of files being worked upon notifications would be of
interest to a sub-set even within the set of active contributors.
Also people sitting on the fence may see all the notification mails as
noise and switch to the wrong side, esp those who are on the list who
lurk and now & then cross-post contributions.

I would suggest sending the notification to the sf.net list of belenix
instead and those interested are free to subscribe as necessary.

belenix-notify at lists.sourceforge.net will become operational within 24
hours. We can pilot it and if people find it useful to have that
information on belenix-dev we can redirect the notifications.

Thoughts ?

-Shiv


From ananth.shrinivas at gmail.com  Sun May 18 04:05:38 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Sun, 18 May 2008 16:35:38 +0530
Subject: [belenix-dev] Commit notifications for belenix repository
In-Reply-To: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
References: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
Message-ID: <f5ff03920805180405u3a22d6faw568a1e39b14ed5a9@mail.gmail.com>

On Sun, May 18, 2008 at 2:53 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

> I was thinking whether it will be good to have all belenix repository
> commit notifications to come to belenix-dev list. That way everyone
> interested belenix development will be aware of what changes are
> going on.
>
> Does anyone has objections ?
>

People who *want* notifications will always subscribe to  the list. Lets not
dump it on those who might not like automated mails spamming their account.

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/9e37e524/attachment.html>

From shivakumar.gn at gmail.com  Sun May 18 04:41:17 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 17:11:17 +0530
Subject: [belenix-dev] Commit notifications for belenix repository
In-Reply-To: <f5ff03920805180405u3a22d6faw568a1e39b14ed5a9@mail.gmail.com>
References: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
	<f5ff03920805180405u3a22d6faw568a1e39b14ed5a9@mail.gmail.com>
Message-ID: <319ee2b10805180441h64f8e5f0w86f3b68f507415a5@mail.gmail.com>

On Sun, May 18, 2008 at 4:35 PM, Ananth Shrinivas
<ananth.shrinivas at gmail.com> wrote:
>
>
> On Sun, May 18, 2008 at 2:53 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>>
>> I was thinking whether it will be good to have all belenix repository
>> commit notifications to come to belenix-dev list. That way everyone
>> interested belenix development will be aware of what changes are
>> going on.
>>
>> Does anyone has objections ?
>
> People who *want* notifications will always subscribe to  the list. Lets not
> dump it on those who might not like automated mails spamming their account.
>

There was no list to subscribe to :)

A belenix-notify at lists.sourceforge.net has been created for the same.
Starting from now on the notifications will be available to those
subscribed to that list.

People may subscribe to the same at
https://lists.sourceforge.net/lists/listinfo/belenix-notify

This is a notification only list. All posts by any list members will
be discarded.

-Shiv


From sriramnrn at gmail.com  Sun May 18 04:46:53 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Sun, 18 May 2008 17:16:53 +0530
Subject: [belenix-dev] [belenix-discuss] Commit notifications for
	belenix repository
In-Reply-To: <319ee2b10805180441h64f8e5f0w86f3b68f507415a5@mail.gmail.com>
References: <46fe20470805180223l43aae79x512e34538dea698e@mail.gmail.com>
	<f5ff03920805180405u3a22d6faw568a1e39b14ed5a9@mail.gmail.com>
	<319ee2b10805180441h64f8e5f0w86f3b68f507415a5@mail.gmail.com>
Message-ID: <49977f270805180446g176cf330v81a0941a259c7155@mail.gmail.com>

On Sun, May 18, 2008 at 5:11 PM, S h i v <shivakumar.gn at gmail.com> wrote:
>
> There was no list to subscribe to :)
>
> A belenix-notify at lists.sourceforge.net has been created for the same.
> Starting from now on the notifications will be available to those
> subscribed to that list.
>
> People may subscribe to the same at
> https://lists.sourceforge.net/lists/listinfo/belenix-notify
>

Sounds good. I just subscribed.

-- Sriram


From manishchaks at gmail.com  Sun May 18 05:04:18 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 17:34:18 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on BeleniX
	0.7 ( for KDE4)
Message-ID: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>

Hello all,

I am attempting to build KDE4 sandboxed into /opt on BeleniX 0.7
I have setup my environment thus:

===========ENV============
manish at beleniXRemiX:~$ export PATH=/opt/kde4/bin/:$PATH
manish at beleniXRemiX:~$ env | grep LD
LD_LIBRARY_PATH=/lib:/usr/lib:/usr/sfw/lib:/usr/X11R6/lib:/usr/openwin/lib
manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/:$PATH
manish at beleniXRemiX:~$ env | grep PKG
PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig
manish at beleniXRemiX:~$ export
PKG_CONFIG_PATH=/opt/kde4/lib/:$PKG_CONFIG_PATH
============================

I am doing a "--prefix=/opt/kde4" for all the "./configure"'s

CLucene and DBus built without a hitch
When I tried compling dbus-glib I get the following error:

====ERROR BULID TRACE======
make[1]: Entering directory `/export/home/manish/kde.build/dbus-glib-0.74'
Making all in dbus
make[2]: Entering directory
`/export/home/manish/kde.build/dbus-glib-0.74/dbus'
make  all-recursive
make[3]: Entering directory
`/export/home/manish/kde.build/dbus-glib-0.74/dbus'
Making all in .
make[4]: Entering directory
`/export/home/manish/kde.build/dbus-glib-0.74/dbus'
/bin/bash ../libtool --tag=CC   --mode=link /usr/sfw/bin/gcc  -g -O2 -Wall
-Wcha
r-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
-Wpoin
ter-arith -Wcast-align -Wfloat-equal -Wsign-compare   -o dbus-binding-tool
dbus-
binding-tool-glib.o dbus-glib-tool.o libdbus-gtool.la libdbus-glib-1.la-ldbus-1
   -R/usr/gnu/lib -L/usr/gnu/lib -lgobject-2.0 -lglib-2.0 -liconv   -lexpat
-lns
l -lsocket
/usr/sfw/bin/gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations
-Wmissing
-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
-Wsign-c
ompare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o dbus-glib-tool.o
./.
libs/libdbus-gtool.a ./.libs/libdbus-glib-1.so -L/usr/gnu/lib -ldbus-1
-lgobject
-2.0 -lglib-2.0 -liconv -lexpat -lnsl -lsocket -R/opt/kde4/lib
-R/usr/gnu/lib
Undefined                       first referenced
 symbol                             in file
libintl_bind_textdomain_codeset     dbus-glib-tool.o  (symbol belongs to
implicit dependency /usr/gnu/lib/libintl.so.8)
libintl_gettext                     dbus-binding-tool-glib.o  (symbol
belongs to implicit dependency /usr/gnu/lib/libintl.so.8)
libintl_textdomain                  dbus-glib-tool.o  (symbol belongs to
implicit dependency /usr/gnu/lib/libintl.so.8)
libintl_bindtextdomain              dbus-glib-tool.o  (symbol belongs to
implicit dependency /usr/gnu/lib/libintl.so.8)
libintl_dgettext                    dbus-glib-tool.o  (symbol belongs to
implicit dependency /usr/gnu/lib/libintl.so.8)
ld: fatal: Symbol referencing errors. No output written to
.libs/dbus-binding-to                                                   ol
collect2: ld returned 1 exit status
make[4]: *** [dbus-binding-tool] Error 1
make[4]: Leaving directory
`/export/home/manish/kde.build/dbus-glib-0.74/dbus'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/home/manish/kde.build/dbus-glib-0.74/dbus'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/home/manish/kde.build/dbus-glib-0.74/dbus'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/export/home/manish/kde.build/dbus-glib-0.74'
make: *** [all] Error 2

=================

These are the list of dbus packages already on my system:
===========DBUS PKG LIST=============
GNOME2      SFEdbus-qt3                    Qt3 binding for DBUS
GNOME2      SFEdbus-qt3-devel              Qt3 binding for DBUS -
development files
SFE         SFEnicdrv-tcfe                 Nic driver for 3Com cardbus/PCI
fast ethernet cards
GNOME2      SUNWdbus                       Simple IPC library based on
messages
GNOME2      SUNWdbus-bindings              Simple IPC library based on
messages
GNOME2      SUNWdbus-bindings-devel        Simple IPC library based on
messages - development files
GNOME2      SUNWdbus-devel                 Simple IPC library based on
messages - development files
GNOME2      SUNWdbus-root                  Simple IPC library based on
messages - / filesystem
====================================

In addition to the above, I have a pristine dbus living in /opt/kde4


I guess I am doing something wrong with the linker here. Can anyone help me
out?

-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/48a6d5ab/attachment.html>

From manishchaks at gmail.com  Sun May 18 05:09:04 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Sun, 18 May 2008 17:39:04 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
Message-ID: <b4dbee910805180509y72d0c2f2m3866ae85c87f32c0@mail.gmail.com>

Small correction
The line
"manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/:$PATH"
should read
"manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/
:$LD_LIBRARY_PATH"

The remainder of the problem description is the same

On Sun, May 18, 2008 at 5:34 PM, Manish Chakravarty <manishchaks at gmail.com>
wrote:

> Hello all,
>
> I am attempting to build KDE4 sandboxed into /opt on BeleniX 0.7
> I have setup my environment thus:
>
> ===========ENV============
> manish at beleniXRemiX:~$ export PATH=/opt/kde4/bin/:$PATH
> manish at beleniXRemiX:~$ env | grep LD
> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/sfw/lib:/usr/X11R6/lib:/usr/openwin/lib
> manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/:$PATH
> manish at beleniXRemiX:~$ env | grep PKG
>
> PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig
> manish at beleniXRemiX:~$ export
> PKG_CONFIG_PATH=/opt/kde4/lib/:$PKG_CONFIG_PATH
> ============================
>
> I am doing a "--prefix=/opt/kde4" for all the "./configure"'s
>
> CLucene and DBus built without a hitch
> When I tried compling dbus-glib I get the following error:
>
> ====ERROR BULID TRACE======
> make[1]: Entering directory `/export/home/manish/kde.build/dbus-glib-0.74'
> Making all in dbus
> make[2]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make  all-recursive
> make[3]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> Making all in .
> make[4]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> /bin/bash ../libtool --tag=CC   --mode=link /usr/sfw/bin/gcc  -g -O2 -Wall
> -Wcha
> r-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
> -Wpoin
> ter-arith -Wcast-align -Wfloat-equal -Wsign-compare   -o dbus-binding-tool
> dbus-
> binding-tool-glib.o dbus-glib-tool.o libdbus-gtool.la libdbus-glib-1.la-ldbus-1
>    -R/usr/gnu/lib -L/usr/gnu/lib -lgobject-2.0 -lglib-2.0 -liconv   -lexpat
> -lns
> l -lsocket
> /usr/sfw/bin/gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations
> -Wmissing
> -prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
> -Wsign-c
> ompare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o
> dbus-glib-tool.o  ./.
> libs/libdbus-gtool.a ./.libs/libdbus-glib-1.so -L/usr/gnu/lib -ldbus-1
> -lgobject
> -2.0 -lglib-2.0 -liconv -lexpat -lnsl -lsocket -R/opt/kde4/lib
> -R/usr/gnu/lib
> Undefined                       first referenced
>  symbol                             in file
> libintl_bind_textdomain_codeset     dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_gettext                     dbus-binding-tool-glib.o  (symbol
> belongs to implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_textdomain                  dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_bindtextdomain              dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_dgettext                    dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> ld: fatal: Symbol referencing errors. No output written to
> .libs/dbus-binding-to                                                   ol
> collect2: ld returned 1 exit status
> make[4]: *** [dbus-binding-tool] Error 1
> make[4]: Leaving directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/export/home/manish/kde.build/dbus-glib-0.74'
> make: *** [all] Error 2
>
> =================
>
> These are the list of dbus packages already on my system:
> ===========DBUS PKG LIST=============
> GNOME2      SFEdbus-qt3                    Qt3 binding for DBUS
> GNOME2      SFEdbus-qt3-devel              Qt3 binding for DBUS -
> development files
> SFE         SFEnicdrv-tcfe                 Nic driver for 3Com cardbus/PCI
> fast ethernet cards
> GNOME2      SUNWdbus                       Simple IPC library based on
> messages
> GNOME2      SUNWdbus-bindings              Simple IPC library based on
> messages
> GNOME2      SUNWdbus-bindings-devel        Simple IPC library based on
> messages - development files
> GNOME2      SUNWdbus-devel                 Simple IPC library based on
> messages - development files
> GNOME2      SUNWdbus-root                  Simple IPC library based on
> messages - / filesystem
> ====================================
>
> In addition to the above, I have a pristine dbus living in /opt/kde4
>
>
> I guess I am doing something wrong with the linker here. Can anyone help me
> out?
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080518/7c655cb8/attachment.html>

From shivakumar.gn at gmail.com  Sun May 18 05:28:58 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 18 May 2008 17:58:58 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <b4dbee910805180509y72d0c2f2m3866ae85c87f32c0@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<b4dbee910805180509y72d0c2f2m3866ae85c87f32c0@mail.gmail.com>
Message-ID: <319ee2b10805180528sfc8f93bm82cc7f6f897bf388@mail.gmail.com>

On Sun, May 18, 2008 at 5:39 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Small correction
> The line
> "manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/
> :$PATH"
> should read
> "manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/
> :$LD_LIBRARY_PATH"
>
> The remainder of the problem description is the same
>

Try including -lintl as one of the linker options. Also there is
probably no libintl.so in the library path. BeleniX has
/lib/libintl.so.1 which will not be used by the linker since
libfoo.so.<n> are not assumed to be exported interfaces.

-Shiv


From moinakg at gmail.com  Sun May 18 09:17:50 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sun, 18 May 2008 21:47:50 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
Message-ID: <46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>

Hi Manish,

   You are better off trying to use the BeleniX spec file system from the
beginning. Lots of env settings headaches will be automatically taken
care of.

You do not need to buil dbus-glib since it is already included as part of
SUNWdbus-bindings package on the livecd. For this problem you need
use the GNU libintl and iconv. So the following env has to be set before
invoking configure:

export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv"

Regards,
Moinak.

On Sun, May 18, 2008 at 5:34 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Hello all,
>
> I am attempting to build KDE4 sandboxed into /opt on BeleniX 0.7
> I have setup my environment thus:
>
> ===========ENV============
> manish at beleniXRemiX:~$ export PATH=/opt/kde4/bin/:$PATH
> manish at beleniXRemiX:~$ env | grep LD
> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/sfw/lib:/usr/X11R6/lib:/usr/openwin/lib
> manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/:$PATH
> manish at beleniXRemiX:~$ env | grep PKG
> PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig
> manish at beleniXRemiX:~$ export
> PKG_CONFIG_PATH=/opt/kde4/lib/:$PKG_CONFIG_PATH
> ============================
>
> I am doing a "--prefix=/opt/kde4" for all the "./configure"'s
>
> CLucene and DBus built without a hitch
> When I tried compling dbus-glib I get the following error:
>
> ====ERROR BULID TRACE======
> make[1]: Entering directory `/export/home/manish/kde.build/dbus-glib-0.74'
> Making all in dbus
> make[2]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make  all-recursive
> make[3]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> Making all in .
> make[4]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> /bin/bash ../libtool --tag=CC   --mode=link /usr/sfw/bin/gcc  -g -O2 -Wall
> -Wcha
> r-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
> -Wpoin
> ter-arith -Wcast-align -Wfloat-equal -Wsign-compare   -o dbus-binding-tool
> dbus-
> binding-tool-glib.o dbus-glib-tool.o libdbus-gtool.la libdbus-glib-1.la
> -ldbus-1
>    -R/usr/gnu/lib -L/usr/gnu/lib -lgobject-2.0 -lglib-2.0 -liconv   -lexpat
> -lns
> l -lsocket
> /usr/sfw/bin/gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations
> -Wmissing
> -prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
> -Wsign-c
> ompare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o dbus-glib-tool.o
> ./.
> libs/libdbus-gtool.a ./.libs/libdbus-glib-1.so -L/usr/gnu/lib -ldbus-1
> -lgobject
> -2.0 -lglib-2.0 -liconv -lexpat -lnsl -lsocket -R/opt/kde4/lib
> -R/usr/gnu/lib
> Undefined                       first referenced
>  symbol                             in file
> libintl_bind_textdomain_codeset     dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_gettext                     dbus-binding-tool-glib.o  (symbol
> belongs to implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_textdomain                  dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_bindtextdomain              dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> libintl_dgettext                    dbus-glib-tool.o  (symbol belongs to
> implicit dependency /usr/gnu/lib/libintl.so.8)
> ld: fatal: Symbol referencing errors. No output written to
> .libs/dbus-binding-to                                                   ol
> collect2: ld returned 1 exit status
> make[4]: *** [dbus-binding-tool] Error 1
> make[4]: Leaving directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory
> `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/export/home/manish/kde.build/dbus-glib-0.74'
> make: *** [all] Error 2
>
> =================
>
> These are the list of dbus packages already on my system:
> ===========DBUS PKG LIST=============
> GNOME2      SFEdbus-qt3                    Qt3 binding for DBUS
> GNOME2      SFEdbus-qt3-devel              Qt3 binding for DBUS -
> development files
> SFE         SFEnicdrv-tcfe                 Nic driver for 3Com cardbus/PCI
> fast ethernet cards
> GNOME2      SUNWdbus                       Simple IPC library based on
> messages
> GNOME2      SUNWdbus-bindings              Simple IPC library based on
> messages
> GNOME2      SUNWdbus-bindings-devel        Simple IPC library based on
> messages - development files
> GNOME2      SUNWdbus-devel                 Simple IPC library based on
> messages - development files
> GNOME2      SUNWdbus-root                  Simple IPC library based on
> messages - / filesystem
> ====================================
>
> In addition to the above, I have a pristine dbus living in /opt/kde4
>
>
> I guess I am doing something wrong with the linker here. Can anyone help me
> out?
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From sriramnrn at gmail.com  Sun May 18 17:48:51 2008
From: sriramnrn at gmail.com (Sriram Narayanan)
Date: Mon, 19 May 2008 06:18:51 +0530
Subject: [belenix-dev] I need the output of Firefox' buildconfig on SPARC
Message-ID: <49977f270805181748w7fa769adw812f9d1db590e950@mail.gmail.com>

To anyone who has access to a SPARC box that can run Firefox:

1. Start Firefox
2. In the address bar, type about:buildconfig
3. Send to me what that page shows.

Thanks.

-- Sriram


From shivakumar.gn at gmail.com  Sun May 18 22:08:06 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Mon, 19 May 2008 10:38:06 +0530
Subject: [belenix-dev] KDE 4.0.74 (KDE 4.1beta) for Belenix 0.7.1
In-Reply-To: <148728.64089.qm@web34205.mail.mud.yahoo.com>
References: <148728.64089.qm@web34205.mail.mud.yahoo.com>
Message-ID: <319ee2b10805182208s7a48cec9w2b831e41fae85e33@mail.gmail.com>

On Mon, May 19, 2008 at 1:53 AM, ken mays <maybird1776 at yahoo.com> wrote:
> Hello,
>
> I'm reviewing a build of KDE 4.0.74 (KDE
> 4.1beta) for Belenix 0.7.1.
>
> A question is in if Belenix 0.8 can have KDE 4.1
> (released in July) for Belenix 0.8? I was hoping to
> see an ON b92 build with KDE 4.1.
>
> Interesting in building KDE 4.0.74 instead to test on
> Belenix 0.7 so we know what we are up against
> beforehand??
>

The set of applications available in a functional & stable form is
what is likely to decide when it will go in. We will depend on people
working on the KDE4 port for BeleniX to provide these inputs, for now
it is one person (Manish) doing it.

Additional support is more than welcome. We will not move to KDE4.x
for BeleniX 0.7.1 since it is just a maintenance release and moving to
newer KDE version cannot be considered as trivial.
Nevertheless, if KDE4 binary packages are built and made available,
they can hosted for people to use them on top of BeleniX 0.7.x
Suggested steps to "pkgrm default installed KDE" and "pkgadd new KDE"
can be provided.

-Shiv


From maybird1776 at yahoo.com  Sun May 18 08:27:48 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Sun, 18 May 2008 08:27:48 -0700 (PDT)
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.4?
Message-ID: <462378.55959.qm@web34205.mail.mud.yahoo.com>

What would hold us back from using ON b92 and KDE
4.0.4 for Belenix 0.7.1 ?!?

I was thinking something like:
1. ON b92
2. KDE 4.0.4
3. Compiz 0.7.4
4. Nvidia driver 169.12 & Intel driver 2.3.0

I'm willing to help... ;o)

~ Ken



      


From shivakumar.gn at gmail.com  Sun May 18 22:48:39 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Mon, 19 May 2008 11:18:39 +0530
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.4
In-Reply-To: <462378.55959.qm@web34205.mail.mud.yahoo.com>
References: <462378.55959.qm@web34205.mail.mud.yahoo.com>
Message-ID: <319ee2b10805182248t2b20887ak8d10a2badc866f2d@mail.gmail.com>

On Sun, May 18, 2008 at 8:57 PM, ken mays <maybird1776 at yahoo.com> wrote:
> What would hold us back from using ON b92 and KDE
> 4.0.4 for Belenix 0.7.1 ?!?
>

Amount of work involved and time required.

> I was thinking something like:
> 1. ON b92
> 2. KDE 4.0.4
> 3. Compiz 0.7.4
> 4. Nvidia driver 169.12 & Intel driver 2.3.0
>
> I'm willing to help... ;o)
>

That would be awesome. Currently Manish has started on KDE4.

Either end of first week or second week of June is what is being
thought of for 0.7.1
Having 0.7.1 is an opportunity to fix bugs, do some cleanup of the
current spec files, etc while the work for 0.8 is being done in
parallel.

There will be a 0.8 in quick succession. That would be a more suitable
target for KDE4.

-Shiv


From moinakg at gmail.com  Sun May 18 22:56:13 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Mon, 19 May 2008 11:26:13 +0530
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.4
In-Reply-To: <319ee2b10805182248t2b20887ak8d10a2badc866f2d@mail.gmail.com>
References: <462378.55959.qm@web34205.mail.mud.yahoo.com>
	<319ee2b10805182248t2b20887ak8d10a2badc866f2d@mail.gmail.com>
Message-ID: <46fe20470805182256q49d213e0m3fbb1162172be6be@mail.gmail.com>

On Mon, May 19, 2008 at 11:18 AM, S h i v <shivakumar.gn at gmail.com> wrote:
> On Sun, May 18, 2008 at 8:57 PM, ken mays <maybird1776 at yahoo.com> wrote:
>> What would hold us back from using ON b92 and KDE
>> 4.0.4 for Belenix 0.7.1 ?!?
>>
>
> Amount of work involved and time required.
>
>> I was thinking something like:
>> 1. ON b92
>> 2. KDE 4.0.4
>> 3. Compiz 0.7.4
>> 4. Nvidia driver 169.12 & Intel driver 2.3.0
>>
>> I'm willing to help... ;o)
>>
>
> That would be awesome. Currently Manish has started on KDE4.
>
> Either end of first week or second week of June is what is being
> thought of for 0.7.1
> Having 0.7.1 is an opportunity to fix bugs, do some cleanup of the
> current spec files, etc while the work for 0.8 is being done in
> parallel.

   I am anyway looking at updating the ON build for 0.7.1 and a newer
   Nvidia driver, but further new stuff like KDE4 will be too much for a
   maintenance release.

Regards,
Moinak.

>
> There will be a 0.8 in quick succession. That would be a more suitable
> target for KDE4.
>
> -Shiv
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From maybird1776 at yahoo.com  Mon May 19 06:07:09 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Mon, 19 May 2008 06:07:09 -0700 (PDT)
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.4
In-Reply-To: <46fe20470805182256q49d213e0m3fbb1162172be6be@mail.gmail.com>
Message-ID: <607896.84835.qm@web34201.mail.mud.yahoo.com>

--- Moinak Ghosh <moinakg at gmail.com> wrote:

> On Mon, May 19, 2008 at 11:18 AM, S h i v
> <shivakumar.gn at gmail.com> wrote:
> > On Sun, May 18, 2008 at 8:57 PM, ken mays
> <maybird1776 at yahoo.com> wrote:
> >> What would hold us back from using ON b92 and KDE
> >> 4.0.4 for Belenix 0.7.1 ?!?
> >>
> >
> > Amount of work involved and time required.
> >
> >> I was thinking something like:
> >> 1. ON b92
> >> 2. KDE 4.0.4
> >> 3. Compiz 0.7.4
> >> 4. Nvidia driver 169.12 & Intel driver 2.3.0
> >>
> >> I'm willing to help... ;o)
> >>
> >
> > That would be awesome. Currently Manish has
> started on KDE4.
> >
> > Either end of first week or second week of June is
> what is being
> > thought of for 0.7.1
> > Having 0.7.1 is an opportunity to fix bugs, do
> some cleanup of the
> > current spec files, etc while the work for 0.8 is
> being done in
> > parallel.
> 
>    I am anyway looking at updating the ON build for
> 0.7.1 and a newer
>    Nvidia driver, but further new stuff like KDE4
> will be too much for a
>    maintenance release.
> 
> Regards,
> Moinak.
> 
> >
> > There will be a 0.8 in quick succession. That
> would be a more suitable
> > target for KDE4.
> >
> > -Shiv


Ok. I reviewed KDE 3.5.9 which would be easy to stick
in Belenix 0.7.1 as a maintenance/security fix to meet
the June deadline. Nothing major that would cause
additional manpower or overhead to do the update.

For Belenix 0.8, I'll work with Manish on KDE 4.1
(currently KDE 4.0.74) integration with GCC.

The other thing would just be an enhanced HD audio
framework moving forward to superceded Sun audio. I
will put in a request for 4front's OSS 4.0/4.1 as an
inclusion so we can integrate that with KDE 4.1. Let
me know if this can be added in the plans or to just
stick with Sun audio for now.

~ Ken



      


From moinakg at gmail.com  Mon May 19 06:17:05 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Mon, 19 May 2008 18:47:05 +0530
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.
In-Reply-To: <607896.84835.qm@web34201.mail.mud.yahoo.com>
References: <46fe20470805182256q49d213e0m3fbb1162172be6be@mail.gmail.com>
	<607896.84835.qm@web34201.mail.mud.yahoo.com>
Message-ID: <46fe20470805190617k6a856733gb53a4429d3b3421f@mail.gmail.com>

On Mon, May 19, 2008 at 6:37 PM, ken mays <maybird1776 at yahoo.com> wrote:
> --- Moinak Ghosh <moinakg at gmail.com> wrote:
>
>> On Mon, May 19, 2008 at 11:18 AM, S h i v
>> <shivakumar.gn at gmail.com> wrote:
>> > On Sun, May 18, 2008 at 8:57 PM, ken mays
>> <maybird1776 at yahoo.com> wrote:
>> >> What would hold us back from using ON b92 and KDE
>> >> 4.0.4 for Belenix 0.7.1 ?!?
>> >>
>> >
>> > Amount of work involved and time required.
>> >
>> >> I was thinking something like:
>> >> 1. ON b92
>> >> 2. KDE 4.0.4
>> >> 3. Compiz 0.7.4
>> >> 4. Nvidia driver 169.12 & Intel driver 2.3.0
>> >>
>> >> I'm willing to help... ;o)
>> >>
>> >
>> > That would be awesome. Currently Manish has
>> started on KDE4.
>> >
>> > Either end of first week or second week of June is
>> what is being
>> > thought of for 0.7.1
>> > Having 0.7.1 is an opportunity to fix bugs, do
>> some cleanup of the
>> > current spec files, etc while the work for 0.8 is
>> being done in
>> > parallel.
>>
>>    I am anyway looking at updating the ON build for
>> 0.7.1 and a newer
>>    Nvidia driver, but further new stuff like KDE4
>> will be too much for a
>>    maintenance release.
>>
>> Regards,
>> Moinak.
>>
>> >
>> > There will be a 0.8 in quick succession. That
>> would be a more suitable
>> > target for KDE4.
>> >
>> > -Shiv
>
>
> Ok. I reviewed KDE 3.5.9 which would be easy to stick
> in Belenix 0.7.1 as a maintenance/security fix to meet
> the June deadline. Nothing major that would cause
> additional manpower or overhead to do the update.

   Yes, that is the plan.

>
> For Belenix 0.8, I'll work with Manish on KDE 4.1
> (currently KDE 4.0.74) integration with GCC.
>
> The other thing would just be an enhanced HD audio
> framework moving forward to superceded Sun audio. I
> will put in a request for 4front's OSS 4.0/4.1 as an
> inclusion so we can integrate that with KDE 4.1. Let
> me know if this can be added in the plans or to just
> stick with Sun audio for now.

   OSS is already included in 0.7. 0.7.1 will move to the
   latest release.

Regards,
Moinak.

>
> ~ Ken
>
>
>
>
>


From manishchaks at gmail.com  Mon May 19 21:57:50 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Tue, 20 May 2008 10:27:50 +0530
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.
In-Reply-To: <607896.84835.qm@web34201.mail.mud.yahoo.com>
References: <46fe20470805182256q49d213e0m3fbb1162172be6be@mail.gmail.com>
	<607896.84835.qm@web34201.mail.mud.yahoo.com>
Message-ID: <b4dbee910805192157sff5ec77yeba51a9f4217ecd8@mail.gmail.com>

[...snip...]
>
> > > That would be awesome. Currently Manish has
> > started on KDE4.
>
I have begun my work and I think I am heading in the right direction.

Ken,
     If you want to pitch into the KDE4 build effort, it would be amazing!
[...SNIP...]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080520/5c327ec9/attachment.html>

From manishchaks at gmail.com  Mon May 19 22:00:43 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Tue, 20 May 2008 10:30:43 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
Message-ID: <b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>

On Sun, May 18, 2008 at 9:47 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

> Hi Manish,
>
>   You are better off trying to use the BeleniX spec file system from the
> beginning. Lots of env settings headaches will be automatically taken
> care of.

How do I do that?

>
>
> You do not need to buil dbus-glib since it is already included as part of
> SUNWdbus-bindings package on the livecd. For this problem you need
> use the GNU libintl and iconv. So the following env has to be set before
> invoking configure:

Qt-copy was unable to find dbus as a part of the build process.
It said  something to the effect of "you need to have dbus installed to
install the QtDbus module".
As you know KDE4 requires the QtDbus module.



>
> export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv

Thanks. I will try the build with these LDFLAGS

>
> Regards,
> Moinak.
>
> On Sun, May 18, 2008 at 5:34 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
> > Hello all,
> >
> > I am attempting to build KDE4 sandboxed into /opt on BeleniX 0.7
> > I have setup my environment thus:
> >
> > ===========ENV============
> > manish at beleniXRemiX:~$ export PATH=/opt/kde4/bin/:$PATH
> > manish at beleniXRemiX:~$ env | grep LD
> >
> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/sfw/lib:/usr/X11R6/lib:/usr/openwin/lib
> > manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/:$PATH
> > manish at beleniXRemiX:~$ env | grep PKG
> >
> PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig
> > manish at beleniXRemiX:~$ export
> > PKG_CONFIG_PATH=/opt/kde4/lib/:$PKG_CONFIG_PATH
> > ============================
> >
> > I am doing a "--prefix=/opt/kde4" for all the "./configure"'s
> >
> > CLucene and DBus built without a hitch
> > When I tried compling dbus-glib I get the following error:
> >
> > ====ERROR BULID TRACE======
> > make[1]: Entering directory
> `/export/home/manish/kde.build/dbus-glib-0.74'
> > Making all in dbus
> > make[2]: Entering directory
> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> > make  all-recursive
> > make[3]: Entering directory
> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> > Making all in .
> > make[4]: Entering directory
> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> > /bin/bash ../libtool --tag=CC   --mode=link /usr/sfw/bin/gcc  -g -O2
> -Wall
> > -Wcha
> > r-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
> > -Wpoin
> > ter-arith -Wcast-align -Wfloat-equal -Wsign-compare   -o
> dbus-binding-tool
> > dbus-
> > binding-tool-glib.o dbus-glib-tool.o libdbus-gtool.la libdbus-glib-1.la
> > -ldbus-1
> >    -R/usr/gnu/lib -L/usr/gnu/lib -lgobject-2.0 -lglib-2.0 -liconv
> -lexpat
> > -lns
> > l -lsocket
> > /usr/sfw/bin/gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations
> > -Wmissing
> > -prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
> > -Wsign-c
> > ompare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o
> dbus-glib-tool.o
> > ./.
> > libs/libdbus-gtool.a ./.libs/libdbus-glib-1.so -L/usr/gnu/lib -ldbus-1
> > -lgobject
> > -2.0 -lglib-2.0 -liconv -lexpat -lnsl -lsocket -R/opt/kde4/lib
> > -R/usr/gnu/lib
> > Undefined                       first referenced
> >  symbol                             in file
> > libintl_bind_textdomain_codeset     dbus-glib-tool.o  (symbol belongs to
> > implicit dependency /usr/gnu/lib/libintl.so.8)
> > libintl_gettext                     dbus-binding-tool-glib.o  (symbol
> > belongs to implicit dependency /usr/gnu/lib/libintl.so.8)
> > libintl_textdomain                  dbus-glib-tool.o  (symbol belongs to
> > implicit dependency /usr/gnu/lib/libintl.so.8)
> > libintl_bindtextdomain              dbus-glib-tool.o  (symbol belongs to
> > implicit dependency /usr/gnu/lib/libintl.so.8)
> > libintl_dgettext                    dbus-glib-tool.o  (symbol belongs to
> > implicit dependency /usr/gnu/lib/libintl.so.8)
> > ld: fatal: Symbol referencing errors. No output written to
> > .libs/dbus-binding-to
> ol
> > collect2: ld returned 1 exit status
> > make[4]: *** [dbus-binding-tool] Error 1
> > make[4]: Leaving directory
> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> > make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory
> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory
> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/export/home/manish/kde.build/dbus-glib-0.74'
> > make: *** [all] Error 2
> >
> > =================
> >
> > These are the list of dbus packages already on my system:
> > ===========DBUS PKG LIST=============
> > GNOME2      SFEdbus-qt3                    Qt3 binding for DBUS
> > GNOME2      SFEdbus-qt3-devel              Qt3 binding for DBUS -
> > development files
> > SFE         SFEnicdrv-tcfe                 Nic driver for 3Com
> cardbus/PCI
> > fast ethernet cards
> > GNOME2      SUNWdbus                       Simple IPC library based on
> > messages
> > GNOME2      SUNWdbus-bindings              Simple IPC library based on
> > messages
> > GNOME2      SUNWdbus-bindings-devel        Simple IPC library based on
> > messages - development files
> > GNOME2      SUNWdbus-devel                 Simple IPC library based on
> > messages - development files
> > GNOME2      SUNWdbus-root                  Simple IPC library based on
> > messages - / filesystem
> > ====================================
> >
> > In addition to the above, I have a pristine dbus living in /opt/kde4
> >
> >
> > I guess I am doing something wrong with the linker here. Can anyone help
> me
> > out?
> >
> > --
> > Manish Chakravarty
> > http://manish-chaks.livejournal.com/
> >
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> >
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080520/03fad2a6/attachment.html>

From moinakg at gmail.com  Tue May 20 00:36:35 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Tue, 20 May 2008 13:06:35 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
	<b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
Message-ID: <46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>

On Tue, May 20, 2008 at 10:30 AM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>
>
> On Sun, May 18, 2008 at 9:47 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>>
>> Hi Manish,
>>
>>   You are better off trying to use the BeleniX spec file system from the
>> beginning. Lots of env settings headaches will be automatically taken
>> care of.
>
> How do I do that?
>>
>>
>> You do not need to buil dbus-glib since it is already included as part of
>> SUNWdbus-bindings package on the livecd. For this problem you need
>> use the GNU libintl and iconv. So the following env has to be set before
>> invoking configure:
>
> Qt-copy was unable to find dbus as a part of the build process.
> It said  something to the effect of "you need to have dbus installed to
> install the QtDbus module".
> As you know KDE4 requires the QtDbus module.

   Huh. That is strange since Qt3 is built with Dbus support nad it was able
   to find all the components. Just check for /usr/lib/libdbus-glib*.
   Can you send me the configure log ?

Regards,
Moinak.

>
>
>>
>>
>> export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv
>
> Thanks. I will try the build with these LDFLAGS
>>
>> Regards,
>> Moinak.
>>
>> On Sun, May 18, 2008 at 5:34 PM, Manish Chakravarty
>> <manishchaks at gmail.com> wrote:
>> > Hello all,
>> >
>> > I am attempting to build KDE4 sandboxed into /opt on BeleniX 0.7
>> > I have setup my environment thus:
>> >
>> > ===========ENV============
>> > manish at beleniXRemiX:~$ export PATH=/opt/kde4/bin/:$PATH
>> > manish at beleniXRemiX:~$ env | grep LD
>> >
>> > LD_LIBRARY_PATH=/lib:/usr/lib:/usr/sfw/lib:/usr/X11R6/lib:/usr/openwin/lib
>> > manish at beleniXRemiX:~$ export LD_LIBRARY_PATH=/opt/kde4/lib/:$PATH
>> > manish at beleniXRemiX:~$ env | grep PKG
>> >
>> > PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig
>> > manish at beleniXRemiX:~$ export
>> > PKG_CONFIG_PATH=/opt/kde4/lib/:$PKG_CONFIG_PATH
>> > ============================
>> >
>> > I am doing a "--prefix=/opt/kde4" for all the "./configure"'s
>> >
>> > CLucene and DBus built without a hitch
>> > When I tried compling dbus-glib I get the following error:
>> >
>> > ====ERROR BULID TRACE======
>> > make[1]: Entering directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74'
>> > Making all in dbus
>> > make[2]: Entering directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
>> > make  all-recursive
>> > make[3]: Entering directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
>> > Making all in .
>> > make[4]: Entering directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
>> > /bin/bash ../libtool --tag=CC   --mode=link /usr/sfw/bin/gcc  -g -O2
>> > -Wall
>> > -Wcha
>> > r-subscripts -Wmissing-declarations -Wmissing-prototypes
>> > -Wnested-externs
>> > -Wpoin
>> > ter-arith -Wcast-align -Wfloat-equal -Wsign-compare   -o
>> > dbus-binding-tool
>> > dbus-
>> > binding-tool-glib.o dbus-glib-tool.o libdbus-gtool.la libdbus-glib-1.la
>> > -ldbus-1
>> >    -R/usr/gnu/lib -L/usr/gnu/lib -lgobject-2.0 -lglib-2.0 -liconv
>> > -lexpat
>> > -lns
>> > l -lsocket
>> > /usr/sfw/bin/gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations
>> > -Wmissing
>> > -prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
>> > -Wsign-c
>> > ompare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o
>> > dbus-glib-tool.o
>> > ./.
>> > libs/libdbus-gtool.a ./.libs/libdbus-glib-1.so -L/usr/gnu/lib -ldbus-1
>> > -lgobject
>> > -2.0 -lglib-2.0 -liconv -lexpat -lnsl -lsocket -R/opt/kde4/lib
>> > -R/usr/gnu/lib
>> > Undefined                       first referenced
>> >  symbol                             in file
>> > libintl_bind_textdomain_codeset     dbus-glib-tool.o  (symbol belongs to
>> > implicit dependency /usr/gnu/lib/libintl.so.8)
>> > libintl_gettext                     dbus-binding-tool-glib.o  (symbol
>> > belongs to implicit dependency /usr/gnu/lib/libintl.so.8)
>> > libintl_textdomain                  dbus-glib-tool.o  (symbol belongs to
>> > implicit dependency /usr/gnu/lib/libintl.so.8)
>> > libintl_bindtextdomain              dbus-glib-tool.o  (symbol belongs to
>> > implicit dependency /usr/gnu/lib/libintl.so.8)
>> > libintl_dgettext                    dbus-glib-tool.o  (symbol belongs to
>> > implicit dependency /usr/gnu/lib/libintl.so.8)
>> > ld: fatal: Symbol referencing errors. No output written to
>> > .libs/dbus-binding-to
>> > ol
>> > collect2: ld returned 1 exit status
>> > make[4]: *** [dbus-binding-tool] Error 1
>> > make[4]: Leaving directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
>> > make[3]: *** [all-recursive] Error 1
>> > make[3]: Leaving directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
>> > make[2]: *** [all] Error 2
>> > make[2]: Leaving directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74/dbus'
>> > make[1]: *** [all-recursive] Error 1
>> > make[1]: Leaving directory
>> > `/export/home/manish/kde.build/dbus-glib-0.74'
>> > make: *** [all] Error 2
>> >
>> > =================
>> >
>> > These are the list of dbus packages already on my system:
>> > ===========DBUS PKG LIST=============
>> > GNOME2      SFEdbus-qt3                    Qt3 binding for DBUS
>> > GNOME2      SFEdbus-qt3-devel              Qt3 binding for DBUS -
>> > development files
>> > SFE         SFEnicdrv-tcfe                 Nic driver for 3Com
>> > cardbus/PCI
>> > fast ethernet cards
>> > GNOME2      SUNWdbus                       Simple IPC library based on
>> > messages
>> > GNOME2      SUNWdbus-bindings              Simple IPC library based on
>> > messages
>> > GNOME2      SUNWdbus-bindings-devel        Simple IPC library based on
>> > messages - development files
>> > GNOME2      SUNWdbus-devel                 Simple IPC library based on
>> > messages - development files
>> > GNOME2      SUNWdbus-root                  Simple IPC library based on
>> > messages - / filesystem
>> > ====================================
>> >
>> > In addition to the above, I have a pristine dbus living in /opt/kde4
>> >
>> >
>> > I guess I am doing something wrong with the linker here. Can anyone help
>> > me
>> > out?
>> >
>> > --
>> > Manish Chakravarty
>> > http://manish-chaks.livejournal.com/
>> >
>> > _______________________________________________
>> > belenix-dev mailing list
>> > belenix-dev at opensolaris.org
>> > http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>> >
>> >
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>


From maybird1776 at yahoo.com  Tue May 20 05:25:14 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Tue, 20 May 2008 05:25:14 -0700 (PDT)
Subject: [belenix-dev] Update to HPLIP 2.8.5
Message-ID: <241201.22390.qm@web34202.mail.mud.yahoo.com>

HPLIP is an HP developed solution for printing,
scanning, and faxing with HP inkjet and laser based
printers in Linux.

The HPLIP project provides printing support for 1,330
printer models, including Deskjet, Officejet,
Photosmart, PSC (Print Scan Copy), Business Inkjet,
LaserJet, Edgeline MFP, and LaserJet MFP

HPLIP 2.8.5 should replace HPIJS 1.6 for Belenix
0.8... ;o)

I was compiling HPLIP 2.8.5 for Belenix 0.7 so thought
it would be something of interest.

~ Ken Mays


      


From manishchaks at gmail.com  Tue May 20 05:34:08 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Tue, 20 May 2008 18:04:08 +0530
Subject: [belenix-dev] Update to HPLIP 2.8.5
In-Reply-To: <241201.22390.qm@web34202.mail.mud.yahoo.com>
References: <241201.22390.qm@web34202.mail.mud.yahoo.com>
Message-ID: <b4dbee910805200534w328f92d4y8ef4e0592a020b67@mail.gmail.com>

I know linux users rely a lot on HPLIP; It would be nice to have HPLIP on
BeleniX

+1

On Tue, May 20, 2008 at 5:55 PM, ken mays <maybird1776 at yahoo.com> wrote:

> HPLIP is an HP developed solution for printing,
> scanning, and faxing with HP inkjet and laser based
> printers in Linux.
>
> The HPLIP project provides printing support for 1,330
> printer models, including Deskjet, Officejet,
> Photosmart, PSC (Print Scan Copy), Business Inkjet,
> LaserJet, Edgeline MFP, and LaserJet MFP
>
> HPLIP 2.8.5 should replace HPIJS 1.6 for Belenix
> 0.8... ;o)
>
> I was compiling HPLIP 2.8.5 for Belenix 0.7 so thought
> it would be something of interest.
>
> ~ Ken Mays
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080520/72768e24/attachment.html>

From moinakg at gmail.com  Tue May 20 05:41:53 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Tue, 20 May 2008 18:11:53 +0530
Subject: [belenix-dev] Update to HPLIP 2.8.5
In-Reply-To: <b4dbee910805200534w328f92d4y8ef4e0592a020b67@mail.gmail.com>
References: <241201.22390.qm@web34202.mail.mud.yahoo.com>
	<b4dbee910805200534w328f92d4y8ef4e0592a020b67@mail.gmail.com>
Message-ID: <46fe20470805200541y662b882ax9c669204ce5f9643@mail.gmail.com>

n Tue, May 20, 2008 at 6:04 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> I know linux users rely a lot on HPLIP; It would be nice to have HPLIP on
> BeleniX
>
> +1

   Yes +1 from me too. it can actually go into 0.7.1.

Regards,
Moinak.

>
> On Tue, May 20, 2008 at 5:55 PM, ken mays <maybird1776 at yahoo.com> wrote:
>>
>> HPLIP is an HP developed solution for printing,
>> scanning, and faxing with HP inkjet and laser based
>> printers in Linux.
>>
>> The HPLIP project provides printing support for 1,330
>> printer models, including Deskjet, Officejet,
>> Photosmart, PSC (Print Scan Copy), Business Inkjet,
>> LaserJet, Edgeline MFP, and LaserJet MFP
>>
>> HPLIP 2.8.5 should replace HPIJS 1.6 for Belenix
>> 0.8... ;o)
>>
>> I was compiling HPLIP 2.8.5 for Belenix 0.7 so thought
>> it would be something of interest.
>>
>> ~ Ken Mays
>>
>>
>>
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From maybird1776 at yahoo.com  Tue May 20 10:36:50 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Tue, 20 May 2008 10:36:50 -0700 (PDT)
Subject: [belenix-dev] Moving to ON b92 & KDE 4.0.
In-Reply-To: <b4dbee910805192157sff5ec77yeba51a9f4217ecd8@mail.gmail.com>
Message-ID: <745557.5441.qm@web34201.mail.mud.yahoo.com>

Ok,

I was able to review these proposed packages for the
KDE project using Belenix 0.7:

1. amarok 1.4.9.1
2. xine-lib 1.1.12 
3. Compiz 0.7.4
4. Kaffeine 0.8.6
5. Mesa 7.0.3
6. Nvidia 169.12 driver

Three packages focus more on the visualization area
while the other focus was on multimedia (video/audio)
concerns.

I had ported Kaffeine 0.8.6 for Blastwave's CSWkdegcc
build and thought it was good to use with amarok as
the current audio player.

The graphic visualization updates polishes off the the
libs needed for porting 3D OpenGL apps. My recent apps
of FlightGEar, 'Dangers of the Deep' and 'Frozen
Bubble (2D) were used to review the apps with Compiz
effects.

More later!! ;o)

~ Ken
 



      


From shivakumar.gn at gmail.com  Wed May 21 09:19:56 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Wed, 21 May 2008 21:49:56 +0530
Subject: [belenix-dev] IPS on BeleniX 0.7
Message-ID: <319ee2b10805210919r56ba92bex57cd0b8f74dcb429@mail.gmail.com>

For those interested in experimenting, getting IPS to work on BeleniX
is pretty simple:
http://opensoars.blogspot.com/2008/05/ips-on-belenix-07.html

-Shiv


From anil.verve at gmail.com  Wed May 21 09:27:12 2008
From: anil.verve at gmail.com (Anil Gulecha)
Date: Wed, 21 May 2008 21:57:12 +0530
Subject: [belenix-dev] IPS on BeleniX 0.7
In-Reply-To: <319ee2b10805210919r56ba92bex57cd0b8f74dcb429@mail.gmail.com>
References: <319ee2b10805210919r56ba92bex57cd0b8f74dcb429@mail.gmail.com>
Message-ID: <148d59250805210927o77e169ebl21e6aa333ea29158@mail.gmail.com>

On 5/21/08, S h i v <shivakumar.gn at gmail.com> wrote:
> For those interested in experimenting, getting IPS to work on BeleniX
>  is pretty simple:
>  http://opensoars.blogspot.com/2008/05/ips-on-belenix-07.html
>

We plan on moving to IPS by 0.8. But if we already have the package
for IPS, we can add it (and packagemanager) to 0.7.1 as experimental,
and it'll help to test this by 0.8.

Thoughts?

~Anil


From shivakumar.gn at gmail.com  Wed May 21 17:06:39 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 22 May 2008 05:36:39 +0530
Subject: [belenix-dev] IPS on BeleniX 0.7
In-Reply-To: <148d59250805210927o77e169ebl21e6aa333ea29158@mail.gmail.com>
References: <319ee2b10805210919r56ba92bex57cd0b8f74dcb429@mail.gmail.com>
	<148d59250805210927o77e169ebl21e6aa333ea29158@mail.gmail.com>
Message-ID: <319ee2b10805211706y713f32cer5f9fb84d1f7f501c@mail.gmail.com>

On Wed, May 21, 2008 at 9:57 PM, Anil Gulecha <anil.verve at gmail.com> wrote:
> On 5/21/08, S h i v <shivakumar.gn at gmail.com> wrote:
>> For those interested in experimenting, getting IPS to work on BeleniX
>>  is pretty simple:
>>  http://opensoars.blogspot.com/2008/05/ips-on-belenix-07.html
>>
>
> We plan on moving to IPS by 0.8. But if we already have the package
> for IPS, we can add it (and packagemanager) to 0.7.1 as experimental,
> and it'll help to test this by 0.8.
>
> Thoughts?
>

Good idea. Infact, in every release, we can possibly follow the idea
of adding upcoming features as "*experimental*". For people interested
in contributing this would be an opportunity to submit their work or
to work on an existing experimental project. Anand's userland
bluetooth stack implementation is one such I can think of.
This is being doing all along, we need make it clear & explicit with a
separate section in the release notes and a simple mechanism for
people to submit experimental work.

The IPS package is 1.3M in size uncompressed, 235K on 7z compression
(this includes py & pyc files). With only py files it is 148K.

The package can be added without actually providing a repo for people
to experiment with OR
Can be hosted on the genunix server like the software clusters that
can be installed via get-pkgs. It will be under the devel or misc
cluster.

-Shiv


From manishchaks at gmail.com  Thu May 22 02:04:29 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Thu, 22 May 2008 14:34:29 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
	<b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
	<46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>
Message-ID: <4A073665-DA97-4682-8AA6-28A473A1A45B@gmail.com>


On 20-May-08, at 1:06 PM, Moinak Ghosh wrote:

> On Tue, May 20, 2008 at 10:30 AM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>>
>>
>> On Sun, May 18, 2008 at 9:47 PM, Moinak Ghosh <moinakg at gmail.com>  
>> wrote:
>>>
>>> Hi Manish,
>>>
>>>  You are better off trying to use the BeleniX spec file system  
>>> from the
>>> beginning. Lots of env settings headaches will be automatically  
>>> taken
>>> care of.
How do I use the belenix spec file system?

[...snip...]


From shivakumar.gn at gmail.com  Thu May 22 02:42:19 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 22 May 2008 15:12:19 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <4A073665-DA97-4682-8AA6-28A473A1A45B@gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
	<b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
	<46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>
	<4A073665-DA97-4682-8AA6-28A473A1A45B@gmail.com>
Message-ID: <319ee2b10805220242p4b61d517y2337e91f39e0b237@mail.gmail.com>

On Thu, May 22, 2008 at 2:34 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>
> On 20-May-08, at 1:06 PM, Moinak Ghosh wrote:
>
>> On Tue, May 20, 2008 at 10:30 AM, Manish Chakravarty
>> <manishchaks at gmail.com> wrote:
>>>
>>>
>>> On Sun, May 18, 2008 at 9:47 PM, Moinak Ghosh <moinakg at gmail.com>
>>> wrote:
>>>>
>>>> Hi Manish,
>>>>
>>>>  You are better off trying to use the BeleniX spec file system
>>>> from the
>>>> beginning. Lots of env settings headaches will be automatically
>>>> taken
>>>> care of.
> How do I use the belenix spec file system?
>

See the last few lines at
http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
Reproduced below:

On BeleniX as root (this step is applicable only for 0.7)
$ get-pkgs devel

To have a pkgbuild environment for building the spec files
    * Install the devel cluster using get-pkgs
    * Download and install Sun Studio 11
    * Download JDS CBE and Install CBEpkgbuild(along with the
mandatory dependencies) using the cbe-install script
    * Modify your user .bashrc to source /opt/jdsbld/bin/envsh

Now you are ready to build your way into the hundreds of softwares
available via the various spec files repositories.

-Shiv


From manishchaks at gmail.com  Thu May 22 03:03:43 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Thu, 22 May 2008 15:33:43 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <319ee2b10805220242p4b61d517y2337e91f39e0b237@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
	<b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
	<46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>
	<4A073665-DA97-4682-8AA6-28A473A1A45B@gmail.com>
	<319ee2b10805220242p4b61d517y2337e91f39e0b237@mail.gmail.com>
Message-ID: <8546D411-4C60-488E-A61C-9112535B5F93@gmail.com>


> [...snip...]
> See the last few lines at
> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
> Reproduced below:
>
> On BeleniX as root (this step is applicable only for 0.7)
> $ get-pkgs devel
>
> To have a pkgbuild environment for building the spec files
>    * Install the devel cluster using get-pkgs
>    * Download and install Sun Studio 11
>    * Download JDS CBE and Install CBEpkgbuild(along with the
> mandatory dependencies) using the cbe-install script
>    * Modify your user .bashrc to source /opt/jdsbld/bin/envsh
>
> Now you are ready to build your way into the hundreds of softwares
> available via the various spec files repositories.
Oh the good old CBE!
This should not be a problem

Thanks a lot!
Manish


From shivakumar.gn at gmail.com  Sat May 24 07:53:32 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sat, 24 May 2008 20:23:32 +0530
Subject: [belenix-dev] Fwd: Distributing Wink
In-Reply-To: <cc0dc6a10805240650uff82117o96ea9325e175278f@mail.gmail.com>
References: <319ee2b10805232329u16e02d11sa9881a3ea2868760@mail.gmail.com>
	<cc0dc6a10805240650uff82117o96ea9325e175278f@mail.gmail.com>
Message-ID: <319ee2b10805240753h52389d96g9803e0a9c1fb36f6@mail.gmail.com>

Hello All,

Thanks to Satish, the developer of Wink (software to create flash
based tutorial/presentation), this software can now be redistributed
for BeleniX.
This is to be used on top of wine.

best regards
Shiv


---------- Forwarded message ----------
From: Satish Kumar S <satish at debugmode.com>
Date: Sat, May 24, 2008 at 7:20 PM
Subject: Re: Distributing Wink
To: S h i v <shivakumar.gn at gmail.com>

Sounds good, please go ahead :)


On Fri, May 23, 2008 at 11:29 PM, S h i v <shivakumar.gn at gmail.com> wrote:
> Hello Satish,
>
> I am one of the developers of BeleniX [1], an opensolaris based
> community distribution.
> I have used wink and found it to be an extremely useful software. I
> would like to request you to provide us permission to redistribute the
> software.
>
> best regards
> Shiv
> [1] http://www.belenix.org
> [2] http://opensoars.blogspot.com
>

--
Cheers
Satish


From moinakg at gmail.com  Sat May 24 08:05:11 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sat, 24 May 2008 20:35:11 +0530
Subject: [belenix-dev] Fwd: Distributing Wink
In-Reply-To: <319ee2b10805240753h52389d96g9803e0a9c1fb36f6@mail.gmail.com>
References: <319ee2b10805232329u16e02d11sa9881a3ea2868760@mail.gmail.com>
	<cc0dc6a10805240650uff82117o96ea9325e175278f@mail.gmail.com>
	<319ee2b10805240753h52389d96g9803e0a9c1fb36f6@mail.gmail.com>
Message-ID: <46fe20470805240805k483bd41fmc0c6d0a18643cf57@mail.gmail.com>

On Sat, May 24, 2008 at 8:23 PM, S h i v <shivakumar.gn at gmail.com> wrote:
> Hello All,
>
> Thanks to Satish, the developer of Wink (software to create flash
> based tutorial/presentation), this software can now be redistributed
> for BeleniX.
> This is to be used on top of wine.

   Great. BTW how big is the package ?

Regards,
Moinak.

>
> best regards
> Shiv
>
>
> ---------- Forwarded message ----------
> From: Satish Kumar S <satish at debugmode.com>
> Date: Sat, May 24, 2008 at 7:20 PM
> Subject: Re: Distributing Wink
> To: S h i v <shivakumar.gn at gmail.com>
>
> Sounds good, please go ahead :)
>
>
> On Fri, May 23, 2008 at 11:29 PM, S h i v <shivakumar.gn at gmail.com> wrote:
>> Hello Satish,
>>
>> I am one of the developers of BeleniX [1], an opensolaris based
>> community distribution.
>> I have used wink and found it to be an extremely useful software. I
>> would like to request you to provide us permission to redistribute the
>> software.
>>
>> best regards
>> Shiv
>> [1] http://www.belenix.org
>> [2] http://opensoars.blogspot.com
>>
>
> --
> Cheers
> Satish
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Sat May 24 10:25:20 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sat, 24 May 2008 22:55:20 +0530
Subject: [belenix-dev] Fwd: [indiana-discuss] How to update Opensolaris
	2008.05 to build 90
In-Reply-To: <12994047.1211649017634.JavaMail.Twebapp@oss-app1>
References: <12994047.1211649017634.JavaMail.Twebapp@oss-app1>
Message-ID: <46fe20470805241025l79b1b501u89fba978016c2191@mail.gmail.com>

Hi Folks,

   I seem to see an idea here. The BeleniX pkg repo (once it is setup)
should be updated to newer builds as and when they are available.
Experimental project packages should also be readily made available.

Regards,
Moinak.

---------- Forwarded message ----------
From: Dirk Steinberg <dws at steinbergnet.net>
Date: Sat, May 24, 2008 at 10:39 PM
Subject: [indiana-discuss] How to update Opensolaris 2008.05 to build 90
To: indiana-discuss at opensolaris.org


Hi,

i'd like to follow Opensolaris development closely for updates
to ZFS, iSCSI, COMSTAR, etc.

Previsously I did that based on SXCR, BFU'ing once in a while
to biweekly onnv builds or even to weekly snapshots.

Well, BFU is a terrible way to do package upgrades, and
"Indiana" was described as the new fast-moving Opensolaris
distribution, and "pkg" looked much better than BFU.
So I went ahead and installed Opensolaris 2008.05.

But now I am stuck at build 86 and struggeling to see how
to update to newer builds, presently that would be onnv_90.

What authority do I have to point pkg to, or where do I find
all the osol builds in pkg-digestable format?

If binary packages do not exist, how can I build them myself?

And what about the other projects, like ZFS crypto and such?
All of them seem to just offer BFU bundles, not pkg authorities.

Is it possible to BFU an Opensolaris 2008.05 base? (Besides the point that
this would of course screw up all the pkg versioning...)

What about the other way around: Is it possible to install additional
pkg packages on top of a SXCR base?

Still a little confused... :-)

Thanks for any helpful pointers.

Cheers,
Dirk
--

This message posted from opensolaris.org

_______________________________________________
indiana-discuss mailing list
indiana-discuss at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss


From ananth.shrinivas at gmail.com  Sat May 24 10:59:31 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Sat, 24 May 2008 23:29:31 +0530
Subject: [belenix-dev] Fwd: [indiana-discuss] How to update Opensolaris
	2008.05 to build 90
In-Reply-To: <46fe20470805241025l79b1b501u89fba978016c2191@mail.gmail.com>
References: <12994047.1211649017634.JavaMail.Twebapp@oss-app1>
	<46fe20470805241025l79b1b501u89fba978016c2191@mail.gmail.com>
Message-ID: <f5ff03920805241059s809fc86v887eb6de415f38d8@mail.gmail.com>

Updating the core ON packages periodically and hosting them on our
repository is a good idea. But I see some unknowns that need to be resolved:

Say we release 0.7.1 with build 89. When ON moves to 90, we publish a new
set of packages that includes the kernel, libc and potentially *all* new ON
packages. Now I am a BeleniX user who wants to update my say,
python-xmlparser package and assume that it depends on SUNWlxml. And
SUNWlxml in turn depends on SUNWcsl which might depend on SUNWckr etc.. and
so on. I *could* potentially end up moving quite a bit of my system binaries
including the kernel to build 90.

The question is do we want this to happen ? There might be people who want
to stay at some stable kernel level and there might be others who don't want
to pull so much of data to just update some userland package. Note that this
would even happen when you do a new installation of some package.

>From the IPS point of view, this happens because publishing a new version of
a package creates a hierarchy and dependencies are always satisfied by
installing the latest version of packages.

To draw a parallel with linux, the kernel and glibc get updated only every 6
months or so. In our case, it could be every 15 days.

I am not against the idea of publishing newer ON builds. In fact, I think
that and hosting repositories of bleeding edge stuff on opensolaris.org -
like say the Crossbow bits or the In-Kernel ext3 implementation [1] would be
an awesome idea. But we would need to work out policies - maybe multiple
repositories or maybe pkg naming conventions - to make sure the regular joe
user doesn't see much impact.

[1] - http://www.opensolaris.org/os/project/ext3

Ananth

On Sat, May 24, 2008 at 10:55 PM, Moinak Ghosh <moinakg at gmail.com> wrote:

> Hi Folks,
>
>   I seem to see an idea here. The BeleniX pkg repo (once it is setup)
> should be updated to newer builds as and when they are available.
> Experimental project packages should also be readily made available.
>
> Regards,
> Moinak.
>
> ---------- Forwarded message ----------
> From: Dirk Steinberg <dws at steinbergnet.net>
> Date: Sat, May 24, 2008 at 10:39 PM
> Subject: [indiana-discuss] How to update Opensolaris 2008.05 to build 90
> To: indiana-discuss at opensolaris.org
>
>
> Hi,
>
> i'd like to follow Opensolaris development closely for updates
> to ZFS, iSCSI, COMSTAR, etc.
>
> Previsously I did that based on SXCR, BFU'ing once in a while
> to biweekly onnv builds or even to weekly snapshots.
>
> Well, BFU is a terrible way to do package upgrades, and
> "Indiana" was described as the new fast-moving Opensolaris
> distribution, and "pkg" looked much better than BFU.
> So I went ahead and installed Opensolaris 2008.05.
>
> But now I am stuck at build 86 and struggeling to see how
> to update to newer builds, presently that would be onnv_90.
>
> What authority do I have to point pkg to, or where do I find
> all the osol builds in pkg-digestable format?
>
> If binary packages do not exist, how can I build them myself?
>
> And what about the other projects, like ZFS crypto and such?
> All of them seem to just offer BFU bundles, not pkg authorities.
>
> Is it possible to BFU an Opensolaris 2008.05 base? (Besides the point that
> this would of course screw up all the pkg versioning...)
>
> What about the other way around: Is it possible to install additional
> pkg packages on top of a SXCR base?
>
> Still a little confused... :-)
>
> Thanks for any helpful pointers.
>
> Cheers,
> Dirk
> --
>
> This message posted from opensolaris.org
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080524/847203b8/attachment.html>

From shivakumar.gn at gmail.com  Sat May 24 19:07:13 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sun, 25 May 2008 07:37:13 +0530
Subject: [belenix-dev] Fwd: Distributing Wink
In-Reply-To: <46fe20470805240805k483bd41fmc0c6d0a18643cf57@mail.gmail.com>
References: <319ee2b10805232329u16e02d11sa9881a3ea2868760@mail.gmail.com>
	<cc0dc6a10805240650uff82117o96ea9325e175278f@mail.gmail.com>
	<319ee2b10805240753h52389d96g9803e0a9c1fb36f6@mail.gmail.com>
	<46fe20470805240805k483bd41fmc0c6d0a18643cf57@mail.gmail.com>
Message-ID: <319ee2b10805241907l4f74501fq9180767daf993fcb@mail.gmail.com>

On Sat, May 24, 2008 at 8:35 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
> On Sat, May 24, 2008 at 8:23 PM, S h i v <shivakumar.gn at gmail.com> wrote:
>> Hello All,
>>
>> Thanks to Satish, the developer of Wink (software to create flash
>> based tutorial/presentation), this software can now be redistributed
>> for BeleniX.
>> This is to be used on top of wine.
>
>   Great. BTW how big is the package ?
>

Please do not mark Satish in cc. He doesn't wish to receive mails from
this list/thread. Initial mail was so that the permission mail was on
the list with a cc.

The software would be 8.9M after installation. The software requires
wine, the resulting interdependencies can be considerable (~100M) in
size.
wine  73M
libaudioio  0.5M
fontforge   13M
(additional dependencies of wine such as lcms, cups, ncurses,
freetype, dbus, gnome-camera, are installed by default in BeleniX).

A spec file to wrapper it around wine is yet to be done.

-Shiv


From manishchaks at gmail.com  Tue May 27 04:30:38 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Tue, 27 May 2008 17:00:38 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <319ee2b10805220242p4b61d517y2337e91f39e0b237@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
	<b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
	<46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>
	<4A073665-DA97-4682-8AA6-28A473A1A45B@gmail.com>
	<319ee2b10805220242p4b61d517y2337e91f39e0b237@mail.gmail.com>
Message-ID: <b4dbee910805270430t21cd924cnf9815a5f77d2d32b@mail.gmail.com>

On Thu, May 22, 2008 at 3:12 PM, S h i v <shivakumar.gn at gmail.com> wrote:
> On Thu, May 22, 2008 at 2:34 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>>
>> On 20-May-08, at 1:06 PM, Moinak Ghosh wrote:
>>
>>> On Tue, May 20, 2008 at 10:30 AM, Manish Chakravarty
>>> <manishchaks at gmail.com> wrote:
>>>>
>>>>
>>>> On Sun, May 18, 2008 at 9:47 PM, Moinak Ghosh <moinakg at gmail.com>
>>>> wrote:
>>>>>
>>>>> Hi Manish,
>>>>>
>>>>>  You are better off trying to use the BeleniX spec file system
>>>>> from the
>>>>> beginning. Lots of env settings headaches will be automatically
>>>>> taken
>>>>> care of.
>> How do I use the belenix spec file system?
>>
>
> See the last few lines at
> http://opensoars.blogspot.com/2008/04/additional-softwarespackages-for.html
> Reproduced below:
>
> On BeleniX as root (this step is applicable only for 0.7)
> $ get-pkgs devel
>
> To have a pkgbuild environment for building the spec files
>    * Install the devel cluster using get-pkgs
>    * Download and install Sun Studio 11
How do I make CBE use gcc instead of Sun Studio ?
would and export CC=/usr/sfw/bin/gcc; export CXX=/usr/sfw/bin/g++ work?
For KDE4 , I am using gcc for building everything.

>    * Download JDS CBE and Install CBEpkgbuild(along with the
> mandatory dependencies) using the cbe-install script
>    * Modify your user .bashrc to source /opt/jdsbld/bin/envsh
>
> Now you are ready to build your way into the hundreds of softwares
> available via the various spec files repositories.
>
> -Shiv
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From ananth.shrinivas at gmail.com  Tue May 27 06:08:48 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Tue, 27 May 2008 18:38:48 +0530
Subject: [belenix-dev] Linker errors while compiling dbus-glib on
	BeleniX 0.7 ( for KDE4)
In-Reply-To: <b4dbee910805270430t21cd924cnf9815a5f77d2d32b@mail.gmail.com>
References: <b4dbee910805180504r8ee0647hfde2409f9d4dac28@mail.gmail.com>
	<46fe20470805180917m7564fea0xbaa1b7d8e3f2ba0d@mail.gmail.com>
	<b4dbee910805192200j56a224aem36e92c8c9fc322f9@mail.gmail.com>
	<46fe20470805200036o156c6863ybb2968570d990448@mail.gmail.com>
	<4A073665-DA97-4682-8AA6-28A473A1A45B@gmail.com>
	<319ee2b10805220242p4b61d517y2337e91f39e0b237@mail.gmail.com>
	<b4dbee910805270430t21cd924cnf9815a5f77d2d32b@mail.gmail.com>
Message-ID: <f5ff03920805270608uf6d4195lca79cb842ab99ea0@mail.gmail.com>

>
>
> > To have a pkgbuild environment for building the spec files
> >    * Install the devel cluster using get-pkgs
> >    * Download and install Sun Studio 11
> How do I make CBE use gcc instead of Sun Studio ?
> would and export CC=/usr/sfw/bin/gcc; export CXX=/usr/sfw/bin/g++ work?
> For KDE4 , I am using gcc for building everything.
>


Yes, exporting CC and CXX will work.

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080527/bb9b6c2c/attachment.html>

From victoredwardocallaghan at gmail.com  Wed May 28 00:35:15 2008
From: victoredwardocallaghan at gmail.com (Edward O'Callaghan)
Date: Wed, 28 May 2008 17:35:15 +1000
Subject: [belenix-dev] Just a offer to help with 0.8
Message-ID: <cbc95d950805280035v4e4beccdm784c3e744a676201@mail.gmail.com>

Hi,
I would just like to offer to help with the 0.8 release in the following
areas:

*Fluxbox integration.
*Media Codec buddy and media framework.
*Small bug fixes. (I have limited times these days from collage .. :p )
*Testing

Thanks,
Edward.

-- 
All Documents adhered to the ISO/IEC 26300  standard file format for
electronic office documents, such as spreadsheets, charts, presentations and
word processing documents from this email address. The author does not take
responsibility of the recipients inability to read international standards
and who use proprietary products such as MS Office.
See: http://www.openoffice.org/
Edward O'Callaghan.
--
http://fedoraproject.org/wiki/EdwardOcallaghan
http://moonshine.opn4.org/
http://www.pcbsd.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080528/62ee681f/attachment.html>

From victoredwardocallaghan at gmail.com  Wed May 28 00:37:40 2008
From: victoredwardocallaghan at gmail.com (Edward O'Callaghan)
Date: Wed, 28 May 2008 17:37:40 +1000
Subject: [belenix-dev] Just a offer to help with 0.8
In-Reply-To: <cbc95d950805280035v4e4beccdm784c3e744a676201@mail.gmail.com>
References: <cbc95d950805280035v4e4beccdm784c3e744a676201@mail.gmail.com>
Message-ID: <cbc95d950805280037k1e88af3w6db2ebad2c78e97a@mail.gmail.com>

>
> Hi,
> I would just like to offer to help with the 0.8 release in the following
> areas:
>
> *Fluxbox integration.
> *Media Codec buddy and media framework.
> *Small bug fixes. (I have limited times these days from collage .. :p )
> *Testing
>
> Thanks,
> Edward.
>
> --
> All Documents adhered to the ISO/IEC 26300  standard file format for
> electronic office documents, such as spreadsheets, charts, presentations and
> word processing documents from this email address. The author does not take
> responsibility of the recipients inability to read international standards
> and who use proprietary products such as MS Office.
> See: http://www.openoffice.org/
> Edward O'Callaghan.
> --
> http://fedoraproject.org/wiki/EdwardOcallaghan
> http://moonshine.opn4.org/
> http://www.pcbsd.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080528/f196909e/attachment.html>

From manishchaks at gmail.com  Wed May 28 02:46:45 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 15:16:45 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
Message-ID: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>

I have setup my env the following way:

export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
export CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
export CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
alias cmakekde="cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/kde4"
export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv"
export CC=/usr/sfw/bin/gcc
export CXX=/usr/sfw/bin/g++


I started building Qt4 like this:
./configure -qt-gif -fast -no-exceptions -no-separate-debug-info
-system-libpng -system-libjpeg -system-zlib -dbus -webkit -no-phonon
-nomake examples -nomake demos -prefix /opt/qt4

I get the following error while building q4:

manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure -qt-gif -fast
-no-exceptions -no-separate-debug-info -system-libpng -system-libjpeg
-system-zlib -dbus -webkit -no-phonon -nomake examples -nomake demos
-prefix /opt/qt4

This is the Qt/X11 Open Source Edition.

You are licensed to use this software under the terms of either
the Q Public License (QPL) or the GNU General Public License (GPL)
versions 2 or 3

Type 'Q' to view the Q Public License.
Type '2' to view the GNU General Public License version 2.
Type '3' to view the GNU General Public License version 3.
Type 'yes' to accept this license offer.
Type 'no' to decline this license offer.

Do you accept the terms of either license? yes

Creating qmake. Please wait...
gmake: Nothing to be done for `first'.
The QtDBus module cannot be enabled because libdbus-1 version 0.62 was
not found.
 Turn on verbose messaging (-v) to ./configure to see the final report.
  If you believe this message is in error you may use the continue
   switch (-continue) to ./configure to continue.
   manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure -qt-gif -fast
-no-exceptions -no-separate-debug-info -system-libpng -system-libjpeg
-system-zlib -dbus -webkit -no-phonon -nomake examples -nomake demos
-prefix /opt/qt4 -v

   This is the Qt/X11 Open Source Edition.

   Determining system architecture... (SunOS:5.11:i86pc)
       32-bit Intel 80x86 (i386)
           'i386' is supported
           System architecture: 'i386'
           Precompiled-headers support disabled.
           Symbol visibility control disabled.
           You are licensed to use this software under the terms of either
           the Q Public License (QPL) or the GNU General Public License (GPL)
           versions 2 or 3

           Type 'Q' to view the Q Public License.
           Type '2' to view the GNU General Public License version 2.
           Type '3' to view the GNU General Public License version 3.
           Type 'yes' to accept this license offer.
           Type 'no' to decline this license offer.

           Do you accept the terms of either license? yes

           Creating qmake. Please wait...
           gmake: Nothing to be done for `first'.
           floatmath auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o floatmath.o floatmath.cpp
           make: CC: Command not found
           make: *** [floatmath.o] Error 127
           floatmath disabled.
           mmx auto-detection... ()
           CC -c -mmmx -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o mmx.o mmx.cpp
           make: CC: Command not found
           make: *** [mmx.o] Error 127
           mmx disabled.
           3dnow auto-detection... ()
           CC -c -m3dnow -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o 3dnow.o 3dnow.cpp
           make: CC: Command not found
           make: *** [3dnow.o] Error 127
           3dnow disabled.
           sse auto-detection... ()
           CC -c -msse -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o sse.o sse.cpp
           make: CC: Command not found
           make: *** [sse.o] Error 127
           sse disabled.
           sse2 auto-detection... ()
           CC -c -msse2 -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o sse2.o sse2.cpp
           make: CC: Command not found
           make: *** [sse2.o] Error 127
           sse2 disabled.
           libtiff auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o libtiff.o libtiff.cpp
           make: CC: Command not found
           make: *** [libtiff.o] Error 127
           libtiff disabled.
           libmng auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o libmng.o libmng.cpp
           make: CC: Command not found
           make: *** [libmng.o] Error 127
           libmng disabled.
           InterBase auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o ibase.o ibase.cpp
           make: CC: Command not found
           make: *** [ibase.o] Error 127
           InterBase disabled.
           MySQL (thread-safe) auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
-I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o mysql.o
../mysql/mysql.cpp
           make: CC: Command not found
           make: *** [mysql.o] Error 127
           MySQL (thread-safe) disabled.
           MySQL (thread-unsafe) auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
-I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o mysql.o mysql.cpp
           make: CC: Command not found
           make: *** [mysql.o] Error 127
           MySQL (thread-unsafe) disabled.
           ODBC auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o odbc.o odbc.cpp
           make: CC: Command not found
           make: *** [odbc.o] Error 127
           ODBC disabled.
           PostgreSQL auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
-I/usr/include/pgsql -I. -I/usr/sfw/include -o psql.o psql.cpp
           make: CC: Command not found
           make: *** [psql.o] Error 127
           PostgreSQL disabled.
           SQLite2 auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o sqlite2.o sqlite2.cpp
           make: CC: Command not found
           make: *** [sqlite2.o] Error 127
           SQLite2 disabled.
           NIS auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o nis.o nis.cpp
           make: CC: Command not found
           make: *** [nis.o] Error 127
           NIS disabled.
           Cups auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o cups.o cups.cpp
           make: CC: Command not found
           make: *** [cups.o] Error 127
           Cups disabled.
           POSIX iconv auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o iconv.o iconv.cpp
           make: CC: Command not found
           make: *** [iconv.o] Error 127
           POSIX iconv disabled.
           GNU libiconv auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
-I/usr/sfw/include -o gnu-libiconv.o gnu-libiconv.cpp
           make: CC: Command not found
           make: *** [gnu-libiconv.o] Error 127
           GNU libiconv disabled.
           D-Bus auto-detection... ()
           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I.
-I/usr/sfw/include -o dbus.o dbus.cpp
           make: CC: Command not found
           make: *** [dbus.o] Error 127
           D-Bus disabled.
           The QtDBus module cannot be enabled because libdbus-1
version 0.62 was not found.
            Turn on verbose messaging (-v) to ./configure to see the
final report.
             If you believe this message is in error you may use the continue
              switch (-continue) to ./configure to continue.




-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From manishchaks at gmail.com  Wed May 28 04:28:52 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 16:58:52 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
References: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
Message-ID: <b4dbee910805280428r759a0e94q6d268d5964974d2@mail.gmail.com>

I installed CBE and sourced the env
After that I adjusted my env in the following manner:
export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
 export CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
 export CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
 export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
alias cmakekde="cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/kde4"
 export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv"
 export CC=/usr/sfw/bin/gcc
 export CXX=/usr/sfw/bin/g++

I get the following error:
cd src/tools/moc/ && gmake -f Makefile
gmake[1]: Entering directory
`/export/home/manish/kde.build/qt-copy/src/tools/moc'
CC -R/opt/qt4/lib -R/opt/qt4/lib -o ../../../bin/moc
release-shared/moc.o release-shared/preprocessor.o
release-shared/generator.o release-shared/parser.o
release-shared/token.o release-shared/main.o release-shared/qglobal.o
release-shared/qmalloc.o release-shared/qnumeric.o
release-shared/qbuffer.o release-shared/qdir.o
release-shared/qdiriterator.o release-shared/qfile.o
release-shared/qfileinfo.o release-shared/qfsfileengine.o
release-shared/qfsfileengine_iterator.o release-shared/qiodevice.o
release-shared/qtemporaryfile.o release-shared/qtextstream.o
release-shared/qurl.o release-shared/qmetatype.o
release-shared/qbytearraymatcher.o release-shared/qdatetime.o
release-shared/qhash.o release-shared/qlistdata.o
release-shared/qlocale.o release-shared/qmap.o
release-shared/qstring.o release-shared/qstringlist.o
release-shared/qvector.o release-shared/qvariant.o
release-shared/qabstractfileengine.o release-shared/qbytearray.o
release-shared/qvsnprintf.o release-shared/qfsfileengine_unix.o
release-shared/qfsfileengine_iterator_unix.o    -L/usr/sfw/lib -ldl
Undefined                       first referenced
 symbol                             in file
operator new[](unsigned)                               release-shared/moc.o
operator new(unsigned)                               release-shared/moc.o
vtable for __cxxabiv1::__si_class_type_info release-shared/qbuffer.o
[Hint: static member vtable for __cxxabiv1::__si_class_type_info must
be defined in the program]

operator delete[](void*)                              release-shared/moc.o
operator delete(void*)                              release-shared/moc.o
_Unwind_Resume                      release-shared/moc.o
vtable for __cxxabiv1::__class_type_info release-shared/qdiriterator.o
[Hint: static member vtable for __cxxabiv1::__class_type_info must be
defined in the program]

__gxx_personality_v0                release-shared/moc.o
__cxa_pure_virtual                  release-shared/qiodevice.o
ld: fatal: Symbol referencing errors. No output written to ../../../bin/moc
gmake[1]: *** [../../../bin/moc] Error 1
gmake[1]: Leaving directory
`/export/home/manish/kde.build/qt-copy/src/tools/moc'
gmake: *** [sub-moc-make_default-ordered] Error 2

This is some kind of linker error.

Can someone help me out with this?

-- Manish



On Wed, May 28, 2008 at 3:16 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> I have setup my env the following way:
>
> export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
> export CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
> export CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
> export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
> alias cmakekde="cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/kde4"
> export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv"
> export CC=/usr/sfw/bin/gcc
> export CXX=/usr/sfw/bin/g++
>
>
> I started building Qt4 like this:
> ./configure -qt-gif -fast -no-exceptions -no-separate-debug-info
> -system-libpng -system-libjpeg -system-zlib -dbus -webkit -no-phonon
> -nomake examples -nomake demos -prefix /opt/qt4
>
> I get the following error while building q4:
>
> manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure -qt-gif -fast
> -no-exceptions -no-separate-debug-info -system-libpng -system-libjpeg
> -system-zlib -dbus -webkit -no-phonon -nomake examples -nomake demos
> -prefix /opt/qt4
>
> This is the Qt/X11 Open Source Edition.
>
> You are licensed to use this software under the terms of either
> the Q Public License (QPL) or the GNU General Public License (GPL)
> versions 2 or 3
>
> Type 'Q' to view the Q Public License.
> Type '2' to view the GNU General Public License version 2.
> Type '3' to view the GNU General Public License version 3.
> Type 'yes' to accept this license offer.
> Type 'no' to decline this license offer.
>
> Do you accept the terms of either license? yes
>
> Creating qmake. Please wait...
> gmake: Nothing to be done for `first'.
> The QtDBus module cannot be enabled because libdbus-1 version 0.62 was
> not found.
>  Turn on verbose messaging (-v) to ./configure to see the final report.
>  If you believe this message is in error you may use the continue
>   switch (-continue) to ./configure to continue.
>   manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure -qt-gif -fast
> -no-exceptions -no-separate-debug-info -system-libpng -system-libjpeg
> -system-zlib -dbus -webkit -no-phonon -nomake examples -nomake demos
> -prefix /opt/qt4 -v
>
>   This is the Qt/X11 Open Source Edition.
>
>   Determining system architecture... (SunOS:5.11:i86pc)
>       32-bit Intel 80x86 (i386)
>           'i386' is supported
>           System architecture: 'i386'
>           Precompiled-headers support disabled.
>           Symbol visibility control disabled.
>           You are licensed to use this software under the terms of either
>           the Q Public License (QPL) or the GNU General Public License (GPL)
>           versions 2 or 3
>
>           Type 'Q' to view the Q Public License.
>           Type '2' to view the GNU General Public License version 2.
>           Type '3' to view the GNU General Public License version 3.
>           Type 'yes' to accept this license offer.
>           Type 'no' to decline this license offer.
>
>           Do you accept the terms of either license? yes
>
>           Creating qmake. Please wait...
>           gmake: Nothing to be done for `first'.
>           floatmath auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o floatmath.o floatmath.cpp
>           make: CC: Command not found
>           make: *** [floatmath.o] Error 127
>           floatmath disabled.
>           mmx auto-detection... ()
>           CC -c -mmmx -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o mmx.o mmx.cpp
>           make: CC: Command not found
>           make: *** [mmx.o] Error 127
>           mmx disabled.
>           3dnow auto-detection... ()
>           CC -c -m3dnow -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o 3dnow.o 3dnow.cpp
>           make: CC: Command not found
>           make: *** [3dnow.o] Error 127
>           3dnow disabled.
>           sse auto-detection... ()
>           CC -c -msse -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o sse.o sse.cpp
>           make: CC: Command not found
>           make: *** [sse.o] Error 127
>           sse disabled.
>           sse2 auto-detection... ()
>           CC -c -msse2 -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o sse2.o sse2.cpp
>           make: CC: Command not found
>           make: *** [sse2.o] Error 127
>           sse2 disabled.
>           libtiff auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o libtiff.o libtiff.cpp
>           make: CC: Command not found
>           make: *** [libtiff.o] Error 127
>           libtiff disabled.
>           libmng auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o libmng.o libmng.cpp
>           make: CC: Command not found
>           make: *** [libmng.o] Error 127
>           libmng disabled.
>           InterBase auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o ibase.o ibase.cpp
>           make: CC: Command not found
>           make: *** [ibase.o] Error 127
>           InterBase disabled.
>           MySQL (thread-safe) auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o mysql.o
> ../mysql/mysql.cpp
>           make: CC: Command not found
>           make: *** [mysql.o] Error 127
>           MySQL (thread-safe) disabled.
>           MySQL (thread-unsafe) auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o mysql.o mysql.cpp
>           make: CC: Command not found
>           make: *** [mysql.o] Error 127
>           MySQL (thread-unsafe) disabled.
>           ODBC auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o odbc.o odbc.cpp
>           make: CC: Command not found
>           make: *** [odbc.o] Error 127
>           ODBC disabled.
>           PostgreSQL auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
> -I/usr/include/pgsql -I. -I/usr/sfw/include -o psql.o psql.cpp
>           make: CC: Command not found
>           make: *** [psql.o] Error 127
>           PostgreSQL disabled.
>           SQLite2 auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o sqlite2.o sqlite2.cpp
>           make: CC: Command not found
>           make: *** [sqlite2.o] Error 127
>           SQLite2 disabled.
>           NIS auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o nis.o nis.cpp
>           make: CC: Command not found
>           make: *** [nis.o] Error 127
>           NIS disabled.
>           Cups auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o cups.o cups.cpp
>           make: CC: Command not found
>           make: *** [cups.o] Error 127
>           Cups disabled.
>           POSIX iconv auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o iconv.o iconv.cpp
>           make: CC: Command not found
>           make: *** [iconv.o] Error 127
>           POSIX iconv disabled.
>           GNU libiconv auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o gnu-libiconv.o gnu-libiconv.cpp
>           make: CC: Command not found
>           make: *** [gnu-libiconv.o] Error 127
>           GNU libiconv disabled.
>           D-Bus auto-detection... ()
>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I.
> -I/usr/sfw/include -o dbus.o dbus.cpp
>           make: CC: Command not found
>           make: *** [dbus.o] Error 127
>           D-Bus disabled.
>           The QtDBus module cannot be enabled because libdbus-1
> version 0.62 was not found.
>            Turn on verbose messaging (-v) to ./configure to see the
> final report.
>             If you believe this message is in error you may use the continue
>              switch (-continue) to ./configure to continue.
>
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From maybird1776 at yahoo.com  Wed May 28 05:31:27 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Wed, 28 May 2008 05:31:27 -0700 (PDT)
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
Message-ID: <596635.5066.qm@web34201.mail.mud.yahoo.com>

Manish,

To get things off the ground do this with Qt 4.4.0:

./configure -prefix /opt/qt4 -without-dbus

Note: You'll need the Webkit & Dbus libraries for KDE
4.0.80 (KDE 4.1b1), Yet, just get through the compile
first.

KDE 4.1 will fully replace KDE 3.5.9, so focus on the
KDE 4.0.80 tarballs for now with Qt 4.4.0/4.4.1.

~ Ken


--- Manish Chakravarty <manishchaks at gmail.com> wrote:

> I have setup my env the following way:
> 
> export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
> export
>
CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
> export
>
CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
> export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
> alias cmakekde="cmake ../
> -DCMAKE_INSTALL_PREFIX=/opt/kde4"
> export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib
> -lgnuintl -lgnuiconv"
> export CC=/usr/sfw/bin/gcc
> export CXX=/usr/sfw/bin/g++
> 
> 
> I started building Qt4 like this:
> ./configure -qt-gif -fast -no-exceptions
> -no-separate-debug-info
> -system-libpng -system-libjpeg -system-zlib -dbus
> -webkit -no-phonon
> -nomake examples -nomake demos -prefix /opt/qt4
> 
> I get the following error while building q4:
> 
> manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure
> -qt-gif -fast
> -no-exceptions -no-separate-debug-info
> -system-libpng -system-libjpeg
> -system-zlib -dbus -webkit -no-phonon -nomake
> examples -nomake demos
> -prefix /opt/qt4
> 
> This is the Qt/X11 Open Source Edition.
> 
> You are licensed to use this software under the
> terms of either
> the Q Public License (QPL) or the GNU General Public
> License (GPL)
> versions 2 or 3
> 
> Type 'Q' to view the Q Public License.
> Type '2' to view the GNU General Public License
> version 2.
> Type '3' to view the GNU General Public License
> version 3.
> Type 'yes' to accept this license offer.
> Type 'no' to decline this license offer.
> 
> Do you accept the terms of either license? yes
> 
> Creating qmake. Please wait...
> gmake: Nothing to be done for `first'.
> The QtDBus module cannot be enabled because
> libdbus-1 version 0.62 was
> not found.
>  Turn on verbose messaging (-v) to ./configure to
> see the final report.
>   If you believe this message is in error you may
> use the continue
>    switch (-continue) to ./configure to continue.
>    manish at beleniXRemiX:~/kde.build/qt-copy$
> ./configure -qt-gif -fast
> -no-exceptions -no-separate-debug-info
> -system-libpng -system-libjpeg
> -system-zlib -dbus -webkit -no-phonon -nomake
> examples -nomake demos
> -prefix /opt/qt4 -v
> 
>    This is the Qt/X11 Open Source Edition.
> 
>    Determining system architecture...
> (SunOS:5.11:i86pc)
>        32-bit Intel 80x86 (i386)
>            'i386' is supported
>            System architecture: 'i386'
>            Precompiled-headers support disabled.
>            Symbol visibility control disabled.
>            You are licensed to use this software
> under the terms of either
>            the Q Public License (QPL) or the GNU
> General Public License (GPL)
>            versions 2 or 3
> 
>            Type 'Q' to view the Q Public License.
>            Type '2' to view the GNU General Public
> License version 2.
>            Type '3' to view the GNU General Public
> License version 3.
>            Type 'yes' to accept this license offer.
>            Type 'no' to decline this license offer.
> 
>            Do you accept the terms of either
> license? yes
> 
>            Creating qmake. Please wait...
>            gmake: Nothing to be done for `first'.
>            floatmath auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o floatmath.o floatmath.cpp
>            make: CC: Command not found
>            make: *** [floatmath.o] Error 127
>            floatmath disabled.
>            mmx auto-detection... ()
>            CC -c -mmmx -O2 
> -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o mmx.o mmx.cpp
>            make: CC: Command not found
>            make: *** [mmx.o] Error 127
>            mmx disabled.
>            3dnow auto-detection... ()
>            CC -c -m3dnow -O2 
> -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o 3dnow.o 3dnow.cpp
>            make: CC: Command not found
>            make: *** [3dnow.o] Error 127
>            3dnow disabled.
>            sse auto-detection... ()
>            CC -c -msse -O2 
> -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o sse.o sse.cpp
>            make: CC: Command not found
>            make: *** [sse.o] Error 127
>            sse disabled.
>            sse2 auto-detection... ()
>            CC -c -msse2 -O2 
> -I../../../mkspecs/solaris-cc -I. -I.
> -I/usr/sfw/include -o sse2.o sse2.cpp
>            make: CC: Command not found
>            make: *** [sse2.o] Error 127
>            sse2 disabled.
>            libtiff auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o libtiff.o libtiff.cpp
>            make: CC: Command not found
>            make: *** [libtiff.o] Error 127
>            libtiff disabled.
>            libmng auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o libmng.o libmng.cpp
>            make: CC: Command not found
>            make: *** [libmng.o] Error 127
>            libmng disabled.
>            InterBase auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o ibase.o ibase.cpp
>            make: CC: Command not found
>            make: *** [ibase.o] Error 127
>            InterBase disabled.
>            MySQL (thread-safe) auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I.
> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o
> mysql.o
> ../mysql/mysql.cpp
>            make: CC: Command not found
>            make: *** [mysql.o] Error 127
>            MySQL (thread-safe) disabled.
>            MySQL (thread-unsafe) auto-detection...
> ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I.
> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o
> mysql.o mysql.cpp
>            make: CC: Command not found
>            make: *** [mysql.o] Error 127
>            MySQL (thread-unsafe) disabled.
>            ODBC auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o odbc.o odbc.cpp
>            make: CC: Command not found
>            make: *** [odbc.o] Error 127
>            ODBC disabled.
>            PostgreSQL auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I.
> -I/usr/include/pgsql -I. -I/usr/sfw/include -o
> psql.o psql.cpp
>            make: CC: Command not found
>            make: *** [psql.o] Error 127
>            PostgreSQL disabled.
>            SQLite2 auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o sqlite2.o sqlite2.cpp
>            make: CC: Command not found
>            make: *** [sqlite2.o] Error 127
>            SQLite2 disabled.
>            NIS auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o nis.o nis.cpp
>            make: CC: Command not found
>            make: *** [nis.o] Error 127
>            NIS disabled.
>            Cups auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o cups.o cups.cpp
>            make: CC: Command not found
>            make: *** [cups.o] Error 127
>            Cups disabled.
>            POSIX iconv auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o iconv.o iconv.cpp
>            make: CC: Command not found
>            make: *** [iconv.o] Error 127
>            POSIX iconv disabled.
>            GNU libiconv auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I. -I.
> -I/usr/sfw/include -o gnu-libiconv.o
> gnu-libiconv.cpp
>            make: CC: Command not found
>            make: *** [gnu-libiconv.o] Error 127
>            GNU libiconv disabled.
>            D-Bus auto-detection... ()
>            CC -c -O2  -I../../../mkspecs/solaris-cc
> -I.
> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
> -I.
> -I/usr/sfw/include -o dbus.o dbus.cpp
>            make: CC: Command not found
>            make: *** [dbus.o] Error 127
>            D-Bus disabled.
>            The QtDBus module cannot be enabled
> because libdbus-1
> version 0.62 was not found.
>             Turn on verbose messaging (-v) to
> ./configure to see the
> final report.
>              If you believe this message is in error
> you may use the continue
>               switch (-continue) to ./configure to
> continue.
> 
> 
> 
> 
> -- 
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
>
http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> 



      


From manishchaks at gmail.com  Wed May 28 06:31:50 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 19:01:50 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <596635.5066.qm@web34201.mail.mud.yahoo.com>
References: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
	<596635.5066.qm@web34201.mail.mud.yahoo.com>
Message-ID: <b4dbee910805280631u4324e9c8o338dfb916355a67@mail.gmail.com>

Hey Ken,

My intention behind compiling qt-copy is to build it for KDE4.
While I could get Qt4.4 working without DBus, it would really not
serve the purpose.

I am building everything from trunk at the moment.

I have the other dependencies in place ( dbus, dbus-glib & clucene)

On Wed, May 28, 2008 at 6:01 PM, ken mays <maybird1776 at yahoo.com> wrote:
> Manish,
>
> To get things off the ground do this with Qt 4.4.0:
>
> ./configure -prefix /opt/qt4 -without-dbus
>
> Note: You'll need the Webkit & Dbus libraries for KDE
> 4.0.80 (KDE 4.1b1), Yet, just get through the compile
> first.
>
> KDE 4.1 will fully replace KDE 3.5.9, so focus on the
> KDE 4.0.80 tarballs for now with Qt 4.4.0/4.4.1.
>
> ~ Ken
>
>
> --- Manish Chakravarty <manishchaks at gmail.com> wrote:
>
>> I have setup my env the following way:
>>
>> export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
>> export
>>
> CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
>> export
>>
> CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
>> export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
>> alias cmakekde="cmake ../
>> -DCMAKE_INSTALL_PREFIX=/opt/kde4"
>> export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib
>> -lgnuintl -lgnuiconv"
>> export CC=/usr/sfw/bin/gcc
>> export CXX=/usr/sfw/bin/g++
>>
>>
>> I started building Qt4 like this:
>> ./configure -qt-gif -fast -no-exceptions
>> -no-separate-debug-info
>> -system-libpng -system-libjpeg -system-zlib -dbus
>> -webkit -no-phonon
>> -nomake examples -nomake demos -prefix /opt/qt4
>>
>> I get the following error while building q4:
>>
>> manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure
>> -qt-gif -fast
>> -no-exceptions -no-separate-debug-info
>> -system-libpng -system-libjpeg
>> -system-zlib -dbus -webkit -no-phonon -nomake
>> examples -nomake demos
>> -prefix /opt/qt4
>>
>> This is the Qt/X11 Open Source Edition.
>>
>> You are licensed to use this software under the
>> terms of either
>> the Q Public License (QPL) or the GNU General Public
>> License (GPL)
>> versions 2 or 3
>>
>> Type 'Q' to view the Q Public License.
>> Type '2' to view the GNU General Public License
>> version 2.
>> Type '3' to view the GNU General Public License
>> version 3.
>> Type 'yes' to accept this license offer.
>> Type 'no' to decline this license offer.
>>
>> Do you accept the terms of either license? yes
>>
>> Creating qmake. Please wait...
>> gmake: Nothing to be done for `first'.
>> The QtDBus module cannot be enabled because
>> libdbus-1 version 0.62 was
>> not found.
>>  Turn on verbose messaging (-v) to ./configure to
>> see the final report.
>>   If you believe this message is in error you may
>> use the continue
>>    switch (-continue) to ./configure to continue.
>>    manish at beleniXRemiX:~/kde.build/qt-copy$
>> ./configure -qt-gif -fast
>> -no-exceptions -no-separate-debug-info
>> -system-libpng -system-libjpeg
>> -system-zlib -dbus -webkit -no-phonon -nomake
>> examples -nomake demos
>> -prefix /opt/qt4 -v
>>
>>    This is the Qt/X11 Open Source Edition.
>>
>>    Determining system architecture...
>> (SunOS:5.11:i86pc)
>>        32-bit Intel 80x86 (i386)
>>            'i386' is supported
>>            System architecture: 'i386'
>>            Precompiled-headers support disabled.
>>            Symbol visibility control disabled.
>>            You are licensed to use this software
>> under the terms of either
>>            the Q Public License (QPL) or the GNU
>> General Public License (GPL)
>>            versions 2 or 3
>>
>>            Type 'Q' to view the Q Public License.
>>            Type '2' to view the GNU General Public
>> License version 2.
>>            Type '3' to view the GNU General Public
>> License version 3.
>>            Type 'yes' to accept this license offer.
>>            Type 'no' to decline this license offer.
>>
>>            Do you accept the terms of either
>> license? yes
>>
>>            Creating qmake. Please wait...
>>            gmake: Nothing to be done for `first'.
>>            floatmath auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o floatmath.o floatmath.cpp
>>            make: CC: Command not found
>>            make: *** [floatmath.o] Error 127
>>            floatmath disabled.
>>            mmx auto-detection... ()
>>            CC -c -mmmx -O2
>> -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o mmx.o mmx.cpp
>>            make: CC: Command not found
>>            make: *** [mmx.o] Error 127
>>            mmx disabled.
>>            3dnow auto-detection... ()
>>            CC -c -m3dnow -O2
>> -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o 3dnow.o 3dnow.cpp
>>            make: CC: Command not found
>>            make: *** [3dnow.o] Error 127
>>            3dnow disabled.
>>            sse auto-detection... ()
>>            CC -c -msse -O2
>> -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o sse.o sse.cpp
>>            make: CC: Command not found
>>            make: *** [sse.o] Error 127
>>            sse disabled.
>>            sse2 auto-detection... ()
>>            CC -c -msse2 -O2
>> -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o sse2.o sse2.cpp
>>            make: CC: Command not found
>>            make: *** [sse2.o] Error 127
>>            sse2 disabled.
>>            libtiff auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o libtiff.o libtiff.cpp
>>            make: CC: Command not found
>>            make: *** [libtiff.o] Error 127
>>            libtiff disabled.
>>            libmng auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o libmng.o libmng.cpp
>>            make: CC: Command not found
>>            make: *** [libmng.o] Error 127
>>            libmng disabled.
>>            InterBase auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o ibase.o ibase.cpp
>>            make: CC: Command not found
>>            make: *** [ibase.o] Error 127
>>            InterBase disabled.
>>            MySQL (thread-safe) auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I.
>> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o
>> mysql.o
>> ../mysql/mysql.cpp
>>            make: CC: Command not found
>>            make: *** [mysql.o] Error 127
>>            MySQL (thread-safe) disabled.
>>            MySQL (thread-unsafe) auto-detection...
>> ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I.
>> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o
>> mysql.o mysql.cpp
>>            make: CC: Command not found
>>            make: *** [mysql.o] Error 127
>>            MySQL (thread-unsafe) disabled.
>>            ODBC auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o odbc.o odbc.cpp
>>            make: CC: Command not found
>>            make: *** [odbc.o] Error 127
>>            ODBC disabled.
>>            PostgreSQL auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I.
>> -I/usr/include/pgsql -I. -I/usr/sfw/include -o
>> psql.o psql.cpp
>>            make: CC: Command not found
>>            make: *** [psql.o] Error 127
>>            PostgreSQL disabled.
>>            SQLite2 auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o sqlite2.o sqlite2.cpp
>>            make: CC: Command not found
>>            make: *** [sqlite2.o] Error 127
>>            SQLite2 disabled.
>>            NIS auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o nis.o nis.cpp
>>            make: CC: Command not found
>>            make: *** [nis.o] Error 127
>>            NIS disabled.
>>            Cups auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o cups.o cups.cpp
>>            make: CC: Command not found
>>            make: *** [cups.o] Error 127
>>            Cups disabled.
>>            POSIX iconv auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o iconv.o iconv.cpp
>>            make: CC: Command not found
>>            make: *** [iconv.o] Error 127
>>            POSIX iconv disabled.
>>            GNU libiconv auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I. -I.
>> -I/usr/sfw/include -o gnu-libiconv.o
>> gnu-libiconv.cpp
>>            make: CC: Command not found
>>            make: *** [gnu-libiconv.o] Error 127
>>            GNU libiconv disabled.
>>            D-Bus auto-detection... ()
>>            CC -c -O2  -I../../../mkspecs/solaris-cc
>> -I.
>> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
>> -I.
>> -I/usr/sfw/include -o dbus.o dbus.cpp
>>            make: CC: Command not found
>>            make: *** [dbus.o] Error 127
>>            D-Bus disabled.
>>            The QtDBus module cannot be enabled
>> because libdbus-1
>> version 0.62 was not found.
>>             Turn on verbose messaging (-v) to
>> ./configure to see the
>> final report.
>>              If you believe this message is in error
>> you may use the continue
>>               switch (-continue) to ./configure to
>> continue.
>>
>>
>>
>>
>> --
>> Manish Chakravarty
>> http://manish-chaks.livejournal.com/
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>>
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>
>
>
>
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From moinakg at gmail.com  Wed May 28 07:03:32 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 19:33:32 +0530
Subject: [belenix-dev] Just a offer to help with 0.8
In-Reply-To: <cbc95d950805280035v4e4beccdm784c3e744a676201@mail.gmail.com>
References: <cbc95d950805280035v4e4beccdm784c3e744a676201@mail.gmail.com>
Message-ID: <46fe20470805280703l2f33d1e2o72c73b9f7746753c@mail.gmail.com>

On Wed, May 28, 2008 at 1:05 PM, Edward O'Callaghan
<victoredwardocallaghan at gmail.com> wrote:
> Hi,
> I would just like to offer to help with the 0.8 release in the following
> areas:
>
> *Fluxbox integration.
> *Media Codec buddy and media framework.
> *Small bug fixes. (I have limited times these days from collage .. :p )
> *Testing

   Great! Thank you for your interest. Please checkout the SVN
   repository, instructions here:

   http://sourceforge.net/svn/?group_id=216118

   Go through the stuff and post here if you have doubts. Also create
   a sourceforge account and let me know your ID, I will add you to
   the developers list.

Regards,
Moinak.

>
> Thanks,
> Edward.
>
> --
> All Documents adhered to the ISO/IEC 26300  standard file format for
> electronic office documents, such as spreadsheets, charts, presentations and
> word processing documents from this email address. The author does not take
> responsibility of the recipients inability to read international standards
> and who use proprietary products such as MS Office.
> See: http://www.openoffice.org/
> Edward O'Callaghan.
> --
> http://fedoraproject.org/wiki/EdwardOcallaghan
> http://moonshine.opn4.org/
> http://www.pcbsd.org/
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From moinakg at gmail.com  Wed May 28 07:16:03 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 19:46:03 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <b4dbee910805280428r759a0e94q6d268d5964974d2@mail.gmail.com>
References: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
	<b4dbee910805280428r759a0e94q6d268d5964974d2@mail.gmail.com>
Message-ID: <46fe20470805280716i1ba990d7gd6e83f6b2cb4aaa3@mail.gmail.com>

Hi Manish,

   In spite of you setting CC and CXX the Qt build is clearly using
SUN Studio: "CC -R/opt/qt4/lib ...". You need to pass the flag:
"-platform solaris-g++" to Qt4's configure.

There is already a Qt4 spec file in SFE see:
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup

Regards,
Moinak.

On Wed, May 28, 2008 at 4:58 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> I installed CBE and sourced the env
> After that I adjusted my env in the following manner:
> export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
>  export CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
>  export CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
>  export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
> alias cmakekde="cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/kde4"
>  export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv"
>  export CC=/usr/sfw/bin/gcc
>  export CXX=/usr/sfw/bin/g++
>
> I get the following error:
> cd src/tools/moc/ && gmake -f Makefile
> gmake[1]: Entering directory
> `/export/home/manish/kde.build/qt-copy/src/tools/moc'
> CC -R/opt/qt4/lib -R/opt/qt4/lib -o ../../../bin/moc
> release-shared/moc.o release-shared/preprocessor.o
> release-shared/generator.o release-shared/parser.o
> release-shared/token.o release-shared/main.o release-shared/qglobal.o
> release-shared/qmalloc.o release-shared/qnumeric.o
> release-shared/qbuffer.o release-shared/qdir.o
> release-shared/qdiriterator.o release-shared/qfile.o
> release-shared/qfileinfo.o release-shared/qfsfileengine.o
> release-shared/qfsfileengine_iterator.o release-shared/qiodevice.o
> release-shared/qtemporaryfile.o release-shared/qtextstream.o
> release-shared/qurl.o release-shared/qmetatype.o
> release-shared/qbytearraymatcher.o release-shared/qdatetime.o
> release-shared/qhash.o release-shared/qlistdata.o
> release-shared/qlocale.o release-shared/qmap.o
> release-shared/qstring.o release-shared/qstringlist.o
> release-shared/qvector.o release-shared/qvariant.o
> release-shared/qabstractfileengine.o release-shared/qbytearray.o
> release-shared/qvsnprintf.o release-shared/qfsfileengine_unix.o
> release-shared/qfsfileengine_iterator_unix.o    -L/usr/sfw/lib -ldl
> Undefined                       first referenced
>  symbol                             in file
> operator new[](unsigned)                               release-shared/moc.o
> operator new(unsigned)                               release-shared/moc.o
> vtable for __cxxabiv1::__si_class_type_info release-shared/qbuffer.o
> [Hint: static member vtable for __cxxabiv1::__si_class_type_info must
> be defined in the program]
>
> operator delete[](void*)                              release-shared/moc.o
> operator delete(void*)                              release-shared/moc.o
> _Unwind_Resume                      release-shared/moc.o
> vtable for __cxxabiv1::__class_type_info release-shared/qdiriterator.o
> [Hint: static member vtable for __cxxabiv1::__class_type_info must be
> defined in the program]
>
> __gxx_personality_v0                release-shared/moc.o
> __cxa_pure_virtual                  release-shared/qiodevice.o
> ld: fatal: Symbol referencing errors. No output written to ../../../bin/moc
> gmake[1]: *** [../../../bin/moc] Error 1
> gmake[1]: Leaving directory
> `/export/home/manish/kde.build/qt-copy/src/tools/moc'
> gmake: *** [sub-moc-make_default-ordered] Error 2
>
> This is some kind of linker error.
>
> Can someone help me out with this?
>
> -- Manish
>
>
>
> On Wed, May 28, 2008 at 3:16 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
>> I have setup my env the following way:
>>
>> export PATH=/opt/qt4/bin:/opt/kde4/bin:$PATH
>> export CMAKE_INCLUDE_PATH=/opt/kde4/include:/opt/qt4/include:$CMAKE_INCLUDE_PATH
>> export CMAKE_LIBRARY_PATH=/opt/kde4/lib:/opt/qt4/lib:$CMAKE_LIBRARY_PATH
>> export PKG_CONFIG_PATH="/opt/qt4/lib:/opt/kde4/lib"
>> alias cmakekde="cmake ../ -DCMAKE_INSTALL_PREFIX=/opt/kde4"
>> export LDFLAGS="-L/usr/gnu/lib -R/usr/gnu/lib -lgnuintl -lgnuiconv"
>> export CC=/usr/sfw/bin/gcc
>> export CXX=/usr/sfw/bin/g++
>>
>>
>> I started building Qt4 like this:
>> ./configure -qt-gif -fast -no-exceptions -no-separate-debug-info
>> -system-libpng -system-libjpeg -system-zlib -dbus -webkit -no-phonon
>> -nomake examples -nomake demos -prefix /opt/qt4
>>
>> I get the following error while building q4:
>>
>> manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure -qt-gif -fast
>> -no-exceptions -no-separate-debug-info -system-libpng -system-libjpeg
>> -system-zlib -dbus -webkit -no-phonon -nomake examples -nomake demos
>> -prefix /opt/qt4
>>
>> This is the Qt/X11 Open Source Edition.
>>
>> You are licensed to use this software under the terms of either
>> the Q Public License (QPL) or the GNU General Public License (GPL)
>> versions 2 or 3
>>
>> Type 'Q' to view the Q Public License.
>> Type '2' to view the GNU General Public License version 2.
>> Type '3' to view the GNU General Public License version 3.
>> Type 'yes' to accept this license offer.
>> Type 'no' to decline this license offer.
>>
>> Do you accept the terms of either license? yes
>>
>> Creating qmake. Please wait...
>> gmake: Nothing to be done for `first'.
>> The QtDBus module cannot be enabled because libdbus-1 version 0.62 was
>> not found.
>>  Turn on verbose messaging (-v) to ./configure to see the final report.
>>  If you believe this message is in error you may use the continue
>>   switch (-continue) to ./configure to continue.
>>   manish at beleniXRemiX:~/kde.build/qt-copy$ ./configure -qt-gif -fast
>> -no-exceptions -no-separate-debug-info -system-libpng -system-libjpeg
>> -system-zlib -dbus -webkit -no-phonon -nomake examples -nomake demos
>> -prefix /opt/qt4 -v
>>
>>   This is the Qt/X11 Open Source Edition.
>>
>>   Determining system architecture... (SunOS:5.11:i86pc)
>>       32-bit Intel 80x86 (i386)
>>           'i386' is supported
>>           System architecture: 'i386'
>>           Precompiled-headers support disabled.
>>           Symbol visibility control disabled.
>>           You are licensed to use this software under the terms of either
>>           the Q Public License (QPL) or the GNU General Public License (GPL)
>>           versions 2 or 3
>>
>>           Type 'Q' to view the Q Public License.
>>           Type '2' to view the GNU General Public License version 2.
>>           Type '3' to view the GNU General Public License version 3.
>>           Type 'yes' to accept this license offer.
>>           Type 'no' to decline this license offer.
>>
>>           Do you accept the terms of either license? yes
>>
>>           Creating qmake. Please wait...
>>           gmake: Nothing to be done for `first'.
>>           floatmath auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o floatmath.o floatmath.cpp
>>           make: CC: Command not found
>>           make: *** [floatmath.o] Error 127
>>           floatmath disabled.
>>           mmx auto-detection... ()
>>           CC -c -mmmx -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o mmx.o mmx.cpp
>>           make: CC: Command not found
>>           make: *** [mmx.o] Error 127
>>           mmx disabled.
>>           3dnow auto-detection... ()
>>           CC -c -m3dnow -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o 3dnow.o 3dnow.cpp
>>           make: CC: Command not found
>>           make: *** [3dnow.o] Error 127
>>           3dnow disabled.
>>           sse auto-detection... ()
>>           CC -c -msse -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o sse.o sse.cpp
>>           make: CC: Command not found
>>           make: *** [sse.o] Error 127
>>           sse disabled.
>>           sse2 auto-detection... ()
>>           CC -c -msse2 -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o sse2.o sse2.cpp
>>           make: CC: Command not found
>>           make: *** [sse2.o] Error 127
>>           sse2 disabled.
>>           libtiff auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o libtiff.o libtiff.cpp
>>           make: CC: Command not found
>>           make: *** [libtiff.o] Error 127
>>           libtiff disabled.
>>           libmng auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o libmng.o libmng.cpp
>>           make: CC: Command not found
>>           make: *** [libmng.o] Error 127
>>           libmng disabled.
>>           InterBase auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o ibase.o ibase.cpp
>>           make: CC: Command not found
>>           make: *** [ibase.o] Error 127
>>           InterBase disabled.
>>           MySQL (thread-safe) auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
>> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o mysql.o
>> ../mysql/mysql.cpp
>>           make: CC: Command not found
>>           make: *** [mysql.o] Error 127
>>           MySQL (thread-safe) disabled.
>>           MySQL (thread-unsafe) auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
>> -I/usr/sfw/include/mysql -I. -I/usr/sfw/include -o mysql.o mysql.cpp
>>           make: CC: Command not found
>>           make: *** [mysql.o] Error 127
>>           MySQL (thread-unsafe) disabled.
>>           ODBC auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o odbc.o odbc.cpp
>>           make: CC: Command not found
>>           make: *** [odbc.o] Error 127
>>           ODBC disabled.
>>           PostgreSQL auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
>> -I/usr/include/pgsql -I. -I/usr/sfw/include -o psql.o psql.cpp
>>           make: CC: Command not found
>>           make: *** [psql.o] Error 127
>>           PostgreSQL disabled.
>>           SQLite2 auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o sqlite2.o sqlite2.cpp
>>           make: CC: Command not found
>>           make: *** [sqlite2.o] Error 127
>>           SQLite2 disabled.
>>           NIS auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o nis.o nis.cpp
>>           make: CC: Command not found
>>           make: *** [nis.o] Error 127
>>           NIS disabled.
>>           Cups auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o cups.o cups.cpp
>>           make: CC: Command not found
>>           make: *** [cups.o] Error 127
>>           Cups disabled.
>>           POSIX iconv auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o iconv.o iconv.cpp
>>           make: CC: Command not found
>>           make: *** [iconv.o] Error 127
>>           POSIX iconv disabled.
>>           GNU libiconv auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I. -I.
>> -I/usr/sfw/include -o gnu-libiconv.o gnu-libiconv.cpp
>>           make: CC: Command not found
>>           make: *** [gnu-libiconv.o] Error 127
>>           GNU libiconv disabled.
>>           D-Bus auto-detection... ()
>>           CC -c -O2  -I../../../mkspecs/solaris-cc -I.
>> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I.
>> -I/usr/sfw/include -o dbus.o dbus.cpp
>>           make: CC: Command not found
>>           make: *** [dbus.o] Error 127
>>           D-Bus disabled.
>>           The QtDBus module cannot be enabled because libdbus-1
>> version 0.62 was not found.
>>            Turn on verbose messaging (-v) to ./configure to see the
>> final report.
>>             If you believe this message is in error you may use the continue
>>              switch (-continue) to ./configure to continue.
>>
>>
>>
>>
>> --
>> Manish Chakravarty
>> http://manish-chaks.livejournal.com/
>>
>
>
>
> --
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From ananth.shrinivas at gmail.com  Wed May 28 07:35:32 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Wed, 28 May 2008 20:05:32 +0530
Subject: [belenix-dev] BeleniX Logo SVG
Message-ID: <f5ff03920805280735x73e8f6f0n3528086fe9c03f24@mail.gmail.com>

Hi Guys,

I need the BeleniX logo in SVG format.

Moinak,

If you have a copy, just commit it to the SVN trunk and let me know the
path.

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080528/4b58826e/attachment.html>

From manishchaks at gmail.com  Wed May 28 07:37:01 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 20:07:01 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <46fe20470805280716i1ba990d7gd6e83f6b2cb4aaa3@mail.gmail.com>
References: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
	<b4dbee910805280428r759a0e94q6d268d5964974d2@mail.gmail.com>
	<46fe20470805280716i1ba990d7gd6e83f6b2cb4aaa3@mail.gmail.com>
Message-ID: <b4dbee910805280737v20d12253k1a426d684ae7bc1b@mail.gmail.com>

On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
> Hi Manish,
>
>   In spite of you setting CC and CXX the Qt build is clearly using
> SUN Studio: "CC -R/opt/qt4/lib ...". You need to pass the flag:
> "-platform solaris-g++" to Qt4's configure.
Thanks a lot for the tip Moinak!
>
> There is already a Qt4 spec file in SFE see:
> http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
As you know , we need to build qt-copy for KDE4,
Qt4 stable might/might not work for KDE4.


[..snip..]


From moinakg at gmail.com  Wed May 28 07:42:18 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 20:12:18 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <b4dbee910805280737v20d12253k1a426d684ae7bc1b@mail.gmail.com>
References: <b4dbee910805280246n10a1f7e3x16fb1be0a16459d3@mail.gmail.com>
	<b4dbee910805280428r759a0e94q6d268d5964974d2@mail.gmail.com>
	<46fe20470805280716i1ba990d7gd6e83f6b2cb4aaa3@mail.gmail.com>
	<b4dbee910805280737v20d12253k1a426d684ae7bc1b@mail.gmail.com>
Message-ID: <46fe20470805280742s2a1d5c4epd7e77182f92539a2@mail.gmail.com>

On Wed, May 28, 2008 at 8:07 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh <moinakg at gmail.com> wrote:
>> Hi Manish,
>>
>>   In spite of you setting CC and CXX the Qt build is clearly using
>> SUN Studio: "CC -R/opt/qt4/lib ...". You need to pass the flag:
>> "-platform solaris-g++" to Qt4's configure.
> Thanks a lot for the tip Moinak!
>>
>> There is already a Qt4 spec file in SFE see:
>> http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
> As you know , we need to build qt-copy for KDE4,
> Qt4 stable might/might not work for KDE4.

   Yeah modify the spec file. The other settings (like configur eoptions)
   should remain same and save you a lot of headache.

Regards,
Moinak.

>
>
> [..snip..]
>


From anil.verve at gmail.com  Wed May 28 07:45:59 2008
From: anil.verve at gmail.com (Anil Gulecha)
Date: Wed, 28 May 2008 20:15:59 +0530
Subject: [belenix-dev] BeleniX Logo SVG
In-Reply-To: <f5ff03920805280735x73e8f6f0n3528086fe9c03f24@mail.gmail.com>
References: <f5ff03920805280735x73e8f6f0n3528086fe9c03f24@mail.gmail.com>
Message-ID: <148d59250805280745l1a38297dhacc537ac13128404@mail.gmail.com>

Mailed offline.

~Anil

On 5/28/08, Ananth Shrinivas <ananth.shrinivas at gmail.com> wrote:
> Hi Guys,
>
> I need the BeleniX logo in SVG format.
>
> Moinak,
>
> If you have a copy, just commit it to the SVN trunk and let me know the
> path.
>
> Ananth
>
> _______________________________________________
>  belenix-dev mailing list
>  belenix-dev at opensolaris.org
>  http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From moinakg at gmail.com  Wed May 28 07:46:41 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 20:16:41 +0530
Subject: [belenix-dev] BeleniX Logo SVG
In-Reply-To: <f5ff03920805280735x73e8f6f0n3528086fe9c03f24@mail.gmail.com>
References: <f5ff03920805280735x73e8f6f0n3528086fe9c03f24@mail.gmail.com>
Message-ID: <46fe20470805280746y26534befk509ea9619418cfe9@mail.gmail.com>

On Wed, May 28, 2008 at 8:05 PM, Ananth Shrinivas
<ananth.shrinivas at gmail.com> wrote:
> Hi Guys,
>
> I need the BeleniX logo in SVG format.
>
> Moinak,
>
> If you have a copy, just commit it to the SVN trunk and let me know the
> path.

   Done deal:

   http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/misc/belenix-branding/belenix-lines.svg?view=log

Regards,
Moinak.

>
> Ananth
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>
>


From maybird1776 at yahoo.com  Wed May 28 09:07:03 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Wed, 28 May 2008 09:07:03 -0700 (PDT)
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <b4dbee910805280737v20d12253k1a426d684ae7bc1b@mail.gmail.com>
Message-ID: <160564.8338.qm@web34201.mail.mud.yahoo.com>

Qt 4.4.0 works fine with KDE 4.0.80 (KDE 4.1beta1).
I'm using it for my builds.

~ Ken

--- Manish Chakravarty <manishchaks at gmail.com> wrote:

> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
> <moinakg at gmail.com> wrote:
> > Hi Manish,
> >
> >   In spite of you setting CC and CXX the Qt build
> is clearly using
> > SUN Studio: "CC -R/opt/qt4/lib ...". You need to
> pass the flag:
> > "-platform solaris-g++" to Qt4's configure.
> Thanks a lot for the tip Moinak!
> >
> > There is already a Qt4 spec file in SFE see:
> >
>
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
> As you know , we need to build qt-copy for KDE4,
> Qt4 stable might/might not work for KDE4.
> 
> 
> [..snip..]
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
>
http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> 



      


From manishchaks at gmail.com  Wed May 28 09:55:48 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 22:25:48 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <160564.8338.qm@web34201.mail.mud.yahoo.com>
References: <b4dbee910805280737v20d12253k1a426d684ae7bc1b@mail.gmail.com>
	<160564.8338.qm@web34201.mail.mud.yahoo.com>
Message-ID: <b4dbee910805280955j1e49eb46h96b6eb3c54c55d1f@mail.gmail.com>

On Wed, May 28, 2008 at 9:37 PM, ken mays <maybird1776 at yahoo.com> wrote:
> Qt 4.4.0 works fine with KDE 4.0.80 (KDE 4.1beta1).
> I'm using it for my builds.
Are you compiling it with or without DBus?

If you are compiling with DBus, can you share the recipe with me?
I am compiling my own DBus and Dbus-glib and sandboxing it into /opt/kde4 .

Thanks
Manish
>
> ~ Ken
>
> --- Manish Chakravarty <manishchaks at gmail.com> wrote:
>
>> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
>> <moinakg at gmail.com> wrote:
>> > Hi Manish,
>> >
>> >   In spite of you setting CC and CXX the Qt build
>> is clearly using
>> > SUN Studio: "CC -R/opt/qt4/lib ...". You need to
>> pass the flag:
>> > "-platform solaris-g++" to Qt4's configure.
>> Thanks a lot for the tip Moinak!
>> >
>> > There is already a Qt4 spec file in SFE see:
>> >
>>
> http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
>> As you know , we need to build qt-copy for KDE4,
>> Qt4 stable might/might not work for KDE4.
>>
>>
>> [..snip..]
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>>
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>
>
>
>
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From maybird1776 at yahoo.com  Wed May 28 10:31:41 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Wed, 28 May 2008 10:31:41 -0700 (PDT)
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <b4dbee910805280955j1e49eb46h96b6eb3c54c55d1f@mail.gmail.com>
Message-ID: <542643.57989.qm@web34204.mail.mud.yahoo.com>

You can use SUNWdbus from SXCE or the Dbus packages
from the JDS project as a workaround.

I advise the Qt 4.4.0 default options enabled as
different KDE4 apps need them (or will request them). 

~ Ken


--- Manish Chakravarty <manishchaks at gmail.com> wrote:

> On Wed, May 28, 2008 at 9:37 PM, ken mays
> <maybird1776 at yahoo.com> wrote:
> > Qt 4.4.0 works fine with KDE 4.0.80 (KDE
> 4.1beta1).
> > I'm using it for my builds.
> Are you compiling it with or without DBus?
> 
> If you are compiling with DBus, can you share the
> recipe with me?
> I am compiling my own DBus and Dbus-glib and
> sandboxing it into /opt/kde4 .
> 
> Thanks
> Manish
> >
> > ~ Ken
> >
> > --- Manish Chakravarty <manishchaks at gmail.com>
> wrote:
> >
> >> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
> >> <moinakg at gmail.com> wrote:
> >> > Hi Manish,
> >> >
> >> >   In spite of you setting CC and CXX the Qt
> build
> >> is clearly using
> >> > SUN Studio: "CC -R/opt/qt4/lib ...". You need
> to
> >> pass the flag:
> >> > "-platform solaris-g++" to Qt4's configure.
> >> Thanks a lot for the tip Moinak!
> >> >
> >> > There is already a Qt4 spec file in SFE see:
> >> >
> >>
> >
>
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
> >> As you know , we need to build qt-copy for KDE4,
> >> Qt4 stable might/might not work for KDE4.
> >>
> >>
> >> [..snip..]
> >> _______________________________________________
> >> belenix-dev mailing list
> >> belenix-dev at opensolaris.org
> >>
> >
>
http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >>
> >
> >
> >
> >
> >
> 
> 
> 
> -- 
> Manish Chakravarty
> http://manish-chaks.livejournal.com/
> 



      


From manishchaks at gmail.com  Wed May 28 10:40:42 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 23:10:42 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <542643.57989.qm@web34204.mail.mud.yahoo.com>
References: <542643.57989.qm@web34204.mail.mud.yahoo.com>
Message-ID: <483D991A.9070704@gmail.com>


Hi Ken,
I recall having faced problems DBus which comes with BeleniX
qt-copy had complained that it could not find dbus on the system.

I shall try with default Qt4 from the spec files + SUNWdbus tomorrow.

Thanks,
Manish
ken mays wrote:
> You can use SUNWdbus from SXCE or the Dbus packages
> from the JDS project as a workaround.
>
> I advise the Qt 4.4.0 default options enabled as
> different KDE4 apps need them (or will request them). 
>
> ~ Ken
>
>
> --- Manish Chakravarty <manishchaks at gmail.com> wrote:
>
>   
>> On Wed, May 28, 2008 at 9:37 PM, ken mays
>> <maybird1776 at yahoo.com> wrote:
>>     
>>> Qt 4.4.0 works fine with KDE 4.0.80 (KDE
>>>       
>> 4.1beta1).
>>     
>>> I'm using it for my builds.
>>>       
>> Are you compiling it with or without DBus?
>>
>> If you are compiling with DBus, can you share the
>> recipe with me?
>> I am compiling my own DBus and Dbus-glib and
>> sandboxing it into /opt/kde4 .
>>
>> Thanks
>> Manish
>>     
>>> ~ Ken
>>>
>>> --- Manish Chakravarty <manishchaks at gmail.com>
>>>       
>> wrote:
>>     
>>>> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
>>>> <moinakg at gmail.com> wrote:
>>>>         
>>>>> Hi Manish,
>>>>>
>>>>>   In spite of you setting CC and CXX the Qt
>>>>>           
>> build
>>     
>>>> is clearly using
>>>>         
>>>>> SUN Studio: "CC -R/opt/qt4/lib ...". You need
>>>>>           
>> to
>>     
>>>> pass the flag:
>>>>         
>>>>> "-platform solaris-g++" to Qt4's configure.
>>>>>           
>>>> Thanks a lot for the tip Moinak!
>>>>         
>>>>> There is already a Qt4 spec file in SFE see:
>>>>>
>>>>>           
> http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
>   
>>>> As you know , we need to build qt-copy for KDE4,
>>>> Qt4 stable might/might not work for KDE4.
>>>>
>>>>
>>>> [..snip..]
>>>> _______________________________________________
>>>> belenix-dev mailing list
>>>> belenix-dev at opensolaris.org
>>>>
>>>>         
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>   
>>>
>>>
>>>
>>>       
>>
>> -- 
>> Manish Chakravarty
>> http://manish-chaks.livejournal.com/
>>
>>     
>
>
>
>       
>   



From moinakg at gmail.com  Wed May 28 10:43:57 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 23:13:57 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <542643.57989.qm@web34204.mail.mud.yahoo.com>
References: <b4dbee910805280955j1e49eb46h96b6eb3c54c55d1f@mail.gmail.com>
	<542643.57989.qm@web34204.mail.mud.yahoo.com>
Message-ID: <46fe20470805281043i70aba8e7j584cb5d9762711f1@mail.gmail.com>

On Wed, May 28, 2008 at 11:01 PM, ken mays <maybird1776 at yahoo.com> wrote:
> You can use SUNWdbus from SXCE or the Dbus packages
> from the JDS project as a workaround.
>
> I advise the Qt 4.4.0 default options enabled as
> different KDE4 apps need them (or will request them).

   Dbus and Dbus-glib are already part of BeleniX 0.7. N things will
   fail to work without it. The KDE 3.5.8 in BeleniX is built with Dbus
   support.
   For some reason Manish's Qt4 build process is failing to detect
   the system dbus. I'd recommend root-causing that failure rather
   than build another copy of Dbus in /opt/qt4. That is unclean and
   can cause problems.

Regards,
Moinak.

>
> ~ Ken
>
>
> --- Manish Chakravarty <manishchaks at gmail.com> wrote:
>
>> On Wed, May 28, 2008 at 9:37 PM, ken mays
>> <maybird1776 at yahoo.com> wrote:
>> > Qt 4.4.0 works fine with KDE 4.0.80 (KDE
>> 4.1beta1).
>> > I'm using it for my builds.
>> Are you compiling it with or without DBus?
>>
>> If you are compiling with DBus, can you share the
>> recipe with me?
>> I am compiling my own DBus and Dbus-glib and
>> sandboxing it into /opt/kde4 .
>>
>> Thanks
>> Manish
>> >
>> > ~ Ken
>> >
>> > --- Manish Chakravarty <manishchaks at gmail.com>
>> wrote:
>> >
>> >> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
>> >> <moinakg at gmail.com> wrote:
>> >> > Hi Manish,
>> >> >
>> >> >   In spite of you setting CC and CXX the Qt
>> build
>> >> is clearly using
>> >> > SUN Studio: "CC -R/opt/qt4/lib ...". You need
>> to
>> >> pass the flag:
>> >> > "-platform solaris-g++" to Qt4's configure.
>> >> Thanks a lot for the tip Moinak!
>> >> >
>> >> > There is already a Qt4 spec file in SFE see:
>> >> >
>> >>
>> >
>>
> http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
>> >> As you know , we need to build qt-copy for KDE4,
>> >> Qt4 stable might/might not work for KDE4.
>> >>
>> >>
>> >> [..snip..]
>> >> _______________________________________________
>> >> belenix-dev mailing list
>> >> belenix-dev at opensolaris.org
>> >>
>> >
>>
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>> >>
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Manish Chakravarty
>> http://manish-chaks.livejournal.com/
>>
>
>
>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From moinakg at gmail.com  Wed May 28 10:45:10 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 23:15:10 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <483D991A.9070704@gmail.com>
References: <542643.57989.qm@web34204.mail.mud.yahoo.com>
	<483D991A.9070704@gmail.com>
Message-ID: <46fe20470805281045k1682ca1aq6f3ecdea81c09469@mail.gmail.com>

On Wed, May 28, 2008 at 11:10 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
>
> Hi Ken,
> I recall having faced problems DBus which comes with BeleniX
> qt-copy had complained that it could not find dbus on the system.
>
> I shall try with default Qt4 from the spec files + SUNWdbus tomorrow.

   No use trying to install SUNWdbus from SXCE. BeleniX already includes
   SUNWdbus.

Regards,
Moinak.

>
> Thanks,
> Manish
> ken mays wrote:
>> You can use SUNWdbus from SXCE or the Dbus packages
>> from the JDS project as a workaround.
>>
>> I advise the Qt 4.4.0 default options enabled as
>> different KDE4 apps need them (or will request them).
>>
>> ~ Ken
>>
>>
>> --- Manish Chakravarty <manishchaks at gmail.com> wrote:
>>
>>
>>> On Wed, May 28, 2008 at 9:37 PM, ken mays
>>> <maybird1776 at yahoo.com> wrote:
>>>
>>>> Qt 4.4.0 works fine with KDE 4.0.80 (KDE
>>>>
>>> 4.1beta1).
>>>
>>>> I'm using it for my builds.
>>>>
>>> Are you compiling it with or without DBus?
>>>
>>> If you are compiling with DBus, can you share the
>>> recipe with me?
>>> I am compiling my own DBus and Dbus-glib and
>>> sandboxing it into /opt/kde4 .
>>>
>>> Thanks
>>> Manish
>>>
>>>> ~ Ken
>>>>
>>>> --- Manish Chakravarty <manishchaks at gmail.com>
>>>>
>>> wrote:
>>>
>>>>> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
>>>>> <moinakg at gmail.com> wrote:
>>>>>
>>>>>> Hi Manish,
>>>>>>
>>>>>>   In spite of you setting CC and CXX the Qt
>>>>>>
>>> build
>>>
>>>>> is clearly using
>>>>>
>>>>>> SUN Studio: "CC -R/opt/qt4/lib ...". You need
>>>>>>
>>> to
>>>
>>>>> pass the flag:
>>>>>
>>>>>> "-platform solaris-g++" to Qt4's configure.
>>>>>>
>>>>> Thanks a lot for the tip Moinak!
>>>>>
>>>>>> There is already a Qt4 spec file in SFE see:
>>>>>>
>>>>>>
>> http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
>>
>>>>> As you know , we need to build qt-copy for KDE4,
>>>>> Qt4 stable might/might not work for KDE4.
>>>>>
>>>>>
>>>>> [..snip..]
>>>>> _______________________________________________
>>>>> belenix-dev mailing list
>>>>> belenix-dev at opensolaris.org
>>>>>
>>>>>
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> Manish Chakravarty
>>> http://manish-chaks.livejournal.com/
>>>
>>>
>>
>>
>>
>>
>>
>
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>


From manishchaks at gmail.com  Wed May 28 10:46:21 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Wed, 28 May 2008 23:16:21 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <46fe20470805281043i70aba8e7j584cb5d9762711f1@mail.gmail.com>
References: <b4dbee910805280955j1e49eb46h96b6eb3c54c55d1f@mail.gmail.com>	
	<542643.57989.qm@web34204.mail.mud.yahoo.com>
	<46fe20470805281043i70aba8e7j584cb5d9762711f1@mail.gmail.com>
Message-ID: <483D9A6D.6070307@gmail.com>

Moinak Ghosh wrote:
> On Wed, May 28, 2008 at 11:01 PM, ken mays <maybird1776 at yahoo.com> wrote:
>   
>> You can use SUNWdbus from SXCE or the Dbus packages
>> from the JDS project as a workaround.
>>
>> I advise the Qt 4.4.0 default options enabled as
>> different KDE4 apps need them (or will request them).
>>    Dbus and Dbus-glib are already part of BeleniX 0.7. N things will
>>    fail to work without it. The KDE 3.5.8 in BeleniX is built with Dbus
>>    support.
>>    For some reason Manish's Qt4 build process is failing to detect
>>    the system dbus. I'd recommend root-causing that failure rather
>>    than build another copy of Dbus in /opt/qt4. That is unclean and
>>    can cause problems
>>     
Moinak,
How do I root-cause the failure? Can you give any tips?

--Manish
>>     
[..snip..]


From moinakg at gmail.com  Wed May 28 10:49:01 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Wed, 28 May 2008 23:19:01 +0530
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <483D9A6D.6070307@gmail.com>
References: <b4dbee910805280955j1e49eb46h96b6eb3c54c55d1f@mail.gmail.com>
	<542643.57989.qm@web34204.mail.mud.yahoo.com>
	<46fe20470805281043i70aba8e7j584cb5d9762711f1@mail.gmail.com>
	<483D9A6D.6070307@gmail.com>
Message-ID: <46fe20470805281049u787228a9yc8c569987e37964d@mail.gmail.com>

On Wed, May 28, 2008 at 11:16 PM, Manish Chakravarty
<manishchaks at gmail.com> wrote:
> Moinak Ghosh wrote:
>>
>> On Wed, May 28, 2008 at 11:01 PM, ken mays <maybird1776 at yahoo.com> wrote:
>>
>>>
>>> You can use SUNWdbus from SXCE or the Dbus packages
>>> from the JDS project as a workaround.
>>>
>>> I advise the Qt 4.4.0 default options enabled as
>>> different KDE4 apps need them (or will request them).
>>>   Dbus and Dbus-glib are already part of BeleniX 0.7. N things will
>>>   fail to work without it. The KDE 3.5.8 in BeleniX is built with Dbus
>>>   support.
>>>   For some reason Manish's Qt4 build process is failing to detect
>>>   the system dbus. I'd recommend root-causing that failure rather
>>>   than build another copy of Dbus in /opt/qt4. That is unclean and
>>>   can cause problems
>>>
>
> Moinak,
> How do I root-cause the failure? Can you give any tips?

   Does the configure script generate a config.log ? If yes then looking at
   that file will help.

Regards,
Moinak.

>
> --Manish
>>>
>>>
>
> [..snip..]
>


From maybird1776 at yahoo.com  Wed May 28 11:46:03 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Wed, 28 May 2008 11:46:03 -0700 (PDT)
Subject: [belenix-dev] Unable to build qt4 on belenix 0.7
In-Reply-To: <46fe20470805281045k1682ca1aq6f3ecdea81c09469@mail.gmail.com>
Message-ID: <523980.98011.qm@web34203.mail.mud.yahoo.com>

I'm away from the dev box at the moment, but will
check what is causing the issue sometime soon...

~ Ken

--- Moinak Ghosh <moinakg at gmail.com> wrote:

> On Wed, May 28, 2008 at 11:10 PM, Manish Chakravarty
> <manishchaks at gmail.com> wrote:
> >
> > Hi Ken,
> > I recall having faced problems DBus which comes
> with BeleniX
> > qt-copy had complained that it could not find dbus
> on the system.
> >
> > I shall try with default Qt4 from the spec files +
> SUNWdbus tomorrow.
> 
>    No use trying to install SUNWdbus from SXCE.
> BeleniX already includes
>    SUNWdbus.
> 
> Regards,
> Moinak.
> 
> >
> > Thanks,
> > Manish
> > ken mays wrote:
> >> You can use SUNWdbus from SXCE or the Dbus
> packages
> >> from the JDS project as a workaround.
> >>
> >> I advise the Qt 4.4.0 default options enabled as
> >> different KDE4 apps need them (or will request
> them).
> >>
> >> ~ Ken
> >>
> >>
> >> --- Manish Chakravarty <manishchaks at gmail.com>
> wrote:
> >>
> >>
> >>> On Wed, May 28, 2008 at 9:37 PM, ken mays
> >>> <maybird1776 at yahoo.com> wrote:
> >>>
> >>>> Qt 4.4.0 works fine with KDE 4.0.80 (KDE
> >>>>
> >>> 4.1beta1).
> >>>
> >>>> I'm using it for my builds.
> >>>>
> >>> Are you compiling it with or without DBus?
> >>>
> >>> If you are compiling with DBus, can you share
> the
> >>> recipe with me?
> >>> I am compiling my own DBus and Dbus-glib and
> >>> sandboxing it into /opt/kde4 .
> >>>
> >>> Thanks
> >>> Manish
> >>>
> >>>> ~ Ken
> >>>>
> >>>> --- Manish Chakravarty <manishchaks at gmail.com>
> >>>>
> >>> wrote:
> >>>
> >>>>> On Wed, May 28, 2008 at 7:46 PM, Moinak Ghosh
> >>>>> <moinakg at gmail.com> wrote:
> >>>>>
> >>>>>> Hi Manish,
> >>>>>>
> >>>>>>   In spite of you setting CC and CXX the Qt
> >>>>>>
> >>> build
> >>>
> >>>>> is clearly using
> >>>>>
> >>>>>> SUN Studio: "CC -R/opt/qt4/lib ...". You need
> >>>>>>
> >>> to
> >>>
> >>>>> pass the flag:
> >>>>>
> >>>>>> "-platform solaris-g++" to Qt4's configure.
> >>>>>>
> >>>>> Thanks a lot for the tip Moinak!
> >>>>>
> >>>>>> There is already a Qt4 spec file in SFE see:
> >>>>>>
> >>>>>>
> >>
>
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEqt.spec?revision=1121&view=markup
> >>
> >>>>> As you know , we need to build qt-copy for
> KDE4,
> >>>>> Qt4 stable might/might not work for KDE4.
> >>>>>
> >>>>>
> >>>>> [..snip..]
> >>>>>
> _______________________________________________
> >>>>> belenix-dev mailing list
> >>>>> belenix-dev at opensolaris.org
> >>>>>
> >>>>>
> >>
>
http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>> Manish Chakravarty
> >>> http://manish-chaks.livejournal.com/
> >>>
> >>>
> >>
> >>
> >>
> >>
> >>
> >
> > _______________________________________________
> > belenix-dev mailing list
> > belenix-dev at opensolaris.org
> >
>
http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> >
> 



      


From ananth.shrinivas at gmail.com  Wed May 28 13:09:52 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Thu, 29 May 2008 01:39:52 +0530
Subject: [belenix-dev] belenix.org - new theme prototype
Message-ID: <f5ff03920805281309h18534420q905a0edb0e037c40@mail.gmail.com>

Hi Guys,

Based on some offline discussions we had, I did a quick prototype of a new
theme for the Belenix site. Have attached a screenshot for your viewing
pleasure (or displeasure).

This is an XHTML/CSS only prototype based on an existing template.
Converting this to a Drupal theme is a completely different ball-game - for
which I really have no hours left to take off my sleeping schedule. If any
of you or your friends or college kids you know etc.. want to experiment
creating a Drupal theme, I would be glad to share what I know.

Meanwhile any early feedback on the theme - Say you don't like green and
want the color of Ubuntu Human (Excreta ?) theme - Rot in Hell ;-)

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080529/936eeebf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot1.png
Type: image/png
Size: 396963 bytes
Desc: not available
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080529/936eeebf/attachment.png>

From shivakumar.gn at gmail.com  Wed May 28 18:32:34 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Thu, 29 May 2008 07:02:34 +0530
Subject: [belenix-dev] belenix.org - new theme prototype
In-Reply-To: <f5ff03920805281309h18534420q905a0edb0e037c40@mail.gmail.com>
References: <f5ff03920805281309h18534420q905a0edb0e037c40@mail.gmail.com>
Message-ID: <319ee2b10805281832q15ac0d0ejf01111535fe8d947@mail.gmail.com>

On Thu, May 29, 2008 at 1:39 AM, Ananth Shrinivas
<ananth.shrinivas at gmail.com> wrote:
> Hi Guys,
>
> Based on some offline discussions we had, I did a quick prototype of a new
> theme for the Belenix site. Have attached a screenshot for your viewing
> pleasure (or displeasure).
>

Simplicity rules.

> If any of you or your friends or college kids you know etc.. want to
> experiment creating a Drupal theme, I would be glad to share what I know.
>
> Meanwhile any early feedback on the theme - Say you don't like green and
> want the color of Ubuntu Human (Excreta ?) theme - Rot in Hell ;-)
>

I do not like Ubuntu Human theme, I do not have a fancy for the green
either, I do have comment, but I do not want to rot in hell :)
Let the person who picks the ball and runs decide...

-Shiv


From manishchaks at gmail.com  Thu May 29 00:04:43 2008
From: manishchaks at gmail.com (Manish Chakravarty)
Date: Thu, 29 May 2008 12:34:43 +0530
Subject: [belenix-dev] belenix.org - new theme prototype
In-Reply-To: <319ee2b10805281832q15ac0d0ejf01111535fe8d947@mail.gmail.com>
References: <f5ff03920805281309h18534420q905a0edb0e037c40@mail.gmail.com>
	<319ee2b10805281832q15ac0d0ejf01111535fe8d947@mail.gmail.com>
Message-ID: <b4dbee910805290004q259e5e28jac0d7256234f79fa@mail.gmail.com>

The theme looks cool!
The theme however does not match with the BeleniX default theme/splash
screen itself.

How about replacing the green with the dark blue of BeleniX?
OR
How about replacing the big green bar at the top with the picture
shown while KDE initializes?
That would look cooool!

If you can pass on the theme to me, I could make the modification.




On Thu, May 29, 2008 at 7:02 AM, S h i v <shivakumar.gn at gmail.com> wrote:
> On Thu, May 29, 2008 at 1:39 AM, Ananth Shrinivas
> <ananth.shrinivas at gmail.com> wrote:
>> Hi Guys,
>>
>> Based on some offline discussions we had, I did a quick prototype of a new
>> theme for the Belenix site. Have attached a screenshot for your viewing
>> pleasure (or displeasure).
>>
>
> Simplicity rules.
>
>> If any of you or your friends or college kids you know etc.. want to
>> experiment creating a Drupal theme, I would be glad to share what I know.
>>
>> Meanwhile any early feedback on the theme - Say you don't like green and
>> want the color of Ubuntu Human (Excreta ?) theme - Rot in Hell ;-)
>>
>
> I do not like Ubuntu Human theme, I do not have a fancy for the green
> either, I do have comment, but I do not want to rot in hell :)
> Let the person who picks the ball and runs decide...
>
> -Shiv
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
>



-- 
Manish Chakravarty
http://manish-chaks.livejournal.com/


From shivakumar.gn at gmail.com  Thu May 29 20:35:17 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Fri, 30 May 2008 09:05:17 +0530
Subject: [belenix-dev] Fwd: Announcing Hackathon event this Saturday
	(05/31/08)
In-Reply-To: <1212111437.30065.120.camel@dmitry-laptop>
References: <1212111437.30065.120.camel@dmitry-laptop>
Message-ID: <319ee2b10805292035k49b08a88kc5b32ac69ae00ae2@mail.gmail.com>

FYI.

If you like the combination of opensolaris kernel and a ubuntu
userland and are a open source developer, this might be of interest to
you.
NexentaOS is a registered project on launchpad.net (ubuntu's
collaboration platform).
NCP 1.0 is based on Ubuntu Dapper sources. NCP will move to 2.0 and be
based on Ubuntu Hardy. There is a hackathon planned around this
effort.

-Shiv


---------- Forwarded message ----------
From: Erast Benson <erast at gnusolaris.org>
Date: Fri, May 30, 2008 at 7:07 AM
Subject: Announcing Hackathon event this Saturday (05/31/08)
To: gnusol-devel <gnusol-devel at gnusolaris.org>
Cc: gnusol-users <gnusol-users at lists.sonic.net>


Dear NexentaOS Developers and Users!

Starting this Saturday, we are inviting all Debian/Nexenta and
OpenSolaris developers and users to participate in our first Hackathon
event.

Hackathon starts on this Saturday 05/31/2008 and continues during first
week of June. Development coordinated at #nexenta on freenode IRC.

We are migrating from Ubuntu Dapper to Ubuntu Hardy user land and will
be hacking on very initial version of NCP 2.0.

You don't need to install Nexenta, (ZFS-powered) build environment and
SSH access to the dedicated Zone will be automatically (see devzone
package) provided to interested developers by request on #nexenta
freenode IRC.

The work coordinated at #nexenta freenode IRC and this static web page:

http://www.nexenta.org/Hackathon

ZFS-powered Nexenta Zones managed on specially prepared NexentaOS build
servers connected to the public Internet. Servers and Internet
collocation kindly provided by Stanford University, CA.

Join now and make a difference! It is going to be fun!

---
The Nexenta Team

_______________________________________________
gnusol-devel mailing list
gnusol-devel at lists.sonic.net
http://lists.sonic.net/mailman/listinfo/gnusol-devel


From maybird1776 at yahoo.com  Fri May 30 06:18:06 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Fri, 30 May 2008 06:18:06 -0700 (PDT)
Subject: [belenix-dev] Request: Nvidia Solaris driver 173.14.05 integration
Message-ID: <838129.54072.qm@web34207.mail.mud.yahoo.com>

I'd like to suggest the new Nvidia Soalris driver 173.14.05 for the Belenix 0.7.1 integration project for laptop support of the newer Nvidia 8xxx/9xxx graphic chips and for support for Nvidia Quadro FX 5600/4600 SDI and Quadro G-Sync II cards in Sun Ultra 25/45 workstations.

This also provides support for the upcoming Xorg 7.4 release!!!!

Ref: http://www.nvidia.com/object/solaris_display_173.14.05.html

Sun has EOLed some of the older Nvidia Quadro 4500 and below cards in place of the Nvidia Quadro 4600/5600 cards - and currently lacks support of the newer Nvidia G80-based cards which is a showstopper for graphic professionals.

~ Ken Mays




      


From shivakumar.gn at gmail.com  Fri May 30 17:32:05 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sat, 31 May 2008 06:02:05 +0530
Subject: [belenix-dev] Request: Nvidia Solaris driver 173.14.05
	integration
In-Reply-To: <838129.54072.qm@web34207.mail.mud.yahoo.com>
References: <838129.54072.qm@web34207.mail.mud.yahoo.com>
Message-ID: <319ee2b10805301732t580bb1ffre172585eae7eaa6d@mail.gmail.com>

On Fri, May 30, 2008 at 6:48 PM, ken mays <maybird1776 at yahoo.com> wrote:
> I'd like to suggest the new Nvidia Soalris driver 173.14.05 for the Belenix 0.7.1 integration project for laptop support of the newer Nvidia 8xxx/9xxx graphic chips and for support for Nvidia Quadro FX 5600/4600 SDI and Quadro G-Sync II cards in Sun Ultra 25/45 workstations.
>
> This also provides support for the upcoming Xorg 7.4 release!!!!
>
> Ref: http://www.nvidia.com/object/solaris_display_173.14.05.html
>

Will do. Thanks for the notification.

-Shiv


From shivakumar.gn at gmail.com  Fri May 30 17:38:25 2008
From: shivakumar.gn at gmail.com (S h i v)
Date: Sat, 31 May 2008 06:08:25 +0530
Subject: [belenix-dev] Request: Nvidia Solaris driver 173.14.05
	integration
In-Reply-To: <838129.54072.qm@web34207.mail.mud.yahoo.com>
References: <838129.54072.qm@web34207.mail.mud.yahoo.com>
Message-ID: <319ee2b10805301738l4d507827u32b037117053468@mail.gmail.com>

On Fri, May 30, 2008 at 6:48 PM, ken mays <maybird1776 at yahoo.com> wrote:
> I'd like to suggest the new Nvidia Soalris driver 173.14.05 for the Belenix 0.7.1 integration project for laptop support of the newer Nvidia 8xxx/9xxx graphic chips and for support for Nvidia Quadro FX 5600/4600 SDI and Quadro G-Sync II cards in Sun Ultra 25/45 workstations.
>

I went to the feature requests page and see that Moinak has already
entered the info:
http://sourceforge.net/tracker/index.php?func=detail&aid=1979311&group_id=216118&atid=1036406

-Shiv


From moinakg at gmail.com  Sat May 31 03:18:51 2008
From: moinakg at gmail.com (Moinak Ghosh)
Date: Sat, 31 May 2008 15:48:51 +0530
Subject: [belenix-dev] New BeleniX server coming up
Message-ID: <46fe20470805310318qc6a8cd6o16d052ce8f9ab586@mail.gmail.com>

Hi Folks,

   Due to the amazing support from the folks at Genunix like Al Hopper
a new server for BeleniX is being setup. It will host the website, IPS
repository and will also have SCM stuff going forward. I have been messing
around on this new machine from yesterday and have managed to move
the Drupal based website to this machine.

You can access it via http://204.152.191.108/. DNS is yet to be configured
since this is work in progress. I dumped the MySQL DB (mysqldump) in the
main website and imported it into a MySQL 5 DB running in this machine
(inside a zone). Then I copied the entire belenix website, except the
downloadable ISO images in binfiles to this machine. I tried to retain the
same directory structure to satisfy references to files and configured Apache
to have virtualhosts for belenix.org and belenix.com.

Request you all to browse the new website left right and center and report
problems if any. One known problem that I am kinda confused is user
logins via http://204.152.191.108/?q=user does not seem to work. The
login is successful but subsequent access to any other page loses the
login session!

In addition we are looking for webmasters to manage the BeleniX website.
There are a bunch of tasks right now, like upgrading to Drupal 6, updating
the website with a new theme etc.

Regards,
Moinak.


From ananth.shrinivas at gmail.com  Sat May 31 06:23:06 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Sat, 31 May 2008 18:53:06 +0530
Subject: [belenix-dev] New BeleniX server coming up
In-Reply-To: <46fe20470805310318qc6a8cd6o16d052ce8f9ab586@mail.gmail.com>
References: <46fe20470805310318qc6a8cd6o16d052ce8f9ab586@mail.gmail.com>
Message-ID: <f5ff03920805310623l43d139cdtf5810fb86b383d5d@mail.gmail.com>

>
> Request you all to browse the new website left right and center and report
> problems if any. One known problem that I am kinda confused is user
> logins via http://204.152.191.108/?q=user does not seem to work. The
> login is successful but subsequent access to any other page loses the
> login session!



Maddening. I would like to do some (d)tracing on that box. Will talk to you
offline about the login details Moinak.

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080531/36cd29af/attachment.html>

From ananth.shrinivas at gmail.com  Sat May 31 07:25:00 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Sat, 31 May 2008 19:55:00 +0530
Subject: [belenix-dev] KDE Battery Applet (WAS: Re: New BeleniX server
	coming up)
Message-ID: <f5ff03920805310725x51603fdched8a57dadfa80422@mail.gmail.com>

Hey Avinash,

First things first - Please don't reply to an existing thread when starting
a new topic. It confuses everybody.

On Sat, May 31, 2008 at 7:26 PM, Avinash Joshi <avinashtjoshi at gmail.com>
wrote:

> Hi belenix users.
>   I am using belenix on my laptop. I just wanted to know if i can get the
> BATTERY APPLET for the K-Desktop Environment. It is not in Belenix (KDE on
> opensolaris doesnt support battery applet as far as i know). Can I know more
> on this?
>

The KDE battery applet was written for Linux. Somone needs to port it to
Solaris - just like darren moffat did the GNOME battery applet:
http://blogs.sun.com/darren/entry/gnome_battery_status_meter_for

However, it should be much simpler now because acpidrv actually gives out
statistics via kstat. You don't need to do ugly ACPI_POWER_STATUS and
ACPI_BATTERY_STATUS ioctl()s. Sample this command: "kstat -p -m battery"

Why don't you take it up as a small project and contribute this feature to
belenix ? ;-)

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080531/4b784f34/attachment.html>

From avinashtjoshi at gmail.com  Sat May 31 06:56:42 2008
From: avinashtjoshi at gmail.com (Avinash Joshi)
Date: Sat, 31 May 2008 19:26:42 +0530
Subject: [belenix-dev] [belenix-discuss] New BeleniX server coming up
In-Reply-To: <46fe20470805310318qc6a8cd6o16d052ce8f9ab586@mail.gmail.com>
References: <46fe20470805310318qc6a8cd6o16d052ce8f9ab586@mail.gmail.com>
Message-ID: <3af7c1a80805310656g6d8af5e1j7998d94540dad10e@mail.gmail.com>

Hi belenix users.
  I am using belenix on my laptop. I just wanted to know if i can get the
BATTERY APPLET for the K-Desktop Environment. It is not in Belenix (KDE on
opensolaris doesnt support battery applet as far as i know). Can I know more
on this?

Regards,
Avinash Joshi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080531/4344ac57/attachment.html>

From maybird1776 at yahoo.com  Sat May 31 10:08:40 2008
From: maybird1776 at yahoo.com (ken mays)
Date: Sat, 31 May 2008 10:08:40 -0700 (PDT)
Subject: [belenix-dev] [belenix-discuss] New BeleniX server coming up
In-Reply-To: <3af7c1a80805310656g6d8af5e1j7998d94540dad10e@mail.gmail.com>
Message-ID: <22346.52543.qm@web34207.mail.mud.yahoo.com>

You can get KBatt at:
1. http://sourceforge.net/projects/kbatt/

~ Ken



--- On Sat, 5/31/08, Avinash Joshi <avinashtjoshi at gmail.com> wrote:

> From: Avinash Joshi <avinashtjoshi at gmail.com>
> Subject: Re: [belenix-dev] [belenix-discuss] New BeleniX server coming up
> To: "Belenix Discuss" <belenix-discuss at opensolaris.org>, "BeleniX Development" <belenix-dev at opensolaris.org>
> Date: Saturday, May 31, 2008, 9:56 AM
> Hi belenix users.
>   I am using belenix on my laptop. I just wanted to know if
> i can get the
> BATTERY APPLET for the K-Desktop Environment. It is not in
> Belenix (KDE on
> opensolaris doesnt support battery applet as far as i
> know). Can I know more
> on this?
> 
> Regards,
> Avinash
> Joshi_______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev


      


From ananth.shrinivas at gmail.com  Sat May 31 10:49:06 2008
From: ananth.shrinivas at gmail.com (Ananth Shrinivas)
Date: Sat, 31 May 2008 23:19:06 +0530
Subject: [belenix-dev] [belenix-discuss] New BeleniX server coming up
In-Reply-To: <22346.52543.qm@web34207.mail.mud.yahoo.com>
References: <3af7c1a80805310656g6d8af5e1j7998d94540dad10e@mail.gmail.com>
	<22346.52543.qm@web34207.mail.mud.yahoo.com>
Message-ID: <f5ff03920805311049l3540f98bve32cf6d4b2bf309b@mail.gmail.com>

Hi Ken,

On Sat, May 31, 2008 at 10:38 PM, ken mays <maybird1776 at yahoo.com> wrote:

> You can get KBatt at:
> 1. http://sourceforge.net/projects/kbatt/


Does kbatt work out of the box on Solaris ? Most of these power applets
assume existence of the /proc/apm kludge.

Ananth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/belenix-dev/attachments/20080531/24208d27/attachment.html>

From ajey at thoughtworks.net  Tue May 20 11:18:42 2008
From: ajey at thoughtworks.net (Ajey Gore)
Date: Tue, 20 May 2008 13:18:42 -0500
Subject: [belenix-dev] Commit notifications for belenix repository
In-Reply-To: <95F23ACD-4A05-4AC9-B3EB-36BAFF131BB0@gmail.com>
Message-ID: <C4588032.64E6%ajey@thoughtworks.net>

May you might have to stop it, if there is too much and convert that to
daily changes instead of per commit notifications.


On 5/18/08 3:32 PM, "Ketan Padegaonkar" <ketanpadegaonkar at gmail.com> wrote:

> I don't think I'd mind if this is not too much noise in the midst of
> regular mails, if there's too much traffic, then a -commit list makes
> more sense.
> 
> Cheers,
> Ketan Padegaonkar
> I blog... therefore I am... http://ketan.padegaonkar.name
> http://swtbot.org/ - a functional testing tool for SWT/Eclipse
> 
> On 18-May-08, at 2:53 PM, Moinak Ghosh wrote:
> 
>> I was thinking whether it will be good to have all belenix repository
>> commit notifications to come to belenix-dev list. That way everyone
>> interested belenix development will be aware of what changes are
>> going on.
>> 
>> Does anyone has objections ?
>> 
>> Regards,
>> Moinak.
>> _______________________________________________
>> belenix-dev mailing list
>> belenix-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/belenix-dev
> 
> 
> _______________________________________________
> belenix-dev mailing list
> belenix-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/belenix-dev