If the Unified Installer failed with a missing gcc message, that probably means that the command "which gcc" didn't turn up an executable. The most likely explanation is that gcc wasn't on the execution path for the invoking user. It's also possible, of course, that there's some logical error in the install.sh script in checking the "which" results. Let me know if you learn more!
Steve On Thu, Jan 8, 2009 at 6:10 PM, Dale DeWitt <[email protected]> wrote: > I had no problem using the standard 3.1.7 unified installer on an > opensolaris/virtualbox/windows. But when using the same unified > installer on opensolaris/bare-metal . . . and a newly downloaded > unified installer, the scripts complained of gcc missing which wasn't > the case (identical package manager listings). So the problem wasn't > with the installer. > > I decided to copy the virtual plone instance over the network. Done. > Then the daemon would kick off after saying it had started. > Disparate, I decided to force the unified installer on this copied > Plone-3.1 Standalone. It got a few necessary steps in and then > logically aborted the installation. That removed the auto stop cited > previous. > > Voila, an opensolaris bare-metal installation by hook'n crook. > Anybody have a more formal logic why bare-metal and the unified > installer failed? I'm hoping this terse diary isn't too vauge. > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > -- Steve McMahon Reid-McMahon, LLC [email protected] [email protected] _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
