Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 174794
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: OpenOffice Team <openoffice@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Christian Heim (RETIRED) <phreak@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 174794 depends on: Show dependency tree
Bug 174794 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-04-16 13:54 0000
openoffice-2.2.0 will fail during src_compile complaining about too old
autoconf, which is masked for some reason (at least on hardened).

> aclocal.m4:14: error: this file was generated for autoconf 2.61.
> You have another version of autoconf.  If you want to use that,
> you should regenerate the build system entirely.

After adding inherit autotools and eautoreconf (in src_unpack), openoffice is
building atm.

------- Comment #1 From Andreas Proschofsky 2007-04-16 14:33:24 0000 -------
Hmm, why is this masked on hardened? On all other platforms it seems to be
marked stable already.

Anyway: Maybe that's just because I rolled the tarball for ooo-build myself, so
if anyone knows how to do this in a better way (never done it before,
actually), please add your input

------- Comment #2 From Christian Heim (RETIRED) 2007-04-16 15:12:22 0000 -------
(In reply to comment #1)
> Hmm, why is this masked on hardened? On all other platforms it seems to be
> marked stable already.

It's masked because of bug 161566.

------- Comment #3 From Hanno Meyer-Thurow 2007-04-16 16:32:23 0000 -------
Christian pointed out the correct way. One should use eautoreconf from
autotools eclass over direct auto* calls in ebuilds.

So replacing autoconf with eautoreconf in src_compile would be correct.

------- Comment #4 From solar 2007-04-16 16:59:59 0000 -------
(In reply to comment #3)
> So replacing autoconf with eautoreconf in src_compile would be correct.

I think you mean src_unpack()

------- Comment #5 From Hanno Meyer-Thurow 2007-04-16 18:11:44 0000 -------
no, look at ebuild. ;)
that's the way there.

------- Comment #6 From solar 2007-04-16 20:53:36 0000 -------
Then thats a QA problem. eauto* should be called at the tail end of a
src_unpack()

------- Comment #7 From Andreas Proschofsky 2007-04-17 04:50:30 0000 -------
(In reply to comment #3)
> Christian pointed out the correct way. One should use eautoreconf from
> autotools eclass over direct auto* calls in ebuilds.
> 
> So replacing autoconf with eautoreconf in src_compile would be correct.
> 

I know, but that's actually not what I was asking about. As I've been rolling
the tarball myself, the cleaner solution might be to use an older autoconf when
doing that instead of having to use an otherwise not necessary call of
eautoreconf.

Still I've fixed this now as proposed (using eautoreconf and moving it up to
src_unpack() where it really belongs), closing

------- Comment #8 From Hanno Meyer-Thurow 2007-04-17 10:02:19 0000 -------
If you take sources from svn or cvs you should run ./autogen.sh, shouldn't you?
What it does is nothing more than what eautoreconf does. And the latter one
does (I guess) some extra Gentooism tweaks.

O well, may be I misunderstand your question again? :) ... then just ignore it.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug