Mailinglist Archive: opensuse-packaging (284 mails)
| < Previous | Next > |
Re: [opensuse-packaging] FLU packaging compiles but no result
- From: Michal Marek <mmarek@xxxxxxx>
- Date: Fri, 11 Feb 2011 17:34:57 +0100
- Message-id: <4D556531.5030703@suse.cz>
On 11.2.2011 16:51, Sascha Manns wrote:
In general, the commands in the Makefile need to be changed from
install somebinary /usr/bin/somebinary
to
install somebinary $(DESTDIR)/usr/bin/somebinary
Often the Makefile is generated by configure from Makefile.in, in that
case you need to make the changes there. Otherwise, try to find out what
generates such commands and add the $(DESTDIR) there.
hth,
Michal
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
Hi Michal,
Michal Marek <mmarek@xxxxxxx> wrote at Friday 11 February 2011:
On 10.2.2011 22:41, Sascha Manns wrote:Thanks for spending time :-)
Now i have just this Problem:
+ make DESTDIR=/usr/src/packages/BUILDROOT/fltk-flu-2.14-6.1.i386
install
=== installing FLU ===
Installing binaries in /usr/bin...
cp: cannot create regular file `/usr/bin/flu-config': Permission de
nied
But that i don't understand. I've set %{buildroot} and flu-config
is a binary and should placed in %{_bindir}.
You need to patch the Makefile to understand DESTDIR.
The Problem i see is, that the Makefile is created by the configure
Script. But the Configure Script is self written by the Author, no
"normal" configure.
Have you an idea, what i must change to make it runable?
In general, the commands in the Makefile need to be changed from
install somebinary /usr/bin/somebinary
to
install somebinary $(DESTDIR)/usr/bin/somebinary
Often the Makefile is generated by configure from Makefile.in, in that
case you need to make the changes there. Otherwise, try to find out what
generates such commands and add the $(DESTDIR) there.
hth,
Michal
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |