Hi,
Faced some compilation issues: any hints?
Jan 06, 2017 Check peer certificate against the file crl in PEM format. A CRL (certificate revocation list) is used when a particular key is compromised but when the overall PKI is still intact. Suppose you had a PKI consisting of a CA, root certificate, and a number of client certificates.
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/libxml2 -I/var/www/piati/pyenv/build/lxml/src/lxml/includes -I/usr/include/python3.3m -I/var/www/piati/pyenv/include/python3.3m -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-3.3/src/lxml/lxml.etree.o
src/lxml/lxml.etree.c:8:22: fatal error: pyconfig.h: No such file or directory
#include 'pyconfig.h'
compilation terminated.
/usr/lib/python3.3/distutils/dist.py:257: UserWarning: Unknown distribution option: 'bugtrack_url'
warnings.warn(msg)
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
Cleaning up...
Removing temporary dir /var/www/piati/pyenv/build...
Command /var/www/piati/pyenv/bin/python3.3 -c 'import setuptools;file='/var/www/piati/pyenv/build/lxml/setup.py';exec(compile(open(file).read().replace('rn', 'n'), file, 'exec'))' install --record /tmp/pip-ljykbz-record/install-record.txt --single-version-externally-managed --install-headers /var/www/piati/pyenv/include/site/python3.3 failed with error code 1 in /var/www/piati/pyenv/build/lxml
Command /var/www/piati/pyenv/bin/python3.3 -c 'import setuptools;file='/var/www/piati/pyenv/build/lxml/setup.py';exec(compile(open(file).read().replace('rn', 'n'), file, 'exec'))' install --record /tmp/pip-ljykbz-record/install-record.txt --single-version-externally-managed --install-headers /var/www/piati/pyenv/include/site/python3.3 failed with error code 1 in /var/www/piati/pyenv/build/lxml
Exception information:
Traceback (most recent call last):
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/basecommand.py', line 134, in main
status = self.run(options, args)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/commands/install.py', line 241, in run
requirement_set.install(install_options, global_options, root=options.root_path)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/req.py', line 1298, in install
requirement.install(install_options, global_options, _args, *_kwargs)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/req.py', line 625, in install
cwd=self.source_dir, filter_stdout=self._filter_install, show_stdout=False)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/util.py', line 670, in call_subprocess
% (command_desc, proc.returncode, cwd))
pip.exceptions.InstallationError: Command /var/www/piati/pyenv/bin/python3.3 -c 'import setuptools;file='/var/www/piati/pyenv/build/lxml/setup.py';exec(compile(open(file).read().replace('rn', 'n'), file, 'exec'))' install --record /tmp/pip-ljykbz-record/install-record.txt --single-version-externally-managed --install-headers /var/www/piati/pyenv/include/site/python3.3 failed with error code 1 in /var/www/piati/pyenv/build/lxml
Traceback (most recent call last):
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/basecommand.py', line 134, in main
status = self.run(options, args)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/commands/install.py', line 241, in run
requirement_set.install(install_options, global_options, root=options.root_path)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/req.py', line 1298, in install
requirement.install(install_options, global_options, _args, *_kwargs)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/req.py', line 625, in install
cwd=self.source_dir, filter_stdout=self._filter_install, show_stdout=False)
File '/var/www/piati/pyenv/lib/python3.3/site-packages/pip/util.py', line 670, in call_subprocess
% (command_desc, proc.returncode, cwd))
pip.exceptions.InstallationError: Command /var/www/piati/pyenv/bin/python3.3 -c 'import setuptools;file='/var/www/piati/pyenv/build/lxml/setup.py';exec(compile(open(file).read().replace('rn', 'n'), file, 'exec'))' install --record /tmp/pip-ljykbz-record/install-record.txt --single-version-externally-managed --install-headers /var/www/piati/pyenv/include/site/python3.3 failed with error code 1 in /var/www/piati/pyenv/build/lxml
hi every one
I'm working of BGM11s using stater kit from this link 'https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2017/08/17/using_low_energytim-9RYB'
i followed the steps and and created the soc_empty project work with LETIMER0 in BLE Stack to create PWM output . when i build the program it shows the error like em_letimer.h 'No such file or directory,'
At first there is no em_letimer.h file in 'inc' folder in 'emlib' file , so i manually copy the em_letimer.h file to that folder. even after i copied that file the project show the same error while build the program . i never experienced this error for a header file . Because i worked on all the timer peripherals in BGM11s before itself and it works as expected but this error only occurs in BLE stack . i have attached the image file of the screen shot.
Don't know were i went wrong , Please help.
Thanks in advance.
- sorry guys the program works.i linked the em_letimer.h to 'inc' folder instead of copy it to the folder. header file should be copied and C file should be linked to 'src' folder only then it works.sorry to wasted a thread , Extremely sorry.thanks
- EmployeeIt looks as if you linked 'em_letimer.h' rather than copying. If you right click on the file and select 'Copy Linked File in to Project' this will fix the problem. BLE and MCU projects do this differently.
- Employee@yuvaraj you can also link header files to your project, but then you need to also modify your project include paths so that the actual location of the file is covered. And easy workaround is just to copy the file into project instead of linking. (However, this may be problematic if you use one header file in multiple projects and the header file may change -> not scalable solution)sorry to wasted a thread , Extremely sorry.No worries, it was perfectly valid question and there was also a logical explanation. Thanks for sharing, this will help other customers who run into the same problem.