Nut upsdev - Dec 2014 - GD libraries and $PREFIX (was Re: building NUT on Mac OS X Yosemite(website/documentation))

After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,

Configuration summary:
=====================build serial drivers: yes 
build USB drivers: yes 
build SNMP drivers: yes 
build neon based XML driver: yes 
enable Avahi support: no 
build Powerman PDU client driver: no
build IPMI driver: no
build Mac OS X meta-driver: yes
build i2c based drivers: no
enable SSL support: yes (OpenSSL)
enable libwrap (tcp-wrappers) support: no
enable libltdl (Libtool dlopen abstraction) support: no
build nut-scanner: no
build CGI programs: no
build and install documentation: no
build and install the development files: no
>>>>>> Then make command looks ok, until:
Making all in docs
Making all in man
/opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. nut.conf.txt
a2x: WARNING: --destination-dir option is only applicable to HTML based outputs
>>>>>> At this stage, the process is kind of hanging, it takes
1 hour to generate the man pages.
>>>>>> then make command ends correctly without issues.




Regarding 'nut-website?, after fresh clone on Yosemite:
>>>>>> ./autogen.sh automatically clone nut and nut-dll in
nut-website.
>>>>>> can I use my own clones here?
Configuration summary:
=====================build serial drivers: yes
build USB drivers: yes
build SNMP drivers: yes
build neon based XML driver: yes
enable Avahi support: no
build Powerman PDU client driver: no
build IPMI driver: no
build Mac OS X meta-driver: yes
build i2c based drivers: no
enable SSL support: yes (OpenSSL)
enable libwrap (tcp-wrappers) support: no
enable libltdl (Libtool dlopen abstraction) support: no
build nut-scanner: no
build CGI programs: no
build and install documentation: no
build and install the development files: no
>>>>>> then make command. I have this one dozen of times:
sort: stray character in field spec: invalid field specification `4.1,4.5rV
>>>>>> and it ends with:
/opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
--attribute icons --attribute linkcss --attribute=badges --attribute=website
--attribute=quirks --attribute=revision=2.7.2 --attribute tree_version=2.7
--attribute localdate=`TZ=UTC date +%Y-%m-%d` --attribute localtime=`TZ=UTC date
+%H:%M:%S` --attribute=date="`TZ=UTC date`" --attribute
iconsdir=./images --attribute scriptsdir=./scripts -o projects.html -a toc
projects.txt
make: *** No rule to make target `-eindex.html', needed by
`ups-html.txt'.  Stop.

>>>>>> I apply aquette patch in
'nut-website/nut/configure.ac?, then apply 'make' command
>>>>>> no more 'sort: stray character in field spec:
invalid field specification `4.1,4.5rV? error... is it because I need to clean
something?
>>>>>> then it is taking long..minutes (near an hour right
now) generating man page:
/opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. ivtscd.txt
a2x: WARNING: --destination-dir option is only applicable to HTML based outputs


regards,
jean


