Hi,
I ran the make file and got  an error message :

make[2]: Entering directory '/home/esim/Desktop/tmp/sdcc-4.0.0/*src/pdk*'
mawk -f ./../SDCCpeeph.awk peeph.def > peeph.rul
g++ -std=gnu++11 -MM -I./.. -I.. -I. -I../.. -I./../../support/util -I.
gen.c main.c peep.c ralloc.c ralloc2.cc >Makefile.dep
gcc -pipe -ggdb -g -O2 -Wall -Wno-parentheses -I./.. -I.. -I. -I../..
-I./../../support/util -I.  -c -o gen.o gen.c
gcc -pipe -ggdb -g -O2 -Wall -Wno-parentheses -I./.. -I.. -I. -I../..
-I./../../support/util -I.  -c -o main.o main.c
gcc -pipe -ggdb -g -O2 -Wall -Wno-parentheses -I./.. -I.. -I. -I../..
-I./../../support/util -I.  -c -o peep.o peep.c
gcc -pipe -ggdb -g -O2 -Wall -Wno-parentheses -I./.. -I.. -I. -I../..
-I./../../support/util -I.  -c -o ralloc.o ralloc.c
g++ -std=gnu++11 -pipe -ggdb -g -O2 -I./.. -I.. -I. -I../..
-I./../../support/util -I.  -c -o ralloc2.o ralloc2.cc
rm -f port.a
ar rc port.a gen.o main.o peep.o ralloc.o ralloc2.o
ranlib port.a
make[2]: Leaving directory '/home/esim/Desktop/tmp/sdcc-4.0.0/src/pdk'
g++ -std=gnu++11  -o ../bin/sdcc NewAlloc.o dbuf.o dbuf_string.o findme.o
SDCCy.o SDCChasht.o SDCCmain.o SDCCsymt.o SDCCopt.o SDCCast.o SDCCmem.o
SDCCval.o SDCCicode.o SDCCbitv.o SDCCset.o SDCClabel.o SDCCBBlock.o
SDCCloop.o SDCCcse.o SDCCcflow.o SDCCdflow.o SDCClrange.o SDCCptropt.o
SDCCpeeph.o SDCCglue.o SDCCasm.o SDCCmacro.o SDCCutil.o SDCCdebug.o
cdbFile.o SDCCdwarf2.o SDCCerr.o SDCCsystem.o SDCCgen.o SDCClex.o
SDCCbtree.o SDCClospre.o SDCCnaddr.o mcs51/port.a z80/port.a ds390/port.a
hc08/port.a stm8/port.a pdk/port.a  -lm
SDCClospre.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:114: recipe for target '../bin/sdcc' failed
make[1]: *** [../bin/sdcc] Error 1
make[1]: Leaving directory '/home/esim/Desktop/tmp/sdcc-4.0.0/src'
Makefile:144: recipe for target 'sdcc-cc' failed
make: *** [sdcc-cc] Error 2

The lines before this were related to STM8 packages, there was no error in
it.
Is there a way I can skip the rest of the process(if it is unnecessary) and
go for *make install as I am only interested in stm8 at the moment*?


On Sun, May 17, 2020 at 6:26 PM Sergey Belyashov <sergey.belyas...@gmail.com>
wrote:

> Hi,
> Do $ apt-cache search texinfo
> Select proper package and do $ apt-get install <package>
>
> вс, 17 мая 2020 г., 15:46 Saurabh Bansode <saurabhbans...@gmail.com>:
>
>> Hello,
>> I am using Ubuntu 16.04, Installed boost via apt-get install
>> libboost-system-dev, and then ran   ./configure --disable-pic14-port
>> --disable-pic16-port as I was faced some issues with pic. The
>> ./configure command runs successfully now.
>>
>> Then after running *make *command, I am getting the following error:
>>
>> /home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/missing: 81:
>> /home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/missing: makeinfo: not
>> found
>> WARNING: 'makeinfo' is missing on your system.
>>          You should only need it if you modified a '.texi' file, or
>>          any other file indirectly affecting the aspect of the manual.
>>          You might want to install the Texinfo package:
>>          <http://www.gnu.org/software/texinfo/>
>>          The spurious makeinfo call might also be the consequence of
>>          using a buggy 'make' (AIX, DU, IRIX), in which case you might
>>          want to install GNU make:
>>          <http://www.gnu.org/software/make/>
>> Makefile:472: recipe for target 'bfd.info' failed
>> make[4]: *** [bfd.info] Error 127
>> make[4]: Leaving directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/bfd/doc'
>> Making info in po
>> make[4]: Entering directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/bfd/po'
>> make[4]: Nothing to be done for 'info'.
>> make[4]: Leaving directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/bfd/po'
>> make[4]: Entering directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/bfd'
>> make[4]: Nothing to be done for 'info-am'.
>> make[4]: Leaving directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/bfd'
>> Makefile:1748: recipe for target 'info-recursive' failed
>> make[3]: *** [info-recursive] Error 1
>> make[3]: Leaving directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils/bfd'
>> Makefile:2692: recipe for target 'all-bfd' failed
>> make[2]: *** [all-bfd] Error 2
>> make[2]: Leaving directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils'
>> Makefile:849: recipe for target 'all' failed
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory
>> '/home/esim/Desktop/tmp/sdcc-4.0.0/support/sdbinutils'
>> Makefile:162: recipe for target 'sdcc-sdbinutils' failed
>> make: *** [sdcc-sdbinutils] Error 2
>>
>>
>>
>>
>> On Sun, May 17, 2020 at 6:04 PM Philipp Klaus Krause <p...@spth.de> wrote:
>>
>>> Am 17.05.20 um 13:50 schrieb Saurabh Bansode:
>>> > Hello,
>>> > After running ./configure as the manual suggests, I faced the following
>>> > error:
>>> >
>>> > /Configure: error: boost library not found
>>> (boost/graph/adjacency_list.hpp)/
>>> >
>>> > After which i came across this post
>>> > <https://sourceforge.net/p/sdcc/discussion/1865/thread/ce681ab6/>, and
>>> > ran the following command but the same error still persists.:
>>> > ./configure CPPFLAGS=-I/opt/local/include
>>> >
>>> > Any suggestions?
>>> >
>>>
>>> Which OS? Do you have boost installed? If yes, where are the headers,
>>> such as adjacency_list.hpp located?
>>>
>>> Philipp
>>>
>>>
>>> _______________________________________________
>>> Sdcc-user mailing list
>>> Sdcc-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>>>
>> _______________________________________________
>> Sdcc-user mailing list
>> Sdcc-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>>
> _______________________________________________
> Sdcc-user mailing list
> Sdcc-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to