Thread: [Refdb-users] Re: Any hint of 0.9.7 final ?
Status: Beta
Brought to you by:
mhoenicka
From: Markus H. <mar...@mh...> - 2006-05-06 23:25:47
|
[I've cc'ed the list as other users may face the same problems or even know solutions. Please keep this discussion on the list] Hi, St=E9phane T=E9letch=E9a writes: > + libtoolize --copy --force > Remember to add `AC=5FPROG=5FLIBTOOL' to `configure.in'. > You should update your `aclocal.m4' by running aclocal. Is that something that the RPM build system forces you to do=3F RefDB does not use libtool. RefDB's own autogen.sh script does not call libtoolize. If you must do this anyway, it is safe to ignore the error message. > checking for dtdparse... no > checking for dtdformat... no > checking for sgrep... no > checking for tidy... /usr/bin/tidy > checking for batik-rasterizer... no These missing programs contribute to the build failure. More below. > checking for shared library run path origin... /bin/sh: ./conf/confi= g.rpath: No such file or directory > done I see this warning on several problems without adverse effect. It seems to be safe to ignore this. > checking for http://www.tei-c.org/Stylesheets/p4/fo/tei.xsl... no > checking for XML file http://www.tei-c.org/Stylesheets/p4/fo/tei.xsl= ... checking for No entry for SYSTEM http://www.tei-c.org/Stylesheets/p= 4/fo/tei.xsl No entry for URI http://www.tei-c.org/Stylesheets/p4/fo/te= i.xsl... no > XML file not found This is strange if you know that the file is installed. Most likely the TEI stylesheets are not correctly listed in the XML catalog, or there is only an entry in one of the SGML catalogs. If this is true, you should file a bug report for the TEI stylesheet package. As a short-term fix, you could try to pass the location of the stylesheets to the configure file by means of the --with-tei-xsl option. > refdbda.c: In function 'daemon=5Fstarted=5Fby=5Finetd': > refdbda.c:2494: warning: pointer targets in passing argument 5 of 'g= etsockopt' differ in signedness I think I've fixed this by adding a proper test to configure.in > refdbdbib.c: In function 'getbib': > refdbdbib.c:905: warning: passing argument 2 of 'iconv' from incompa= tible pointer type > refdbdbib.c:1004: warning: passing argument 2 of 'iconv' from incomp= atible pointer type There seems to be no portable solution to this problem. Some systems use char**, others use const char**, and no matter what you use in your code, it'll generate a warning in half of the systems. > refdbc.c: In function 'addref': > refdbc.c:2890: warning: call to =5F=5Fbuiltin=5F=5F=5Fstrncpy=5Fchk = will always overflow destination buffer > refdbc.c: In function 'com=5Fgetref': > refdbc.c:1820: warning: call to =5F=5Fbuiltin=5F=5F=5Fstrncpy=5Fchk = will always overflow destination buffer > refdbc.c: In function 'addnote': > refdbc.c:3587: warning: call to =5F=5Fbuiltin=5F=5F=5Fstrncpy=5Fchk = will always overflow destination buffer > refdbc.c: In function 'com=5Fgetnote': > refdbc.c:4538: warning: call to =5F=5Fbuiltin=5F=5F=5Fstrncpy=5Fchk = will always overflow destination buffer > refdbc.c: In function 'addlink': > refdbc.c:5076: warning: call to =5F=5Fbuiltin=5F=5F=5Fstrncpy=5Fchk = will always overflow destination buffer > refdbc.c: In function 'com=5Fupdatejo': > refdbc.c:5399: warning: call to =5F=5Fbuiltin=5F=5F=5Fstrncpy=5Fchk = will always overflow destination buffer I've fixed the incorrect string sizes. > nmed2ris.c: In function 'main': > nmed2ris.c:182: warning: incompatible implicit declaration of built-= in function 'exit' nmed2ris has essentially been replaced by the med2ris Perl script years ago. I've removed it instead of attempting to fix it. > bib2ris.c: In function 'log=5Fprint': > bib2ris.c:1887: warning: incompatible implicit declaration of built-= in function 'strftime' > bib2ris.c:1887: warning: passing argument 4 of 'strftime' makes poin= ter from integer without a cast I can't figure out what's wrong with this one. All you need to declare strftime properly is to include <time.h> which I did. It doesn't help here. Other files use the same strftime call, include <time.h>, and do not generate this warning (e.g. refdbdref.c). I'm stymied. > ../scripts/statgen.pl docbook > refdb-manual-statustable.xml > make[1]: *** No rule to make target `include/doc-html.dsl', needed b= y `refdb-manual/ch01.html'. Stop. I've changed the doc build system from SGML to XML after 0.9.6, so I'm not surprised to see a few glitches. This one seems to be caused by an incorrect dependency (dsl files are used no more). I've fixed this. In any case, make should not attempt to build the docs as they are shipped pre-built in the tar.gz archives. You should only need to rebuild them after running maintainer-clean. If you do that, or if the RPM build process mandates that, you'll need the additional tools that I mentioned above when looking at your configure output. I've uploaded a new prerelease (0.9.7-pre6) based on these changes. Please give it a try and let me know. http://refdb.sourceforge.net/pre/refdb-latest.tar.gz regards Markus --=20 Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
From: Markus H. <mar...@mh...> - 2006-05-06 23:35:32
|
me typing too fast... Markus Hoenicka writes: > These missing programs contribute to the build failure. More below. These missing programs may contribute to a build failure. More below. > > I see this warning on several problems without adverse effect. It > seems to be safe to ignore this. > I see this warning on several operating systems without adverse effect. regards, Markus -- Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
From: <ste...@jo...> - 2006-05-09 08:06:51
|
Markus Hoenicka a =E9crit : > [I've cc'ed the list as other users may face the same problems or even > know solutions. Please keep this discussion on the list] >=20 > I've uploaded a new prerelease (0.9.7-pre6) based on these > changes. Please give it a try and let me know. >=20 > http://refdb.sourceforge.net/pre/refdb-latest.tar.gz I've used this one to get a building rpm (by disabling the doc=20 generation which seems to still fail, some more dependancies are needed=20 for them). I'm now working on enabling the various databases connectors (mysql,=20 pgsql, ...) and last i'll check everything works by importing/exporting=20 some stuff (in the end, this is what i need ;-). I'll try to give as much input as possible on the list. I think it is=20 better to discuss this on the refdb-devel list (to which i've subscribed=20 to). I don't know if it is better to get both lists involved or keep the=20 track on ly on the devel, i'll see from your answers (on the devel list). St=E9phane --=20 St=E9phane T=E9letch=E9a, PhD. http://www.steletch.org Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.inra.f= r/mig INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |
From: Markus H. <mar...@mh...> - 2006-05-09 11:25:47
|
St=E9phane T=E9letch=E9a <ste...@jo...> was heard to say: > I've used this one to get a building rpm (by disabling the doc=3D20 > generation which seems to still fail, some more dependancies are needed= =3D20 > for them). This is still a mystery to me. Everything that might ever be built in the= doc subdir is shipped with the archive. Therefore a simple "make" should not attempt to rebuild the doc subdir. Is this caused by your RPM build frame= work, or does this happen always on your box? > I don't know if it is better to get both lists involved or keep the=3D2= 0 > track on ly on the devel, i'll see from your answers (on the devel list= ). > As a rule of thumb, if other users might help to fix a problem, or if you= find a problem which might be important to them, please send it to refdb-users. = If it's just about packaging issues, dependencies, build failures and such, the refdb-devel list seems more appropriate. regards, Markus --=20 Markus Hoenicka mar...@ca... (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de |
From: <ste...@jo...> - 2006-05-09 11:54:54
|
Markus Hoenicka a =E9crit : > St=E9phane T=E9letch=E9a <ste...@jo...> was heard to say: >=20 >=20 >>I've used this one to get a building rpm (by disabling the doc=3D20 >>generation which seems to still fail, some more dependancies are needed= =3D20 >>for them). >=20 >=20 > This is still a mystery to me. Everything that might ever be built in t= he doc > subdir is shipped with the archive. Therefore a simple "make" should no= t > attempt to rebuild the doc subdir. Is this caused by your RPM build fra= mework, > or does this happen always on your box? Oh, sorry, i should have responded on this specifically. I presume it is=20 coming from the rpm environnment where i build. I'm not completely=20 familiar with it for the moment. One goal for instance for this quite exhaustive building process is to=20 provide documentation, info pages, man pages, and other stuff that i=20 don't for now understand extensively. >=20 >>I don't know if it is better to get both lists involved or keep the=3D2= 0 >>track on ly on the devel, i'll see from your answers (on the devel list= ). >> >=20 >=20 > As a rule of thumb, if other users might help to fix a problem, or if y= ou find a > problem which might be important to them, please send it to refdb-users= . If it's > just about packaging issues, dependencies, build failures and such, the > refdb-devel list seems more appropriate. Nice, i'll continue then on appropriate list when i'll be more advanced. > regards, > Markus Best wishes, St=E9phane --=20 St=E9phane T=E9letch=E9a, PhD. http://www.steletch.org Unit=E9 Math=E9matique Informatique et G=E9nome http://migale.jouy.inra.f= r/mig INRA, Domaine de Vilvert T=E9l : (33) 134 652 891 78352 Jouy-en-Josas cedex, France Fax : (33) 134 652 901 |