From tonino-pablo at lycos.com  Sun Apr  5 00:42:28 2009
From: tonino-pablo at lycos.com (x x)
Date: Sat, 04 Apr 2009 18:42:28 -0400 (EDT)
Subject: bsd.mp
Message-ID: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>

An HTML attachment was scrubbed...
URL: http://mailman.theapt.org/pipermail/openbsd-newbies/attachments/20090404/014f9303/attachment.html 

From brakeb at gmail.com  Sun Apr  5 02:24:43 2009
From: brakeb at gmail.com (Bryan)
Date: Sun, 5 Apr 2009 00:24:43 +0000
Subject: bsd.mp
In-Reply-To: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
References: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
Message-ID: <6532b7c80904041724v1c6f2be0wf67bd8401e296065@mail.gmail.com>

I do "cp bsd bsd.sp && cp bsd.mp bsd"  I was told once that using cp
is better in the nearly unlikely event that something panics while you
are doing the copy...

Regards,
Bryan

On Sat, Apr 4, 2009 at 22:42, x x <tonino-pablo at lycos.com> wrote:
> Is it ok to do cp bsd.rd bsd.mp, or should I do mv bsd.mp bsd, what is the
> best way to make .mp the default boot kernel?

From tony at servacorp.com  Sun Apr  5 03:00:06 2009
From: tony at servacorp.com (Tony Abernethy)
Date: Sat, 4 Apr 2009 20:00:06 -0500
Subject: bsd.mp
In-Reply-To: <6532b7c80904041724v1c6f2be0wf67bd8401e296065@mail.gmail.com>
Message-ID: <F3558BB638FC4955AE96D9E224F0E39F@TONY>

Bryan wrote
> 
> I do "cp bsd bsd.sp && cp bsd.mp bsd"  I was told once that using cp
> is better in the nearly unlikely event that something panics while you
> are doing the copy...
> 
> Regards,
> Bryan

It is very good practice to do things in an order so that you survive
no matter WHEN something bad happens. Like power supply up in flames.
Good practice to ALWAYS do things that way.  You survive longer.