> Le 20 nov. 2014 ? 15:10, Charles Lepple <clepple at gmail.com> a
?crit :
> 
> On Nov 20, 2014, at 7:11 AM, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com <mailto:jpweb.taf at gmail.com>> wrote:
> 
>> Hello,
>> Here is a summary of discussions around NUT builds on Mac OS X 10.10.
>> 
>> Starting from https://github.com/networkupstools/nut-website/issues/7
<https://github.com/networkupstools/nut-website/issues/7>
>> 
>> @JeanPerriault
>> I've found msort on macports
(https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile
<https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile>,
http://billposer.org/Software/Downloads/
<http://billposer.org/Software/Downloads/>
>> msort.pdf), but I'm not sure where to implement it, should I
replace all sort ocurrences I find in code?
>> 
>> @clepple
>> I think checking for gsort in the configure script would be better
(since that is what is used when 'sort' is invoked on Linux), and then
sort would get replaced with @GSORT@ or whatever. However, when I mentioned via
email that the website doesn't build on OS X, I wasn't thinking that it
needed to be solved soon - we can build the website and documentation on Linux
systems for now.
>> 
>> @aquette
>> considering the context and limited impact, we could simply check for
gsort first, and then sort.
>> --- a/configure.ac
>> +++ b/configure.ac
>> @@ -101,6 +101,7 @@ AC_PROG_CXX
>> AC_PROG_INSTALL
>> AC_PROG_EGREP
>> AC_PATH_PROG(AR, ar)
>> +AC_CHECK_PROGS(SORT, gsort sort)
>> AC_CHECK_TOOL(RANLIB, ranlib, :)
>> dnl Postpone call to AC_PROG_LIBTOOL to allow disabling static lib
>> AC_C_BIGENDIAN
> 
> Just to clarify, the sort error is only when building nut-website:
> 
> 	sort: stray character in field spec: invalid field specification
`4.1,4.5rV'
> 
> Also, you had mentioned dependencies for building documentation. This
affects NUT non-website builds as well, but the list looks something like this:
> 
> 	? asciidoc
> 	? asciidoc-a2x (if packaged separately)
> 	? docbook-xsl (symptom for Debian bug #635347; xsltproc will otherwise try
to download DocBook files from the net)
> 	? dblatex
> 
> We are trying to reduce the dependencies needed to build the .tar.gz
snapshots, so you might want to try one of them:
> 
> http://buildbot.networkupstools.org/snapshots
<http://buildbot.networkupstools.org/snapshots>
> 
> The snapshots include some HTML rendered versions of the documentation. (I
think we are missing the PDF files.) They are generated from Git commits to
branches in the main GitHub repository. If you have a branch you want to test,
let us know and we can push it over.
> 
> -- 
> Charles Lepple
> clepple at gmail
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141123/6b5ef6e6/attachment.html>

Sorry I ran ?make' command in nut-website/nut... (I still can?t understand
why creating man page is so long, it is much more faster on ubuntu.)
When running ?make? in nut-website, same issue then described previously, even
with Arno patch
> sort: stray character in field spec: invalid field specification `4.1,4.5rV
> 
> >>>>>> and it ends with:
> 
> /opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
--attribute icons --attribute linkcss --attribute=badges --attribute=website
--attribute=quirks --attribute=revision=2.7.2 --attribute tree_version=2.7
--attribute localdate=`TZ=UTC date +%Y-%m-%d` --attribute localtime=`TZ=UTC date
+%H:%M:%S` --attribute=date="`TZ=UTC date`" --attribute
iconsdir=./images --attribute scriptsdir=./scripts -o projects.html -a toc
projects.txt
> make: *** No rule to make target `-eindex.html', needed by
`ups-html.txt'.  Stop.

regards, jean
> Le 23 nov. 2014 ? 21:19, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com> a ?crit :
> 
> After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,
> 
> Configuration summary:
> =====================> build serial drivers: yes 
> build USB drivers: yes 
> build SNMP drivers: yes 
> build neon based XML driver: yes 
> enable Avahi support: no 
> build Powerman PDU client driver: no
> build IPMI driver: no
> build Mac OS X meta-driver: yes
> build i2c based drivers: no
> enable SSL support: yes (OpenSSL)
> enable libwrap (tcp-wrappers) support: no
> enable libltdl (Libtool dlopen abstraction) support: no
> build nut-scanner: no
> build CGI programs: no
> build and install documentation: no
> build and install the development files: no
> 
> >>>>>> Then make command looks ok, until:
> 
> Making all in docs
> Making all in man
> /opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. nut.conf.txt
> a2x: WARNING: --destination-dir option is only applicable to HTML based
outputs
> 
> >>>>>> At this stage, the process is kind of hanging, it
takes 1 hour to generate the man pages.
> 
> >>>>>> then make command ends correctly without issues.
> 
> 
> 
> 
> 
> Regarding 'nut-website?, after fresh clone on Yosemite:
> 
> >>>>>> ./autogen.sh automatically clone nut and nut-dll
in nut-website.
> >>>>>> can I use my own clones here?
> 
> Configuration summary:
> =====================> build serial drivers: yes
> build USB drivers: yes
> build SNMP drivers: yes
> build neon based XML driver: yes
> enable Avahi support: no
> build Powerman PDU client driver: no
> build IPMI driver: no
> build Mac OS X meta-driver: yes
> build i2c based drivers: no
> enable SSL support: yes (OpenSSL)
> enable libwrap (tcp-wrappers) support: no
> enable libltdl (Libtool dlopen abstraction) support: no
> build nut-scanner: no
> build CGI programs: no
> build and install documentation: no
> build and install the development files: no
> 
> >>>>>> then make command. I have this one dozen of times:
> 
> sort: stray character in field spec: invalid field specification `4.1,4.5rV
> 
> >>>>>> and it ends with:
> 
> /opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
--attribute icons --attribute linkcss --attribute=badges --attribute=website
--attribute=quirks --attribute=revision=2.7.2 --attribute tree_version=2.7
--attribute localdate=`TZ=UTC date +%Y-%m-%d` --attribute localtime=`TZ=UTC date
+%H:%M:%S` --attribute=date="`TZ=UTC date`" --attribute
iconsdir=./images --attribute scriptsdir=./scripts -o projects.html -a toc
projects.txt
> make: *** No rule to make target `-eindex.html', needed by
`ups-html.txt'.  Stop.
> 
> 
> >>>>>> I apply aquette patch in
'nut-website/nut/configure.ac?, then apply 'make' command
> >>>>>> no more 'sort: stray character in field spec:
invalid field specification `4.1,4.5rV? error... is it because I need to clean
something?
> >>>>>> then it is taking long..minutes (near an hour
right now) generating man page:
> 
> /opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. ivtscd.txt
> a2x: WARNING: --destination-dir option is only applicable to HTML based
outputs
> 
> 
> regards,
> jean
> 
> 
> 
>> Le 20 nov. 2014 ? 15:10, Charles Lepple <clepple at gmail.com
<mailto:clepple at gmail.com>> a ?crit :
>> 
>> On Nov 20, 2014, at 7:11 AM, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com <mailto:jpweb.taf at gmail.com>> wrote:
>> 
>>> Hello,
>>> Here is a summary of discussions around NUT builds on Mac OS X
10.10.
>>> 
>>> Starting from
https://github.com/networkupstools/nut-website/issues/7
<https://github.com/networkupstools/nut-website/issues/7>
>>> 
>>> @JeanPerriault
>>> I've found msort on macports
(https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile
<https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile>,
http://billposer.org/Software/Downloads/
<http://billposer.org/Software/Downloads/>
>>> msort.pdf), but I'm not sure where to implement it, should I
replace all sort ocurrences I find in code?
>>> 
>>> @clepple
>>> I think checking for gsort in the configure script would be better
(since that is what is used when 'sort' is invoked on Linux), and then
sort would get replaced with @GSORT@ or whatever. However, when I mentioned via
email that the website doesn't build on OS X, I wasn't thinking that it
needed to be solved soon - we can build the website and documentation on Linux
systems for now.
>>> 
>>> @aquette
>>> considering the context and limited impact, we could simply check
for gsort first, and then sort.
>>> --- a/configure.ac
>>> +++ b/configure.ac
>>> @@ -101,6 +101,7 @@ AC_PROG_CXX
>>> AC_PROG_INSTALL
>>> AC_PROG_EGREP
>>> AC_PATH_PROG(AR, ar)
>>> +AC_CHECK_PROGS(SORT, gsort sort)
>>> AC_CHECK_TOOL(RANLIB, ranlib, :)
>>> dnl Postpone call to AC_PROG_LIBTOOL to allow disabling static lib
>>> AC_C_BIGENDIAN
>> 
>> Just to clarify, the sort error is only when building nut-website:
>> 
>> 	sort: stray character in field spec: invalid field specification
`4.1,4.5rV'
>> 
>> Also, you had mentioned dependencies for building documentation. This
affects NUT non-website builds as well, but the list looks something like this:
>> 
>> 	? asciidoc
>> 	? asciidoc-a2x (if packaged separately)
>> 	? docbook-xsl (symptom for Debian bug #635347; xsltproc will otherwise
try to download DocBook files from the net)
>> 	? dblatex
>> 
>> We are trying to reduce the dependencies needed to build the .tar.gz
snapshots, so you might want to try one of them:
>> 
>> http://buildbot.networkupstools.org/snapshots
<http://buildbot.networkupstools.org/snapshots>
>> 
>> The snapshots include some HTML rendered versions of the documentation.
(I think we are missing the PDF files.) They are generated from Git commits to
branches in the main GitHub repository. If you have a branch you want to test,
let us know and we can push it over.
>> 
>> -- 
>> Charles Lepple
>> clepple at gmail
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141123/5bd7bbc4/attachment-0001.html>

> which sort
/usr/bin/sort
> sort --version
sort (GNU coreutils) 5.93
> Le 23 nov. 2014 ? 21:59, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com> a ?crit :
> 
> Sorry I ran ?make' command in nut-website/nut... (I still can?t
understand why creating man page is so long, it is much more faster on ubuntu.)
> When running ?make? in nut-website, same issue then described previously,
even with Arno patch
> 
>> sort: stray character in field spec: invalid field specification
`4.1,4.5rV
>> 
>> >>>>>> and it ends with:
>> 
>> /opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
--attribute icons --attribute linkcss --attribute=badges --attribute=website
--attribute=quirks --attribute=revision=2.7.2 --attribute tree_version=2.7
--attribute localdate=`TZ=UTC date +%Y-%m-%d` --attribute localtime=`TZ=UTC date
+%H:%M:%S` --attribute=date="`TZ=UTC date`" --attribute
iconsdir=./images --attribute scriptsdir=./scripts -o projects.html -a toc
projects.txt
>> make: *** No rule to make target `-eindex.html', needed by
`ups-html.txt'.  Stop.
> 
> 
> regards, jean
> 
>> Le 23 nov. 2014 ? 21:19, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com <mailto:jpweb.taf at gmail.com>> a ?crit :
>> 
>> After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,
>> 
>> Configuration summary:
>> =====================>> build serial drivers: yes 
>> build USB drivers: yes 
>> build SNMP drivers: yes 
>> build neon based XML driver: yes 
>> enable Avahi support: no 
>> build Powerman PDU client driver: no
>> build IPMI driver: no
>> build Mac OS X meta-driver: yes
>> build i2c based drivers: no
>> enable SSL support: yes (OpenSSL)
>> enable libwrap (tcp-wrappers) support: no
>> enable libltdl (Libtool dlopen abstraction) support: no
>> build nut-scanner: no
>> build CGI programs: no
>> build and install documentation: no
>> build and install the development files: no
>> 
>> >>>>>> Then make command looks ok, until:
>> 
>> Making all in docs
>> Making all in man
>> /opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. nut.conf.txt
>> a2x: WARNING: --destination-dir option is only applicable to HTML based
outputs
>> 
>> >>>>>> At this stage, the process is kind of hanging,
it takes 1 hour to generate the man pages.
>> 
>> >>>>>> then make command ends correctly without
issues.
>> 
>> 
>> 
>> 
>> 
>> Regarding 'nut-website?, after fresh clone on Yosemite:
>> 
>> >>>>>> ./autogen.sh automatically clone nut and
nut-dll in nut-website.
>> >>>>>> can I use my own clones here?
>> 
>> Configuration summary:
>> =====================>> build serial drivers: yes
>> build USB drivers: yes
>> build SNMP drivers: yes
>> build neon based XML driver: yes
>> enable Avahi support: no
>> build Powerman PDU client driver: no
>> build IPMI driver: no
>> build Mac OS X meta-driver: yes
>> build i2c based drivers: no
>> enable SSL support: yes (OpenSSL)
>> enable libwrap (tcp-wrappers) support: no
>> enable libltdl (Libtool dlopen abstraction) support: no
>> build nut-scanner: no
>> build CGI programs: no
>> build and install documentation: no
>> build and install the development files: no
>> 
>> >>>>>> then make command. I have this one dozen of
times:
>> 
>> sort: stray character in field spec: invalid field specification
`4.1,4.5rV
>> 
>> >>>>>> and it ends with:
>> 
>> /opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
--attribute icons --attribute linkcss --attribute=badges --attribute=website
--attribute=quirks --attribute=revision=2.7.2 --attribute tree_version=2.7
--attribute localdate=`TZ=UTC date +%Y-%m-%d` --attribute localtime=`TZ=UTC date
+%H:%M:%S` --attribute=date="`TZ=UTC date`" --attribute
iconsdir=./images --attribute scriptsdir=./scripts -o projects.html -a toc
projects.txt
>> make: *** No rule to make target `-eindex.html', needed by
`ups-html.txt'.  Stop.
>> 
>> 
>> >>>>>> I apply aquette patch in
'nut-website/nut/configure.ac?, then apply 'make' command
>> >>>>>> no more 'sort: stray character in field
spec: invalid field specification `4.1,4.5rV? error... is it because I need to
clean something?
>> >>>>>> then it is taking long..minutes (near an hour
right now) generating man page:
>> 
>> /opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. ivtscd.txt
>> a2x: WARNING: --destination-dir option is only applicable to HTML based
outputs
>> 
>> 
>> regards,
>> jean
>> 
>> 
>> 
>>> Le 20 nov. 2014 ? 15:10, Charles Lepple <clepple at gmail.com
<mailto:clepple at gmail.com>> a ?crit :
>>> 
>>> On Nov 20, 2014, at 7:11 AM, Jean Perriault (GM TAF) <jpweb.taf
at gmail.com <mailto:jpweb.taf at gmail.com>> wrote:
>>> 
>>>> Hello,
>>>> Here is a summary of discussions around NUT builds on Mac OS X
10.10.
>>>> 
>>>> Starting from
https://github.com/networkupstools/nut-website/issues/7
<https://github.com/networkupstools/nut-website/issues/7>
>>>> 
>>>> @JeanPerriault
>>>> I've found msort on macports
(https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile
<https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile>,
http://billposer.org/Software/Downloads/
<http://billposer.org/Software/Downloads/>
>>>> msort.pdf), but I'm not sure where to implement it, should
I replace all sort ocurrences I find in code?
>>>> 
>>>> @clepple
>>>> I think checking for gsort in the configure script would be
better (since that is what is used when 'sort' is invoked on Linux), and
then sort would get replaced with @GSORT@ or whatever. However, when I mentioned
via email that the website doesn't build on OS X, I wasn't thinking that
it needed to be solved soon - we can build the website and documentation on
Linux systems for now.
>>>> 
>>>> @aquette
>>>> considering the context and limited impact, we could simply
check for gsort first, and then sort.
>>>> --- a/configure.ac
>>>> +++ b/configure.ac
>>>> @@ -101,6 +101,7 @@ AC_PROG_CXX
>>>> AC_PROG_INSTALL
>>>> AC_PROG_EGREP
>>>> AC_PATH_PROG(AR, ar)
>>>> +AC_CHECK_PROGS(SORT, gsort sort)
>>>> AC_CHECK_TOOL(RANLIB, ranlib, :)
>>>> dnl Postpone call to AC_PROG_LIBTOOL to allow disabling static
lib
>>>> AC_C_BIGENDIAN
>>> 
>>> Just to clarify, the sort error is only when building nut-website:
>>> 
>>> 	sort: stray character in field spec: invalid field specification
`4.1,4.5rV'
>>> 
>>> Also, you had mentioned dependencies for building documentation.
This affects NUT non-website builds as well, but the list looks something like
this:
>>> 
>>> 	? asciidoc
>>> 	? asciidoc-a2x (if packaged separately)
>>> 	? docbook-xsl (symptom for Debian bug #635347; xsltproc will
otherwise try to download DocBook files from the net)
>>> 	? dblatex
>>> 
>>> We are trying to reduce the dependencies needed to build the
.tar.gz snapshots, so you might want to try one of them:
>>> 
>>> http://buildbot.networkupstools.org/snapshots
<http://buildbot.networkupstools.org/snapshots>
>>> 
>>> The snapshots include some HTML rendered versions of the
documentation. (I think we are missing the PDF files.) They are generated from
Git commits to branches in the main GitHub repository. If you have a branch you
want to test, let us know and we can push it over.
>>> 
>>> -- 
>>> Charles Lepple
>>> clepple at gmail
>> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141123/ce2d4aad/attachment-0001.html>

On Nov 23, 2014, at 3:19 PM, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com> wrote:
> After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,
The version number is simply a placeholder, indicating that the Git tree has
changes beyond v2.7.2, and is not yet released as v2.7.3. After we start making
changes, you may want to use "git describe --tags" or the Git commit
ID.

[...]
> >>>>>> Then make command looks ok, until:
> 
> Making all in docs
> Making all in man
> /opt/local/bin/a2x --doctype manpage --format manpage --attribute
mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute manmanual="NUT Manual"
--destination-dir=. nut.conf.txt
> a2x: WARNING: --destination-dir option is only applicable to HTML based
outputs
> 
> >>>>>> At this stage, the process is kind of hanging, it
takes 1 hour to generate the man pages.
If you have internet access while building, your a2x/Docbook toolchain might
still be trying to download additional components (and it is probably not
caching them between runs). The OS X Buildbot slave sets
"ASCIIDOC_VERBOSE=-v" in the environment to print out the exact
commands being invoked (although this only seems to work for the HTML
documentation, rather than the man pages).

Also, a2x accepts an XSLTPROC_OPTS environment variable that you can set to
"--nonet". I suppose we could add that to the makefiles.
> Regarding 'nut-website?, after fresh clone on Yosemite:
> 
> >>>>>> ./autogen.sh automatically clone nut and nut-dll
in nut-website.
> >>>>>> can I use my own clones here?
Should be possible. Again, I appreciate the effort here, but for a basic OS X
build of NUT, we don't need to build nut-website (yet).
> >>>>>> then make command. I have this one dozen of times:
> 
> sort: stray character in field spec: invalid field specification `4.1,4.5rV
> 
> >>>>>> and it ends with:
> 
> /opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
--attribute icons --attribute linkcss --attribute=badges --attribute=website
--attribute=quirks --attribute=revision=2.7.2 --attribute tree_version=2.7
--attribute localdate=`TZ=UTC date +%Y-%m-%d` --attribute localtime=`TZ=UTC date
+%H:%M:%S` --attribute=date="`TZ=UTC date`" --attribute
iconsdir=./images --attribute scriptsdir=./scripts -o projects.html -a toc
projects.txt
> make: *** No rule to make target `-eindex.html', needed by
`ups-html.txt'.  Stop.
I see that on OS X as well.

Jean, I CC'd Dan, who wrote the build rules for nut-website. Dan, what I
would like to do is split some of the sort pipelines up into intermediate files
so we can debug this better - I tried using gsort on my local copy, and it did
not work the same as the last time I tried it.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141124/b1708105/attachment.html>

Hi Dan

Charles and Jean are having an issue with the nut-website buildrules.
would you have a bit of time to check to help them?

thx and cheers,
Arno

2014-11-24 14:59 GMT+01:00 Charles Lepple <clepple at gmail.com>:
> On Nov 23, 2014, at 3:19 PM, Jean Perriault (GM TAF) <jpweb.taf at
gmail.com>
> wrote:
>
> After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,
>
>
> The version number is simply a placeholder, indicating that the Git tree
> has changes beyond v2.7.2, and is not yet released as v2.7.3. After we
> start making changes, you may want to use "git describe --tags"
or the Git
> commit ID.
>
> [...]
>
> >>>>>> Then make command looks ok, until:
>
> Making all in docs
> Making all in man
> /opt/local/bin/a2x --doctype manpage --format manpage --attribute
> mansource="Network UPS Tools" --attribute
manversion="2.7.2.5" --attribute
> manmanual="NUT Manual" --destination-dir=. nut.conf.txt
> a2x: WARNING: --destination-dir option is only applicable to HTML based
> outputs
>
> >>>>>> At this stage, the process is kind of hanging, it
takes 1 hour to
> generate the man pages.
>
>
> If you have internet access while building, your a2x/Docbook toolchain
> might still be trying to download additional components (and it is probably
> not caching them between runs). The OS X Buildbot slave sets
> "ASCIIDOC_VERBOSE=-v" in the environment to print out the exact
commands
> being invoked (although this only seems to work for the HTML documentation,
> rather than the man pages).
>
> Also, a2x accepts an XSLTPROC_OPTS environment variable that you can set
> to "--nonet". I suppose we could add that to the makefiles.
>
> Regarding 'nut-website?, after fresh clone on Yosemite:
>
> >>>>>> ./autogen.sh automatically clone nut and nut-dll
in nut-website.
> >>>>>> can I use my own clones here?
>
>
> Should be possible. Again, I appreciate the effort here, but for a basic
> OS X build of NUT, we don't need to build nut-website (yet).
>
> >>>>>> then make command. I have this one dozen of times:
>
> sort: stray character in field spec: invalid field specification `4.1,4.5rV
>
> >>>>>> and it ends with:
>
> /opt/local/bin/asciidoc --backend=xhtml11 --conf-file=./web-layout.conf
> --attribute icons --attribute linkcss --attribute=badges
> --attribute=website --attribute=quirks --attribute=revision=2.7.2
> --attribute tree_version=2.7 --attribute localdate=`TZ=UTC date +%Y-%m-%d`
> --attribute localtime=`TZ=UTC date +%H:%M:%S`
--attribute=date="`TZ=UTC
> date`" --attribute iconsdir=./images --attribute scriptsdir=./scripts
-o
> projects.html -a toc projects.txt
> make: *** No rule to make target `-eindex.html', needed by
> `ups-html.txt'.  Stop.
>
>
> I see that on OS X as well.
>
> Jean, I CC'd Dan, who wrote the build rules for nut-website. Dan, what
I
> would like to do is split some of the sort pipelines up into intermediate
> files so we can debug this better - I tried using gsort on my local copy,
> and it did not work the same as the last time I tried it.
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
>


-- 
Eaton Data Center Automation - Opensource Leader
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141201/307cd91f/attachment.html>

On Dec 3, 2014, at 7:05 PM, simon-alioth at eazimail.com wrote:
> One other issue I noticed is with the placement of the GD libraries, if
they
> are not installed under the root it will not find them
> 
> If I build GD into /build/usr and add the following lines to my make script
> for nut:
> 
> 	PREFIX=/build/usr
> 
> 	configure \
> 		--with-gd-includes="-I${sPREFIX}/include/libgd" \
> 		--with-gd-libs="-L${sPREFIX}/lib64" \
> 		......
> 
> Configure will abort with a GD libary not found. If I set PREFIX=/build and
> rebuild GD and NUT then configure will identify the GD libs. Not sure where
> the problem is exactly.
> 
> (this is with the latest public code release from the git repository).
Can you elaborate on how you are using PREFIX versus sPREFIX?

-- 
Charles Lepple
clepple at gmail

Hi Charles,

Typo on my part (copy pasting diff scripts). 

I tried building libGD in the following directory (sPREFIX is an env name I
use in scripts):
 	sPREFIX=${PWD}/../build/usr

This works, all files in the correct directory.

Next I try building NUT with the following params:

 	sPREFIX=${PWD}/../build/usr
 	configure \
 		--with-gd-includes="-I${sPREFIX}/include/libgd" \
 		--with-gd-libs="-L${sPREFIX}/lib64" \
 		......

This fails to locate LibGD and aborts.

If I build libGD using "sPREFIX=${PWD}/../build" and include this in
the NUT
build 

 		--with-gd-includes="-I${sPREFIX}/include/libgd" \
 		--with-gd-libs="-L${sPREFIX}/lib64" \
 		......

This works. It did this consistently across several openSUSE platforms.

This is a minor annoyance as normally all of the working libs are in
/usr/lib|lib64, not /lib. 


Thanks,

Simon

-----Original Message-----
From: Charles Lepple [mailto:clepple at gmail.com] 
Sent: Thursday, December 04, 2014 01:47
To: simon-alioth at eazimail.com
Cc: nut-upsdev
Subject: [Nut-upsdev] GD libraries and $PREFIX (was Re: building NUT on Mac
OS X Yosemite(website/documentation))

On Dec 3, 2014, at 7:05 PM, simon-alioth at eazimail.com wrote:
> One other issue I noticed is with the placement of the GD libraries, 
> if they are not installed under the root it will not find them
> 
> If I build GD into /build/usr and add the following lines to my make 
> script for nut:
> 
> 	PREFIX=/build/usr
> 
> 	configure \
> 		--with-gd-includes="-I${sPREFIX}/include/libgd" \
> 		--with-gd-libs="-L${sPREFIX}/lib64" \
> 		......
> 
> Configure will abort with a GD libary not found. If I set 
> PREFIX=/build and rebuild GD and NUT then configure will identify the 
> GD libs. Not sure where the problem is exactly.
> 
> (this is with the latest public code release from the git repository).
Can you elaborate on how you are using PREFIX versus sPREFIX?

--
Charles Lepple
clepple at gmail