checking sytemd system unit dir… configure: error: systemd system unit directory is required
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=bluez&project=home%3Aryanbach%3Abranches%3ABase%3ASystem&repository=openSUSE_Factory
This doesn’t seem to work anymore:
%if 0%{?has_systemd}
–with-systemdunitdir=%{_unitdir}
%endif
Any clue on what I should do? Thanks in advance.
On Mon 28 Jan 2013 12:36:01 AM CST, ryanbach wrote:
checking sytemd system unit dir… configure: error: systemd system unit
directory is required
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=bluez&project=home%3Aryanbach%3Abranches%3ABase%3ASystem&repository=openSUSE_Factory
This doesn’t seem to work anymore:
%if 0%{?has_systemd}
–with-systemdunitdir=%{_unitdir}
%endif
Any clue on what I should do? Thanks in advance.
Hi
This is why;
97s] configure: WARNING: unrecognized options:
--with-systemdunitdir, --enable-gstreamer, --enable-alsa,
--enable-bccmd, --enable-hid2hci, --enable-dfutool, --enable-pand,
--enable-dund, --enable-wiimote, --enable-pcmcia
It doesn’t understand the above…
–
Cheers Malcolm °¿° (Linux Counter #276890 )
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 1 day 8:07, 3 users, load average: 0.30, 0.12, 0.07
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
On Mon 28 Jan 2013 08:46:02 PM CST, ryanbach wrote:
I have some problems now with unpackaged files, could I get someone to
do that?
http://tinyurl.com/alpu687
Here is the spec file:
http://tinyurl.com/b52gh3l
Hi
So on 12.2 files are here /usr/lib64/obex/obexd
and /usr/sbin/bluetoothd and bccmb
You need to check your configure options…
–
Cheers Malcolm °¿° (Linux Counter #276890 )
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 2 days 4:10, 3 users, load average: 0.08, 0.06, 0.05
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
I have packed the files as best as I can but there are still some that aren’t done yet. Do all of the debug files go under devel subpackage?
Hi
No, the debug files are automatically generated during the build and packaged up automatically as well.
Okay, thanks. I am just having trouble with the rest of the files…
sumski
January 30, 2013, 5:03am
9
File not found: /home/abuild/rpmbuild/BUILDROOT/bluez-5.1-171.1.x86_64/usr/lib64/bluetooth/bluetoothd
File not found: /home/abuild/rpmbuild/BUILDROOT/bluez-5.1-171.1.x86_64/usr/lib64/bluetooth/obexd
File must begin with "/": %{_sharedir}/dbus-1/services/org.bluez.obex.service
Installed (but unpackaged) file(s) found:
/lib/bluetooth/bluetoothd
/lib/bluetooth/obexd
You should probably re-check your configure flags
%{_datarootdir}, at least on 12.2
configure: error: expected an absolute directory name for --libexecdir:
Before this was just /usr/ but someone said that wasn’t the right configuration. What should it be?
On Sun 10 Feb 2013 01:06:02 AM CST, ryanbach wrote:
configure: error: expected an absolute directory name for --libexecdir:
Before this was just /usr/ but someone said that wasn’t the right
configuration. What should it be?
Hi
If you run the %configure macro when building it should take care of it
all, but if manually added it’s;
--libexecdir=/usr/lib
–
Cheers Malcolm °¿° (Linux Counter #276890 )
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 2 days 5:22, 5 users, load average: 0.59, 0.36, 0.17
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
checking sytemd system unit dir... configure: error: systemd system unit directory is required
Why does this not work?
%if 0%{?has_systemd} --with-systemdunitdir=%{_unitdir} \
--with-systemdsysdir=%{_sysdir} \
%else
---without-systemdunitdir
%endif
This is under the %configure prefix, any clue on what I should do?
Where is has_systemd defined?
%{?systemd_requires}
%define has_systemd 1
%endif
This isn’t correct what should I do (for variables like below): or should I put the directories (anyone know them)?
--with-systemdunitdir=%{_unitdir} \
--with-systemdsysdir=%{_sysdir} \
Please post full code that includes opening %if?
-with-systemdunitdir=/etc/systemd/system/what is --with-systemdsysdir=
?
configure: WARNING: unrecognized options: --with-systemdunitdir, --with-systemdsysdir,
I already recommended running “configure --help”. Did you do it? Does it list these options?