cp versus mv can be misleading,
if / is much much too big and the copy sits outside where bios can reach
then the system becomes unbootable.
(that's why small root partition -- among others)

Any differences in efficiency between cp and mv 
with be swamped by any time taken thinking about it.

There is also /etc/boot.conf  (man boot.conf) which can control a lot.

bsd.rd is the somewhat limited kernel used to install/update/upgrade

> 
> On Sat, Apr 4, 2009 at 22:42, x x <tonino-pablo at lycos.com> wrote:
> > Is it ok to do cp bsd.rd bsd.mp, or should I do mv bsd.mp 
> bsd, what is the
> > best way to make .mp the default boot kernel?
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
> 


From andres at msu.edu  Sun Apr  5 02:39:31 2009
From: andres at msu.edu (STeve Andre')
Date: Sat, 4 Apr 2009 20:39:31 -0400
Subject: bsd.mp
In-Reply-To: <6532b7c80904041724v1c6f2be0wf67bd8401e296065@mail.gmail.com>
References: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
	<6532b7c80904041724v1c6f2be0wf67bd8401e296065@mail.gmail.com>
Message-ID: <200904042039.32428.andres@msu.edu>

I have three kernels: bsd.sp, bsd.mp and bsd.ntfs.  I normally
copy bsd.mp to bsd and reboot.  By keeping seperate kernels
which are copied to /bsd, you can't mix them up.

--STeve Andre'

On Saturday 04 April 2009 20:24:43 Bryan wrote:
> I do "cp bsd bsd.sp && cp bsd.mp bsd"  I was told once that using cp
> is better in the nearly unlikely event that something panics while you
> are doing the copy...
>
> Regards,
> Bryan
>
> On Sat, Apr 4, 2009 at 22:42, x x <tonino-pablo at lycos.com> wrote:
> > Is it ok to do cp bsd.rd bsd.mp, or should I do mv bsd.mp bsd, what is
> > the best way to make .mp the default boot kernel?
>
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies



From josh at jggimi.homeip.net  Sun Apr  5 02:10:01 2009
From: josh at jggimi.homeip.net (Josh Grosse)
Date: Sat, 4 Apr 2009 20:10:01 -0400
Subject: bsd.mp
In-Reply-To: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
References: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
Message-ID: <20090405001001.GA23742@jggimi.homeip.net>

On Sat, Apr 04, 2009 at 06:42:28PM -0400, x x wrote:
> Is it ok to do cp bsd.rd bsd.mp, or should I do mv bsd.mp bsd, what is the best way to make .mp the default boot kernel?

The best practice is to use boot.conf(5), and "set image bsd.mp".  This will
avoid any confusion, avoid problems with upgrade, and allow you to manually
boot the uniprocessor kernel if necessary.

From mike at erdelynet.com  Sun Apr  5 05:20:32 2009
From: mike at erdelynet.com (Mike Erdely)
Date: Sat, 4 Apr 2009 23:20:32 -0400
Subject: bsd.mp
In-Reply-To: <20090405001001.GA23742@jggimi.homeip.net>
References: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
	<20090405001001.GA23742@jggimi.homeip.net>
Message-ID: <20090405032032.GW31001@erdelynet.com>

On Sat, Apr 04, 2009 at 08:10:01PM -0400, Josh Grosse wrote:
> On Sat, Apr 04, 2009 at 06:42:28PM -0400, x x wrote:
> > Is it ok to do cp bsd.rd bsd.mp, or should I do mv bsd.mp bsd, what is the best way to make .mp the default boot kernel?
> 
> The best practice is to use boot.conf(5), and "set image bsd.mp".  This will
> avoid any confusion, avoid problems with upgrade, and allow you to manually
> boot the uniprocessor kernel if necessary.

This is excellent advice and has another bonus: when you upgrade, you
won't have to remember to `cp /bsd.mp /bsd` every time.

-ME

From marmot at pennswoods.net  Sun Apr  5 05:07:39 2009
From: marmot at pennswoods.net (Woodchuck)
Date: Sat, 4 Apr 2009 23:07:39 -0400 (EDT)
Subject: bsd.mp
In-Reply-To: <20081206101218.GC8089@gir.theapt.org>
References: <20081206033958.HM.0000000000004dF@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
	<20081206101218.GC8089@gir.theapt.org>
Message-ID: <Pine.BSO.4.64.0904042306380.12380@rachel.chuck>

On Sat, 6 Dec 2008, Peter Hessler wrote:

> you want to do `cp /bsd.mp /bsd`.  By default, the bootloader loads /bsd.

	The problem is if the system crashes or file system is corrupted
or during the cp.

Dave

From marmot at pennswoods.net  Sun Apr  5 05:14:02 2009
From: marmot at pennswoods.net (Woodchuck)
Date: Sat, 4 Apr 2009 23:14:02 -0400 (EDT)
Subject: bsd.mp
In-Reply-To: <6532b7c80904041724v1c6f2be0wf67bd8401e296065@mail.gmail.com>
References: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
	<6532b7c80904041724v1c6f2be0wf67bd8401e296065@mail.gmail.com>
Message-ID: <Pine.BSO.4.64.0904042308120.12380@rachel.chuck>

On Sun, 5 Apr 2009, Bryan wrote:

> I do "cp bsd bsd.sp && cp bsd.mp bsd"  I was told once that using cp
> is better in the nearly unlikely event that something panics while you
> are doing the copy...
> 
> Regards,
> Bryan

I think you're backwards about this.  The second cp is the dangerous
one, and if it fails, might leave /bsd corrupted.  The idea is not
to save the trouble of using the console, but to insure that the
directory entry /bsd *always* points to a valid kernel.  (Consider
a machine to which console access is difficult or impossible).

mv and ln are very short operations.

mv is a wrapper to rename(2).

ln is just a wrapper to link(2).

See my other post on this thread for the "official" method.

Dave
--
        The problem with socialism is that you eventually
        run out of other people's money.
                       -- Margaret Thatcher

From marmot at pennswoods.net  Sun Apr  5 05:31:59 2009
From: marmot at pennswoods.net (Woodchuck)
Date: Sat, 4 Apr 2009 23:31:59 -0400 (EDT)
Subject: bsd.mp
In-Reply-To: <F3558BB638FC4955AE96D9E224F0E39F@TONY>
References: <F3558BB638FC4955AE96D9E224F0E39F@TONY>
Message-ID: <Pine.BSO.4.64.0904042314560.12380@rachel.chuck>

On Sat, 4 Apr 2009, Tony Abernethy wrote:

> Any differences in efficiency between cp and mv 
> with be swamped by any time taken thinking about it.

Huh?  the difference in efficiency isn't the issue, the issue is the
state of the disc directory "/".

cp /bsd.foo /bsd

Suppose the / fs is the old, standard ffs and is mounted async.

It may be "some time" before the file buffers are flushed (synced).
A crash during that interval can result in a corrupted /bsd.  This,
I think is the old bugaboo.  

mv will be a call to "rename(2)", and in most sane implementations
of ffs, the resulting changed directory entry (i.e. the changed inode)
will be flushed to disk immediately.

There was a time when disk writes were much slower than now.  

Still, we should consider the time taken by cp to be "long", and
since I believe that cp is "interruptable", cp may be paged out for
higher priority activities.  This being the case, we cannot guarantee
that cp will complete in certain time, or if it will complete at
all.  Cp makes many system calls, and can be interrupted or even
swapped out.  This is a distinct possiblilty on a busy machine or
one that is "swapping".  OpenBSD is not magic -- and its behavior
when swapping is actually miserable.  (1GHz dual Pentium III:
five-ten second delays refreshing the screen with mozilla when that
bloated, memory-leaking, crash-prone pig has consumed 400 MB of
core and is eating into swap -- this even when X itself is offloaded
to an X-terminal).

so anything with /bsd as the destination of a cp(3) is "dangerous".

Dave

From marmot at pennswoods.net  Sun Apr  5 05:06:25 2009
From: marmot at pennswoods.net (Woodchuck)
Date: Sat, 4 Apr 2009 23:06:25 -0400 (EDT)
Subject: bsd.mp
In-Reply-To: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
References: <20090404184228.HM.0000000000005gY@tonino-pablo.mail-wwl12.bo3.lycos.com.lycos.com>
Message-ID: <Pine.BSO.4.64.0904042241460.12380@rachel.chuck>

On Sat, 4 Apr 2009, x x wrote:

> Is it ok to do cp bsd.rd bsd.mp, or should I do mv bsd.mp bsd, what is
> the best way to make .mp the default boot kernel?

I keep these kernels handy:
	bsd.sg
	bsd.mp
	bsd.rd

(bsd.rd is handy to boot when one wants to "do strange things" to
one's root partition.  It is nice to boot bsd.rd single-user.)

To decide which one to boot by default, I use:

	ln /bsd.mp /bsd		# don't use -s for this, please

Using a hard link avoids problems involved with cp.
The problems with cp arise should the system crash or the file system
be corrupted at an inopportune time during the cp.  

But I actually use ln because I use small root partitions, and am
stingy with disk space.  Some newbies fear ln because it is not
present in inferior file/operating systems.  But ln is ancient in
Unix, and is your friend.  Soft links are a little goofy, and are
the mother of tricks and confusion, but the hard link is simple and
clean.  A hard link is just another directory entry pointing to the
same inode, and can be done very cleany (I hesitate to say "atomically",
but if not atomic, it is as close to that as it can get).

Should one build one's own kernel, the "official" Makefile installs
the new kernel in / with:

(The current working directory is something like 
/usr/src/sys/arch/i386/compile/GENERIC.MP, note that.)

        rm -f /obsd
        ln /bsd /obsd
        cp bsd /nbsd
        mv /nbsd /bsd

This is the "official" safe way.

if / has bsd.sg, bsd.mp and bsd.rd in it, then the equivalent would be

	cd /
	rm -f obsd
	ln /bsd /obsd	# (presumably, /bsd exists )
	cp /bsd.mp /nbsd
	mv /nbsd /bsd

This might be described as the "belt and suspenders" method.

Dave
--
        The problem with socialism is that you eventually
        run out of other people's money.
                       -- Margaret Thatcher

From bsd4me at cableone.net  Mon Apr 13 05:50:16 2009
From: bsd4me at cableone.net (Michael)
Date: Sun, 12 Apr 2009 21:50:16 -0600
Subject: opera
Message-ID: <20090413035016.GB2627@mariah2.my.domain>


I installed Opera from ports. After installation, it runs fine till I reboot and then after rebooting, I get:
$ /usr/local/bin/opera &                                                       
[1] 20625
$ Abort trap 
Abort trap

After the first couple of times of getting this, I did a pkg_delete opera, reinstalled from ports and opera ran fine till I had to reboot.

I googled, but didn't really find anything quit the same as what is happening here. The ports installation installed the fedora pkg, so that's covered. 

Any ideas/solutions? 
btw- I forgot to mention I'm running 4.4 with security updates.
I don't know what info would be helpful.

Thanks.
Mike

From sparctacus at gmail.com  Mon Apr 13 06:05:15 2009
From: sparctacus at gmail.com (Bryan Irvine)
Date: Sun, 12 Apr 2009 21:05:15 -0700
Subject: opera
In-Reply-To: <20090413035016.GB2627@mariah2.my.domain>
References: <20090413035016.GB2627@mariah2.my.domain>
Message-ID: <53d706300904122105i51e9092bv565005f76e2833bd@mail.gmail.com>

On Sun, Apr 12, 2009 at 8:50 PM, Michael <bsd4me at cableone.net> wrote:
>
> I installed Opera from ports. After installation, it runs fine till I reboot and then after rebooting, I get:
> $ /usr/local/bin/opera &
> [1] 20625
> $ Abort trap
> Abort trap
>
> After the first couple of times of getting this, I did a pkg_delete opera, reinstalled from ports and opera ran fine till I had to reboot.
>
> I googled, but didn't really find anything quit the same as what is happening here. The ports installation installed the fedora pkg, so that's covered.
>
> Any ideas/solutions?

The installer runs sysctl kern.emul.linux=1 when you reboot it sets it back.
/usr/ports/www/opera/pkg/PLIST: @sysctl kern.emul.linux=1

uncomment the following in /etc/sysctl.conf:
#kern.emul.linux=1

-Bryan

From bsd4me at cableone.net  Mon Apr 13 15:20:36 2009
From: bsd4me at cableone.net (Michael)
Date: Mon, 13 Apr 2009 07:20:36 -0600
Subject: opera
In-Reply-To: <53d706300904122105i51e9092bv565005f76e2833bd@mail.gmail.com>
References: <20090413035016.GB2627@mariah2.my.domain>
	<53d706300904122105i51e9092bv565005f76e2833bd@mail.gmail.com>
Message-ID: <20090413132036.GA13205@mariah2.my.domain>

On Sun, Apr 12, 2009 at 09:05:15PM -0700, Bryan Irvine wrote:
> On Sun, Apr 12, 2009 at 8:50 PM, Michael <bsd4me at cableone.net> wrote:
> >
> > I installed Opera from ports. After installation, it runs fine till I reboot and then after rebooting, I get:
> > $ /usr/local/bin/opera &
> > [1] 20625
> > $ Abort trap
> > Abort trap
> >
> > After the first couple of times of getting this, I did a pkg_delete opera, reinstalled from ports and opera ran fine till I had to reboot.
> >
> > I googled, but didn't really find anything quit the same as what is happening here. The ports installation installed the fedora pkg, so that's covered.
> >
> > Any ideas/solutions?
> 
> The installer runs sysctl kern.emul.linux=1 when you reboot it sets it back.
> /usr/ports/www/opera/pkg/PLIST: @sysctl kern.emul.linux=1
> 
> uncomment the following in /etc/sysctl.conf:
> #kern.emul.linux=1
> 
> -Bryan

Thank-you. That was it. Obviously I didn't read the PLIST, but now I know :) 

Mike

> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies

From stu at spacehopper.org  Mon Apr 13 15:27:46 2009
From: stu at spacehopper.org (Stuart Henderson)
Date: Mon, 13 Apr 2009 13:27:46 +0000 (UTC)
Subject: lbdb question
References: <20090314154554.GA32584@mariahII.my.domain>
Message-ID: <slrngu6fei.c6o.stu@naiad.spacehopper.org>

On 2009-03-14, Michael <bsd4me at cableone.net> wrote:
> I haven't been able to get lbdbq to work or even run lbdbq or lbdb-munge.

this is a port bug. if the bash shell is installed at package build time,
the resulting package also requires bash to be installed. "pkg_add bash"
will help you for now, and i've just fixed the port so it won't happen
for packages built in the future. 



From bsd4me at cableone.net  Tue Apr 14 01:10:55 2009
From: bsd4me at cableone.net (Michael)
Date: Mon, 13 Apr 2009 17:10:55 -0600
Subject: lbdb question
In-Reply-To: <slrngu6fei.c6o.stu@naiad.spacehopper.org>
References: <20090314154554.GA32584@mariahII.my.domain>
	<slrngu6fei.c6o.stu@naiad.spacehopper.org>
Message-ID: <20090413231055.GA3146@mariah2.my.domain>

On Mon, Apr 13, 2009 at 01:27:46PM +0000, Stuart Henderson wrote:
> On 2009-03-14, Michael <bsd4me at cableone.net> wrote:
> > I haven't been able to get lbdbq to work or even run lbdbq or lbdb-munge.
> 
> this is a port bug. if the bash shell is installed at package build time,
> the resulting package also requires bash to be installed. "pkg_add bash"
> will help you for now, and i've just fixed the port so it won't happen
> for packages built in the future. 
> 
> 

Thanks Stuart.
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies

From bsd4me at cableone.net  Sat Apr 18 04:25:10 2009
From: bsd4me at cableone.net (Michael)
Date: Fri, 17 Apr 2009 20:25:10 -0600
Subject: lbdb question
In-Reply-To: <slrngu6fei.c6o.stu@naiad.spacehopper.org>
References: <20090314154554.GA32584@mariahII.my.domain>
	<slrngu6fei.c6o.stu@naiad.spacehopper.org>
Message-ID: <20090418022510.GA60@mariahII.my.domain>

On Mon, Apr 13, 2009 at 01:27:46PM +0000, Stuart Henderson wrote:
> On 2009-03-14, Michael <bsd4me at cableone.net> wrote:
> > I haven't been able to get lbdbq to work or even run lbdbq or lbdb-munge.
> 
> this is a port bug. if the bash shell is installed at package build time,
> the resulting package also requires bash to be installed. "pkg_add bash"
> will help you for now, and i've just fixed the port so it won't happen
> for packages built in the future. 
> 
Stuart, I don't know if this will help, but on two systems that I have lbdb installed, I have also had to install gawk. Once bash and gawk were installed, lbdbq worked.

Mike

> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies

From stu at spacehopper.org  Sat Apr 18 11:11:43 2009
From: stu at spacehopper.org (Stuart Henderson)
Date: Sat, 18 Apr 2009 09:11:43 +0000 (UTC)
Subject: lbdb question
References: <20090314154554.GA32584@mariahII.my.domain>
	<slrngu6fei.c6o.stu@naiad.spacehopper.org>
	<20090418022510.GA60@mariahII.my.domain>
Message-ID: <slrnguj6af.7a3.stu@naiad.spacehopper.org>

On 2009-04-18, Michael <bsd4me at cableone.net> wrote:
> On Mon, Apr 13, 2009 at 01:27:46PM +0000, Stuart Henderson wrote:
>> On 2009-03-14, Michael <bsd4me at cableone.net> wrote:
>> > I haven't been able to get lbdbq to work or even run lbdbq or lbdb-munge.
>> 
>> this is a port bug. if the bash shell is installed at package build time,
>> the resulting package also requires bash to be installed. "pkg_add bash"
>> will help you for now, and i've just fixed the port so it won't happen
>> for packages built in the future. 
>> 
> Stuart, I don't know if this will help, but on two systems that
> I have lbdb installed, I have also had to install gawk. Once bash
> and gawk were installed, lbdbq worked.

It does, thanks for the report - I've just fixed it in the port.
Somebody went a bit over the top with the use of autoconf in lbdb.

Most port maintainers (well, the non-slack ones anyway..!) would
like to hear if people have a problem using their ports or the
packages produced by them; pkg_info <portname> shows who to get
in touch with.



From vim.unix at googlemail.com  Sat Apr 25 19:24:17 2009
From: vim.unix at googlemail.com (Pau)
Date: Sat, 25 Apr 2009 19:24:17 +0200
Subject: openoffice3 install from ports breaking
Message-ID: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>

Hello,

I tried to compile openoffice3 from ports in 4.5 after a fresh install
from the CDs. It gave me the following problem:

> ===>  Patching for gcc-4.2.20070307
> cd /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libstdc++-v3
> && AUTOCONF_VERSION=2.59 autoconf
> ===>  Configuring for gcc-4.2.20070307
> loading site script /usr/ports/infrastructure/db/config.site
> creating cache ./config.cache
> checking host system type... i386-unknown-openbsd4.5
> checking target system type... i386-unknown-openbsd4.5
> checking build system type... i386-unknown-openbsd4.5
> checking for a BSD compatible install... /usr/bin/install -c -o root -g bin
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for gcc... /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
> checking whether the C compiler
> (/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc -O2 -g ) works...
> no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.

I asked in ports@ and got the following answer:

"You need /usr/lib/libc.so.42.0
Of course, the doc says that you should use a package..."

Could somebody be as kind as to decrypt this oracle for me?

thanks a lot,

Pau

From ajacoutot at bsdfrog.org  Sat Apr 25 19:54:21 2009
From: ajacoutot at bsdfrog.org (Antoine Jacoutot)
Date: Sat, 25 Apr 2009 19:54:21 +0200 (CEST)
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
Message-ID: <alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>

On Sat, 25 Apr 2009, Pau wrote:

> Hello,
> 
> I tried to compile openoffice3 from ports in 4.5 after a fresh install
> from the CDs. It gave me the following problem:
> 
> > ===>  Patching for gcc-4.2.20070307
> > cd /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libstdc++-v3
> > && AUTOCONF_VERSION=2.59 autoconf
> > ===>  Configuring for gcc-4.2.20070307
> > loading site script /usr/ports/infrastructure/db/config.site
> > creating cache ./config.cache
> > checking host system type... i386-unknown-openbsd4.5
> > checking target system type... i386-unknown-openbsd4.5
> > checking build system type... i386-unknown-openbsd4.5
> > checking for a BSD compatible install... /usr/bin/install -c -o root -g bin
> > checking whether ln works... yes
> > checking whether ln -s works... yes
> > checking for gcc... /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
> > checking whether the C compiler
> > (/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc -O2 -g ) works...
> > no
> > configure: error: installation or configuration problem: C compiler
> > cannot create executables.
> 
> I asked in ports@ and got the following answer:
> 
> "You need /usr/lib/libc.so.42.0
> Of course, the doc says that you should use a package..."

You either need to get and install /usr/lib/libc.so.42.0 from a previous 
OpenBSD version because this lib was used to bootstrap ada.
Or, you can wait for 4.5 to came out and install gcc4 from package.


-- 
Antoine

From stu at spacehopper.org  Sun Apr 26 01:04:35 2009
From: stu at spacehopper.org (Stuart Henderson)
Date: Sat, 25 Apr 2009 23:04:35 +0000 (UTC)
Subject: openoffice3 install from ports breaking
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
Message-ID: <slrngv75o2.mo5.stu@naiad.spacehopper.org>

On 2009-04-25, Antoine Jacoutot <ajacoutot at bsdfrog.org> wrote:
> On Sat, 25 Apr 2009, Pau wrote:
>
>> Hello,
>> 
>> I tried to compile openoffice3 from ports in 4.5 after a fresh install
>> from the CDs. It gave me the following problem:
>> 
>> > ===>  Patching for gcc-4.2.20070307
>> > cd /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libstdc++-v3
>> > && AUTOCONF_VERSION=2.59 autoconf
>> > ===>  Configuring for gcc-4.2.20070307
>> > loading site script /usr/ports/infrastructure/db/config.site
>> > creating cache ./config.cache
>> > checking host system type... i386-unknown-openbsd4.5
>> > checking target system type... i386-unknown-openbsd4.5
>> > checking build system type... i386-unknown-openbsd4.5
>> > checking for a BSD compatible install... /usr/bin/install -c -o root -g bin
>> > checking whether ln works... yes
>> > checking whether ln -s works... yes
>> > checking for gcc... /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
>> > checking whether the C compiler
>> > (/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc -O2 -g ) works...
>> > no
>> > configure: error: installation or configuration problem: C compiler
>> > cannot create executables.
>> 
>> I asked in ports@ and got the following answer:
>> 
>> "You need /usr/lib/libc.so.42.0
>> Of course, the doc says that you should use a package..."
>
> You either need to get and install /usr/lib/libc.so.42.0 from a previous 
> OpenBSD version because this lib was used to bootstrap ada.
> Or, you can wait for 4.5 to came out and install gcc4 from package.
>
>

openoffice3 is *huge*. it will probably take more than 12 hours to
build, very much more if you don't have enough ram or have a slow cpu.
that is on top of gcc 4.2, the JDK and other dependencies.
it's definitely recommended to use the packages for this one if
you possibly can.

that said, and note that I haven't tested this, but you should be
able to build gcc 4.2 like this:

$ cd /usr/ports/lang/gcc/4.2
$ FLAVOR="c++ fortran objc" make

this is the default on cpu architectures other than i386 anyway so,
for example, if you're trying to build on amd64 you won't run into
this problem in the first place.

you will also need to adjust the amount of memory that a process is
permitted to use by adjusting the resource limits in login.conf.
increase datasize-max for the class your login account uses, and
either bump it up using "ulimit -d <number of K>", or by increasing
datasize-cur as well. you will need to logout and log back in for
this change to take effect. (if you're building ports as root,
first look at the various ports tutorials and learn about setting
SUDO in /etc/mk.conf, and if you still want to build as root,
you need to adjust the login.conf entry for the class "daemon"
which is also used for software run from /etc/rc.local).



From vim.unix at googlemail.com  Sun Apr 26 14:07:51 2009
From: vim.unix at googlemail.com (Pau)
Date: Sun, 26 Apr 2009 14:07:51 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
Message-ID: <30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>

something's broken....

I installed it with your FLAVOR and then went to
/usr/ports/editors/openoffice3 and... look below

I think I will wait for the gcc4.2 binary and then try again. I want
to compile openoffice on my own because i hope to get some speeding up
factor... probably I could get it by compiling rather than installing
the binary from an ftp srver...

Cheers,

Pau

hux# make install
===>  Checking files for openoffice-3.0.1
`/usr/ports/distfiles/openoffice/ooo-desktop-0.1.tar.gz' is up to date.
`/usr/ports/distfiles/openoffice/OOo_3.0.1_src_binfilter.tar.bz2' is up to date.
`/usr/ports/distfiles/openoffice/OOo_3.0.1_src_core.tar.bz2' is up to date.
`/usr/ports/distfiles/openoffice/OOo_3.0.1_src_extensions.tar.bz2' is
up to date.
`/usr/ports/distfiles/openoffice/OOo_3.0.1_src_l10n.tar.bz2' is up to date.
`/usr/ports/distfiles/openoffice/OOo_3.0.1_src_system.tar.bz2' is up to date.
>> (SHA256) openoffice/ooo-desktop-0.1.tar.gz: OK
>> (SHA256) openoffice/OOo_3.0.1_src_binfilter.tar.bz2: OK
>> (SHA256) openoffice/OOo_3.0.1_src_core.tar.bz2: OK
>> (SHA256) openoffice/OOo_3.0.1_src_extensions.tar.bz2: OK
>> (SHA256) openoffice/OOo_3.0.1_src_l10n.tar.bz2: OK
>> (SHA256) openoffice/OOo_3.0.1_src_system.tar.bz2: OK
===>  openoffice-3.0.1p2 depends on: gcc-* - found
===>  openoffice-3.0.1p2 depends on: g++-* - not found
===>  Verifying install for g++-* in lang/gcc/4.2
===>  Checking files for gcc-4.2.20070307
`/usr/ports/distfiles/gcc/gcc-4.2-20070307.tar.bz2' is up to date.
`/usr/ports/distfiles/gcc/adastrap-i386-3.3.6-5.tgz' is up to date.
>> (SHA256) gcc/gcc-4.2-20070307.tar.bz2: OK
>> (SHA256) gcc/adastrap-i386-3.3.6-5.tgz: OK
===>  g++-4.2.20070307p9 depends on: autoconf-2.59 - found
===>  g++-4.2.20070307p9 depends on: metaauto-* - found
===>  g++-4.2.20070307p9 depends on: bison-* - found
===>  g++-4.2.20070307p9 depends on: gmake-* - found
===>  g++-4.2.20070307p9 depends on: libtool-* - found
===>  g++-4.2.20070307p9 depends on: bzip2-* - found
===>  g++-4.2.20070307p9 depends on: gmp->=4.2 - found
===>  g++-4.2.20070307p9 depends on: mpfr-* - found
===>  Verifying specs: gmp mpfr c c c c m c c c
===>  found gmp.7.1 mpfr.0.2 c.50.1 m.5.0
===>  Extracting for gcc-4.2.20070307
echo "#! /bin/sh" >/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
echo 'GNAT_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap
GCC_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap exec
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap/bin/egcc "$@"'
>>/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
chmod a+x /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
echo "#! /bin/sh" >/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatbind
echo 'GNAT_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap
GCC_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap exec
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap/bin/gnatbind
"$@"' >>/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatbind
chmod a+x /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatbind
echo "#! /bin/sh" >/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatmake
echo 'GNAT_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap
GCC_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap exec
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap/bin/gnatmake
"$@"' >>/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatmake
chmod a+x /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatmake
echo "#! /bin/sh" >/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatlink
echo 'GNAT_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap
GCC_ROOT=/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap exec
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bootstrap/bin/gnatlink
"$@"' >>/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatlink
chmod a+x /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/gnatlink
ln -s /usr/bin/nm /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/enm
echo "# This file automatically generated" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBestdc++_LTVERSION = -version-info 8:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBgfortran_LTVERSION = -version-info 2:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIB-org-w3c-dom_LTVERSION = -version-info 1:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIB-org-xml-sax_LTVERSION = -version-info 1:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBgcj_LTVERSION = -version-info 5:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBobjc_LTVERSION = -version-info 2:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBobjc_gc_LTVERSION = -version-info 2:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBssp_LTVERSION = -version-info 0:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
echo "LIBgomp_LTVERSION = -version-info 1:0" >>
/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libversions
===>  Patching for gcc-4.2.20070307
cd /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libstdc++-v3
&& AUTOCONF_VERSION=2.59 autoconf
===>  Configuring for gcc-4.2.20070307
loading site script /usr/ports/infrastructure/db/config.site
creating cache ./config.cache
checking host system type... i386-unknown-openbsd4.5
checking target system type... i386-unknown-openbsd4.5
checking build system type... i386-unknown-openbsd4.5
checking for a BSD compatible install... /usr/bin/install -c -o root -g bin
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
checking whether the C compiler
(/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc -O2 -g ) works...
no
configure: error: installation or configuration problem: C compiler
cannot create executables.
*** Error code 1

Stop in /usr/ports/lang/gcc/4.2 (line 2147 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/lang/gcc/4.2 (line 1427 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/lang/gcc/4.2 (line 1967 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/lang/gcc/4.2 (line 1457 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/openoffice3 (line 1604 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/openoffice3 (line 2001 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/openoffice3 (line 1427 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/openoffice3 (line 1967 of
/usr/ports/infrastructure/mk/bsd.port.mk).
*** Error code 1

Stop in /usr/ports/editors/openoffice3 (line 1457 of
/usr/ports/infrastructure/mk/bsd.port.mk).



2009/4/26 Pau <vim.unix at googlemail.com>:
> Hello,
>
>> $ cd /usr/ports/lang/gcc/4.2
>> $ FLAVOR="c++ fortran objc" make
>
> thanks, it's compiling now... But... what is that supposed to do,
> compared to simply "make"? Can you please elaborate a bit? What kind
> (flavour) of gcc42 will I be "left with"? Remind that this is
> "newbies" and not misc (this was the reason for posting here, because
> I assumed there would be too many basic things to ask), and even if I
> have been using openbsd for everything for three years already, there
> are many things I still do not understand. "I am not a technician", I
> am a Physicist, but I do not put this forward as a (ridiculous)
> argument, I want to know and understand.
>
> As for your other statements: I have already built openoffice 2.4.2
> from ports from scratch, including java etc... It's good that I made a
> 20G (!) /usr partition, because openoffice 2.4.2 took something like
> 70% of it when building. Not bad. The compilation took some 8 hours,
> yes.
> Why do I need openoffice3, then, if I compiled successfully 2.4.2? I
> found that it was buggy. Some pop-up menus were unclickeable (I
> apologise for the barbarism.
>
> Best,
>
> Pau
>
> 2009/4/26 Stuart Henderson <stu at spacehopper.org>:
>> On 2009-04-25, Antoine Jacoutot <ajacoutot at bsdfrog.org> wrote:
>>> On Sat, 25 Apr 2009, Pau wrote:
>>>
>>>> Hello,
>>>>
>>>> I tried to compile openoffice3 from ports in 4.5 after a fresh install
>>>> from the CDs. It gave me the following problem:
>>>>
>>>> > ===> ?Patching for gcc-4.2.20070307
>>>> > cd /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libstdc++-v3
>>>> > && AUTOCONF_VERSION=2.59 autoconf
>>>> > ===> ?Configuring for gcc-4.2.20070307
>>>> > loading site script /usr/ports/infrastructure/db/config.site
>>>> > creating cache ./config.cache
>>>> > checking host system type... i386-unknown-openbsd4.5
>>>> > checking target system type... i386-unknown-openbsd4.5
>>>> > checking build system type... i386-unknown-openbsd4.5
>>>> > checking for a BSD compatible install... /usr/bin/install -c -o root -g bin
>>>> > checking whether ln works... yes
>>>> > checking whether ln -s works... yes
>>>> > checking for gcc... /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
>>>> > checking whether the C compiler
>>>> > (/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc -O2 -g ) works...
>>>> > no
>>>> > configure: error: installation or configuration problem: C compiler
>>>> > cannot create executables.
>>>>
>>>> I asked in ports@ and got the following answer:
>>>>
>>>> "You need /usr/lib/libc.so.42.0
>>>> Of course, the doc says that you should use a package..."
>>>
>>> You either need to get and install /usr/lib/libc.so.42.0 from a previous
>>> OpenBSD version because this lib was used to bootstrap ada.
>>> Or, you can wait for 4.5 to came out and install gcc4 from package.
>>>
>>>
>>
>> openoffice3 is *huge*. it will probably take more than 12 hours to
>> build, very much more if you don't have enough ram or have a slow cpu.
>> that is on top of gcc 4.2, the JDK and other dependencies.
>> it's definitely recommended to use the packages for this one if
>> you possibly can.
>>
>> that said, and note that I haven't tested this, but you should be
>> able to build gcc 4.2 like this:
>>
>> $ cd /usr/ports/lang/gcc/4.2
>> $ FLAVOR="c++ fortran objc" make
>>
>> this is the default on cpu architectures other than i386 anyway so,
>> for example, if you're trying to build on amd64 you won't run into
>> this problem in the first place.
>>
>> you will also need to adjust the amount of memory that a process is
>> permitted to use by adjusting the resource limits in login.conf.
>> increase datasize-max for the class your login account uses, and
>> either bump it up using "ulimit -d <number of K>", or by increasing
>> datasize-cur as well. you will need to logout and log back in for
>> this change to take effect. (if you're building ports as root,
>> first look at the various ports tutorials and learn about setting
>> SUDO in /etc/mk.conf, and if you still want to build as root,
>> you need to adjust the login.conf entry for the class "daemon"
>> which is also used for software run from /etc/rc.local).
>>
>>
>> _______________________________________________
>> Openbsd-newbies mailing list
>> Openbsd-newbies at sfobug.org
>> http://mailman.theapt.org/listinfo/openbsd-newbies
>>
>
>
>
> --
> Let there be peace on earth. And let it begin with misc
>



-- 
Let there be peace on earth. And let it begin with misc

From vim.unix at googlemail.com  Sun Apr 26 12:15:05 2009
From: vim.unix at googlemail.com (Pau)
Date: Sun, 26 Apr 2009 12:15:05 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <slrngv75o2.mo5.stu@naiad.spacehopper.org>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
Message-ID: <30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>

Hello,

> $ cd /usr/ports/lang/gcc/4.2
> $ FLAVOR="c++ fortran objc" make

thanks, it's compiling now... But... what is that supposed to do,
compared to simply "make"? Can you please elaborate a bit? What kind
(flavour) of gcc42 will I be "left with"? Remind that this is
"newbies" and not misc (this was the reason for posting here, because
I assumed there would be too many basic things to ask), and even if I
have been using openbsd for everything for three years already, there
are many things I still do not understand. "I am not a technician", I
am a Physicist, but I do not put this forward as a (ridiculous)
argument, I want to know and understand.

As for your other statements: I have already built openoffice 2.4.2
from ports from scratch, including java etc... It's good that I made a
20G (!) /usr partition, because openoffice 2.4.2 took something like
70% of it when building. Not bad. The compilation took some 8 hours,
yes.
Why do I need openoffice3, then, if I compiled successfully 2.4.2? I
found that it was buggy. Some pop-up menus were unclickeable (I
apologise for the barbarism.

Best,

Pau

2009/4/26 Stuart Henderson <stu at spacehopper.org>:
> On 2009-04-25, Antoine Jacoutot <ajacoutot at bsdfrog.org> wrote:
>> On Sat, 25 Apr 2009, Pau wrote:
>>
>>> Hello,
>>>
>>> I tried to compile openoffice3 from ports in 4.5 after a fresh install
>>> from the CDs. It gave me the following problem:
>>>
>>> > ===> ?Patching for gcc-4.2.20070307
>>> > cd /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/gcc-4.2-20070307/libstdc++-v3
>>> > && AUTOCONF_VERSION=2.59 autoconf
>>> > ===> ?Configuring for gcc-4.2.20070307
>>> > loading site script /usr/ports/infrastructure/db/config.site
>>> > creating cache ./config.cache
>>> > checking host system type... i386-unknown-openbsd4.5
>>> > checking target system type... i386-unknown-openbsd4.5
>>> > checking build system type... i386-unknown-openbsd4.5
>>> > checking for a BSD compatible install... /usr/bin/install -c -o root -g bin
>>> > checking whether ln works... yes
>>> > checking whether ln -s works... yes
>>> > checking for gcc... /usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc
>>> > checking whether the C compiler
>>> > (/usr/ports/lang/gcc/4.2/w-gcc-4.2.20070307/bin/egcc -O2 -g ) works...
>>> > no
>>> > configure: error: installation or configuration problem: C compiler
>>> > cannot create executables.
>>>
>>> I asked in ports@ and got the following answer:
>>>
>>> "You need /usr/lib/libc.so.42.0
>>> Of course, the doc says that you should use a package..."
>>
>> You either need to get and install /usr/lib/libc.so.42.0 from a previous
>> OpenBSD version because this lib was used to bootstrap ada.
>> Or, you can wait for 4.5 to came out and install gcc4 from package.
>>
>>
>
> openoffice3 is *huge*. it will probably take more than 12 hours to
> build, very much more if you don't have enough ram or have a slow cpu.
> that is on top of gcc 4.2, the JDK and other dependencies.
> it's definitely recommended to use the packages for this one if
> you possibly can.
>
> that said, and note that I haven't tested this, but you should be
> able to build gcc 4.2 like this:
>
> $ cd /usr/ports/lang/gcc/4.2
> $ FLAVOR="c++ fortran objc" make
>
> this is the default on cpu architectures other than i386 anyway so,
> for example, if you're trying to build on amd64 you won't run into
> this problem in the first place.
>
> you will also need to adjust the amount of memory that a process is
> permitted to use by adjusting the resource limits in login.conf.
> increase datasize-max for the class your login account uses, and
> either bump it up using "ulimit -d <number of K>", or by increasing
> datasize-cur as well. you will need to logout and log back in for
> this change to take effect. (if you're building ports as root,
> first look at the various ports tutorials and learn about setting
> SUDO in /etc/mk.conf, and if you still want to build as root,
> you need to adjust the login.conf entry for the class "daemon"
> which is also used for software run from /etc/rc.local).
>
>
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
>



-- 
Let there be peace on earth. And let it begin with misc

From stu at spacehopper.org  Tue Apr 28 21:25:40 2009
From: stu at spacehopper.org (Stuart Henderson)
Date: Tue, 28 Apr 2009 19:25:40 +0000 (UTC)
Subject: openoffice3 install from ports breaking
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
Message-ID: <slrngvem1k.mo5.stu@naiad.spacehopper.org>

On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
> Hello,
>
>> $ cd /usr/ports/lang/gcc/4.2
>> $ FLAVOR="c++ fortran objc" make
>
> thanks, it's compiling now... But... what is that supposed to do,
> compared to simply "make"? Can you please elaborate a bit? What kind
> (flavour) of gcc42 will I be "left with"? Remind that this is
> "newbies" and not misc (this was the reason for posting here, because
> I assumed there would be too many basic things to ask), and even if I
> have been using openbsd for everything for three years already, there
> are many things I still do not understand. "I am not a technician", I
> am a Physicist, but I do not put this forward as a (ridiculous)
> argument, I want to know and understand.

The FLAVOR influences how a port is built; sometimes to choose between
alternative versions which can't be built together (for example, in
bacula you can choose between different mutually-exclusive databases),
other times to add non-standard patches (as in mutt with various patches
like the sidebar), and others to prevent parts from being built (e.g.
here in gcc 4, or php5/extensions).

You can of course find these in the port's Makefile or files it pulls 
in (sometimes you also need to consult Makefile.inc in the parent
directory), but there's an easier way to see the list of possible
flavors:

$ make show=FLAVORS 
 c++ fortran objc java ada

and also the list of default flavors on an i386 machine:

$ make show=FLAVOR  
c++ fortran objc ada

setting other variables can affect the "make show" output; a simple
but pointless example:

$ FLAVOR="c++ fortran" make show=FLAVOR
c++ fortran

or we can pretend we have an amd64 and show the list of default
flavors there:

$ MACHINE_ARCH=amd64 make show=FLAVOR  
c++ fortran objc

(as you can see here; the ada bootstrap we're having problems with here
is for i386 only; it's not built on amd64).


On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
> something's broken....
>
> I installed it with your FLAVOR and then went to
> /usr/ports/editors/openoffice3 and... look below

Aha; an opportunity to explain a bit about sub-packages too :-)
they're related but different to FLAVORs.

If you have software which builds a large set of files, and it's
common for users not to need all of them, the port can build the whole
lot, and produce separate packages from this. Here it's the C compiler,
C++ compiler, standard C++ library, Fortran compiler, Ada compiler,
and Objective C compiler. Let's take a look at some files in some
of the PLISTs here:

$ cd /usr/ports/lang/gcc/4.2; grep bin/ pkg/PLIST-{main,c++,f95}
pkg/PLIST-main:@bin bin/ecpp
pkg/PLIST-main:@bin bin/egcc
pkg/PLIST-main:bin/egccbug
pkg/PLIST-main:@bin bin/egcov
pkg/PLIST-main:@bin bin/${CONFIG}-egcc
pkg/PLIST-main:@bin bin/${CONFIG}-gcc-${V}
pkg/PLIST-c++:@bin bin/ec++
pkg/PLIST-c++:@bin bin/eg++
pkg/PLIST-c++:@bin bin/${CONFIG}-ec++
pkg/PLIST-c++:@bin bin/${CONFIG}-eg++
pkg/PLIST-f95:@bin bin/egfortran
pkg/PLIST-f95:@bin bin/${CONFIG}-egfortran

So at the packaging stage (where the /usr/ports/packages/ARCH/all/*.tgz
files are produced), you get a subset of files in each package, according
to the packing list (pkg/PLIST* and pkg/PFRAG* files).

This probably isn't the simplest port to demonstrate with, but not too
bad; the FLAVOR affects the set of files produced - this port doesn't
bother building the Fortran compiler unless the FLAVOR is set
appropriately, and it removes -f95 from the list of sub-packages to
build *.tgz for.

$ make show=MULTI_PACKAGES
-main -c++ -estdc -f95 -objc -ada

$ FLAVOR="c++ objc" make show=MULTI_PACKAGES
-main -c++ -estdc -objc

We wanted to remove the Ada compiler because it requires a pre-built
version of the Ada compiler to "bootstrap" from and we don't have the
right libraries to do that; so you can set the FLAVOR how I showed
earlier and check which packages will be built.

>===>  openoffice-3.0.1p2 depends on: gcc-* - found
>===>  openoffice-3.0.1p2 depends on: g++-* - not found
>===>  Verifying install for g++-* in lang/gcc/4.2

so, it found the "gcc" subpackage, the C compiler, but not the "g++"
subpackage. But you already built it; it's there in /usr/ports/packages.
What happened is the "make install" target just installs one of the
subpackages, not the whole lot. You can either "make install-all" for
everything you built, or you manually pkg_add the package you just
built:

# PKG_PATH=/usr/ports/packages/i386/all/ pkg_add g++

(When you "make install" in the OpenBSD ports tree, it always builds
a package, then pkg_add's it. Some other OS do this the other way round;
they install under the live system, then "make package" is an optional
later step e.g. if you want to move the package to a different machine
without rebuilding).

When openoffice is trying to install g++ as a dependency, it doesn't
know about /usr/ports/packages, it uses the ports tree to attempt the
installation - and it doesn't know anything about gcc's FLAVOR, so
it attempts to re-build the whole lot of gcc, which fails for the
original reason.

> I think I will wait for the gcc4.2 binary and then try again. I want
> to compile openoffice on my own because i hope to get some speeding up
> factor... probably I could get it by compiling rather than installing
> the binary from an ftp srver...

The binary packages on ftp are built in exactly the same way as
packages you build yourself from ports; unless you adjust compiler
optimization flags (which except in special circumstances will
waste more of your time than it saves at runtime), there should
be no difference at all between the package you make via ports,
and the packages made in the bulk builds for the ftp servers.



From vim.unix at googlemail.com  Tue Apr 28 22:29:50 2009
From: vim.unix at googlemail.com (Pau)
Date: Tue, 28 Apr 2009 22:29:50 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <slrngvem1k.mo5.stu@naiad.spacehopper.org>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
Message-ID: <30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>

Hello Stuart,

thanks!

That was _very_ useful.

I remember reading this in "Absolute OpenBSD", but it was ~ 2 yrs ago.

I had totally forgotten.

I am compiling now openoffice3 (I am stubborn)

I wonder what will happen to /usr/local/bin/soffice later... this is
currently openoffice 2.4.2

I should probably move it to /usr/local/bin/soffice.2.4.2 manually

thank you very much again for the detailed information

pau


2009/4/28 Stuart Henderson <stu at spacehopper.org>:
> On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
>> Hello,
>>
>>> $ cd /usr/ports/lang/gcc/4.2
>>> $ FLAVOR="c++ fortran objc" make
>>
>> thanks, it's compiling now... But... what is that supposed to do,
>> compared to simply "make"? Can you please elaborate a bit? What kind
>> (flavour) of gcc42 will I be "left with"? Remind that this is
>> "newbies" and not misc (this was the reason for posting here, because
>> I assumed there would be too many basic things to ask), and even if I
>> have been using openbsd for everything for three years already, there
>> are many things I still do not understand. "I am not a technician", I
>> am a Physicist, but I do not put this forward as a (ridiculous)
>> argument, I want to know and understand.
>
> The FLAVOR influences how a port is built; sometimes to choose between
> alternative versions which can't be built together (for example, in
> bacula you can choose between different mutually-exclusive databases),
> other times to add non-standard patches (as in mutt with various patches
> like the sidebar), and others to prevent parts from being built (e.g.
> here in gcc 4, or php5/extensions).
>
> You can of course find these in the port's Makefile or files it pulls
> in (sometimes you also need to consult Makefile.inc in the parent
> directory), but there's an easier way to see the list of possible
> flavors:
>
> $ make show=FLAVORS
> ?c++ fortran objc java ada
>
> and also the list of default flavors on an i386 machine:
>
> $ make show=FLAVOR
> c++ fortran objc ada
>
> setting other variables can affect the "make show" output; a simple
> but pointless example:
>
> $ FLAVOR="c++ fortran" make show=FLAVOR
> c++ fortran
>
> or we can pretend we have an amd64 and show the list of default
> flavors there:
>
> $ MACHINE_ARCH=amd64 make show=FLAVOR
> c++ fortran objc
>
> (as you can see here; the ada bootstrap we're having problems with here
> is for i386 only; it's not built on amd64).
>
>
> On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
>> something's broken....
>>
>> I installed it with your FLAVOR and then went to
>> /usr/ports/editors/openoffice3 and... look below
>
> Aha; an opportunity to explain a bit about sub-packages too :-)
> they're related but different to FLAVORs.
>
> If you have software which builds a large set of files, and it's
> common for users not to need all of them, the port can build the whole
> lot, and produce separate packages from this. Here it's the C compiler,
> C++ compiler, standard C++ library, Fortran compiler, Ada compiler,
> and Objective C compiler. Let's take a look at some files in some
> of the PLISTs here:
>
> $ cd /usr/ports/lang/gcc/4.2; grep bin/ pkg/PLIST-{main,c++,f95}
> pkg/PLIST-main:@bin bin/ecpp
> pkg/PLIST-main:@bin bin/egcc
> pkg/PLIST-main:bin/egccbug
> pkg/PLIST-main:@bin bin/egcov
> pkg/PLIST-main:@bin bin/${CONFIG}-egcc
> pkg/PLIST-main:@bin bin/${CONFIG}-gcc-${V}
> pkg/PLIST-c++:@bin bin/ec++
> pkg/PLIST-c++:@bin bin/eg++
> pkg/PLIST-c++:@bin bin/${CONFIG}-ec++
> pkg/PLIST-c++:@bin bin/${CONFIG}-eg++
> pkg/PLIST-f95:@bin bin/egfortran
> pkg/PLIST-f95:@bin bin/${CONFIG}-egfortran
>
> So at the packaging stage (where the /usr/ports/packages/ARCH/all/*.tgz
> files are produced), you get a subset of files in each package, according
> to the packing list (pkg/PLIST* and pkg/PFRAG* files).
>
> This probably isn't the simplest port to demonstrate with, but not too
> bad; the FLAVOR affects the set of files produced - this port doesn't
> bother building the Fortran compiler unless the FLAVOR is set
> appropriately, and it removes -f95 from the list of sub-packages to
> build *.tgz for.
>
> $ make show=MULTI_PACKAGES
> -main -c++ -estdc -f95 -objc -ada
>
> $ FLAVOR="c++ objc" make show=MULTI_PACKAGES
> -main -c++ -estdc -objc
>
> We wanted to remove the Ada compiler because it requires a pre-built
> version of the Ada compiler to "bootstrap" from and we don't have the
> right libraries to do that; so you can set the FLAVOR how I showed
> earlier and check which packages will be built.
>
>>===> ?openoffice-3.0.1p2 depends on: gcc-* - found
>>===> ?openoffice-3.0.1p2 depends on: g++-* - not found
>>===> ?Verifying install for g++-* in lang/gcc/4.2
>
> so, it found the "gcc" subpackage, the C compiler, but not the "g++"
> subpackage. But you already built it; it's there in /usr/ports/packages.
> What happened is the "make install" target just installs one of the
> subpackages, not the whole lot. You can either "make install-all" for
> everything you built, or you manually pkg_add the package you just
> built:
>
> # PKG_PATH=/usr/ports/packages/i386/all/ pkg_add g++
>
> (When you "make install" in the OpenBSD ports tree, it always builds
> a package, then pkg_add's it. Some other OS do this the other way round;
> they install under the live system, then "make package" is an optional
> later step e.g. if you want to move the package to a different machine
> without rebuilding).
>
> When openoffice is trying to install g++ as a dependency, it doesn't
> know about /usr/ports/packages, it uses the ports tree to attempt the
> installation - and it doesn't know anything about gcc's FLAVOR, so
> it attempts to re-build the whole lot of gcc, which fails for the
> original reason.
>
>> I think I will wait for the gcc4.2 binary and then try again. I want
>> to compile openoffice on my own because i hope to get some speeding up
>> factor... probably I could get it by compiling rather than installing
>> the binary from an ftp srver...
>
> The binary packages on ftp are built in exactly the same way as
> packages you build yourself from ports; unless you adjust compiler
> optimization flags (which except in special circumstances will
> waste more of your time than it saves at runtime), there should
> be no difference at all between the package you make via ports,
> and the packages made in the bulk builds for the ftp servers.
>
>
> _______________________________________________
> Openbsd-newbies mailing list
> Openbsd-newbies at sfobug.org
> http://mailman.theapt.org/listinfo/openbsd-newbies
>



-- 
Let there be peace on earth. And let it begin with misc

From vim.unix at googlemail.com  Thu Apr 30 09:55:11 2009
From: vim.unix at googlemail.com (Pau)
Date: Thu, 30 Apr 2009 09:55:11 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
	<30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
Message-ID: <30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>

Hello,

mission accomplished.

I started compiling the day before yesterday at 21h30, left the laptop
on during the night, took it with me to work, as usual, but this time
compiling, spent the whole day at the institute. There the compilation
crashed, because /usr was full! I have a 20G /usr partition. True, I
had also compiled other things, but I had plenty of space before
starting to compile, at least I thought so. So I did a make clean in
/usr/ports and resumed the compilation (make install again).

Then I came back with it still compiling and left if compiling last night.

Today in the morning it was ready. At some point during the night it
finished, but I do not know when. It could not install because it
found office2.4.2 installed, so I had to remove it and install

Now it's up and running. Halleluia, brother....

And look at /usr :

/dev/sd0f     19.7G   18.8G   -110M   101%    /usr

Not bad!

After a make clean (this all comes from openoffice3, since I had made
a make clean on /usr/ports before) :

/dev/sd0f     19.7G    7.4G   11.3G    40%    /usr

Still a lof of G are taken.... mmmh...

hux(pd)| du -hs /usr/ports/* | grep G
1.9G    /usr/ports/distfiles
4.9G    /usr/ports/packages

Now i understand... but what is the difference between distfiles and packages ?

I see tgz in the two of them. Why two separate folders?

Pau



2009/4/28 Pau <vim.unix at googlemail.com>:
> Hello Stuart,
>
> thanks!
>
> That was _very_ useful.
>
> I remember reading this in "Absolute OpenBSD", but it was ~ 2 yrs ago.
>
> I had totally forgotten.
>
> I am compiling now openoffice3 (I am stubborn)
>
> I wonder what will happen to /usr/local/bin/soffice later... this is
> currently openoffice 2.4.2
>
> I should probably move it to /usr/local/bin/soffice.2.4.2 manually
>
> thank you very much again for the detailed information
>
> pau
>
>
> 2009/4/28 Stuart Henderson <stu at spacehopper.org>:
>> On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
>>> Hello,
>>>
>>>> $ cd /usr/ports/lang/gcc/4.2
>>>> $ FLAVOR="c++ fortran objc" make
>>>
>>> thanks, it's compiling now... But... what is that supposed to do,
>>> compared to simply "make"? Can you please elaborate a bit? What kind
>>> (flavour) of gcc42 will I be "left with"? Remind that this is
>>> "newbies" and not misc (this was the reason for posting here, because
>>> I assumed there would be too many basic things to ask), and even if I
>>> have been using openbsd for everything for three years already, there
>>> are many things I still do not understand. "I am not a technician", I
>>> am a Physicist, but I do not put this forward as a (ridiculous)
>>> argument, I want to know and understand.
>>
>> The FLAVOR influences how a port is built; sometimes to choose between
>> alternative versions which can't be built together (for example, in
>> bacula you can choose between different mutually-exclusive databases),
>> other times to add non-standard patches (as in mutt with various patches
>> like the sidebar), and others to prevent parts from being built (e.g.
>> here in gcc 4, or php5/extensions).
>>
>> You can of course find these in the port's Makefile or files it pulls
>> in (sometimes you also need to consult Makefile.inc in the parent
>> directory), but there's an easier way to see the list of possible
>> flavors:
>>
>> $ make show=FLAVORS
>> ?c++ fortran objc java ada
>>
>> and also the list of default flavors on an i386 machine:
>>
>> $ make show=FLAVOR
>> c++ fortran objc ada
>>
>> setting other variables can affect the "make show" output; a simple
>> but pointless example:
>>
>> $ FLAVOR="c++ fortran" make show=FLAVOR
>> c++ fortran
>>
>> or we can pretend we have an amd64 and show the list of default
>> flavors there:
>>
>> $ MACHINE_ARCH=amd64 make show=FLAVOR
>> c++ fortran objc
>>
>> (as you can see here; the ada bootstrap we're having problems with here
>> is for i386 only; it's not built on amd64).
>>
>>
>> On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
>>> something's broken....
>>>
>>> I installed it with your FLAVOR and then went to
>>> /usr/ports/editors/openoffice3 and... look below
>>
>> Aha; an opportunity to explain a bit about sub-packages too :-)
>> they're related but different to FLAVORs.
>>
>> If you have software which builds a large set of files, and it's
>> common for users not to need all of them, the port can build the whole
>> lot, and produce separate packages from this. Here it's the C compiler,
>> C++ compiler, standard C++ library, Fortran compiler, Ada compiler,
>> and Objective C compiler. Let's take a look at some files in some
>> of the PLISTs here:
>>
>> $ cd /usr/ports/lang/gcc/4.2; grep bin/ pkg/PLIST-{main,c++,f95}
>> pkg/PLIST-main:@bin bin/ecpp
>> pkg/PLIST-main:@bin bin/egcc
>> pkg/PLIST-main:bin/egccbug
>> pkg/PLIST-main:@bin bin/egcov
>> pkg/PLIST-main:@bin bin/${CONFIG}-egcc
>> pkg/PLIST-main:@bin bin/${CONFIG}-gcc-${V}
>> pkg/PLIST-c++:@bin bin/ec++
>> pkg/PLIST-c++:@bin bin/eg++
>> pkg/PLIST-c++:@bin bin/${CONFIG}-ec++
>> pkg/PLIST-c++:@bin bin/${CONFIG}-eg++
>> pkg/PLIST-f95:@bin bin/egfortran
>> pkg/PLIST-f95:@bin bin/${CONFIG}-egfortran
>>
>> So at the packaging stage (where the /usr/ports/packages/ARCH/all/*.tgz
>> files are produced), you get a subset of files in each package, according
>> to the packing list (pkg/PLIST* and pkg/PFRAG* files).
>>
>> This probably isn't the simplest port to demonstrate with, but not too
>> bad; the FLAVOR affects the set of files produced - this port doesn't
>> bother building the Fortran compiler unless the FLAVOR is set
>> appropriately, and it removes -f95 from the list of sub-packages to
>> build *.tgz for.
>>
>> $ make show=MULTI_PACKAGES
>> -main -c++ -estdc -f95 -objc -ada
>>
>> $ FLAVOR="c++ objc" make show=MULTI_PACKAGES
>> -main -c++ -estdc -objc
>>
>> We wanted to remove the Ada compiler because it requires a pre-built
>> version of the Ada compiler to "bootstrap" from and we don't have the
>> right libraries to do that; so you can set the FLAVOR how I showed
>> earlier and check which packages will be built.
>>
>>>===> ?openoffice-3.0.1p2 depends on: gcc-* - found
>>>===> ?openoffice-3.0.1p2 depends on: g++-* - not found
>>>===> ?Verifying install for g++-* in lang/gcc/4.2
>>
>> so, it found the "gcc" subpackage, the C compiler, but not the "g++"
>> subpackage. But you already built it; it's there in /usr/ports/packages.
>> What happened is the "make install" target just installs one of the
>> subpackages, not the whole lot. You can either "make install-all" for
>> everything you built, or you manually pkg_add the package you just
>> built:
>>
>> # PKG_PATH=/usr/ports/packages/i386/all/ pkg_add g++
>>
>> (When you "make install" in the OpenBSD ports tree, it always builds
>> a package, then pkg_add's it. Some other OS do this the other way round;
>> they install under the live system, then "make package" is an optional
>> later step e.g. if you want to move the package to a different machine
>> without rebuilding).
>>
>> When openoffice is trying to install g++ as a dependency, it doesn't
>> know about /usr/ports/packages, it uses the ports tree to attempt the
>> installation - and it doesn't know anything about gcc's FLAVOR, so
>> it attempts to re-build the whole lot of gcc, which fails for the
>> original reason.
>>
>>> I think I will wait for the gcc4.2 binary and then try again. I want
>>> to compile openoffice on my own because i hope to get some speeding up
>>> factor... probably I could get it by compiling rather than installing
>>> the binary from an ftp srver...
>>
>> The binary packages on ftp are built in exactly the same way as
>> packages you build yourself from ports; unless you adjust compiler
>> optimization flags (which except in special circumstances will
>> waste more of your time than it saves at runtime), there should
>> be no difference at all between the package you make via ports,
>> and the packages made in the bulk builds for the ftp servers.
>>
>>
>> _______________________________________________
>> Openbsd-newbies mailing list
>> Openbsd-newbies at sfobug.org
>> http://mailman.theapt.org/listinfo/openbsd-newbies
>>
>
>
>
> --
> Let there be peace on earth. And let it begin with misc
>



-- 
Let there be peace on earth. And let it begin with misc

From phessler at theapt.org  Thu Apr 30 10:05:21 2009
From: phessler at theapt.org (Peter Hessler)
Date: Thu, 30 Apr 2009 10:05:21 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
	<30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
	<30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
Message-ID: <20090430080520.GE15986@gir.theapt.org>

On 2009 Apr 30 (Thu) at 09:55:11 +0200 (+0200), Pau wrote:
:Hello,
:
:mission accomplished.
:
:I started compiling the day before yesterday at 21h30, left the laptop
:on during the night, took it with me to work, as usual, but this time
:compiling, spent the whole day at the institute. There the compilation
:crashed, because /usr was full! I have a 20G /usr partition. True, I
:had also compiled other things, but I had plenty of space before
:starting to compile, at least I thought so. So I did a make clean in
:/usr/ports and resumed the compilation (make install again).
:
:Then I came back with it still compiling and left if compiling last night.
:
:Today in the morning it was ready. At some point during the night it
:finished, but I do not know when. It could not install because it
:found office2.4.2 installed, so I had to remove it and install
:
:Now it's up and running. Halleluia, brother....
:
:And look at /usr :
:
:/dev/sd0f     19.7G   18.8G   -110M   101%    /usr
:
:Not bad!
:
:After a make clean (this all comes from openoffice3, since I had made
:a make clean on /usr/ports before) :
:
:/dev/sd0f     19.7G    7.4G   11.3G    40%    /usr
:
:Still a lof of G are taken.... mmmh...

Yes, OpenOffice is *HUGE*.  Massively so.


:
:hux(pd)| du -hs /usr/ports/* | grep G
:1.9G    /usr/ports/distfiles
:4.9G    /usr/ports/packages
:
:Now i understand... but what is the difference between distfiles and packages ?

The distfile is the original source package, downloaded from the original
authors.

Packages, are the binary install packages.

Ports, fetches the distfile, untars it, applies patches, runs configure
and make, does an install into a fake hierarchy, packages it all up into
the package, then untars the package in the correct place.

Of course, thats a /very/ simplified version of how ports work.  More
details are at http://www.openbsd.org/faq/faq15.html


:
:I see tgz in the two of them. Why two separate folders?
:
:Pau
:
:
:
:2009/4/28 Pau <vim.unix at googlemail.com>:
:> Hello Stuart,
:>
:> thanks!
:>
:> That was _very_ useful.
:>
:> I remember reading this in "Absolute OpenBSD", but it was ~ 2 yrs ago.
:>
:> I had totally forgotten.
:>
:> I am compiling now openoffice3 (I am stubborn)
:>
:> I wonder what will happen to /usr/local/bin/soffice later... this is
:> currently openoffice 2.4.2
:>
:> I should probably move it to /usr/local/bin/soffice.2.4.2 manually
:>
:> thank you very much again for the detailed information
:>
:> pau
:>
:>
:> 2009/4/28 Stuart Henderson <stu at spacehopper.org>:
:>> On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
:>>> Hello,
:>>>
:>>>> $ cd /usr/ports/lang/gcc/4.2
:>>>> $ FLAVOR="c++ fortran objc" make
:>>>
:>>> thanks, it's compiling now... But... what is that supposed to do,
:>>> compared to simply "make"? Can you please elaborate a bit? What kind
:>>> (flavour) of gcc42 will I be "left with"? Remind that this is
:>>> "newbies" and not misc (this was the reason for posting here, because
:>>> I assumed there would be too many basic things to ask), and even if I
:>>> have been using openbsd for everything for three years already, there
:>>> are many things I still do not understand. "I am not a technician", I
:>>> am a Physicist, but I do not put this forward as a (ridiculous)
:>>> argument, I want to know and understand.
:>>
:>> The FLAVOR influences how a port is built; sometimes to choose between
:>> alternative versions which can't be built together (for example, in
:>> bacula you can choose between different mutually-exclusive databases),
:>> other times to add non-standard patches (as in mutt with various patches
:>> like the sidebar), and others to prevent parts from being built (e.g.
:>> here in gcc 4, or php5/extensions).
:>>
:>> You can of course find these in the port's Makefile or files it pulls
:>> in (sometimes you also need to consult Makefile.inc in the parent
:>> directory), but there's an easier way to see the list of possible
:>> flavors:
:>>
:>> $ make show=FLAVORS
:>> ?c++ fortran objc java ada
:>>
:>> and also the list of default flavors on an i386 machine:
:>>
:>> $ make show=FLAVOR
:>> c++ fortran objc ada
:>>
:>> setting other variables can affect the "make show" output; a simple
:>> but pointless example:
:>>
:>> $ FLAVOR="c++ fortran" make show=FLAVOR
:>> c++ fortran
:>>
:>> or we can pretend we have an amd64 and show the list of default
:>> flavors there:
:>>
:>> $ MACHINE_ARCH=amd64 make show=FLAVOR
:>> c++ fortran objc
:>>
:>> (as you can see here; the ada bootstrap we're having problems with here
:>> is for i386 only; it's not built on amd64).
:>>
:>>
:>> On 2009-04-26, Pau <vim.unix at googlemail.com> wrote:
:>>> something's broken....
:>>>
:>>> I installed it with your FLAVOR and then went to
:>>> /usr/ports/editors/openoffice3 and... look below
:>>
:>> Aha; an opportunity to explain a bit about sub-packages too :-)
:>> they're related but different to FLAVORs.
:>>
:>> If you have software which builds a large set of files, and it's
:>> common for users not to need all of them, the port can build the whole
:>> lot, and produce separate packages from this. Here it's the C compiler,
:>> C++ compiler, standard C++ library, Fortran compiler, Ada compiler,
:>> and Objective C compiler. Let's take a look at some files in some
:>> of the PLISTs here:
:>>
:>> $ cd /usr/ports/lang/gcc/4.2; grep bin/ pkg/PLIST-{main,c++,f95}
:>> pkg/PLIST-main:@bin bin/ecpp
:>> pkg/PLIST-main:@bin bin/egcc
:>> pkg/PLIST-main:bin/egccbug
:>> pkg/PLIST-main:@bin bin/egcov
:>> pkg/PLIST-main:@bin bin/${CONFIG}-egcc
:>> pkg/PLIST-main:@bin bin/${CONFIG}-gcc-${V}
:>> pkg/PLIST-c++:@bin bin/ec++
:>> pkg/PLIST-c++:@bin bin/eg++
:>> pkg/PLIST-c++:@bin bin/${CONFIG}-ec++
:>> pkg/PLIST-c++:@bin bin/${CONFIG}-eg++
:>> pkg/PLIST-f95:@bin bin/egfortran
:>> pkg/PLIST-f95:@bin bin/${CONFIG}-egfortran
:>>
:>> So at the packaging stage (where the /usr/ports/packages/ARCH/all/*.tgz
:>> files are produced), you get a subset of files in each package, according
:>> to the packing list (pkg/PLIST* and pkg/PFRAG* files).
:>>
:>> This probably isn't the simplest port to demonstrate with, but not too
:>> bad; the FLAVOR affects the set of files produced - this port doesn't
:>> bother building the Fortran compiler unless the FLAVOR is set
:>> appropriately, and it removes -f95 from the list of sub-packages to
:>> build *.tgz for.
:>>
:>> $ make show=MULTI_PACKAGES
:>> -main -c++ -estdc -f95 -objc -ada
:>>
:>> $ FLAVOR="c++ objc" make show=MULTI_PACKAGES
:>> -main -c++ -estdc -objc
:>>
:>> We wanted to remove the Ada compiler because it requires a pre-built
:>> version of the Ada compiler to "bootstrap" from and we don't have the
:>> right libraries to do that; so you can set the FLAVOR how I showed
:>> earlier and check which packages will be built.
:>>
:>>>===> ?openoffice-3.0.1p2 depends on: gcc-* - found
:>>>===> ?openoffice-3.0.1p2 depends on: g++-* - not found
:>>>===> ?Verifying install for g++-* in lang/gcc/4.2
:>>
:>> so, it found the "gcc" subpackage, the C compiler, but not the "g++"
:>> subpackage. But you already built it; it's there in /usr/ports/packages.
:>> What happened is the "make install" target just installs one of the
:>> subpackages, not the whole lot. You can either "make install-all" for
:>> everything you built, or you manually pkg_add the package you just
:>> built:
:>>
:>> # PKG_PATH=/usr/ports/packages/i386/all/ pkg_add g++
:>>
:>> (When you "make install" in the OpenBSD ports tree, it always builds
:>> a package, then pkg_add's it. Some other OS do this the other way round;
:>> they install under the live system, then "make package" is an optional
:>> later step e.g. if you want to move the package to a different machine
:>> without rebuilding).
:>>
:>> When openoffice is trying to install g++ as a dependency, it doesn't
:>> know about /usr/ports/packages, it uses the ports tree to attempt the
:>> installation - and it doesn't know anything about gcc's FLAVOR, so
:>> it attempts to re-build the whole lot of gcc, which fails for the
:>> original reason.
:>>
:>>> I think I will wait for the gcc4.2 binary and then try again. I want
:>>> to compile openoffice on my own because i hope to get some speeding up
:>>> factor... probably I could get it by compiling rather than installing
:>>> the binary from an ftp srver...
:>>
:>> The binary packages on ftp are built in exactly the same way as
:>> packages you build yourself from ports; unless you adjust compiler
:>> optimization flags (which except in special circumstances will
:>> waste more of your time than it saves at runtime), there should
:>> be no difference at all between the package you make via ports,
:>> and the packages made in the bulk builds for the ftp servers.
:>>
:>>
:>> _______________________________________________
:>> Openbsd-newbies mailing list
:>> Openbsd-newbies at sfobug.org
:>> http://mailman.theapt.org/listinfo/openbsd-newbies
:>>
:>
:>
:>
:> --
:> Let there be peace on earth. And let it begin with misc
:>
:
:
:
:-- 
:Let there be peace on earth. And let it begin with misc
:_______________________________________________
:Openbsd-newbies mailing list
:Openbsd-newbies at sfobug.org
:http://mailman.theapt.org/listinfo/openbsd-newbies
:

-- 
The older I grow, the less important the comma becomes.  Let the reader
catch his own breath.
		-- Elizabeth Clarkson Zwart

From stu at spacehopper.org  Thu Apr 30 10:10:45 2009
From: stu at spacehopper.org (Stuart Henderson)
Date: Thu, 30 Apr 2009 09:10:45 +0100
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
	<30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
	<30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
Message-ID: <20090430081045.GZ5825@symphytum.spacehopper.org>

On 2009/04/30 09:55, Pau wrote:
> I started compiling the day before yesterday at 21h30, left the laptop
> on during the night, took it with me to work, as usual, but this time
> compiling, spent the whole day at the institute. There the compilation
> crashed, because /usr was full! I have a 20G /usr partition. True, I
> had also compiled other things, but I had plenty of space before
> starting to compile, at least I thought so. So I did a make clean in
> /usr/ports and resumed the compilation (make install again).

That sounds about right for this software (-: You can make it easier to
clean up after port builds - set WRKOBJDIR in /etc/mk.conf and instead
of creating directories under each port it will create them in the
directory you specify. e.g.

WRKOBJDIR=/usr/obj/ports

Then you can easily rm -r when you need the space back.

This is also useful if /usr is full but you have more space elsewhere
you can build in.

You can also set this on a port-by-port basis, bsd.port.mk(5) tells
you more under the WRKOBJDIR description.

> hux(pd)| du -hs /usr/ports/* | grep G
> 1.9G    /usr/ports/distfiles
> 4.9G    /usr/ports/packages
> 
> Now i understand... but what is the difference between distfiles and packages ?
> 
> I see tgz in the two of them. Why two separate folders?

distfiles are downloaded source code used to build the port; packages
are the binary packages built by the port. There are multiple directories
inside the packages directory; the files for most ports will appear in
each of them (all, ftp, cdrom), but they don't take any extra place as
they are hard-links (extra directory entries pointing to the same inode
on the filesystem) - see ln(1) and ls -li.


From vim.unix at googlemail.com  Thu Apr 30 10:35:41 2009
From: vim.unix at googlemail.com (Pau)
Date: Thu, 30 Apr 2009 10:35:41 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <20090430081045.GZ5825@symphytum.spacehopper.org>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
	<30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
	<30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
	<20090430081045.GZ5825@symphytum.spacehopper.org>
Message-ID: <30c383e70904300135yb42b3afsb8916324d862be84@mail.gmail.com>

I start to enjoy the ports system...

What about those packages? Could I use them for another machine
runnning the same obsd release? If i have another laptop in hwich I
want to install openoffice3, could i simply copy over openoffice*.tgz
and install it with pkg_add?
I guess so, but I prefer to ask, just in case of.
And can I remove everything in distfiles? Since the packages built and
were installed, it seems to be the most natural thing.

But I should do a bit reading before asking so much...

in any case, thanks a lot

Pau

2009/4/30 Stuart Henderson <stu at spacehopper.org>:
> On 2009/04/30 09:55, Pau wrote:
>> I started compiling the day before yesterday at 21h30, left the laptop
>> on during the night, took it with me to work, as usual, but this time
>> compiling, spent the whole day at the institute. There the compilation
>> crashed, because /usr was full! I have a 20G /usr partition. True, I
>> had also compiled other things, but I had plenty of space before
>> starting to compile, at least I thought so. So I did a make clean in
>> /usr/ports and resumed the compilation (make install again).
>
> That sounds about right for this software (-: You can make it easier to
> clean up after port builds - set WRKOBJDIR in /etc/mk.conf and instead
> of creating directories under each port it will create them in the
> directory you specify. e.g.
>
> WRKOBJDIR=/usr/obj/ports
>
> Then you can easily rm -r when you need the space back.
>
> This is also useful if /usr is full but you have more space elsewhere
> you can build in.
>
> You can also set this on a port-by-port basis, bsd.port.mk(5) tells
> you more under the WRKOBJDIR description.
>
>> hux(pd)| du -hs /usr/ports/* | grep G
>> 1.9G ? ?/usr/ports/distfiles
>> 4.9G ? ?/usr/ports/packages
>>
>> Now i understand... but what is the difference between distfiles and packages ?
>>
>> I see tgz in the two of them. Why two separate folders?
>
> distfiles are downloaded source code used to build the port; packages
> are the binary packages built by the port. There are multiple directories
> inside the packages directory; the files for most ports will appear in
> each of them (all, ftp, cdrom), but they don't take any extra place as
> they are hard-links (extra directory entries pointing to the same inode
> on the filesystem) - see ln(1) and ls -li.
>
>



-- 
Let there be peace on earth. And let it begin with misc

From stu at spacehopper.org  Thu Apr 30 10:49:49 2009
From: stu at spacehopper.org (Stuart Henderson)
Date: Thu, 30 Apr 2009 09:49:49 +0100
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904300135yb42b3afsb8916324d862be84@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
	<30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
	<30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
	<20090430081045.GZ5825@symphytum.spacehopper.org>
	<30c383e70904300135yb42b3afsb8916324d862be84@mail.gmail.com>
Message-ID: <20090430084949.GC5825@symphytum.spacehopper.org>

On 2009/04/30 10:35, Pau wrote:
> I start to enjoy the ports system...
> 
> What about those packages? Could I use them for another machine
> runnning the same obsd release? If i have another laptop in hwich I
> want to install openoffice3, could i simply copy over openoffice*.tgz
> and install it with pkg_add?
> I guess so, but I prefer to ask, just in case of.

Yes, sure, this is exactly what happens with the bulk-build packages on
the ftp servers. You can use an scp:// url in PKG_PATH, too - you need to
specify the username since pkg_add runs as root.

PKG_PATH=scp://username at host/usr/ports/packages/i386/all/

> And can I remove everything in distfiles? Since the packages built and
> were installed, it seems to be the most natural thing.

That depends if you might want to build them again (and if disk space
is more of a problem than bandwidth). I tend to keep them around unless
it's a space-limited system. (Actually I put /usr/ports/distfiles on
NFS since I often build on a few different machine types). But my
use probably isn't normal.


From phessler at theapt.org  Thu Apr 30 10:52:34 2009
From: phessler at theapt.org (Peter Hessler)
Date: Thu, 30 Apr 2009 10:52:34 +0200
Subject: openoffice3 install from ports breaking
In-Reply-To: <30c383e70904300135yb42b3afsb8916324d862be84@mail.gmail.com>
References: <30c383e70904251024q14b18c57y4675fd7df9b35d49@mail.gmail.com>
	<alpine.BSO.2.00.0904251950290.22943@janus.obspm.bsdfrog.org>
	<slrngv75o2.mo5.stu@naiad.spacehopper.org>
	<30c383e70904260315k62c67422o235bae51dfe1487e@mail.gmail.com>
	<30c383e70904260507r2c849d12o77b8f39714e4d3fc@mail.gmail.com>
	<slrngvem1k.mo5.stu@naiad.spacehopper.org>
	<30c383e70904281329s3bee3d21q1a681c6e0e24aa0b@mail.gmail.com>
	<30c383e70904300055g3d79b6a1yc0d69d0291ed773d@mail.gmail.com>
	<20090430081045.GZ5825@symphytum.spacehopper.org>
	<30c383e70904300135yb42b3afsb8916324d862be84@mail.gmail.com>
Message-ID: <20090430085234.GF15986@gir.theapt.org>

Yes.  You can use these packages on different systems.  IFF they are the
same release, and same architecture.  amd64 packages won't work on i386,
etc.  The packages also refuse to install, if you have the wrong
versions of libraries installed.  4.4 packages won't work on 4.5, of course.


On 2009 Apr 30 (Thu) at 10:35:41 +0200 (+0200), Pau wrote:
:I start to enjoy the ports system...
:
:What about those packages? Could I use them for another machine
:runnning the same obsd release? If i have another laptop in hwich I
:want to install openoffice3, could i simply copy over openoffice*.tgz
:and install it with pkg_add?
:I guess so, but I prefer to ask, just in case of.
:And can I remove everything in distfiles? Since the packages built and
:were installed, it seems to be the most natural thing.
:
:But I should do a bit reading before asking so much...
:
:in any case, thanks a lot
:
:Pau
:
:2009/4/30 Stuart Henderson <stu at spacehopper.org>:
:> On 2009/04/30 09:55, Pau wrote:
:>> I started compiling the day before yesterday at 21h30, left the laptop
:>> on during the night, took it with me to work, as usual, but this time
:>> compiling, spent the whole day at the institute. There the compilation
:>> crashed, because /usr was full! I have a 20G /usr partition. True, I
:>> had also compiled other things, but I had plenty of space before
:>> starting to compile, at least I thought so. So I did a make clean in
:>> /usr/ports and resumed the compilation (make install again).
:>
:> That sounds about right for this software (-: You can make it easier to
:> clean up after port builds - set WRKOBJDIR in /etc/mk.conf and instead
:> of creating directories under each port it will create them in the
:> directory you specify. e.g.
:>
:> WRKOBJDIR=/usr/obj/ports
:>
:> Then you can easily rm -r when you need the space back.
:>
:> This is also useful if /usr is full but you have more space elsewhere
:> you can build in.
:>
:> You can also set this on a port-by-port basis, bsd.port.mk(5) tells
:> you more under the WRKOBJDIR description.
:>
:>> hux(pd)| du -hs /usr/ports/* | grep G
:>> 1.9G ? ?/usr/ports/distfiles
:>> 4.9G ? ?/usr/ports/packages
:>>
:>> Now i understand... but what is the difference between distfiles and packages ?
:>>
:>> I see tgz in the two of them. Why two separate folders?
:>
:> distfiles are downloaded source code used to build the port; packages
:> are the binary packages built by the port. There are multiple directories
:> inside the packages directory; the files for most ports will appear in
:> each of them (all, ftp, cdrom), but they don't take any extra place as
:> they are hard-links (extra directory entries pointing to the same inode
:> on the filesystem) - see ln(1) and ls -li.
:>
:>
:
:
:
:-- 
:Let there be peace on earth. And let it begin with misc
:_______________________________________________
:Openbsd-newbies mailing list
:Openbsd-newbies at sfobug.org
:http://mailman.theapt.org/listinfo/openbsd-newbies
:

-- 
If you have a procedure with 10 parameters, you probably missed some.