cairo-dock-plugins does not support prefix on make install

Bug #531317 reported by Sylvestre Ledru on 2010-03-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cairo-Dock Plug-ins
Undecided
Unassigned

Bug Description

Hello

Compiling and installing cairo-dock-plugins with a prefix fails.

The commands:
$ ./configure --prefix=/tmp/cairo-plugins && make install

Will fail here:
test -z "/usr/lib/cairo-dock" || /bin/mkdir -p "/usr/lib/cairo-dock"
/bin/mkdir: ne peut créer le répertoire `/usr/lib/cairo-dock': Permission non accordée

Related branches

Matthieu Baerts (matttbe) wrote :

Heelo,

If you set a prefix, please chose the same as the core. e.g.:
  $ cd cairo-dock_2.1.3-6/
  $ autoreconf -isvf && ./configure --prefix=/usr && make
  # make install
  $ cd ../cairo-dock-plugins_2.1.3-6/
  $ autoreconf -isvf && ./configure --prefix=/usr && make
  # make install

Whitout this prefix, CD is installed on "/usr/local/".

Notre wiki est complet et bien documenté ;) => http://www.glx-dock.org/ww_page.php?p=Par%20compilation&lang=fr

Sylvestre Ledru (sylvestre) wrote :

It was just an example to show the issue ;)

Matthieu Baerts (matttbe) wrote :

Ok but most of people uses a prefix :) .
I use it to make deb packages, on my computer, etc.

I just know that it could have some bugs on Mandriva and OpenSuse for 64bits users because this repertory /usr/lib64/ isn't a symbolic link of /usr/lib/

So if you already have this bug with previous given commands, simply add the output from your terminal here !

Fabounet (fabounet03) wrote :

the prefix must be the same for both the core and the plug-ins.
this is because the core has to know where the plug-ins are, therefore it defines this at the same time it is compiled.
Then the plug-ins ask the core where they should install ($libdir and $datadir are consequently overwritten).

this is not really an issue, this is just the way plug-ins should be compiled :-)

Changed in cairo-dock-plug-ins:
status: New → Invalid
Sylvestre Ledru (sylvestre) wrote :

It is an issue since the path provided as prefix is not taken in account.
The configure should at least stop when it detects that the prefix is not the same path as cairo-dock.

Changed in cairo-dock-plug-ins:
status: Invalid → New
Fabounet (fabounet03) wrote :

ok well then I'll add a test in the configure, and be more clear about it in the INSTALL file.

Fabounet (fabounet03) on 2010-03-04
Changed in cairo-dock-plug-ins:
status: New → In Progress
Fabounet (fabounet03) on 2010-03-04
Changed in cairo-dock-plug-ins:
status: In Progress → Fix Committed
Changed in cairo-dock-plug-ins:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers