LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Getting lots of errors when compiling sip from source. What do they mean? (https://www.linuxquestions.org/questions/linux-newbie-8/getting-lots-of-errors-when-compiling-sip-from-source-what-do-they-mean-439311/)

BillWho? 04-27-2006 06:07 AM

Getting lots of errors when compiling sip from source. What do they mean?
 
I have been trying to install the HP driver "HPLIP" from Linux printing on my computer. I already have printing working on the HP PSC 1410 All In One using "HPOJ" and Cups but am now trying to get scanning to work and for this I need "HPLIP".
According to the "HPLIP" instructions that were in the source tarball I intend to use I need.

PyQt3.11 or higher ( I have downloaded version 3.15.1 source code from Riverbankcomputing.co.uk, this item requires sip)

Sip ( I have version 4.4.1 ) No other requirements are listed in the readme

As the first step in trying to install HPLIP I have been trying to install sip 4.4.1 from source
I seem to have no problems with the configuration, which I understand means that I do not have any missing dependentcies, is this correct? But I am getting lots of errors when I enter the make command as can be seen in these examples.

I first tried the default configuration, which I believe would be fine for Puppy as everything goes in a subdirectory of /usr with these results

# python configure.py

This is SIP 4.4.1 for Python on Linux 2
The SIP code generator will be installed in /usr/bin.
The SIP module will be installed in /usr/lib/python2.4/site-packages.
The SIP header file will be installed in /usr/include/python2.4
The default directory to install .sip files in is /usr/share/sip.
The platform/compiler configuration is linux-g++
Creating sipconfig.py...
Creating top level Makefille...
Creating sip code generator Makefile...
Creating sip module Makefile...


# make

siplib.c: At top level:
siplib.c:6755: error: parse error before "sipSigArg"
siplib.c: In function `sipFindSigArgType':
siplib.c:6757: error: `em' undeclared (first use in this function)
siplib.c:6759: error: `at' undeclared (first use in this function)
siplib.c:6769: error: `name' undeclared (first use in this function)
siplib.c:6769: error: `len' undeclared (first use in this function)
siplib.c:6771: error: `tem' undeclared (first use in this function)
siplib.c:6797: error: `indir' undeclared (first use in this function)
make[1]: *** [siplib.o] Error 1
make[1]: Leaving directory `/mnt/pupxxx/sip/sip-4.4.1/siplib'
make: *** [all] Error 2

I then tried specifying that everything went in /usr with these results

# python configure.py -b /usr -d /usr -e /usr -v /usr

This is SIP 4.4.1 for Python 2.4.2 on linux2.
The SIP code generator will be installed in /usr.
The SIP module will be installed in /usr.
The SIP header file will be installed in /usr.
The default directory to install .sip files in is /usr.
The platform/compiler configuration is linux-g++.
Creating sipconfig.py...
Creating top level Makefile...
Creating sip code generator Makefile...
Creating sip module Makefile...


# make

siplib.c: At top level:
siplib.c:6755: error: parse error before "sipSigArg"
siplib.c: In function `sipFindSigArgType':
siplib.c:6757: error: `em' undeclared (first use in this function)
siplib.c:6759: error: `at' undeclared (first use in this function)
siplib.c:6769: error: `name' undeclared (first use in this function)
siplib.c:6769: error: `len' undeclared (first use in this function)
siplib.c:6771: error: `tem' undeclared (first use in this function)
siplib.c:6797: error: `indir' undeclared (first use in this function)
make[1]: *** [siplib.o] Error 1
make[1]: Leaving directory `/mnt/pupxxx/sip/sip-4.4.1/siplib'
make: *** [all] Error 2

And finally I entered the make command with a debugging flag with this result.

# make -d

siplib.c: At top level:
siplib.c:6755: error: parse error before "sipSigArg"
siplib.c: In function `sipFindSigArgType':
siplib.c:6757: error: `em' undeclared (first use in this function)
siplib.c:6759: error: `at' undeclared (first use in this function)
siplib.c:6769: error: `name' undeclared (first use in this function)
siplib.c:6769: error: `len' undeclared (first use in this function)
siplib.c:6771: error: `tem' undeclared (first use in this function)
siplib.c:6797: error: `indir' undeclared (first use in this function)
Got a SIGCHLD; 1 unreaped children.
Reaping losing child 0x080717f0 PID 13694
make[1]: *** [siplib.o] Error 1
Removing child 0x080717f0 PID 13694 from chain.
make[1]: Leaving directory `/mnt/pupxxx/sip/sip-4.4.1/siplib'
Got a SIGCHLD; 1 unreaped children.
Reaping losing child 0x08070ad0 PID 13692
make: *** [all] Error 2
Removing child 0x08070ad0 PID 13692 from chain.

What do these errors mean, and can you explain them to me for future use please?

If there was a debugging log file created I have been unable to find it. The examples above are only part of the information I was able to read in In the terminal but, even then I could not scroll back to the beginning of the output.

Any help that can be given will be greatly appreciated

bigrigdriver 04-27-2006 09:06 AM

I can't help you with the errors. I'd suspect one or more corrupt or missing files in the package you downloaded.

Regarding scrolling through the output, you can capture that output to a text file with the tee command for later reading.

make | tee sip_install.txt. Tee replicates output to stdout to a text file.

Agrouf 04-27-2006 09:09 AM

Please post the offending part of code in siplib.c

BillWho? 04-28-2006 04:30 AM

Quote:

Originally Posted by Agrouf
Please post the offending part of code in siplib.c

two questions here
1 How do I locate and isolate the offending code ?
2 Once I locate the code will I be able to simply copy it to be able to post it ?

I'm still pretty green and working mostly from the GUI

Quote:

Originally Posted by bigrigdriver
Regarding scrolling through the output, you can capture that output to a text file with the tee command for later reading.

Thanks for the tip I will be trying it shortly

Agrouf 04-28-2006 11:10 AM

Quote:

Originally Posted by BillWho?
two questions here
1 How do I locate and isolate the offending code ?
2 Once I locate the code will I be able to simply copy it to be able to post it ?

1/ It is written in the error output you posted. post the lines from 6700 to 6800.
2/ yes

BillWho? 04-28-2006 08:37 PM

Here are lines 6700 to 6800

siplib.c:6701: error: `indir' undeclared (first use in this function)
siplib.c:6702: error: `at' undeclared (first use in this function)
siplib.c: At top level:
siplib.c:6721: error: parse error before '*' token
siplib.c: In function `findEnumArg':
siplib.c:6727: error: `emd' undeclared (first use in this function)
siplib.c:6731: error: `name' undeclared (first use in this function)
siplib.c:6731: error: `len' undeclared (first use in this function)
siplib.c:6737: error: `indir' undeclared (first use in this function)
siplib.c:6738: error: `at' undeclared (first use in this function)
siplib.c: At top level:
siplib.c:6755: error: parse error before "sipSigArg"
siplib.c: In function `sipFindSigArgType':
siplib.c:6757: error: `em' undeclared (first use in this function)
siplib.c:6759: error: `at' undeclared (first use in this function)
siplib.c:6769: error: `name' undeclared (first use in this function)
siplib.c:6769: error: `len' undeclared (first use in this function)
siplib.c:6771: error: `tem' undeclared (first use in this function)
siplib.c:6797: error: `indir' undeclared (first use in this function)
make[1]: *** [siplib.o] Error 1
make: *** [all] Error 2

If as I suspect you want everything begining with siplib.c let me know and I wil post it.
Quote:

Originally Posted by bigrigdriver
Regarding scrolling through the output, you can capture that output to a text file with the tee command for later reading.

make | tee sip_install.txt. Tee replicates output to stdout to a text file.

I am only getting 11 lines not the entire output that I was unable to scroll through. Any suggestions?

BillWho? 05-04-2006 07:13 AM

Update for anyone else having similar problems

It seems this may have been a Puppy OS specific problem.
I found that Make was trying to access files in /usr/include/Python2.4/ but the package I used to install Python does not seem to have installed this directory and it contents.
I removed the Python package and reinstalled Python this time from source then recompiled SIP, this time I was successful.

Thanks for the advise


All times are GMT -5. The time now is 04:25 PM.