LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 05-05-2017, 02:48 PM   #1
riscv
Member
 
Registered: Mar 2017
Posts: 34

Rep: Reputation: Disabled
PKG-CONFIG and libglip package not found


Hello,

I'm running a configure command and I got the following error.


Code:
alpha@alpha-VirtualBox:~/lowrisc-chip/opensocdebug/software/build$ ../configure --prefix=$OSD_ROOT --enable-python-bindings
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether make supports nested variables... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc -std=gnu99... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no
checking for gcc -std=gnu99 option to produce PIC... -fPIC -DPIC
checking if gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes
checking if gcc -std=gnu99 static flag -static works... yes
checking if gcc -std=gnu99 supports -c -o file.o... yes
checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes
checking whether the gcc -std=gnu99 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for a sed that does not truncate output... (cached) /bin/sed
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libglip... no
configure: error: Package requirements (libglip >= 0.1) were not met:

No package 'libglip' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables libglip_CFLAGS
and libglip_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I tired the following, of which none seems to have worked:

Code:
    sudo rm /var/lib/apt/lists/* -vf   

    sudo apt-get --fix-broken install

    sudo apt-get update 

    sudo apt-get clean  

    sudo apt-get autoclean 

    sudo apt-get autoremove

    sudo dpkg --configure -a 

    sudo apt-get update
Then I installed the Synaptic package manager, but I don't know which packages to install or to remove.
PS: There are no broken packages on Synaptic.

Could you please tell me how I can fix this ?
Thank you !
 
Old 05-05-2017, 03:23 PM   #2
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 20 MATE
Posts: 8,048
Blog Entries: 5

Rep: Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918
Did you carry out this stage to build glip?

http://www.lowrisc.org/docs/debug-v0.3/osdsoftware/

It would be better if you were to tell us what it is you are trying to do, where the instructions are that you are following, and what you have achieved so far...
 
Old 05-05-2017, 03:36 PM   #3
riscv
Member
 
Registered: Mar 2017
Posts: 34

Original Poster
Rep: Reputation: Disabled
Yes, the glip stage is done:
Code:
alpha@alpha-VirtualBox:~/lowrisc-chip/opensocdebug/glip/build$ ../configure --prefix=$OSD_ROOT --enable-tcp --enable-uart
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether make supports nested variables... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc -std=gnu99... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no
checking for gcc -std=gnu99 option to produce PIC... -fPIC -DPIC
checking if gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes
checking if gcc -std=gnu99 static flag -static works... yes
checking if gcc -std=gnu99 supports -c -o file.o... yes
checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes
checking whether the gcc -std=gnu99 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for a sed that does not truncate output... (cached) /bin/sed
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for doxygen... no
configure: WARNING: doxygen not found - will not generate any doxygen documentation
checking for perl... /usr/bin/perl
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/tools/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

        glip 0.1.0-dev
        =====

        prefix:                 /home/alpha/lowrisc-chip/tools
        sysconfdir:             ${prefix}/etc
        libdir:                 ${exec_prefix}/lib
        includedir:             ${prefix}/include

        compiler:               gcc -std=gnu99
        cflags:                 -g -O2
        ldflags:                

        backends:
        uart                    yes
        cypressfx2              no
        tcp                     yes
        jtag                    no

alpha@alpha-VirtualBox:~/lowrisc-chip/opensocdebug/glip/build$ make && make install
make --no-print-directory all-recursive
Making all in src
Making all in .
  CC       libglip_la-cbuf.lo
  CC       libglip_la-glip.lo
  CC       libglip_la-util.lo
  CC       backend_uart/sw/libglip_la-backend_uart.lo
  CC       backend_tcp/sw/libglip_la-backend_tcp.lo
  CCLD     libglip.la
Making all in tools
  CC       glip_loopback_measure-loopback_measure.o
  CC       glip_loopback_measure-options.o
  CCLD     glip_loopback_measure
  GEN      libglip.pc
Making install in src
Making install in .
 /bin/mkdir -p '/home/alpha/lowrisc-chip/tools/lib'
 /bin/bash ../libtool   --mode=install /usr/bin/install -c   libglip.la '/home/alpha/lowrisc-chip/tools/lib'
libtool: install: /usr/bin/install -c .libs/libglip.so.0.0.0 /home/alpha/lowrisc-chip/tools/lib/libglip.so.0.0.0
libtool: install: (cd /home/alpha/lowrisc-chip/tools/lib && { ln -s -f libglip.so.0.0.0 libglip.so.0 || { rm -f libglip.so.0 && ln -s libglip.so.0.0.0 libglip.so.0; }; })
libtool: install: (cd /home/alpha/lowrisc-chip/tools/lib && { ln -s -f libglip.so.0.0.0 libglip.so || { rm -f libglip.so && ln -s libglip.so.0.0.0 libglip.so; }; })
libtool: install: /usr/bin/install -c .libs/libglip.lai /home/alpha/lowrisc-chip/tools/lib/libglip.la
libtool: finish: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/sbin" ldconfig -n /home/alpha/lowrisc-chip/tools/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /home/alpha/lowrisc-chip/tools/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
 /bin/mkdir -p '/home/alpha/lowrisc-chip/tools/include/glip'
 /usr/bin/install -c -m 644 ../../include/libglip.h '/home/alpha/lowrisc-chip/tools/include/glip'
Making install in tools
 /bin/mkdir -p '/home/alpha/lowrisc-chip/tools/bin'
  /bin/bash ../../libtool   --mode=install /usr/bin/install -c glip_loopback_measure '/home/alpha/lowrisc-chip/tools/bin'
libtool: install: /usr/bin/install -c .libs/glip_loopback_measure /home/alpha/lowrisc-chip/tools/bin/glip_loopback_measure
make[3]: Nothing to be done for `install-data-am'.
make[2]: Nothing to be done for `install-exec-am'.
 /bin/mkdir -p '/home/alpha/lowrisc-chip/tools/lib/pkgconfig'
 /usr/bin/install -c -m 644 libglip.pc '/home/alpha/lowrisc-chip/tools/lib/pkgconfig'
The software stage yields the error in the original post.

Am I missing something ?
 
Old 05-05-2017, 03:41 PM   #4
riscv
Member
 
Registered: Mar 2017
Posts: 34

Original Poster
Rep: Reputation: Disabled
As for what I have done so far: I tried implementing Lowrisc ( debug) untethered v2.0. Did not go as far as simulation and RTL because I do not dispose of the two default fpga boards, I have a zedboard.
So, I'm following the instruction to implement lowrisc version 3.0 (even though the fpga_board variable says nexys...)
I have installed Vivado, Verilator, the lowrisc-chip v3.0 and the RISCV toolchain.

Any supplementary advice ?

Last edited by riscv; 05-05-2017 at 04:02 PM.
 
Old 05-05-2017, 03:43 PM   #5
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 20 MATE
Posts: 8,048
Blog Entries: 5

Rep: Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918
Can you tell me what you are trying to do, which instructions and/or pages of instructions you have carried out so far, and on which page is located the instruction that generated the initial error.

Problems can only be solved in context. You need to provide that context.

Edit: You posted while I was typing this. Ok, I'll have a look.

Last edited by hydrurga; 05-05-2017 at 03:45 PM.
 
Old 05-05-2017, 03:48 PM   #6
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 20 MATE
Posts: 8,048
Blog Entries: 5

Rep: Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918
By "Lowrisc debug v2.0", do you mean this page?

http://www.lowrisc.org/docs/untether-v0.2/

If not, can you point at me at the exact page(s) that you have followed so far.
 
Old 05-05-2017, 04:00 PM   #7
riscv
Member
 
Registered: Mar 2017
Posts: 34

Original Poster
Rep: Reputation: Disabled
Sorry, I should have said untethered. Yes it was that page. I stopped following those instructions because it did not work for the Zedboard.

As for now and in regard with the errors I'm having, I started from here: http://www.lowrisc.org/docs/debug-v0.3, then followed these http://www.lowrisc.org/docs/debug-v0.3/environment/
In this http://www.lowrisc.org/docs/debug-v0.3/lowriscsetup, I ran the following (post #3):
Code:
cd $TOP/opensocdebug/glip
./autogen.sh
mkdir build; cd build
../configure --prefix=$OSD_ROOT --enable-tcp --enable-uart
make && make install
And in original post #1, I had done the following:
Code:
cd $TOP/opensocdebug/software
./autogen.sh
mkdir build; cd build
../configure --prefix=$OSD_ROOT --enable-python-bindings
The error is after running ../configure --prefix=$OSD_ROOT --enable-python-bindings.
In the code provided in post #1 the last lines say
Code:
 
checking pkg-config is at least version 0.9.0... yes
checking for libglip... no
configure: error: Package requirements (libglip >= 0.1) were not met:

No package 'libglip' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables libglip_CFLAGS
and libglip_LIBS to avoid the need to call pkg-c
 
Old 05-05-2017, 04:06 PM   #8
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 20 MATE
Posts: 8,048
Blog Entries: 5

Rep: Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918Reputation: 2918
Ok, thanks. I see that you're working in VirtualBox. What might have been a good idea would have to have created a snapshot before you began the first attempt (v0.2) and then reverted to the original state before beginning the attempt at v0.3. That would have assured that the first attempt didn't influence the second attempt. Or perhaps you did do that? It's always a good idea to create a VirtualBox snapshot before manually installing software in case things go awry.

Anyway, I'll have a look at v0.3.

If you still have the command line open, and your history extends that far back, can you just go over all the instructions that you've carried out since the "sudo apt-get install autoconf..." line and check that there have been no more errors (or important-looking warnings) before the error in the opening post. Cheers.
 
Old 05-05-2017, 04:12 PM   #9
riscv
Member
 
Registered: Mar 2017
Posts: 34

Original Poster
Rep: Reputation: Disabled
Actually, I'm working on v0.3 on a different virtual machine than v2.0.
I did not have any errors or warning messages after sudo apt-get install autoconf... I just re-ran it and everything seems fine ?
Code:
alpha@alpha-VirtualBox:~$ sudo apt-get install autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libncurses5-dev libusb-1.0-0 libboost-dev swig git
Reading package lists... Done
Building dependency tree       
Reading state information... Done
autoconf is already the newest version.
automake is already the newest version.
autotools-dev is already the newest version.
bison is already the newest version.
build-essential is already the newest version.
flex is already the newest version.
gawk is already the newest version.
git is already the newest version.
gperf is already the newest version.
libboost-dev is already the newest version.
libgmp-dev is already the newest version.
libmpc-dev is already the newest version.
libmpfr-dev is already the newest version.
libncurses5-dev is already the newest version.
libusb-1.0-0 is already the newest version.
swig is already the newest version.
texinfo is already the newest version.
curl is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
Old 05-09-2017, 01:14 PM   #10
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
Is libglip provided by the thing that's checking for it?

Otherwise:

$ ./configure --help | less

There is probably an option to disable the feature that requires libglip. Which would be one way to work around the issue. --disable-libglip --without-libglip or similar type thing.

https://github.com/TUM-LIS/glip/blob...lude/libglip.h

Otherwise get glip and the glip.pc file that pkg-config looks for to satisfy the dependency. It's not a part of debian jessie (x86_64), so nothing that I care to install atm.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Package xmuu was not found in the pkg-config search path shachter Linux - Software 7 11-23-2014 04:05 PM
pkg-config error , no package found... anks Linux - Software 5 05-25-2014 11:46 AM
[SOLVED] Package xproto was not found in the pkg-config search path. shitou Linux - Kernel 1 10-18-2010 10:39 AM
Package gstreamer-0.10.23 was not found in the pkg-config search path. HarryBoy Linux - Newbie 1 12-16-2009 03:41 PM
pkg-config, gaim.pc not found ncharoe Linux - Newbie 12 01-15-2005 11:07 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration