[gentoo-amd64] Openoffice build error (#2 to keep them in line)

[gentoo-amd64] Openoffice build error (#2 to keep them in line)

[sean]

Any ideas on this latest build problem below?
Not sure where to start on troubleshooting this one yet.

gcc-config -l
  [1] x86_64-pc-linux-gnu-3.4.6 *
  [2] x86_64-pc-linux-gnu-3.4.6-hardened
  [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
  [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
  [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
  [6] x86_64-pc-linux-gnu-4.1.1



swing:
Compiling 6 source files to 
/var/tmp/portage/openoffice-2.0.4/work/ooo/build/OOO 

_2_0_4/hsqldb/unxlngx6.pro/misc/build/hsqldb/classes
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x00002acaebdf5def, pid=18525, tid=1088727376
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (Blackdown-1.4.2-03 mixed mode)
# Problematic frame:
# V  [libjvm.so+0x3fadef]
#
# An error report file with more information is saved as hs_err_pid18525.log

hsqldb:
#
# If you would like to submit a bug report, please visit:
#   http://www.blackdown.org/cgi-bin/jdk
#
dmake:  Error code 134, while making 'ANTBUILD'
'---* tg_merge.mk *---'
dmake:  Error code 255, while making 
'./unxlngx6.pro/misc/build/so_built_so_hsql 

db'
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making 
/var/tmp/portage/openoffice-2.0.4/work/ 

ooo/build/OOO_2_0_4/hsqldb
make: *** [stamp/build] Error 1

!!! ERROR: app-office/openoffice-2.0.4 failed.
Call stack:
   ebuild.sh, line 1546:   Called dyn_compile
   ebuild.sh, line 937:   Called src_compile
   openoffice-2.0.4.ebuild, line 274:   Called die

!!! Build failed
!!! If you need support, post the topmost build error, and the call 
stack if rel
evant.

!!! When you file a bug report, please include the following information:
GENTOO_VM=blackdown-jdk-1.4.2  CLASSPATH="" 
JAVA_HOME="/opt/blackdown-jdk-1.4.2. 

03"
JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""
and of course, the output of emerge --info



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Openoffice build error (#2 to keep them in line)

[Vladimir G. Ivanovic]

On Fri, 2006-10-27 at 15:58 -0400, sean wrote:
> Any ideas on this latest build problem below?
> Not sure where to start on troubleshooting this one yet.
> 
> gcc-config -l
>   [1] x86_64-pc-linux-gnu-3.4.6 *
>   [2] x86_64-pc-linux-gnu-3.4.6-hardened
>   [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
>   [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
>   [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
>   [6] x86_64-pc-linux-gnu-4.1.1

As an aside, why are you not using 4.1.1? I've been using it without any
problems since late May 2006, and for 4.1.0, since late March 2006. The
GCC 4.x series is supposed to be a significant improvement over the 3.x
series.

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Openoffice build error (#2 to keep them in line)

[Vladimir G. Ivanovic]

On Fri, 2006-10-27 at 15:58 -0400, sean wrote:
> 
> ERROR: Error 65280 occurred while making 
> /var/tmp/portage/openoffice-2.0.4/work/ 

Interesting. I don't know if it makes a difference, but for me, emerge
uses

        /var/tmp/portage/app-office/openoffice-2.0.4/work/
                         ^^^^^^^^^^

for $WORKDIR.

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Duncan]

"Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
1161980743.12569.46.camel@scarlatti.leonora.org, excerpted below, on  Fri,
27 Oct 2006 13:25:43 -0700:

> On Fri, 2006-10-27 at 15:58 -0400, sean wrote:
>> 
>> ERROR: Error 65280 occurred while making 
>> /var/tmp/portage/openoffice-2.0.4/work/ 
> 
> Interesting. I don't know if it makes a difference, but for me, emerge
> uses
> 
>         /var/tmp/portage/app-office/openoffice-2.0.4/work/
>                          ^^^^^^^^^^
> 
> for $WORKDIR.

The addition of $CATEGORY in $WORKDIR is very new to portage.  You are
probably running ~amd64 and have a portage with it.  Sean will be running
an older portage (maybe latest stable?), without it.  That's the
difference there.  It /shouldn't/ have anything to do with the problem.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Duncan]

"Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
1161980210.12569.39.camel@scarlatti.leonora.org, excerpted below, on  Fri,
27 Oct 2006 13:16:50 -0700:

> On Fri, 2006-10-27 at 15:58 -0400, sean wrote:
>> Any ideas on this latest build problem below?
>> Not sure where to start on troubleshooting this one yet.
>> 
>> gcc-config -l
>>   [1] x86_64-pc-linux-gnu-3.4.6 *
>>   [2] x86_64-pc-linux-gnu-3.4.6-hardened
>>   [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
>>   [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
>>   [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
>>   [6] x86_64-pc-linux-gnu-4.1.1
> 
> As an aside, why are you not using 4.1.1? I've been using it without any
> problems since late May 2006, and for 4.1.0, since late March 2006. The
> GCC 4.x series is supposed to be a significant improvement over the 3.x
> series.

Same here, but I won't use java as its not Freedomware yet (the latest
headlines say by Christmas), and don't need an office suite installed, so
I presumed he was using the old gcc for something OOo or Java specific. 
If not, that might be a problem, tho it doesn't seem to be related to this
one, which looks to be Blackdown specific.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Openoffice build error (#2 to keep them in line)

[sean]

Vladimir G. Ivanovic wrote:
> On Fri, 2006-10-27 at 15:58 -0400, sean wrote:
>> Any ideas on this latest build problem below?
>> Not sure where to start on troubleshooting this one yet.
>>
>> gcc-config -l
>>   [1] x86_64-pc-linux-gnu-3.4.6 *
>>   [2] x86_64-pc-linux-gnu-3.4.6-hardened
>>   [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
>>   [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
>>   [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
>>   [6] x86_64-pc-linux-gnu-4.1.1
> 
> As an aside, why are you not using 4.1.1? I've been using it without any
> problems since late May 2006, and for 4.1.0, since late March 2006. The
> GCC 4.x series is supposed to be a significant improvement over the 3.x
> series.
> 
> --- Vladimir
> 

I was running 3.4.6 because I did not know any better.
I have only been running Gentoo (amd64 or any other version) for a short 
time now on a regular basis and did not know any better.

Still learning (slowly as time and problems arise) what I need to do to 
maintain the system.

After reading your post I went to work on how to update gcc. Completed 
that earlier today then went to work on Openoffice.

Openoffice had been a bear to compile. Had many problems, failed often, 
plus the storm that came through caused power problems. Finally have 
managed to get a clean build and all is working. OO definitely starts up 
faster after being compiled, rather then the bin.

	Thanks all for the help and pointers, it made the difference.
				Sean
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[sean]

Duncan wrote:
> "Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
> 1161980743.12569.46.camel@scarlatti.leonora.org, excerpted below, on  Fri,
> 27 Oct 2006 13:25:43 -0700:
> 
>> On Fri, 2006-10-27 at 15:58 -0400, sean wrote:
>>> ERROR: Error 65280 occurred while making 
>>> /var/tmp/portage/openoffice-2.0.4/work/ 
>> Interesting. I don't know if it makes a difference, but for me, emerge
>> uses
>>
>>         /var/tmp/portage/app-office/openoffice-2.0.4/work/
>>                          ^^^^^^^^^^
>>
>> for $WORKDIR.
> 
> The addition of $CATEGORY in $WORKDIR is very new to portage.  You are
> probably running ~amd64 and have a portage with it.  Sean will be running
> an older portage (maybe latest stable?), without it.  That's the
> difference there.  It /shouldn't/ have anything to do with the problem.
> 

What do you mean by running a very new portage versus an older portage?

I know the difference between stable and the ~amd64 unstable sign.
However, how do I specify, or know that I am running at least the most 
recent stable version of portage?

I was under the impression that when I did the following

'emerge --sync; emerge portage; emerge --update --deep --newuse 
world;revdep-rebuild;revdep-rebuild'

that portage was brought up to date and all packages with it?

I have to find time to look over more of the Gentoo docs to see what 
regular maintenance I need to keep up on.



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Openoffice build error (#2 to keep them in line)

[Vladimir G. Ivanovic]

On Sat, 2006-10-28 at 22:19 -0400, sean wrote:
> I was running 3.4.6 because I did not know any better.
> I have only been running Gentoo (amd64 or any other version) for a short 
> time now on a regular basis and did not know any better.
> 
> Still learning (slowly as time and problems arise) what I need to do to 
> maintain the system.

Yes, we all live and learn. It's worth remembering that we all didn't
know this stuff at some point in our lives.

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Duncan]

sean <tech.junk@verizon.net> posted 45440FA2.4070509@verizon.net,
excerpted below, on  Sat, 28 Oct 2006 22:19:14 -0400:

> Still learning (slowly as time and problems arise) what I need to do to
> maintain the system.
> 
> After reading your post I went to work on how to update gcc. Completed
> that earlier today then went to work on Openoffice.
> 
> Openoffice had been a bear to compile. Had many problems, failed often,
> plus the storm that came through caused power problems. Finally have
> managed to get a clean build and all is working. OO definitely starts up
> faster after being compiled, rather then the bin.
> 
> 	Thanks all for the help and pointers, it made the difference.

Hey, thanks for the feedback, too.  It's great to see someone finally work
thru a problem and get things working, and even greater when they were
able to learn something new from it, making things easier the next time.
=8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Duncan]

sean <tech.junk@verizon.net> posted 45441105.6060907@verizon.net,
excerpted below, on  Sat, 28 Oct 2006 22:25:09 -0400:

> Duncan wrote:

>> The addition of $CATEGORY in $WORKDIR is very new to portage.  You are
>> probably running ~amd64 and have a portage with it.  Sean will be
>> running an older portage (maybe latest stable?), without it.  That's
>> the difference there.  It /shouldn't/ have anything to do with the
>> problem.
>> 
>> 
> What do you mean by running a very new portage versus an older portage?
> 
> I know the difference between stable and the ~amd64 unstable sign.
> However, how do I specify, or know that I am running at least the most
> recent stable version of portage?
> 
> I was under the impression that when I did the following
> 
> 'emerge --sync; emerge portage; emerge --update --deep --newuse
> world;revdep-rebuild;revdep-rebuild'
> 
> that portage was brought up to date and all packages with it?
> 
> I have to find time to look over more of the Gentoo docs to see what
> regular maintenance I need to keep up on.

Yes.  That's all that's needed.  In fact, it's more than many do.  Many
don't routinely --update --deep, only --update, and many don't routinely
--newuse either.  I prefer to keep all dependencies and USE flags updated,
so I --sync and --update --deep --newuse world several times a week, but
only revdep-rebuild maybe once a month unless I suspect something might be
wrong.

What I was suggesting was that you are probably at the newest stable,
while I and presumably Vladimir are running newest ~amd64.  I've not
updated yet today and skipped yesterday, but...

$emerge --pretend portage

These are the packages that would be merged, in order:

Calculating dependencies ... done!
[ebuild   R   ] sys-apps/portage-2.1.2_pre3-r9

I believe the category addition to the portage workdir path he mentioned
was only added to the 2.1.2_preX branch, which will certainly not be
stable, only ~arch, at this point.  2.1.1 will be the latest portage stable
series at this point, and I don't believe it has the package category in
the workdir path.  Thus, I was simply saying that he probably had it as
he's running unstable, whereas you were probably running stable and
therefore didn't have it.

That should explain that.  As for reading up on the docs, I'd suggest the
stuff in the Gentoo Handbook beyond installation, if you haven't read it
yet.  Namely, read (some sections you can just skim, you'll probably
figure out which ones) the Working with Gentoo and Working with Portage
parts of the handbook.  Gentoo is fairly well known in the community for
its generally great documentation, and it's a shame that so many Gentoo
users don't even read the handbook beyond the installation section.  It's
WELL worth the time it takes to do so, and by doing so, you'll know more
about efficiently sysadmining your Gentoo system, AND (unfortunately for
those that skip it) already have a step up on I'd guess at least 50% of
Gentoo users less than six months in.  As I said, it's unfortunate that so
many skip it, as it sure did ME a world of good, but a lot do...

Beyond that, read the various portage manpages, portage, emerge,
make.conf, ebuild (both man 1 ebuild and man 5 ebuild) and the notes in
make.conf.example and make.conf.global.  Of course, you don't have to do
this all at once.  Take a year to do it if you want, more if you need.  But
it's there when you are ready. There's all sorts of directions you can go
after that.  Gentoo is virtually infinitely customizable, and what's more,
it's relatively easy to do, AND there are quite good directions available
for a fair sized share of it!  The only limits are time, and those you
place on yourself!  =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Vladimir G. Ivanovic]

On Sun, 2006-10-29 at 12:55 +0000, Duncan wrote:
> What I was suggesting was that you are probably at the newest stable,
> while I and presumably Vladimir are running newest ~amd64.

Yes, I am running ~amd64 (ACCEPT_KEYWORDS="amd64 ~amd64"
in /etc/make.conf.) I also changed to the 2006.0 profile, although I've
forgotten how I did that.

So far (more than 6 months), no serious problems. (Knock on wood.)

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Duncan]

"Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
1162146694.4486.5.camel@scarlatti.leonora.org, excerpted below, on  Sun,
29 Oct 2006 10:31:34 -0800:

> Yes, I am running ~amd64 (ACCEPT_KEYWORDS="amd64 ~amd64"
> in /etc/make.conf.) I also changed to the 2006.0 profile, although I've
> forgotten how I did that.

FWIW, I update profiles when or somewhat before they go public, so have
been on 2006.1/desktop for some time now.

I /think/ it covers changing profiles in the manual, either that or in a
howto somewhere, but normally, it's just make sure you are up2date where
you are (emerge --sync, emerge --newuse --deep --update world,
revdep-rebuild, preferrably at least look at emerge --pretend --depclean
and either unmerge the ebuilds or add to world as needed, then do another
revdep-rebuild), point your /etc/make.profile symlink at the new profile
desired, and do another emerge --newuse --deep --update world to update to
anything the new profile changed.

Of course, those emerges should be previewed with --pretend --verbose
first, to see what it's going to do, so nothing unexpected hits you in the
face.  That's PARTICULARLY true with the first one after updating the
profile symlink, as until you start merging stuff, no harm done and it's
easy to reverse if necessary, but it might not be so easy after you start
merging stuff.

Not all profile updates are routine, however.  2006 has been pretty
smooth, but for us folks on Gentoo/amd64, the 2004.3 and 2005 profile
updates were rather major, as they involved rather large changes to the
way multilib was handled, and if the update wasn't done following the
instructions precisely, it could (and did) leave people with broken
systems.  Some of them worked their way out of the mess.  Others gave up
and decided it was easier to start over from a fresh stage install.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Vladimir G. Ivanovic]

On Sun, 2006-10-29 at 22:34 +0000, Duncan wrote:
> "Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
> 1162146694.4486.5.camel@scarlatti.leonora.org, excerpted below, on  Sun,
> 29 Oct 2006 10:31:34 -0800:
> 
> > Yes, I am running ~amd64 (ACCEPT_KEYWORDS="amd64 ~amd64"
> > in /etc/make.conf.) I also changed to the 2006.0 profile, although I've
> > forgotten how I did that.
> 
> FWIW, I update profiles when or somewhat before they go public, so have
> been on 2006.1/desktop for some time now.

Thanks for the nice writeup. A quick question: Any idea why all the
examples for changing a profile in the "Gentoo Upgrading Guide" have two
leading periods, as in:

ln -s ../usr/portage/profiles/default-linux/amd64/2006.1/desktop \ 
      /etc/make.profile
         
The two periods seem completely redundant to me.

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Boyd Stephen Smith Jr.]

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

On Tuesday 31 October 2006 03:16, "Vladimir G. Ivanovic" 
<vgivanovic@comcast.net> wrote about 'Re: [gentoo-amd64]  Re: Openoffice 
build error (#2 to keep them in line)':
> Any idea why all the
> examples for changing a profile in the "Gentoo Upgrading Guide" have two
> leading periods, as in:
>
> ln -s ../usr/portage/profiles/default-linux/amd64/2006.1/desktop \
>       /etc/make.profile
>
> The two periods seem completely redundant to me.

Think of having a Gentoo system under, e.g., /chroot while / has another OS 
or just a Gentoo system that uses a different PORTDIR.  You 
need /chroot/etc/make.profile to point to /chroot/usr/portage/<stuff> 
before your execute the 'chroot /chroot /bin/bash' command 
and /usr/portage/<stuff> afterwards.  Using a relative path, as opposed to 
an absolute path, is required to get that behavior.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Vladimir G. Ivanovic]

On Tue, 2006-10-31 at 07:21 -0500, Boyd Stephen Smith Jr. wrote:
> On Tuesday 31 October 2006 03:16, "Vladimir G. Ivanovic" 
> <vgivanovic@comcast.net> wrote about 'Re: [gentoo-amd64]  Re: Openoffice 
> build error (#2 to keep them in line)':
> > Any idea why all the
> > examples for changing a profile in the "Gentoo Upgrading Guide" have two
> > leading periods, as in:
> >
> > ln -s ../usr/portage/profiles/default-linux/amd64/2006.1/desktop \
> >       /etc/make.profile
> >
> > The two periods seem completely redundant to me.
> 
> Think of having a Gentoo system under, e.g., /chroot while / has another OS 
> or just a Gentoo system that uses a different PORTDIR.  You 
> need /chroot/etc/make.profile to point to /chroot/usr/portage/<stuff> 
> before your execute the 'chroot /chroot /bin/bash' command 
> and /usr/portage/<stuff> afterwards.  Using a relative path, as opposed to 
> an absolute path, is required to get that behavior.

OK, got it. Thanks.

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Openoffice build error (#2 to keep them in line)

[Duncan]

"Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
1162286197.11774.7.camel@scarlatti.leonora.org, excerpted below, on  Tue,
31 Oct 2006 01:16:37 -0800:

> Thanks for the nice writeup. A quick question: Any idea why all the
> examples for changing a profile in the "Gentoo Upgrading Guide" have two
> leading periods, as in:
> 
> ln -s ../usr/portage/profiles/default-linux/amd64/2006.1/desktop \
>       /etc/make.profile
>          
> The two periods seem completely redundant to me.

It's relative paths vs. absolute paths.  These are of course from the
make.profile location in etc, but in some cases, the $ROOT (see the entry
for that variable in the make.conf manpage) won't be /, so ../usr,
relative from the location of the symlink, may not be the same thing as
/usr, the absolute path, at all.

IOW, for a regular installation, the two paths may be the same, but not
all installations are "regular installations"! =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list