Commit 200e3736 authored by Jonathan Currier's avatar Jonathan Currier

Force mboxd to always link with $(CC)

Linking with CXX breaks building on toolchains without c++ support,
even when you point CXX to CC.
Therefore, force always link with CC (it should work even if c++ code is
being linked in).
parent 6b5aff62
...@@ -13,6 +13,9 @@ mboxd_SOURCES = \ ...@@ -13,6 +13,9 @@ mboxd_SOURCES = \
transport_mbox.c \ transport_mbox.c \
windows.c \ windows.c \
mtd.c mtd.c
mboxd_LINK = $(LINK)
mboxd_LDFLAGS = $(LIBSYSTEMD_LIBS) mboxd_LDFLAGS = $(LIBSYSTEMD_LIBS)
mboxd_CFLAGS = $(LIBSYSTEMD_CFLAGS) mboxd_CFLAGS = $(LIBSYSTEMD_CFLAGS)
......
...@@ -32,10 +32,10 @@ The build system is a standard autotools setup. `bootstrap.sh` runs all the ...@@ -32,10 +32,10 @@ The build system is a standard autotools setup. `bootstrap.sh` runs all the
jobs necessary to initialise autotools. jobs necessary to initialise autotools.
By default mboxd is configured and built _without_ the 'virtual PNOR' feature By default mboxd is configured and built _without_ the 'virtual PNOR' feature
discussed below. The virtual PNOR functionality is written in C++, and due to discussed below. The virtual PNOR functionality is written in C++, and in
some autotools clunkiness even if it is disabled mboxd will still be linked prevous versions, due to some autotools clunkiness even if it is disabled mboxd
with `CXX`. Point `CXX` to `cc` at configure time if you do not have a C++ will still be linked with `CXX`. This is no longer true. mboxd always links
compiler for your target (`./configure CXX=cc`). with $(CC).
If you are hacking on the reference implementation it's recommended to run If you are hacking on the reference implementation it's recommended to run
`bootstrap.sh` with the `dev` argument: `bootstrap.sh` with the `dev` argument:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment