bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error In Installation


From: Adam Fedor
Subject: Re: Error In Installation
Date: Wed, 30 Apr 2014 08:29:19 -0400

On Apr 30, 2014, at 4:05 AM, Richard Frith-Macdonald 
<richardfrithmacdonald@gmail.com> wrote:

> 
> On 28 Apr 2014, at 22:54, Aman kumar choudhary <amankch@gmail.com> wrote:
> 
>> Still facing problem after successfully installing "libicu-dev" package. 
>> When invoking "$ make" command it's produce error and abort the 
>> installation. Again I am going to attach screen-shot of error and 
>> logs.tar.gz file with this mail. As on before help is appreciated.
>> 
>> Thank You.
>> 
>> 
>> --
> 
> Could it be that you are using an old version of the startup package to build 
> an un to date version of GNUstep?
> 
> The reason for this suspicion is that nowadays the default installation for 
> the gnustep libraries is the local domain (/usr/GNUstep/Local) and the logs 
> show them being installed there.  However, the error you are seeing from the 
> startup script is looking for things in the system domain 
> (/usr/GNUstep/System) which is where things used to be installed by default.
> 
> The startup script was altered so it should explicitly build things to 
> install in the system domain a few years ago ... so the logs *shouldn't* be 
> showing installation in the local domain.
> 
> Anyway, from the logs it looks like things are getting everything built and 
> installed in the local domain, but the script is complaining because it 
> expects to find them in the system domain, so it is probably producing a 
> usable installation in spite of the error reports.

I can’t really see what could be wrong either.  Base seems to detect that it 
should be installed in System, but then it installs itself in Local anyways, 
despite the fact that Startup always should force the installation to System.  
Perhaps there is an old file (like GNUstep.conf) left over from the debian 
installation that is causing a problem.  Still it should be usable anyway.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]