Le Thursday 26 March 2009 02:34:23 David Baelde, vous avez écrit :
> Hi,
Hi all !
Thanks for your nice feedback !
> Thanks for the feedback, it might indeed be useful.
>
> 2009/3/25 Orama Avis <[email protected]>:
> > setenv CPPFLAGS -I/usr/local/include
> > setenv LDFLAGS -L/usr/local/lib
>
> Okay. There might also be a way to pass them as parameters to configure.
Indeed, calling configure like:
./configure CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib"
should make this permanent, including during build.
> > Due to problem with gmake / make, the fastest (but obviously not the
> > proper) way was to edit Makefile and replace all occurences of "make"
> > with "gmake". Those were only few, and it worked fine.
>
> We should get rid of those. A quick check showed that many libraries
> call make in the doc target, instead of calling $(MAKE) which would
> implicitly be gmake. In liquidsoap, the situation might not be ideal:
> the MAKE variable is set in Makefile.defs, depending on what configure
> detects -- I'm wondering if this definition is ever needed.
Ok, I just fixed this in trunk/
> > gmake:
> > ------------
> >
> > The build immediately started to complain about linker problems:
> >
> > /usr/bin/ld -lshout
> > ld: cannot find -lshout
>
> This is also bad. The problem should be reported at configure-time.
> It's a matter of passing the right variable at the right place -- easy
> to say..
As said above, this should be permanent when added at configure time.
> > /usr/bin/ld: cannot find -l-L/usr/local/lib
> > gmake[3]: *** [dllbjack_stubs.so] Error 2
>
> Yuk.
Humm.. Strange issue.. I am currently unable to find the culprit for this.. If
you can give more detailed informations, probably we could fix it..
> > gmake install:
> > -----------------------
> >
> > Almost all is fine, the only thing is that you have to manually create
> > user liquidsoap and group liquidsoap before running gmake install.
> > Also log file and pid file directory must be created manually.
>
> This is all normal. We leave the creation of users and directories to
> the user, or the distro-specific packages.
Humm.. from liquidsoap/Makefile:
# User ${user} and group ${group} are expected to exist.
# They are defined in Makefile.defs, written by configure.
but then it will try even if they don't exist..
Probably we should issue a warning and not fail when user and group do not
exist.. What is the most standard way to check if a user/group exist in both
linux and BSD ?
Romain
------------------------------------------------------------------------------
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
