On Tue, Apr 22, 2008 at 09:54:46AM -0700, Richard E. Miles wrote:
>
> On Apr 22, 2008, at 8:11 AM, Daniel Macks wrote:
>
> > On Tue, Apr 22, 2008 at 04:02:06PM +0200, Jean-Fran?ois Mertens wrote:
> >>
> >> On 22 Apr 2008, at 12:11, Les Bowen wrote:
> >>> Confirming that this problem also exists on PowerPC OSX 10.5.2.
> >>
> >> here build proceeds quite well with automake-10 installed..
> >> so at worst a builddep on automaken might suffice.
> >> But didn't try yet w/o any automake _ I suspect the problem
> >> might be different)
> >>
> >> Note that configure has a hard-coded am__api_version="1.6",
> >> and
> >> ACLOCAL=${ACLOCAL-"${am_missing_run}aclocal-${am__api_version}"}
> >> leads it find _ on 10.4 ! _ aclocal-1.6 in /usr ..
> >>
> >> leading thus to a major error : direct install into /usr :
> >>
> >>> checking for aclocal directory... /usr/share/aclocal
> >>> ....
> >>> Making install in m4
> >>> make[2]: Nothing to be done for `install-exec-am'.
> >>> /bin/sh ../mkinstalldirs /usr/share/aclocal
> >>> /sw/bin/ginstall -c -m 644 dvdnav.m4 /usr/share/aclocal/dvdnav.m4
> >>
> >> But even on 10.5, with automake-1.6 installed, I guess this
> >> will be a direct install too (in %p this time).
> >
> > And --build-as-nobody doesn't catch it because the logic is:
> >
> > if root:
> > if `aclocal` found:
> > install to that aclocal's data dir directly
> > else:
> > install to /usr/local/share/aclocal directly
> > else:
> > use $prefix/share/aclocal and respect DESTDIR
> >
> > I just committed a change to make root detection fail in that test and
> > removed the automake1.10 dep. "works for me" as root and nobody,
> > please test.
>
> I tried yesterday to build this package and it ran for 6 hours and
> locked up my computer. I had to press the power button on the back of
> the imac display as I could not use mouse or keyboard to force quit.
> It seems to go over and over and over trying to determine
> dependencies. I use leopard 10.5 intel imac. I suspect that it must of
> consumed all available memory or something to lock up my computer in
> this manner. I don't know how to fix this so I am no longer doing fink
> update-all.
I have never recommended update-all as a good solution for
*anything*:) All I'm trying to do is solve the specific bug at
hand--if you're having some other problem or unrelated symptoms with
this or another package, please file a separate bug report.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
