[Top][All Lists]

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

Re: [Aspell-user] Building aspell-0.60 rpm from the source

From: Christoph Hintermüller
Subject: Re: [Aspell-user] Building aspell-0.60 rpm from the source
Date: Tue, 5 Oct 2004 18:55:31 +0200
User-agent: KMail/1.6.2

Hi Pawel
Am Montag, 4. Oktober 2004 22:15 schrieb Pawel Tatera:
> Hello
> 1.
> Well I don't have a problem with apell itself but how to build the RPM 
> from source code (aspell-0.60.tar). I'd like to create the RPM but I can't 
> find any rpm.spec file to create it. Can I use a the file from earlier 
> releases (I got one from aspell-0.33) and modify it a bit.
> Specially do i still need a pspell-devel to build it? 
No You don't if you would read the website and afaik the user and 
developement manual you'd know that it doesn't need pspell anymore as aspell 
since kevin maintains it and that's since 0.50.x is all you need
> I already made some  
> tests with command './configure && make' and I menaged to buld aspell-0.60 
> with pspell-0.11.2-2 and gcc-2.96-112.7.1 (RedHat Linux 7.1) not having 
> pspell-devll even installed - it built with no errors at all.

> -----------piece from aspell- src rpm----------
> Requires: pspell = 3:0.12.2
> Buildrequires: pspell-devel = 3:0.12.2, gcc-c++       // do I need this 
No see above
> BuildRoot: %{_tmppath}/%{name}-%{version}-root
> Obsoletes: ispell
> ---------------------------------------------------------------------
Hm the two lines above look good allthough i do not know anything about rpm 
spec files.
> 2. 
> Where can I read the destination paths from ? - to put compiled executables, 
> manuals docs and so on?
Hm why not dooing a ./configure --help to get all the configure parameters 
setting pathes and than telling rpm to set them on configure run explicitly
 eg: ./configure --prefix /usr would put all the aspell related files in 
the /usr hirachy and aspell binary would endup in /usr/bin

but there are a lot more parameters you could explicitly force by ./configure 
switches. Thus why bothering where ./configure per default likes to put the 
different parts of aspell when beeing able to enforce specific locations.
So i think there are some lines in the spec file which will do this for you 
implicitly and might be will help you too
> Can you answere my questions or direct me where can I find some more help?
Yes see the above link

reply via email to

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