On 04/21/2018 05:53 PM, Ken Moffat wrote:
I fixed my scm script (for once, it was easy), so I've been trying
to build what will be texlive-2018.
Not unexpectedly, poppler-0.64 breaks it:
g++ -DHAVE_CONFIG_H -I. -I../../../texk/web2c -I./w2c
-I/scratch/working/texlive-2018-r47463-source/texlive-build/texk
-I/scratch/working/texlive-2018-r47463-source/texk -I/usr/include/libpng16
-DPOPPLER_VERSION=\"0.64.0\" -I/usr/include/poppler
-I../../../texk/web2c/libmd5 -I../../../texk/web2c/pdftexdir -Wreturn-type
-Wno-write-strings -O2 -march=native -MT pdftexdir/pdftosrc-pdftosrc.o -MD -MP -MF
pdftexdir/.deps/pdftosrc-pdftosrc.Tpo -c -o pdftexdir/pdftosrc-pdftosrc.o `test -f
'pdftexdir/pdftosrc.cc' || echo '../../../texk/web2c/'`pdftexdir/pdftosrc.cc
../../../texk/web2c/pdftexdir/pdftosrc.cc: In function 'int main(int, char**)':
../../../texk/web2c/pdftexdir/pdftosrc.cc:112:50: error: invalid conversion
from 'const char*' to 'char*' [-fpermissive]
The actual error is, to me, somewhat surprising (I had assumed a
const char* could be converted to a char* even if the converse was
illegal).
If you are passing a pointer, you can't pass a const char* to a function
that expects a char* because the compiler does not know if the function
will modify the value. That would negate the const designation.
You should be able to pass a char* to a function that expects a const
char* because the function is saying it will not modify the contents of
the pointer.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
