date
int64
1,220B
1,719B
question_description
stringlengths
28
29.9k
accepted_answer
stringlengths
12
26.4k
question_title
stringlengths
14
159
1,486,153,211,000
I was trying to build R myself and put it in a temp_R folder by giving a command like ./configure --prefix=/dir/where/I/wanted/to/put/R. But it seems that some of the important stuff was put into the temp_R folder all the same. Should I have extracted the archive to the folder where I wanted to have R before compiling, or what other solution should I use?
When you run ./configure --prefix ... it typically puts all the files in the directory you just downloaded to anyway. The --prefix option is utilized during the make and make install steps that you run afterwards. Primarily the make install step will install all the software that the make step compiled to the locations derived from --prefix /some/path.
Can the --prefix path be the same as the directory where I downloaded/unzipped the source?
1,486,153,211,000
I compiled an application with a Makefile and g++ and it turned out, that g++ doesn't have to recompile the whole application again when I modify the Makefile (I changed to paths to the dynamic link libraries). At that time the application haven't yet compiled successfully, so there was no final executable application available. But g++ didn't compile the whole application again. Where is this information or compiled sources stored? I didn't see anything neither in /tmp nor in any hidden file within my home dir, nor within the root directory of the application itself. (Maybe I didn't look well enough).
GCC stores what it generates wherever you (or in this case, the Makefile) tell it to (with the -o output option). It doesn't do compilation result-caching by itself. What makes partial recompiles possible is the Makefile itself. It's a set of targets (executable, object files, possibly other things) with what they depend on and rules to generate the target from these dependencies. make looks at everything that needs to be built by evaluating the dependency chains, and rebuilding all the target that either don't exist yet, or have dependencies that are more recent than the target. For instance, let's say you have this simple Makefile: foo.o: foo.c foo.h gcc -o foo.o -c foo.c foo: foo.o gcc -o foo foo.o If you invoke make foo, it will look at the Makefile, see that foo depends on foo.o. So it looks up foo.o, and sees that that depends on both foo.c and foo.h. If foo.o is older then either of these two files, or if foo.o doesn't exist, it executes the compile line gcc -o foo.o -c foo.c, which generates foo.o. If you rerun make foo right after that, foo.o will be newer than both the C file and the header, so make won't re-compile foo.o, and skip to linking the final executable (if that's necessary - it might just say that nothing needs to be done).
Where does g++ store compiled sources?
1,486,153,211,000
I'm having a problem building GPG on my system; when I try to run make it fairly well before it suddenly bails out with an error. Here's my latest result from running it: make all-recursive Making all in m4 make[2]: Nothing to be done for `all'. Making all in gl make all-am make[3]: Nothing to be done for `all-am'. Making all in include make[2]: Nothing to be done for `all'. Making all in jnlib make[2]: Nothing to be done for `all'. Making all in common make all-am make[3]: Nothing to be done for `all-am'. Making all in kbx make[2]: Nothing to be done for `all'. Making all in g10 make[2]: Nothing to be done for `all'. Making all in keyserver make[2]: Nothing to be done for `all'. Making all in sm make[2]: Nothing to be done for `all'. Making all in agent make[2]: Nothing to be done for `all'. Making all in scd gcc -DHAVE_CONFIG_H -I. -I.. -I../gl -I../intl -I../common -DLOCALEDIR=\"/usr/local/share/locale\" -DGNUPG_BINDIR="\"/usr/local/bin\"" -DGNUPG_LIBEXECDIR="\"/usr/local/libexec\"" -DGNUPG_LIBDIR="\"/usr/local/lib/gnupg\"" -DGNUPG_DATADIR="\"/usr/local/share/gnupg\"" -DGNUPG_SYSCONFDIR="\"/usr/local/etc/gnupg\"" -g -O2 -Wall -Wno-pointer-sign -Wpointer-arith -MT gnupg_pcsc_wrapper-pcsc-wrapper.o -MD -MP -MF .deps/gnupg_pcsc_wrapper-pcsc-wrapper.Tpo -c -o gnupg_pcsc_wrapper-pcsc-wrapper.o `test -f 'pcsc-wrapper.c' || echo './'`pcsc-wrapper.c pcsc-wrapper.c:69: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’ pcsc-wrapper.c:129: error: expected specifier-qualifier-list before ‘pcsc_dword_t’ pcsc-wrapper.c:149: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘pcsc_protocol’ pcsc-wrapper.c:153: error: expected ‘)’ before ‘scope’ pcsc-wrapper.c:160: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:162: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:164: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:167: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:168: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:170: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:172: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:173: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:174: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:175: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:177: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:179: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:180: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:181: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:182: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:185: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:189: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:192: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:194: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:196: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:198: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:200: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c:201: error: expected declaration specifiers or ‘...’ before ‘pcsc_dword_t’ pcsc-wrapper.c: In function ‘load_pcsc_driver’: pcsc-wrapper.c:347: error: ‘pcsc_establish_context’ undeclared (first use in this function) pcsc-wrapper.c:347: error: (Each undeclared identifier is reported only once pcsc-wrapper.c:347: error: for each function it appears in.) pcsc-wrapper.c: In function ‘handle_open’: pcsc-wrapper.c:411: error: ‘pcsc_dword_t’ undeclared (first use in this function) pcsc-wrapper.c:411: error: expected ‘;’ before ‘nreader’ pcsc-wrapper.c:413: error: expected ‘;’ before ‘card_state’ pcsc-wrapper.c:428: warning: implicit declaration of function ‘pcsc_establish_context’ pcsc-wrapper.c:437: error: ‘nreader’ undeclared (first use in this function) pcsc-wrapper.c:437: error: too many arguments to function ‘pcsc_list_readers’ pcsc-wrapper.c:446: error: too many arguments to function ‘pcsc_list_readers’ pcsc-wrapper.c:487: error: ‘pcsc_protocol’ undeclared (first use in this function) pcsc-wrapper.c:487: warning: passing argument 3 of ‘pcsc_connect’ makes pointer from integer without a cast pcsc-wrapper.c:487: error: too many arguments to function ‘pcsc_connect’ pcsc-wrapper.c:509: error: expected ‘;’ before ‘readerlen’ pcsc-wrapper.c:511: error: ‘atrlen’ undeclared (first use in this function) pcsc-wrapper.c:512: error: ‘readerlen’ undeclared (first use in this function) pcsc-wrapper.c:515: error: ‘card_state’ undeclared (first use in this function) pcsc-wrapper.c:515: error: ‘card_protocol’ undeclared (first use in this function) pcsc-wrapper.c:516: error: too many arguments to function ‘pcsc_status’ pcsc-wrapper.c: In function ‘handle_close’: pcsc-wrapper.c:558: error: ‘pcsc_protocol’ undeclared (first use in this function) pcsc-wrapper.c: In function ‘handle_status’: pcsc-wrapper.c:587: error: ‘struct pcsc_readerstate_s’ has no member named ‘current_state’ pcsc-wrapper.c:590: error: too many arguments to function ‘pcsc_get_status_change’ pcsc-wrapper.c:602: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:604: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:607: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:614: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:624: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:625: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:626: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:627: error: ‘struct pcsc_readerstate_s’ has no member named ‘event_state’ pcsc-wrapper.c:629: error: ‘pcsc_protocol’ undeclared (first use in this function) pcsc-wrapper.c: In function ‘handle_reset’: pcsc-wrapper.c:645: error: ‘pcsc_dword_t’ undeclared (first use in this function) pcsc-wrapper.c:645: error: expected ‘;’ before ‘nreader’ pcsc-wrapper.c:646: error: expected ‘;’ before ‘card_state’ pcsc-wrapper.c:660: error: too many arguments to function ‘pcsc_disconnect’ pcsc-wrapper.c:678: error: ‘pcsc_protocol’ undeclared (first use in this function) pcsc-wrapper.c:678: warning: passing argument 3 of ‘pcsc_connect’ makes pointer from integer without a cast pcsc-wrapper.c:678: error: too many arguments to function ‘pcsc_connect’ pcsc-wrapper.c:689: error: ‘atrlen’ undeclared (first use in this function) pcsc-wrapper.c:690: error: ‘nreader’ undeclared (first use in this function) pcsc-wrapper.c:693: error: ‘card_state’ undeclared (first use in this function) pcsc-wrapper.c:693: error: ‘card_protocol’ undeclared (first use in this function) pcsc-wrapper.c:694: error: too many arguments to function ‘pcsc_status’ pcsc-wrapper.c: In function ‘handle_transmit’: pcsc-wrapper.c:716: error: ‘pcsc_dword_t’ undeclared (first use in this function) pcsc-wrapper.c:716: error: expected ‘;’ before ‘recv_len’ pcsc-wrapper.c:729: error: ‘pcsc_protocol’ undeclared (first use in this function) pcsc-wrapper.c:734: error: ‘recv_len’ undeclared (first use in this function) pcsc-wrapper.c:736: warning: passing argument 4 of ‘pcsc_transmit’ makes pointer from integer without a cast pcsc-wrapper.c:736: error: too many arguments to function ‘pcsc_transmit’ pcsc-wrapper.c: In function ‘handle_control’: pcsc-wrapper.c:756: error: ‘pcsc_dword_t’ undeclared (first use in this function) pcsc-wrapper.c:756: error: expected ‘;’ before ‘ioctl_code’ pcsc-wrapper.c:757: error: expected ‘;’ before ‘recv_len’ pcsc-wrapper.c:763: error: ‘ioctl_code’ undeclared (first use in this function) pcsc-wrapper.c:767: error: ‘recv_len’ undeclared (first use in this function) pcsc-wrapper.c:769: error: too many arguments to function ‘pcsc_control’ make[2]: *** [gnupg_pcsc_wrapper-pcsc-wrapper.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2
Your version of the GPG source code has a typo on line 69 in scd/pcsc-wrapper.c: someone mistyped unsigned as unsinged. Fix that, and GPG will compile.
Problem building GPG
1,486,153,211,000
I am trying to install the linux_monitor package under Centos 5.5. When I try make I get: make[3]: Entering directory `/tmp/linux_monitor-2.0RC3/src/server' if gcc -DHAVE_CONFIG_H -I. -I. -I../../src -I/usr/include/openssl -g -O2 -Wall -MT linux_mond.o -MD -MP -MF ".deps/linux_mond.Tpo" \ -c -o linux_mond.o `test -f 'linux_mond.c' || echo './'`linux_mond.c; \ then mv -f ".deps/linux_mond.Tpo" ".deps/linux_mond.Po"; \ else rm -f ".deps/linux_mond.Tpo"; exit 1; \ fi In file included from linux_mond.c:23: linux_mond.h:40:18: error: glib.h: No such file or directory linux_mond.c: In function ‘server’: linux_mond.c:155: warning: pointer targets in passing argument 3 of ‘accept’ differ in signedness linux_mond.c: In function ‘client’: linux_mond.c:334: warning: pointer targets in passing argument 1 of ‘strlen’ differ in signedness I understand it is not finding glib.h, right? I know it is present at /usr/include/glib-1.2/, but I tried several configure flags and looked at the different files and can't find how to let know to configure where that library is.
If you know it's in /usr/include/glib-1.2 then you should be able to add -I/usr/include/glib-1.2 to the 'INCLUDE' definition in your Makefile. I don't have the package or it's source so I can't be any less vague than that. EDIT I just downloaded the package you indicated above. Go to src/server and add -I/usr/include/glib-1.2 to the line DEFAULT_INCLUDES =-I. -I$(srcdir) -I$(top_builddir)/src DEFAULT_INCLUDES =-I. -I$(srcdir) -I$(top_builddir)/src -I/usr/include/glib-1.2 If you look just below that line you'll see COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) which is the line I was referring to in my comment below. EDIT EDIT Or more nicely ./configure --with-cpp-flags=-I/usr/include/glib-1.2
mon linux monitor install on centos - can't find glib.h although present
1,486,153,211,000
Did anybody here manage to install GCC 13.1.0 on their computer? When I try to build it from source on my 64-bit Debian Linux, I get the following error message: /usr/bin/ld: .libs/hwasan.o: relocation R_X86_64_PC32 against undefined symbol `__ehdr_start' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: nonrepresentable section on output collect2: error: ld returned 1 exit status make[4]: *** [Makefile:559: libhwasan.la] Error 1 make[4]: Leaving directory '/home/teo/gcc-objdir/x86_64-pc-linux-gnu/libsanitizer/hwasan' make[3]: *** [Makefile:532: all-recursive] Error 1 make[3]: Leaving directory '/home/teo/gcc-objdir/x86_64-pc-linux-gnu/libsanitizer' make[2]: *** [Makefile:419: all] Error 2 make[2]: Leaving directory '/home/teo/gcc-objdir/x86_64-pc-linux-gnu/libsanitizer' make[1]: *** [Makefile:22725: all-target-libsanitizer] Error 2 make[1]: Leaving directory '/home/teo/gcc-objdir' make: *** [Makefile:1090: all] Error 2 I configured it with ../gcc-13.1.0/configure --enable-languages=c,c++ --disable-multilib. My current GCC version is: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/12.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-12.2.0/configure --enable-languages=c,c++,ada --disable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.2.0 (GCC) Since this is a linking error, I suppose my current linker may be relevant. It is: GNU ld (GNU Binutils for Debian) 2.31.1 Copyright (C) 2018 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) a later version. This program has absolutely no warranty. So, what do you think is the problem and how can I solve it? The probability that I will manage to install it on Windows is so low it's not even worth trying. Do you agree?
This error seems to be caused by a bug in ld 2.31.1: https://sourceware.org/bugzilla/show_bug.cgi?id=24458. The bug was fixed in ld 2.32 and a later point release of 2.31 (but not one that seems to have made it into the Debian 10 package repository). While I have not tried it, a likely workaround is to obtain a newer ld (perhaps building it from source), and then use it for the gcc build (I'm not sure offhand what build flag allows specifying the linker to use, but presumably there is one).
Installing GCC 13.1.0 on x86_64 Debian
1,486,153,211,000
I'm wondering what are good practices about compilation and manual installation of software on Linux systems. I mean getting, building and installing code by this usual way : git clone https://a-repo/foo.git cd foo/ ./configure make make install Should that be avoided ? Or is it recommended ? Maybe it is better to make a package for the distribution in use ? Are there some tricks to manage versions and updates ? Does good practices exists when doing ./configure, particularly with --prefix= ? How can I install / uninstall properly ? Should I always keep the sources to do make uninstall ? I have seen some tools like stow, but this seems to be a controversial solution... Maybe an other one ? I prefer solutions that are independents of distro, but all suggestions and advices are welcome ! Thank you ! EDIT: It seems that people don't understand my question. I'm not opening a debate, I just want an answer as clear as possible for the various points above. I really think this could be helpful for some people. Thank you for your contribution.
The problem with your method is figuring out what files have to be deleted when you want to uninstall the software. The best practice is to build a package for the distribution. This has several advantages. It allows you to easily install, upgrade, & remove packages. It allows you to compile the software on a seperate machine avoiding putting compilers on every machine. It allows you to easily upgrade the package when the upstream goes to another version/release. And, it allows you to build the software without being root. A quick & dirty work around I used before I learned how to use rpmbuild & spec files was to: ./configure make make DESTDIR=/tmp/build install This puts all the "installed" files with the correct installation tree under the /tmp/build directory. Then change the owner/group for all the files in the directory. Then: tar cvfj <filename> -C /tmp/build/ To install them: tar xvf <filename> -C / To uninstall them: tar tf <filename> | xargs rm
Good practices when installing from sources on Linux
1,486,153,211,000
GNU Typist is a well-known typing practice program for the terminal. I wanted to use it so I downloaded the .tar.gz from https://ftp.gnu.org/gnu/gtypist/?C=M;O=D. But when I untarred it and ran configure, it gives me the error Error: both library and header files for the ncursesw library are required to build this package. See INSTALL file for further information. On Debian/Ubuntu you need to install libncursesw5-dev. I already have ncurses and ncurses-dev installed (the branch is v3.15). I also tried installing ncurses5 and ncurses5-libs from branch v3.13 + ncurses-dev, but it shows me the same error. How do I fix this error?
Nevermind, I was being too pedantic with "everything must be managed by the package manager". In the configure file, the error was triggered by if test -n "$HAVE_NCURSESW_H" -a -n "$HAVE_LIBNCURSESW"; then LIBS="-lncursesw $LIBS" else echo -e "Error: both library and header files for the ncursesw library\n"\ "are required to build this package. See INSTALL file for"\ "further information. On Debian/Ubuntu you need to install libncursesw5-dev." exit 1; fi HAVE_NCURSESW_H is determined by these lines: ac_fn_c_check_header_mongrel "$LINENO" "ncursesw/ncurses.h" "ac_cv_header_ncursesw_ncurses_h" "$ac_includes_default" if test "x$ac_cv_header_ncursesw_ncurses_h" = xyes; then : HAVE_NCURSESW_H=1 fi ac_fn_c_check_header_mongrel checks if a header exists. So I created a folder named ncursesw in /usr/include (temporarily) and copied ncurses.h to the folder. Ran configure and everything worked perfectly after that.
How do I compile gtypist-2.9.5 on Alpine Linux?
1,486,153,211,000
Do .config file in /boot has any role other than an information about the modules' presence? A .configXXXX in linux kernel source tree is used while building the kernel to ON/OFF a feature. But after installing what is it's role in /boot?
Their only role is to provide the configuration of the corresponding kernel, for information purposes. They are not required for anything else. (Note that they don’t only provide information about the presence of modules; they include all the kernel’s build configuration.)
Do config file in /boot has any role other than an information about the modules presence?
1,486,153,211,000
TL;DR: Once I already compiled the Linux (Debian) kernel with "make deb-pkg", how to generate a new one after minor changes in .config? Hello, I'm trying to compile the kernel following https://www.debian.org/doc//manuals/debian-handbook/sect.kernel-compilation.pl.html. Well, I did. It took a while, then I installed it, but it doesn't start. So I'm trying again. I edited the .config and want to compile a new one. But I can't find a way to do it without starting all over, removing and then compiling the whole thing. Just "make" seems to do nothing. I mean, it does something, but doesn't change the linux-image. Just "make deb-pkg", without removing all the produced files before, returns error. I searched for it, but all the answers I found seems to predate the use of "make deb-pkg" and didn't work. Thank you.
In the beginning of Chapter 8.10.4 of the very handbook you linked: NOTE Clean up before rebuilding If you have already compiled once in the directory and wish to rebuild everything from scratch (for example, because you substantially changed the kernel configuration), you will have to run make clean to remove the compiled files. At its heart, the make command uses a series of simple rules defined in Makefiles. For example, one rule might say that file X is built from files A, B and C using these commands. When deciding if file X needs to be rebuilt or not, make will usually just check if X exists, and if it does, whether it is newer than any of the source files A, B or C. If X does not exist or is older than one of its sources, it will be rebuilt. If there are other rules for building A, B and/or C, they will be evaluated first before deciding on X, and so on, recursively. (Over the decades of its existence, the make command and especially its GNU version have accumulated many extensions, but this is still the basic idea behind its operations.) You said you made "minor changes in .config". Some of the .config options enable/disable new modules to be built. If you e.g. enable a module that used to be disabled, that would require a new *.ko file to exist that was not there before, and that would most likely be detectable by the kernel Makefile system. But other options only cause changes by activating/deactivating some #ifdef blocks within individual source code files, or by changing some #define values. These can not be easily detected by the kernel Makefile system. So, without knowing exactly what your kernel configuration was before and the exact option(s) you changed, it will be impossible to say whether this is a known/expected issue or something that should have worked. The kernel Makefile system is a pretty complicated thing by itself; it's probably far too complicated to cover all the possible combinations of changes to kernel configuration options in a mathematically perfect fashion - it will err on the side of caution, ensuring that all configuration changes take effect. Sometimes that can cause rebuilding of more files than would be strictly optimal. A configuration change will update include/generated/autoconf.h, which is included by include/linux/kconfig.h, and since the latter is included by default, this would cause basically everything to be rebuilt anyway. Based on the NOTE I quoted above, the recommended procedure seems to be: "before re-running make deb-pkg, run make clean". I have experienced something similar with make deb-pkg: if I recall correctly, I think the error in re-running it is related more to the .deb package building steps than to the actual kernel compilation.
Recompile kernel after editing .config in Debian
1,486,153,211,000
I am new to linux and ran into this issue. I am trying to run USSD commands and i was recommended to use atinout, however checking from their page, I can;t seem to find how to install it. I downloaded the zip from sourceforge, it is atinout-0.9.1. I tried to run make (though I wasn't sure it could work) and got this output: gcc -o atinout -W -Wall -Wextra -Werror -DVERSION=\"0.9.1\" -g atinout.c atinout.c: In function ‘is_final_result’: atinout.c:141:6: error: this statement may fall through [-Werror=implicit-fallthrough=] 141 | if (strcmp(&response[1], "K\r\n") == 0) { | ^ atinout.c:145:2: note: here 145 | default: | ^~~~~~~ cc1: all warnings being treated as errors make: *** [Makefile:14: atinout] Error 1 Could someone guide me on this? Thanks.
I get the same error with GCC 9.3.0. One possible fix is to remove -Werror from this line in Makefile: CFLAGS = -W -Wall -Wextra -Werror \ so that it looks like that: CFLAGS = -W -Wall -Wextra \ It's possible when atinout was developed GCC didn't have implicit-fallthrough warning yet (it was implemented only in 2016 in commit 81fea426da8 ) or another compiler was used to compile it. Another fix is to try a different compiler, for example I don't get any warnings or errors with clang 10.0.1: $ make CC=clang clang -o atinout -W -Wall -Wextra -Werror -DVERSION=\"0.9.1\" -g atinout.c In both cases you'll end up with atinout in the current working directory: $ ./atinout --version atinout version 0.9.1 Copyright (C) 2013 Håkon Løvdal <[email protected]> This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; see http://www.gnu.org/licenses/gpl.html for details.
How do i install atinout on linux
1,486,153,211,000
I've been trying to compile digikam and as part of that process needed to compile jasper. Jasper developers use cmake, I wanted to make a .deb package -- in fact was trying to learn how to make a package to share -- and so tried to do this (which errors as below): sudo checkinstall -D "sudo cmake --build '/home/username/Downloads/jasper/buildlocal' --target install" Checkinstall run with sudo returns a "not found" error (end of 4th line) despite the command being passed to it working successfully: Installing with sudo cmake --build '/home/username/Downloads/jasper/buildlocal' --target install... ========================= Installation results =========================== /var/tmp/tmp.miGWYgiNzT/installscript.sh: 4: sudo cmake --build '/home/username/Downloads/jasper/buildlocal' --target install: not found **** Installation failed. Aborting package creation. Cleaning up...OK Bye. To repeat, the command sudo cmake --build '/home/username/Downloads/jasper/buildlocal' --target install was successful, but neither sudo checkinstall, nor sudo cmake with plain checkinstall, nor using sudo for both, worked. How can I pass the write invocation to checkinstall to make a package here. More details of all commands run at my blog, but I feel this is enough to answer the question.
IIRC you're supposed to run checkinstall with the actual install command as arguments, not as a single quoted argument. So: sudo checkinstall -D cmake --build '/home/username/Downloads/jasper/buildlocal' --target install This is not very clear from the manpage, but the README has some examples: Run checkinstall: checkinstall NOTE: If you give no arguments to checkinstall it will run a "make install". If you give arguments, the first non-option argument will be used as the install command. This is useful when the install command is not "make install" but something else like "make install_packages" or "setup" or whatever, i.e. checkinstall make install_packages checkinstall make modules_install checkinstall install.sh checkinstall setup checkinstall rpm -i my-package-1.0.i386-1.rpm
Using checkinstall in place of sudo cmake?
1,486,153,211,000
I'm trying to hack a MSYS package, so I found https://www.msys2.org/wiki/Creating-Packages/ - as an example: git clone "https://github.com/msys2/MSYS2-packages" cd MSYS2-packages/flex makepkg -sCLf So, if I run this, I get the sources built, and I get a package. Now, let's say, I change something in the source of the flex package, and I want to rebuild. I tried the makepkg -sCLf, but that command actually deletes the source directory - including my hacks - and so, that command in particular, cannot be used to build a package with hacks/changed source files. What command could I use instead, to build (hopefully only) the changed files in the source, and to build a package from that source?
The makepkg(8) manual states for the option -C: -C, --cleanbuild Remove the $srcdir before building the package. Try the command without the option -C to not remove the $srcdir: $ makepkg -sLf
Using PKGBUILD to build after hacking/changing sources?
1,486,153,211,000
As far as I understand, an interpreter runs code line by line; but I find probable that my reasoning is incorrect. If in this example case the first if line returns true, will the program know to skip to fi after echo "APPROVED" (and will it know which line fi is in?) or will it still take some time to check the next lines, and not execute them when they are inside an elif or else? if [ $AVERAGE -ge "6" ] then echo "APPROVED" # Does shell know how to directly get from here /\... elif [ $AVERAGE -lt "2" ] then echo "FAILED" else echo "RETAKE TEST" # ... To here? \/ fi Thank you!
As Michael Horner pointed out, a shell must parse the entire command first because if it's in a pipeline or is backgrounded, that will affect the execution of the command. This is true of any command that the shell executes, and it's pretty obvious if you write a multi-line shell command at an interactive prompt that it does so, since it will wait for you to complete the command before executing it. The shell will correctly execute each condition and stop once it reaches a case where the condition is true. It will not execute further elif conditions. The behavior of Unix shells is well specified by POSIX. Whether the shell has optimizations to make things run faster or more efficiently is a quality of implementation issue. A small shell, such as busybox's, would probably prefer to be as small as possible at the cost of a small amount of speed, whereas other shells might prefer to optimize things more. In general, shell scripting isn't a very efficient way to write code, since you end up forking and execing a large number of processes, so in my experience optimizations like you'd find in a typical optimizing compiler tend to be absent, since they don't improve things that much. It's generally more efficient to provide more built-in commands, which avoid the need for spawning external processes at all and give you more bang for your buck.
Does the shell script interpreter optimize if else chains?
1,486,153,211,000
I am trying to get the buttons on my Canon CanoScan LiDE 60 to work. So far I installed the sane-utils, the printer is detected and I can scan. However the front buttons on the scanner are not detected by SANE. I read in this case, one should compile scandb from sources and run ./configure --enable-scanbuttond which I did and then run make. However make doesn't complete, as there is a warning which is treated as an error: config.c: In function ‘cfg_do_parse’: config.c:117:5: error: ‘strncpy’ specified bound 4096 equals destination size [-Werror=stringop-truncation] strncpy(config_file, config_file_name, PATH_MAX); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors make[1]: *** [Makefile:503: config.o] Error 1 make[1]: Leaving directory '/usr/local/src/scanbd-1.5.1/src/scanbd' make: *** [Makefile:425: all-recursive] Error 1 Is there either a simpler way to get the buttons working or how can I compile scanbd to get my buttons to work?
The warning that's being treated as an error By the C compiler is causing the compilation to fail. You can have it treated as a warning by compiling with the following: make CFLAGS="-Wno-error=stringop-truncation" If you receive errors where it's the CXX compiler: make CXXLAGS="-Wno-error=format-truncation"
How can I compile scanbd on Raspberry Pi?
1,486,153,211,000
I installed ViM by compiling the source code from GitHub and then I used checkinstall to install it on my system. Now I'd like to install another program with the apt package manager (which is vifm), but when I try to install it it tells me that it will install vim-common and vim-addon-manager. As far as I understand by reading the packages web pages (vim-common and vim-addon-manager) I suspect I've already everything installed on my system to install vifm (even though I cannot be 100% sure). How can I install vifm without installing those two packages? Even better, if it turns out I'm right in suspecting that I already have everything those two packages provide installed on my system, how can I make apt aware of it? Thanks in advance.
The apt command uses dpkg as its package database. If the application was not installed by either of these utilities as a .deb package, there is no way they would know about it. You would want to create a proper .deb package for the new version, you should be able to reference the sources of the current packages to get an idea of how to do it. Since the vifm package depends on the official vim-common, it may also depend on the specific version that is provided by the distribution. In which case, you would need to also build vifm from source.
Manage manually compiled ViM (Debian)
1,486,153,211,000
The most current xf86-input-wacom version on Debian is 2 years old (0.34.99.1-1) it seems like and there is a bug where the touchscreen would not work spontaneously anymore which is fixed in version 0.36.1. I now obviously want that version on my Debian (currently still Buster, but I could update). Is building the package acceptable and will it be invincible to updates, or will a single update cause the whole thing to break down? In that case, should I just stay at Debian Buster, because its frozen? I know I am creating a "franken Debian" by doing that, so how to do it the correct Debian way without causing to much trouble? Handy Links I found so far: https://sourceforge.net/p/linuxwacom/bugs/349/ https://packages.debian.org/source/sid/xf86-input-wacom https://github.com/linuxwacom/xf86-input-wacom/wiki/Building-The-Driver
There are a couple of approaches to upgrade a package to a newer version which isn’t packaged yet, without risking the upgraded version being overwritten by a new package: package the new version yourself, or build an updated source package (in this case, Ubuntu has a package of version 0.36); uninstall the package and install from source. The former is far more “Debian-like”. However, in your particular scenario, the best solution might be to stop using xf86-input-wacom altogether: libinput supports Wacom touchscreens, and has better multitouch support. It will handle the touchscreen automatically once the Wacom driver is removed. If libinput doesn’t work, the best way to get an updated Wacom driver without resorting to a FrankenDebian is to rebuild the driver: install some tools we’ll need sudo apt install build-essential devscripts retrieve the Ubuntu source package dget -ux https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/xf86-input-wacom/1:0.36.1-0ubuntu2/xf86-input-wacom_0.36.1-0ubuntu2.dsc go into the extracted directory cd xf86-input-wacom* create a package to represent the build dependencies (this will make cleanup easier) mk-build-deps debian/control install it sudo apt install ./*build-deps*.deb move it out of the way mv ./*build-deps*.deb .. build the package dpkg-buildpackage -us -uc install the generated packages sudo debi clean up sudo apt --autoremove purge xf86-input-wacom-build-deps xserver-xorg-input-wacom-dbgsym
Updating Software on Debian to non packaged version
1,486,153,211,000
I'm running an alpine linux box, and am trying to install radare2. I downloaded the git repo, then ran the install.sh script. It seems to run fine until running into an error: In file included from p/native/linux/linux_debug.c:6: /home/nomad/GitRepos/radare2/libr/include/r_debug.h:609:115: note: expected 'r_ptrace_data_t' {aka 'int'} but argument is of type 'void *' static inline long r_debug_ptrace(RDebug *dbg, r_ptrace_request_t request, pid_t pid, void *addr, r_ptrace_data_t data) { ~~~~~~~~~~~~~~~~^~~~ CC linux_coredump.c p/native/linux/linux_coredump.c:10:10: fatal error: asm/ptrace.h: No such file or directory #include <asm/ptrace.h> ^~~~~~~~~~~~~~ compilation terminated. make[4]: *** [/home/nomad/GitRepos/radare2/libr/../global.mk:36: p/native/linux/linux_coredump.o] Error 1 make[3]: *** [Makefile:13: foo] Error 2 make[2]: *** [Makefile:157: debug] Error 2 make[1]: *** [Makefile:28: all] Error 2 make: *** [Makefile:61: all] Error 2 I've had a look around online, but haven't been able to find much relating to "Error 2". From the error it looks like I'm missing a library, but I'm not sure what library it is, or how to install it as I'm relatively new to alpine linux.
On Alpine Linux, the asm/ptrace.h header is provided by the linux-headers package. For installing the Linux headers package, run the following: apk add linux-headers Then, try repeating the install process.
Make Error installing radare2 on alpine linux
1,567,237,870,000
I have f30 installed 3 weeks and I keep seeing this error when I try to compile C++ of maybe fortran code. It is an error connected to ld : error: ld returned 126 exit status I've tried to look into it and so far I have no explanation. What I can share is that ld resides in /usr/bin which is a soft link from /etc/alternatives. [astamato@pcen35240 ~]$ ls -al /usr/bin/ld* lrwxrwxrwx. 1 root root 20 Apr 26 04:27 /usr/bin/ld -> /etc/alternatives/ld -rwxr-xr-x. 1 root root 13536 Aug 11 11:27 /usr/bin/ld.bfd -rwxr-xr-x. 1 root root 5441 Jun 6 13:55 /usr/bin/ldd -rwxr-xr-x. 1 root root 3853632 Mar 6 11:00 /usr/bin/ld.gold When I try to execute ld by it self (so not having it called from another program or installation script), I get the following [astamato@pcen35240 talys]$ /usr/bin/ld bash: /usr/bin/ld: cannot execute binary file: Exec format error [astamato@pcen35240 talys]$ sudo /usr/bin/ld /usr/bin/ld: /usr/bin/ld: cannot execute binary file Then I searched the original /etc/alternatives location, but it's again a soft link [astamato@pcen35240 talys]$ ls -al /etc/alternatives/ld* lrwxrwxrwx. 1 root root 15 Apr 26 04:27 /etc/alternatives/ld -> /usr/bin/ld.bfd Surprisingly enough, the link is to a ld.bfd file which is in /usr/bin. I tried to find the version of ld.bfd but it seems that it cannot be executed [astamato@pcen35240 talys]$ /usr/bin/ld.bfd --version bash: /usr/bin/ld.bfd: cannot execute binary file: Exec format error [astamato@pcen35240 talys]$ sudo /usr/bin/ld.bfd --version /usr/bin/ld.bfd: /usr/bin/ld.bfd: cannot execute binary file Any idea on how to understand what is wrong and solve the issue? EDIT After @steeldriver 's suggestion I report the following outputs $ file -L /usr/bin/ld.bfd /usr/bin/ld.bfd: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=d88173c7f8919542e59738a8c5b626f6ed81d7d8, stripped, too many notes (256) $ uname -m x86_64
I don't really know why it happened or if it could be fixed otherwise or if it will have an effect somewhere else but I just reinstalled binutils and it seems it solved it. So just type sudo yum reinstall binutils and it should be ok.
Cannot execute ld : error 126
1,567,237,870,000
I need to install MySmartUSB Light in linux LMDE 3 Cindy as programer for avr in linux,so i downloaded this driver (Linux_3.x.x_4.x.x_VCP_Driver_Source) from this link: based of it's note shown below: Last modified July 12, 2019 This bundle contains a modified CP210x driver for the 4.10.0 kernel (Ubuntu 17.04). It contains: Support for the CP2102N NOTE: This driver is an example of how to perform GPIO operations within the CP210x driver since the driver on kernel.org does not support GPIO at this time. This driver has only been written and tested on the Linux 3.13.0 kernel on Ubuntu 14.04. This driver is a modified version of the existing driver in the Linux 3.13.0 kernel, which is maintained at kernel.org. It is recommened to use the driver there that matches your specific kernel version: www.kernel.org Build instrutions: Ubuntu: 1. make ( your cp210x driver ) 2. cp cp210x.ko to /lib/modules//kernel/drivers/usb/serial 3. insmod /lib/modules/ When i want to run sudo make in the driver folder i get this error: so@notebook:~/Downloads/Compressed/Linux_3.x.x_4.x.x_VCP_Driver_Source$ sudo make [sudo] password for so: Sorry, try again. [sudo] password for so: make -C /lib/modules/`uname -r`/build M= modules make[1]: Entering directory '/usr/src/linux-headers-4.9.0-9-amd64' /usr/src/linux-headers-4.9.0-9-common/scripts/Makefile.build:44: /usr/src/linux-headers-4.9.0-9-common/scripts/basic/Makefile: No such file or directory make[5]: *** No rule to make target '/usr/src/linux-headers-4.9.0-9-common/scripts/basic/Makefile'. Stop. /usr/src/linux-headers-4.9.0-9-common/Makefile:444: recipe for target 'scripts_basic' failed make[4]: *** [scripts_basic] Error 2 /usr/src/linux-headers-4.9.0-9-common/scripts/Makefile.build:44: /usr/src/linux-headers-4.9.0-9-common/arch/x86/entry/syscalls/Makefile: No such file or directory make[4]: *** No rule to make target '/usr/src/linux-headers-4.9.0-9-common/arch/x86/entry/syscalls/Makefile'. Stop. arch/x86/Makefile:231: recipe for target 'archheaders' failed make[3]: *** [archheaders] Error 2 Makefile:152: recipe for target 'sub-make' failed make[2]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.9.0-9-amd64' Makefile:7: recipe for target 'all' failed make: *** [all] Error 2 SO how could i solve this problem?
Have you used this system to run make to build drivers before? It's possible you need a few extra packages. This guide might be somewhat helpful as it describes the necessary steps prior to compiling a software package, although the most important step in your case is probably the first: sudo apt-get install build-essential checkinstall Once this is run, try compiling the drivers with sudo make again. If it doesn't work, it's possible you don't have the proper kernel headers. Kernel headers are basically just the C header files for the kernel itself, which is necessary for compilation of things that interface with the kernel (such as the drivers). Here is an installation guide which explains that upgrading/installing the kernel headers is as easy as running: sudo apt update sudo apt install linux-headers-$(uname -r)
Error on Installing MySmartUSB Light in linux LMDE 3 Cindy (Makefile: No such file or directory)
1,567,237,870,000
I need custom patch my linux kernel so it can access the MacBook Pro (2018/2019) SSD for Ubuntu installation. Luckily, someone made a patch that seems to work. I have a second computer with a 1TB drive and there was several hundred GB's (maybe 500GB?). So I thought I would go ahead and compile from source (kernel 5.2). Well, I guess I should have cleaned my config file, because the kernal compile returned error that there was not enough disk space to proceed. Whaaaa? Anyway, I'm having difficulty finding out where all the space went. When the compile fails, where are the files? What should I delete from the failed compile to try again with a much better config? I guess I could just rewipe the partition and reinstall linux again, but I'd like to avoid that if the fix is relatively easy.
In general, you can do: make clean to clean up most artifacts generated by the build.
How to free up space after kernel compile fail - where are the extraneous stuff
1,567,237,870,000
I'm trying to compile libtorrent on Alpine Linux. autogen and configure work fine but after invoking make it fails with the following message: local_addr.cc:45:10: fatal error: linux/netlink.h: No such file or directory I looked in /usr/include and found only netlink/netlink.h. However the next include in the source file is rtnetlink.h which doesn't exist. Is this due to a missing dependency or perhaps a problem related to glibc/musl? How do you build libtorrent/rtorrent under Alpine Linux? I am aware there is an rtorrent package for Alpine but would rather prefer to build it myself, so I can customize the build options. These are the packages I installed prior to my build attempt: autoconf automake libtool pkgconfig ncurses-dev zlib-dev libsigc++-dev libcurl curl-dev libnl-dev
It appears that the linux-headers package contains netlink.h, so install it: apk add --update linux-headers
Alpine Linux - can't build libtorrent, missing linux/netlink.h
1,567,237,870,000
In OS Windows I used openconnect-gui. After I changed the OS on Debian, I didn't find a version for Debian and I don't understand how to build openconnect-gui for Debian.
From the application sources you're linking: Supported Platforms Microsoft Windows 7 and newer macOS 10.11 and newer This isn't made readily available for Linux. There is no need to compile a GUI for openconnect, it's already available as a NetworkManager plugin called network-manager-openconnect-gnome at Debian. Please note that this is a plugin for NetworkManager, not a stand-alone program with a command directly usable. As such you're supposed to be using NetworkManager, its own applet GUI nm-applet provided by network-manager-gnome and add there a new VPN configuration of type openconnect (and subtype Cisco or Juniper/Pulse etc.) (picture might be slightly different depending on installed versions) If for some reason you really want to access sources as shipped by Debian, you should first read there: https://wiki.debian.org/Packaging/SourcePackage . Package description above has a link to sources informations. Providing full informations on how to build with all caveats is out of scope.
How to build openconnect-gui? [closed]
1,567,237,870,000
after removing the default exfat-fuse package version 1.2.5 from my Debian Stretch system and replacing it with version 1.3.0, compiled from source, running mount using type exfat results to an unknown filesystem error. Checking with /proc/filesystems reveals that exfat is not listed. Manually mounting exfat drives with mount.exfat works fine, the executables reside in /usr/local/sbin. How can I configure mount to use mount.exfat when appropriate?
Install or symlink it as /sbin/mount.exfat. (I checked strace -f mount -t nosuchfs nowhere nowhere. It tries /sbin/mount.nosuchfs, /sbin/fs.d/mount.nosuchfs, and /sbin/fs/mount.nosuchfs only). What's the worst that could happen :). If you forget and try to apt install exfat-fuse again, it's either going to give you a nice error message to remind you, or overwrite it.
Configure mount to recognize self compiled fuse exfat
1,567,237,870,000
When compiling the kernel, if I choose Ethernet Gadget (with CDC Ethernet support) or Network Control Model (NCM) instead of the Android composite device, I get an error: drivers/built-in.o:coresight-tmc.c:function tmc_etr_store_out_mode: error: undefined reference to 'usb_qdss_close' drivers/built-in.o:coresight-tmc.c:function tmc_etr_store_out_mode: error: undefined reference to 'usb_qdss_open' drivers/built-in.o:coresight-tmc.c:function tmc_disable: error: undefined reference to 'usb_qdss_close' drivers/built-in.o:coresight-tmc.c:function tmc_enable: error: undefined reference to 'usb_qdss_open' drivers/built-in.o:coresight-tmc.c:function tmc_enable: error: undefined reference to 'usb_qdss_close' Makefile:878: recipe for target '.tmp_vmlinux1' failed make: *** [.tmp_vmlinux1] Error 1 Kernel version: 3.4.0 Toolchain: google arm-linux-androideabi-4.6
coresight-tmc.c seems to refer to Coresight Trace Memory Controller, which seems to be a kernel/hardware debugging tool on ARM architecture. You may have found an undeclared dependency in the kernel configuration: the Trace Memory Controller seems to depend on the Android composite device, but the kernel configurator is not aware of this fact and so allows you to choose a configuration that includes the Trace Memory Controller driver but not the Android composite device. Your options with the kernel version you're using are: keep the Android composite device in your kernel configuration to satisfy Coresight's dependency, or disable the CORESIGHT_* configuration items in your kernel configuration, and so give up Coresight support. Since the kernel version 3.4.0 is no longer in active development, there's probably no point in reporting the bug unless you can reproduce it with a newer kernel version: the oldest kernel version with active long-term upstream support is 3.16.60 at this time.
Android kernel compiling error
1,567,237,870,000
This is a follow up to my previous question regarding Building QuantLib on Amazon Linux. I followed the instructions in the answer posted by MLu: Download the source RPM (QuantLib-1.4-7.el7.src.rpm) Install rpmbuild Run rpmbuild --rebuild QuantLib-1.4-7.el7.src.rpm However the result was a series of QuantLib-(devel/doc/test)-1.4-7.el7.rpm rpms. I had hoped the result would be QuantLib-1.13.el7.src.rpm. Is it possible to modify the rebuild process to use the newest release of the library 1.13? The source code is available here https://github.com/lballabio/QuantLib
rpmbuild --rebuild QuantLib-1.4-7.el7.src.rpm will "just" extract the source package to ~/rpmbuild/{SPEC,SOURCES}/ and run rpmbuild -ba ~/rpmbuild/SPEC/QuantLib. Nothing else. You want to rebase to new version, which can be easy or tricky. Hard to say in advance. The easy version is that you rpm -Uvh QuantLib-1.4-7.el7.src.rpm cd ~/rpmbuild/SOURCE create tar.gz from the upstream git repository and put it to this directory. optionaly you can dele the old version which is in this directory. edit ~/rpmbuild/SPEC/QuantLib.spec and change Version, Release, Source0 and edit %changelog. run rpmbuild -ba ~/rpmbuild/SPEC/QuantLib.spec Sometimes this work. Usually for simple projects or for well maintained projects. Sometimes the last step fails with ... nearly anything. There is zilion options to fail. To fix that you should really know how packaging RPM works. The good start is to read https://rpm-packaging-guide.github.io/ Note that QuantLib maintain spec file in their github repository. This may help you. And once you build the package, you can make world better and build it in https://copr.fedorainfracloud.org where others can easily find it and use it.
Rebuild from src.rpm using new version
1,567,237,870,000
I'm trying to compile a very basic magic file with the command: $ file -C -m foo I get this error: foo, 1: Warning: type `' invalid foo, 2: Warning: offset `search' invalid foo, 3: Warning: type `' invalid foo, 4: Warning: offset `Itis42file' invalid My file looks like this: 42 search 42 Itis42file I have followed the man magic and it doesn't work.
The format of the magic file is described in the magic(5) manual on your system (man 5 magic). On an Ubuntu system I have access to (as well as on my OpenBSD system), the format is described as a collection of lines with the following fields: offset type test message I'm guessing that your file should therefore not contain four lines, but one: 42 search 42 Itis42file This does indeed work on OpenBSD: $ cat ~/.magic 42 search 42 Itis42file $ cat file.txt 42 hello $ file file.txt file.txt: Itis42file
When trying to compile magic file : Warning: type `' invalid and Warning: offset `search' invalid
1,567,237,870,000
Hi i have a problem in linux terminal line. So i tried compiling a file to .o like this gcc -c palindrome.c and the error is palindrome.c:2:21: fatal error: reverse.h: No such file or directory compilation terminated. The file reverse.h indeed is in the directory because i copied everything from lab2 directory to lab 3. So why is it saying that? Thanks for the help cscstuff@ubuntu:~/inlab2$ ls -l total 32 -rwxrwxr-x 1 cscstuff cscstuff 8784 Oct 1 08:26 main1 -rw-rw-r-- 1 cscstuff cscstuff 338 Oct 1 08:20 main1.c -rw-rw-r-- 1 cscstuff cscstuff 1888 Oct 1 08:24 main1.o -rw-rw-r-- 1 cscstuff cscstuff 204 Oct 1 08:26 reverse.c -rw-rw-r-- 1 cscstuff cscstuff 84 Oct 1 08:19 reverse.h -rw-rw-r-- 1 cscstuff cscstuff 1472 Oct 1 08:26 reverse.o cscstuff@ubuntu:~/inlab2$ cd cscstuff@ubuntu:~$ cd inlab3 cscstuff@ubuntu:~/inlab3$ ls -l total 16 drwxrwxr-x 2 cscstuff cscstuff 4096 Oct 1 08:33 inlab2 -rw-rw-r-- 1 cscstuff cscstuff 247 Oct 1 09:21 main2.c -rw-rw-r-- 1 cscstuff cscstuff 297 Oct 15 11:01 palindrome.c -rw-rw-r-- 1 cscstuff cscstuff 51 Oct 1 08:34 palindrome.h cscstuff@ubuntu:~/inlab3$ gcc -c palindrome.c palindrome.c:2:21: fatal error: reverse.h: No such file or directory compilation terminated. cscstuff@ubuntu:~/inlab3$
From inlab3 either add -I../inlab2 to compiler (e.g. gcc -I../inlab2 -c palindrome.c, this will tell gcc to look in ../inlab2 for the header file) use #include "../inlab2/reverse.h" in include line (this will give relative path for the header file) copy from inlab2 cp ../inlab2/reverse.h . (this will make a copy of the header file available in inlab3)
fatal error no such file or directory [closed]
1,567,237,870,000
I built OpenCV library from source on Raspberry Pi 3 and I don't want to repeat same, time consuming task on my other Raspberry Pis. Is there any way to generate binary or deb files of the built opencv library so that I can copy them and install using dpkg or apt ? As you might know, make for opencv takes forever (approx 4 hours using make -j2. So having a binary will save lots of time.
If those are libraries you can build with the classical ./configure make make install you can install checkinstall: apt-get install checkinstall and simply change the last step to: ./configure make checkinstall Answer the questions and have your debian package. Please note that checkinstall will not free you from caring about dependencies, so if you are lazy, the packages will work on other identical systems, but will also install without warning on systems with missing dependencies. You remain responsible for informing checkinstall about that!
How to make a binary or .deb from application built from source?
1,567,237,870,000
I am trying to compile software that was meant for windows from source. The software I am specifically trying to compile is an application called Keeperfx for Dungeon Keeper. I enjoy that game so I thought I could compile its source on linux and see if it works. However, I am not having so much luck. Doing the make command only gives this output: mkdir -p obj/std Building file: src/main.cpp g++ -I"directx/include" -I"sdl/include" -I"libav/include" -c -fmessage-length=0 -Wall -Wno-sign-compare -Wno-unused-parameter -Wno-strict-aliasing -Wno-unknown-pragmas -MMD -MP -MF"obj/std/main.d" -MT"obj/std/main.d" -march=i686 -fno-omit-frame-pointer -O3 -DBFDEBUG_LEVEL=0 -o"obj/std/main.o" "src/main.cpp" src/main.cpp:1:0: error: CPU you selected does not support x86-64 instruction set #pragma region includes ^ src/main.cpp:1:0: error: CPU you selected does not support x86-64 instruction set Makefile:658: recipe for target 'obj/std/main.o' failed make: *** [obj/std/main.o] Error 1 So I thought I would use mingw. But I keep getting errors. ../src/bflib_crash.c: In function ‘sigstr’: ../src/bflib_crash.c:77:10: error: ‘SIGBREAK’ undeclared (first use in this function) case SIGBREAK : return "Ctrl-Break (Win32)"; ^ ../src/bflib_crash.c:77:10: note: each undeclared identifier is reported only once for each function it appears in ../src/bflib_crash.c: In function ‘LbErrorParachuteInstall’: ../src/bflib_crash.c:189:12: error: ‘SIGBREAK’ undeclared (first use in this function) signal(SIGBREAK,ctrl_handler); ^ In file included from ../src/bflib_dernc.c:26:0: /usr/include/fcntl.h:202:12: error: conflicting types for ‘creat’ extern int creat (const char *__file, mode_t __mode) __nonnull ((1)); ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:314:15: note: previous declaration of ‘creat’ was here int __cdecl creat(const char *_Filename,int _PermissionMode) __MINGW_ATTRIB_D ^ In file included from ../src/bflib_dernc.c:27:0: /usr/include/sys/stat.h:283:12: error: conflicting types for ‘chmod’ extern int chmod (const char *__file, __mode_t __mode) ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:311:15: note: previous declaration of ‘chmod’ was here int __cdecl chmod(const char *_Filename,int _AccessMode) __MINGW_ATTRIB_DEPRE ^ In file included from ../src/bflib_dernc.c:27:0: /usr/include/sys/stat.h:311:17: error: conflicting types for ‘umask’ extern __mode_t umask (__mode_t __mask) __THROW; ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:328:15: note: previous declaration of ‘umask’ was here int __cdecl umask(int _Mode) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ In file included from ../src/bflib_dernc.c:27:0: /usr/include/sys/stat.h:320:12: error: conflicting types for ‘mkdir’ extern int mkdir (const char *__path, __mode_t __mode) ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:267:15: note: previous declaration of ‘mkdir’ was here int __cdecl mkdir (const char *) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ In file included from ../src/bflib_fileio.c:28:0: /usr/include/fcntl.h:202:12: error: conflicting types for ‘creat’ extern int creat (const char *__file, mode_t __mode) __nonnull ((1)); ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:314:15: note: previous declaration of ‘creat’ was here int __cdecl creat(const char *_Filename,int _PermissionMode) __MINGW_ATTRIB_D ^ In file included from ../src/bflib_fileio.c:29:0: /usr/include/sys/stat.h:283:12: error: conflicting types for ‘chmod’ extern int chmod (const char *__file, __mode_t __mode) ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:311:15: note: previous declaration of ‘chmod’ was here int __cdecl chmod(const char *_Filename,int _AccessMode) __MINGW_ATTRIB_DEPRE ^ In file included from ../src/bflib_fileio.c:29:0: /usr/include/sys/stat.h:311:17: error: conflicting types for ‘umask’ extern __mode_t umask (__mode_t __mask) __THROW; ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:328:15: note: previous declaration of ‘umask’ was here int __cdecl umask(int _Mode) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ In file included from ../src/bflib_fileio.c:29:0: /usr/include/sys/stat.h:320:12: error: conflicting types for ‘mkdir’ extern int mkdir (const char *__path, __mode_t __mode) ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:267:15: note: previous declaration of ‘mkdir’ was here int __cdecl mkdir (const char *) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ ../src/bflib_fileio.c: In function ‘LbFileOpen’: ../src/bflib_fileio.c:237:43: error: ‘O_BINARY’ undeclared (first use in this function) rc = _sopen(fname, O_RDWR|O_CREAT|O_BINARY, SH_DENYNO, S_IREAD|S_IWRITE ^ ../src/bflib_fileio.c:237:43: note: each undeclared identifier is reported only once for each function it appears in In file included from /usr/include/bits/errno.h:24:0, from /usr/include/errno.h:35, from /usr/share/mingw-w64/include/intrin.h:65, from /usr/include/SDL2/SDL_cpuinfo.h:44, from /usr/include/SDL2/SDL.h:38, from ../src/bflib_keybrd.c:25: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory compilation terminated. ../src/bflib_math.c: In function ‘LbRandomSeries’: ../src/bflib_math.c:746:11: warning: implicit declaration of function ‘_lrotr’ [-Wimplicit-function-declaration] *seed = _lrotr(i, 13); ^ ../src/bflib_tcpsp.c:26:26: fatal error: SDL2/SDL_net.h: No such file or directory #include <SDL2/SDL_net.h> ^ compilation terminated. In file included from /usr/include/bits/errno.h:24:0, from /usr/include/errno.h:35, from /usr/share/mingw-w64/include/intrin.h:65, from /usr/include/SDL2/SDL_cpuinfo.h:44, from /usr/include/SDL2/SDL.h:38, from ../src/bflib_video.c:27: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory compilation terminated. In file included from /usr/include/bits/errno.h:24:0, from /usr/include/errno.h:35, from /usr/share/mingw-w64/include/intrin.h:65, from /usr/include/SDL2/SDL_cpuinfo.h:44, from /usr/include/SDL2/SDL.h:38, from ../src/bflib_vidsurface.c:25: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory compilation terminated. ../src/config.c: In function ‘recognize_conf_command’: ../src/config.c:275:13: warning: implicit declaration of function ‘strnicmp’ [-Wimplicit-function-declaration] if (strnicmp(buf+(*pos), commands[i].name, cmdname_len) == 0) ^ ../src/config.c: In function ‘get_language_lwrstr’: ../src/config.c:424:3: warning: implicit declaration of function ‘strlwr’ [-Wimplicit-function-declaration] strlwr(lang_str); ^ ../src/front_network.c: In function ‘net_write_config_file’: ../src/front_network.c:503:9: warning: implicit declaration of function ‘strupr’ [-Wimplicit-function-declaration] strupr(net_config_info.str_atz); ^ ../src/lvl_filesdk1.c: In function ‘get_level_number_from_file_name’: ../src/lvl_filesdk1.c:108:7: warning: implicit declaration of function ‘strnicmp’ [-Wimplicit-function-declaration] if (strnicmp(fname,"map",3) != 0) ^ ../src/lvl_script.c: In function ‘get_next_word’: ../src/lvl_script.c:446:9: warning: implicit declaration of function ‘strupr’ [-Wimplicit-function-declaration] strupr(param); ^ ../src/lvl_script.c: In function ‘get_map_location_code_name’: ../src/lvl_script.c:792:9: warning: implicit declaration of function ‘itoa’ [-Wimplicit-function-declaration] itoa(apt->num, name, 10); ^ nicholas@LinuxNick ~/.apps/keeperfx/bin $ sudo i686-w64-mingw32-gcc-win32 -I/usr/include -L/usr/local/lib -liconv ../src/*.c -o keeperfx/ [sudo] password for nicholas: ../src/bflib_crash.c: In function ‘sigstr’: ../src/bflib_crash.c:77:10: error: ‘SIGBREAK’ undeclared (first use in this function) case SIGBREAK : return "Ctrl-Break (Win32)"; ^ ../src/bflib_crash.c:77:10: note: each undeclared identifier is reported only once for each function it appears in ../src/bflib_crash.c: In function ‘LbErrorParachuteInstall’: ../src/bflib_crash.c:189:12: error: ‘SIGBREAK’ undeclared (first use in this function) signal(SIGBREAK,ctrl_handler); ^ In file included from ../src/bflib_dernc.c:26:0: /usr/include/fcntl.h:202:12: error: conflicting types for ‘creat’ extern int creat (const char *__file, mode_t __mode) __nonnull ((1)); ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:314:15: note: previous declaration of ‘creat’ was here int __cdecl creat(const char *_Filename,int _PermissionMode) __MINGW_ATTRIB_D ^ In file included from ../src/bflib_dernc.c:27:0: /usr/include/sys/stat.h:283:12: error: conflicting types for ‘chmod’ extern int chmod (const char *__file, __mode_t __mode) ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:311:15: note: previous declaration of ‘chmod’ was here int __cdecl chmod(const char *_Filename,int _AccessMode) __MINGW_ATTRIB_DEPRE ^ In file included from ../src/bflib_dernc.c:27:0: /usr/include/sys/stat.h:311:17: error: conflicting types for ‘umask’ extern __mode_t umask (__mode_t __mask) __THROW; ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:328:15: note: previous declaration of ‘umask’ was here int __cdecl umask(int _Mode) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ In file included from ../src/bflib_dernc.c:27:0: /usr/include/sys/stat.h:320:12: error: conflicting types for ‘mkdir’ extern int mkdir (const char *__path, __mode_t __mode) ^ In file included from ../src/bflib_dernc.c:25:0: /usr/share/mingw-w64/include/io.h:267:15: note: previous declaration of ‘mkdir’ was here int __cdecl mkdir (const char *) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ In file included from ../src/bflib_fileio.c:28:0: /usr/include/fcntl.h:202:12: error: conflicting types for ‘creat’ extern int creat (const char *__file, mode_t __mode) __nonnull ((1)); ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:314:15: note: previous declaration of ‘creat’ was here int __cdecl creat(const char *_Filename,int _PermissionMode) __MINGW_ATTRIB_D ^ In file included from ../src/bflib_fileio.c:29:0: /usr/include/sys/stat.h:283:12: error: conflicting types for ‘chmod’ extern int chmod (const char *__file, __mode_t __mode) ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:311:15: note: previous declaration of ‘chmod’ was here int __cdecl chmod(const char *_Filename,int _AccessMode) __MINGW_ATTRIB_DEPRE ^ In file included from ../src/bflib_fileio.c:29:0: /usr/include/sys/stat.h:311:17: error: conflicting types for ‘umask’ extern __mode_t umask (__mode_t __mask) __THROW; ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:328:15: note: previous declaration of ‘umask’ was here int __cdecl umask(int _Mode) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ In file included from ../src/bflib_fileio.c:29:0: /usr/include/sys/stat.h:320:12: error: conflicting types for ‘mkdir’ extern int mkdir (const char *__path, __mode_t __mode) ^ In file included from ../src/bflib_basics.h:23:0, from ../src/bflib_fileio.h:23, from ../src/bflib_fileio.c:22: /usr/share/mingw-w64/include/io.h:267:15: note: previous declaration of ‘mkdir’ was here int __cdecl mkdir (const char *) __MINGW_ATTRIB_DEPRECATED_MSVC2005; ^ ../src/bflib_fileio.c: In function ‘LbFileOpen’: ../src/bflib_fileio.c:237:43: error: ‘O_BINARY’ undeclared (first use in this function) rc = _sopen(fname, O_RDWR|O_CREAT|O_BINARY, SH_DENYNO, S_IREAD|S_IWRITE ^ ../src/bflib_fileio.c:237:43: note: each undeclared identifier is reported only once for each function it appears in In file included from /usr/include/bits/errno.h:24:0, from /usr/include/errno.h:35, from /usr/share/mingw-w64/include/intrin.h:65, from /usr/include/SDL2/SDL_cpuinfo.h:44, from /usr/include/SDL2/SDL.h:38, from ../src/bflib_keybrd.c:25: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory compilation terminated. ../src/bflib_math.c: In function ‘LbRandomSeries’: ../src/bflib_math.c:746:11: warning: implicit declaration of function ‘_lrotr’ [-Wimplicit-function-declaration] *seed = _lrotr(i, 13); ^ ../src/bflib_tcpsp.c:26:26: fatal error: SDL2/SDL_net.h: No such file or directory #include <SDL2/SDL_net.h> ^ compilation terminated. In file included from /usr/include/bits/errno.h:24:0, from /usr/include/errno.h:35, from /usr/share/mingw-w64/include/intrin.h:65, from /usr/include/SDL2/SDL_cpuinfo.h:44, from /usr/include/SDL2/SDL.h:38, from ../src/bflib_video.c:27: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory compilation terminated. In file included from /usr/include/bits/errno.h:24:0, from /usr/include/errno.h:35, from /usr/share/mingw-w64/include/intrin.h:65, from /usr/include/SDL2/SDL_cpuinfo.h:44, from /usr/include/SDL2/SDL.h:38, from ../src/bflib_vidsurface.c:25: /usr/include/linux/errno.h:1:23: fatal error: asm/errno.h: No such file or directory compilation terminated. ../src/config.c: In function ‘recognize_conf_command’: ../src/config.c:275:13: warning: implicit declaration of function ‘strnicmp’ [-Wimplicit-function-declaration] if (strnicmp(buf+(*pos), commands[i].name, cmdname_len) == 0) ^ ../src/config.c: In function ‘get_language_lwrstr’: ../src/config.c:424:3: warning: implicit declaration of function ‘strlwr’ [-Wimplicit-function-declaration] strlwr(lang_str); ^ ../src/front_network.c: In function ‘net_write_config_file’: ../src/front_network.c:503:9: warning: implicit declaration of function ‘strupr’ [-Wimplicit-function-declaration] strupr(net_config_info.str_atz); ^ ../src/lvl_filesdk1.c: In function ‘get_level_number_from_file_name’: ../src/lvl_filesdk1.c:108:7: warning: implicit declaration of function ‘strnicmp’ [-Wimplicit-function-declaration] if (strnicmp(fname,"map",3) != 0) ^ ../src/lvl_script.c: In function ‘get_next_word’: ../src/lvl_script.c:446:9: warning: implicit declaration of function ‘strupr’ [-Wimplicit-function-declaration] strupr(param); ^ ../src/lvl_script.c: In function ‘get_map_location_code_name’: ../src/lvl_script.c:792:9: warning: implicit declaration of function ‘itoa’ [-Wimplicit-function-declaration] itoa(apt->num, name, 10); ^ I am using the command i686-w64-mingw32-gcc-win32 -I/usr/include -L/usr/local/lib -liconv ../src/*.c for compiling. However, even adding an output location, doesn't spit out an output file. I don't know what else to do here. My system runs 64-bit Linux Mint version 18.1 on Cinnamon.
The first set of errors happens because the source code is only intended for 32-bit targets. When building KeeperFX, you can force this (if your compiler is set up correctly) by running make CPP="g++ -m32" but then you run into missing headers — windows.h, winbase.h, io.h, basetyps.h when building src/main.cpp — which suggests that the code is written for Windows with no portability concerns. It’s not “pure C/C++”. KeeperFX does appear to support building with some versions of MinGW or MinGW-w64 at least, but as has been pointed out in the comments that only allows you to build a Windows binary on Linux. So you can build on Linux, using make CROSS_COMPILE=i686-w64-mingw32- and an appropriate cross-compiler, but the resulting binary will need Wine to run on Linux. (On Mint, the appropriate cross-compiler is g++-mingw-w64.) It might be possible to port KeeperFX to SDL without huge amounts of effort, I haven’t looked into it in detail.
Is it possible to cross-compile C++ source code, that was originally written for Microsoft's Windows to Gnu/linux?
1,567,237,870,000
I'm trying to build a simple application using Qt 5.7 on CentOS 7.3. But when I try to compile it, I get the following errors: cannot find -lGL collect2: error: ld returned 1 exit status The application code is irrelevant because any GUI application (Qt Widgets or QtQuick) gives the same errors. My graphics card is Intel HD4000 Graphics which comes with Intel i7-3610QM CPU. What can be the problem? How do I solve it? Thanks in advance.
-lGL means libGL.so. Finding the package providing libGL.so : yum provides */libGL.so Install the package(s) : # yum install mesa-libGL-devel mesa-libGLU-devel
ld cannot find -lGL on CentOS 7
1,567,237,870,000
I've followed this tutorial which shows how you can enable the GCC compiler on ChromeOS, which uses the following commands below. sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 2 sudo mount -i -o remount,exec /home/chronos/user/ export C_INCLUDE_PATH=~/Toolchain/usr/include/ export LD_LIBRARY_PATH=~/Toolchain/usr/lib:~/Toolchain/usr/lib/binutils/armv7a-hardfloat-linux-gnueabi/2.25.1/ export PATH=$PATH:~/Toolchain/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.9.3/:~/Toolchain/usr/armv7a-hardfloat-linux-gnueabi/binutils-bin/2.25.1/ sudo sed -i 's/\/usr/\/home\/chronos\/user\/Toolchain\/usr/g' ~/Toolchain/usr/lib/libc.so Once executed, I'm able to compile source files right up until my shell instance terminates. Once I return to the shell later, all attempts at source compilation via ./configure fail. I suspected that the exported variables become lost after the instance is terminated. I try implementing the same commands exactly as before, but the ability to compile seems irrevocably lost. The config.log stream presents the following error: configure:3378: checking whether the C compiler works configure:3400: gcc conftest.c >&5 /home/chronos/user/Toolchain/usr/armv7a-hardfloat-linux-gnueabi/binutils-bin/2.25.1/ld: cannot find /home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/usr/lib/libc_nonshared.a collect2: error: ld returned 1 exit status configure:3404: $? = 1 configure:3442: result: no Something really peculiar happens to the path... cannot find /home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/home/chronos/user/Toolchain/usr/lib/libc_nonshared.a I feel that I've exhausted my limited knowledge of Linux to resolve this issue. Is anyone able to provide some insight as to what's going on?
The problem is that when you repeatedly use sed in this way, you keep appending to the shared object file ~/Toolchain/usr/lib/libc.so. So after the first run, this corrupts the file path. If your path is corrupted, navigate to the file and manually change the contents of libc.so to the following: /* GNU ld script Use the shared library, but some functions are only in the static library, so try that secondarily. */ OUTPUT_FORMAT(elf32-littlearm) GROUP ( /lib/libc.so.6 /home/chronos/user/Toolchain/usr/lib/libc_nonshared.a AS_NEEDED ( /lib/ld-linux-armhf.so.3 ) ) Trouble is, when the shell has been closed, it's important that if you wish to keep compiling once you do return, you must re-run the export flags since these do get lost. You need to do this until you seek a more permanent solution which establishes the flags upon initialization of the shell, i.e. via ~/.bashrc.
Why does GCC stop working?
1,567,237,870,000
The commands I use to compile a Latex terminal is: $latex <file>.tex $dvips -Go -ta4 -Ppdf <file>.div $ps2pdf <file>.ps What I want to do is make an script that I will run like $./ltx <file>.tex and it will make all the commands listed above, changing the .tex extension to .div and .ps when necessary. How do I that and what do I have to study to know how to do this kind of stuff in the future?
I'll enter another Answer just to give some additional perspective for future efforts. Part of your Question says run like $./ltx <file>.tex ... which implies (via the ./ syntax) that the ltx script exists in your current directory. This is an artificial limitation, IMHO, as maybe next week you want to work on some different files in a different directory. Creating a shell script is one obvious solution to the problem -- you have multiple commands that you chain together all the time, and you don't want to type them every time you want to generate a new postscript file. jcoppens showed how to do this; as one of the commenters pointed out, you can put this shell script somewhere more central (~/bin?) and update your $PATH to include that directory so that you can then type ltx file.tex anywhere there's a file.tex and it'll do what you want. Another option is to create an alias. Aliases are limited, though, because the shell only expands them when they are the first word in your command, and don't have a way to refer back to the passed parameter multiple times (it just gets appended to your alias text). Yet another option is to create a function. Functions can be defined in your shell's startup files and so would not need any modification to your $PATH and could be executed from any directory you find yourself in. Here's a first draft of a function that does what you want: function ltx() { latex "$1" && \ dvips -Go -ta4 -Ppdf "${1%.tex}.div" && \ ps2pdf "${1%.tex}.ps" } I've made two major modifications and one minor tweak to your initial commands: at the ends of the lines, I've added && symbols that tell the shell: "only execute the next command if this previous one has returned successfully." This saves extra errors if you've specified a file.tex that doesn't exist, or if the latex command fails for some reason. The last character in the line, \, tells the shell that the following line should be considered part of the current line -- a continuation. It's not strictly necessary in this case, since the shell recognizes && as requiring another command to follow it. I like to include it in scripts that I write to make it more obvious that the intention is for these two (or more) lines to go together. I've also indented the subsequent lines to make it even more clear. I've changed file.tex to $1 in the first call, and used bash's parameter expansion in the following calls, in order to refer to the file.tex that you pass to the function and then to remove the .tex extension to add back in the .div or .ps extensions. I've also quoted the variable expansions so that you can name your file file with spaces.tex if you'd like, and the shell will preserve the filename across all of the commands. This first draft of the function will work, but I'll point out a couple extra steps that I would take: function ltx() { [ -r "$1" ] || return 1 [[ $1 =~ .tex$ ]] || return 2 echo latex "$1" && dvips -Go -ta4 -Ppdf "${1%.tex}.div" && ps2pdf "${1%.tex}.ps" } The first new additional line checks to see if the parameter you passed in actually exists and is readable. If it's not, the function will return without calling any other commands, with a return code of 1. You could change this test to output something else (That file does not exist, please try something else), or keep it out entirely, knowing then that the latex command will give you an error about a missing input file. The second additional line is bash-specific, and is checking to see that the parameter you passed in ends with the string .tex. I added this because the subsequent commands expect such a file, and the parameter expansion is attempting to remove such an extension, so if you call ltx somefile, the revised function will return an exit code of 2 and not call latex. The last part of your question is: what do I have to study to know how to do this kind of stuff in the future? I think you've started down the right road: you have a real-world problem that you think could be made better with a shell script (or somehow). You've come to an environment at U&L that has like-minded people with knowledge of these things. This site also has thousands of similar questions and answers that solve various people's specific problems. Study other answers to similar questions, such as the ones in shell-script, shell, and bash (as you tagged originally). Sort through the highest-rated ones, or the shortest ones, or the newest ones, and see if you can understand how they work. Copy interesting ones to a playground area on your system and experiment with them. Change them to see what happens! Look at the shells you might have available on your system (such as bash, zsh, ksh) and read through their man pages to see what features they offer. Experiment with those features until you understand them. While reading through the descriptions, think of other problems that you might be able to solve or improve upon.
Script to compile a Latex file
1,567,237,870,000
Following the steps on Samba wiki page, I was able to build the samba source code. However, after sudo make install, I could not start the samba service since there is no systemd entry under /usr/lib/systemd/ folder. Am I missing any steps? Thanks!
When compiling/installing from source, as with most software distributions like this, the service will not be installed. You need to do those steps manually (or with configuration management of some type). Here's an example that I find, specifically for Samba 4 on a systemd based Linux system. Translating from here: https://dev.tranquil.it/wiki/SAMBA_-_Fichier_systemd_samba4 Create the file /lib/systemd/system/samba.service with an editor containing the following: [Service] Type=forking PIDFile=/usr/local/samba/var/run/samba.pid LimitNOFILE=16384 EnvironmentFile=-/etc/conf.d/samba ExecStart=/usr/local/samba/sbin/samba ExecReload=/usr/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target Then run, as root: # systemctl enable samba # systemctl start samba If you have errors when starting, check the logs as indicated with" # journalctl -xe
Install samba4.4.4 from source on centos7
1,567,237,870,000
I wrote a simple module for the Linux Kernel and it has a stack buffer overflow vulnerability. I want to exploit the module, but I have to turn off the stack protector in the kernel first. How could I do this quickly and simply? Is it required to compile the kernel every time? Is there any other way to turn off stack protection in a module of the Linux Kernel (without compiling the kernel)?
Those options work by passing options to the compiler, so the most straightforward way is to recompile the kernel. However for a reproducible and module-specific way kbuild allows you to set custom CFLAGs on a per-module basis. https://www.kernel.org/doc/Documentation/kbuild/makefiles.txt You particularly want to set -fno-stack-protector for the modules you want to exploit. DKMS additionally allows you to set up automatic rebuild for out of tree drivers against arbitrary kernel versions.
How to turn off stack protector in linux kernel easily? [duplicate]
1,567,237,870,000
I have a shell script (build.sh) that ends by attempting to copy some files into a new directory. However it says: mkdir: cannot create directory ‘/files/ondisk/shared//comp/auto/bleeding-1169-b28d31a’: Permission denied when running the script. The command is: ( umask 000; mkdir -p "${BASE}/${TARGET}" ) || exit -1 ( umask 000; cp -r ${STORE} "${BASE}/${TARGET}" ) || exit -1 Does umask 000 not ensure that I am able to write to this location?
That double-slash in the pathname looks odd. Perhaps you have no permission to write the ${BASE}, which might be /files/ondisk/shared. The umask value is irrelevant, because it only affects the permissions of the directories and files which mkdir and cp create — not the permissions of the existing directory into which you are copying.
Shell script getting 'permission denied' despite using umask 000 before command
1,567,237,870,000
My linux cluster has installed ifort compiler now. But for some purpose, I need pgi compiler in the same computer. Can they coexist? I'm not familiar with this area, afraid of meeting trouble.
You'll be fine, using multiple compilers (Fortran or any other language) is pretty common, and their default installations shouldn't interfere with each other. Of course, anytime you're using multiple compilers for a language, you should organize your projects so that you remember which compiler you targeted. At a minimum, make a note in a README or INSTALL file, so that you and other users can easily compile your software in the future.
Can ifort and pgi complier coexist in the same system?
1,567,237,870,000
I'm trying to install kiwix on fedora 23 when I tried to compile kiwix sourcecode under my computer. and when I want to run make, it shows me this message! [ar.lnx@host kiwix-0.9] $ make make: *** No targets specified and no makefile found. Stop. Log NOTE: I follow the installation steps here [ar.lnx@host kiwix-0.9] $ ./autogen.sh configure.ac:45: installing './compile' configure.ac:38: installing './missing' src/components/contentManager/Makefile.am: installing './depcomp' [ar.lnx@host kiwix-0.9] $ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... no 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 for style of include used by make... GNU checking dependency style of gcc... gcc3 checking whether ln -s works... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking for g++... g++ checking for upx... 0 checking for cl.exe... no checking for Xcode... no checking for zip... zip 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... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /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 the maximum length of command line arguments... 1572864 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 object... ok checking for sysroot... no checking for a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc 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... yes checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... no checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for ranlib... (cached) ranlib checking whether make sets $(MAKE)... (cached) yes checking for pkg-config... pkg-config checking for perl... perl checking for java... java checking for javah... javah checking for jarsigner... jarsigner checking for stat64... yes Package libxul was not found in the pkg-config search path. Perhaps you should add the directory containing 'libxul.pc' to the PKG_CONFIG_PATH environment variable No package 'libxul' found configure: WARNING: unable to determine Gecko SDK version checking for Gecko version... 0 configure: WARNING: unable to find nsISupports.idl checking for xpidl... no checking for python... /usr/bin/python configure: WARNING: unable to find either the xpidl binary or the typelib.py or header.py scripts in '/home/ar.lnx/Documents/kiwix-0.9/src/dependencies/xulrunner-sdk/bin' directory. checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for zlibVersion in -lz... yes checking for xapian-config... no configure: error: cannot find xapian-config [ar.lnx@host kiwix-0.9] $ make make: *** No targets specified and no makefile found. Stop. [ar.lnx@host kiwix-0.9] $ could anybody help me solving this problem.
The error is right in the output. It says: configure: error: cannot find xapian-config So, you'll need that — and it looks like we have it packaged in Fedora... do sudo dnf install /usr/bin/xapian-config Then, rerun ./configure. You may have further problems; continue to resolve them in the same way (check for error messages saying something is missing, then add that thing) until it runs without error.
can not install, No targets specified and no makefile found. Error
1,567,237,870,000
I unpacked the .tar.gz file. I installed the gcc compiler. I ran the ./configure command with various flags and options. I ran make check and found an error. The exit status is 2. Only 0 is without errors. In the output I see this: /bin/ld: cannot find -lcap collect2: error: ld returned 1 exit status make[6]: *** [test-crypto] Error 1 The ld utility is installed. I don't know what "-lcap" is. I found one website that seemed to have lcap packages. But the links were broken for Centos version 7. If you post a place where I can download lcap (which is not installed on my CentOS 7 server), please confirm the link isn't broken. How do I fix this error so I can use the make install command to get NTP installed?
I don't know what "-lcap" is The -l flag to the GCC C compiler tells it to link in a library, in this case called cap, which is an abbreviated version of the library name. The full name is libcap.so.2.22 on CentOS 7, with the alias libcap.so.2. Chasing such details down is not your problem; leave it to the linker. What does matter here is that you're missing the development package, which installs libcap.so, without the version number, which is what GCC's linker is looking for. It also installs a bunch more files which may also be necessary. So: $ sudo yum install libcap-devel That is a common pattern: to build programs using libfoo, you typically need to install libfoo-devel first.
How do I install NTP from source on CentOS v7? (/bin/ld: cannot find -lcap)
1,567,237,870,000
I'm attempting compile BFLT Utils (https://github.com/nihilus/bflt-utils), but keep getting the following error: $:/tmp/bflt-utils/flthdr# make gcc -Wall -g -O2 compress.c -c gcc -Wall -g -O2 stubs.c -c gcc -Wall -g -O2 flthdr.c -c flthdr.c:22:23: fatal error: libiberty.h: No such file or directory #include <libiberty.h> ^ compilation terminated. Makefile:16: recipe for target 'flthdr.o' failed make: *** [flthdr.o] Error 1 I have installed libiberty-dev using apt-get install libiberty-dev. And using find / -name libiberty.* yields: /usr/include/libiberty/libiberty.h I have attempted to modify the Makefile to add the path using: CC=gcc CFLAGS=-Wall -g -O2 -L/usr/include/libiberty LDFLAGS=-lz -lc -lbfd -liberty TARGET=flthdr $(TARGET): compress.o stubs.o flthdr.o $(CC) $(CFLAGS) -o $(TARGET) *.o $(LDFLAGS) compress.o: $(CC) $(CFLAGS) compress.c -c stubs.o: $(CC) $(CFLAGS) stubs.c -c flthdr.o: $(CC) $(CFLAGS) flthdr.c -c clean: rm -f *.o $(TARGET) But I still get the same error. Why is the header file not being found?
Mark's comment above is correct: Your CFLAGS addition should use -I, not -L. The -L flag to the compiler tells it where to find libraries, but you're failing to find a header file instead. (Yes, the header file is called libiberty.h, but that doesn't make it a library.) Generally you use -L flags in makefiles in LDFLAGS and related variables. (I've reported this issue to the project, so hopefully it won't bite anyone else, once fixed. Maybe you will provide a patch or pull request, Torra.)
Having trouble compiling BFLT Utils: can't find libiberty.h, despite being installed
1,567,237,870,000
I tried to compile GNU Freedink as described in the BUILD file but when I try to configure it couldn't find SDL2. Log: http://pastebin.com/GYHHa4T0
To install the build-dependencies: apt-get build-dep freedink That will ensure all the files required to build Freedink are available, but with SDL 1.2 only. To use SDL2: apt-get install libsdl2-dev libsdl2-image-dev libsdl-ttf2.0-dev libsdl2-mixer-dev If you just want to be able to play Freedink, it's in Debian already: apt-get install freedink If you're trying to build the current development version (from the git repository for example), you'll need to build the current development versions of the various SDL dependencies; Freedink expects newer versions than have been released. The BUILD file lists the bug fixes needed on top of the current releases. You could try modifying configure.ac so the versions aren't compared strictly; line 140: PKG_CHECK_MODULES([SDL2], [sdl2 >= 2.0 SDL2_image >= 2.0.0 SDL2_mixer >= 2.0.0 SDL2_ttf >= 2.0.12 SDL2_gfx >= 1.0.0], but you'll come across the bugs mentioned in the BUILD file...
Compile freedink couldn't find SDL2
1,567,237,870,000
When I run make-kpkg --initrd buildpackage with concurrency_level set to 17, all cores are at 100% according to gnome-system-monitor, when running the cc1-jobs. When I run fakeroot make-kpkg --initrd buildpackage with concurrency_level set to 17 as well, the cores stay at around 40-60%. What am I doing wrong? Do I have to use fakeroot-ng? p.s.: The xsltproc-jobs take 100%, btw. I am confused.
make-kpkg --rootcmd fakeroot --initrd kernel_image kernel_headers kernel_source kernel_manual kernel_debug is the way to go. I don't know why make-kpkg --rootcmd fakeroot --initrd buildpackage has problems.
fakeroot make-kpkg buildpackage
1,567,237,870,000
I've inherited some Centos servers (6.2) that I want to get up to date, we have one dev machine. I'm starting off on the dev machine going through updates with security amendments, and applying ones that look most critical first (feel free to shout if there's any recommended sites or processes to follow relating to this). Most look straightforward, but then there's kernel packages and glibc ones. We have quite a lot of custom compiled software. If we updated packages like the kernel and glibc ones, would the custom compiled software (things like apache, perl) carry on to work as is, or would they need to be recompiled again ? I'm assuming things like kernel package updates would need a reboot ?
Minor versions like 6.2, 6.3 etc. are designed to be compatible after update (i.e. as long as 6.2 stays 6.2, and upgrades are made within it). Most importantly, kernel major and minor versions as well as glibc major and minor versions will stay the same. Any updates to these will not mean you need to re-compile applications. You would need to re-compile kernel modules and such if you had them, after a kernel upgrade. Most people do not compile their own kernel modules. If you upgrade from 6.2 to 6.6, however, it may mean trouble. Since it is very easy to do backups it may be worth switching one system, doing tests, then be able to switch back.
Safely updating packages on Centos and custom compiled applications
1,567,237,870,000
Is there an automatic way to understand the order in which individual libraries of the X11R7.7 package should be built when I want to build all of util, lib and xcb?
Either in the order listed in the X.Org build.sh script or by figuring out the dependency tree in the X.Org jhbuild modules file. Note that X11R7.7 is nearly three years old now, and many of the modules have had newer versions, with security fixes, released since then, in the X.Org individual releases archive.
build X11R7.7 from sources - in which order
1,421,228,458,000
I executed the minimal building directions of xcape: $ sudo apt-get install git gcc make pkg-config libx11-dev libxtst-dev libxi-dev $ mkdir xcape $ cd xcape $ git clone https://github.com/alols/xcape.git . $ make But when I press xcape it says xcape: command not found. It errors even when I'm in the xcape folder with a program that seems to be called xcape inside it. Why is this?
Have you tried ./xcape ? You have to execute it this way, because the location is probably not defined in the $PATH variable.
Installing Xcape (question involving the "make" command)
1,421,228,458,000
I'm trying to build a custom kernel from a git repository on my Ubuntu virtual machine. I run the make command as follows : sudo apt-get install vim libncurses5-dev gcc make git exuberant-ctags mkdir -p git/kernels; cd git/kernels git clone -b staging-next git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git cd staging cp /boot/config-`uname -r`* .config make olddefconfig make menuconfig make The build process ends with the following error. drivers/staging/media/cxd2099/cxd2099.c: In function ‘slot_reset’: drivers/staging/media/cxd2099/cxd2099.c:537:4: error: expected ‘;’ before ‘if’ make[4]: [drivers/staging/media/cxd2099/cxd2099.o] Error 1 make[3]: [drivers/staging/media/cxd2099] Error 2 make[2]: [drivers/staging/media] Error 2 make[1]: [drivers/staging] Error 2 make: [drivers] Error 2 How should I repair this error?
staging-next is, as of right now, currently broken, specifically f823182bc289 of staging-next is broken. If you really want to use staging-next, check out fcf1b73d08cd, which is near the top and does compile.
Compilation error when building a custom kernel
1,421,228,458,000
I'm a starting security/Linux student and I'm having headache-problems getting my wireless to work on Kali Linux. Recently I've bought a new laptop, to be specific the: Lenovo IdeaPad Z50-70-01418NL It comes with the wireless card: Realtek RTL8723BE Wireless LAN 802.11n PCI-E Lenovo only supports Windows, so I went searching for possibilities to get my wireless to work (After all, I've bought a laptop for a reason) I Really have googled everything, and because of that I'm losing track of what is relevant and what is not, what is the right way and what isn't. The https://github.com/lwfinger/rtl8723be shows the following line: "Code for new variety of the 8723 PCI cards - temp until code added to kernel" So I assume that I must compile the driver and ultimately install the driver into my system as following: command 'make' to compile the driver get the driver in the right place Profit! I try to 'make' the "rtl8723be" code but whatever I try it keeps giving me build errors. Since I have been trying almost anything in the hope it will work there is a long history of errors, but mostly the errors point at the line of: $(MAKE) -C $(KSRC) M=$(PWD) modules Ultimately I want to get my rtl8723be driver to work. If I use ndiswrapper -i <.inf-file>' It seems that ndiswrapper installs the .inf file and ndiswrapper -l is showing the driver. But I've red that you must use modprobe ndiswrapper This results in: FATAL: Module ndiswrapper not found ~~~~~~~~~~ EDIT ~~~~~~~~~~~~ So I have reinstalled the OS. (First tried to install kernel 3.15 but still no wifi adapter) Installed the needed kernel-headers. And I downloaded the new "rtl8723be" from https://github.com/lwfinger/rtlwifi_new (The new version fixes the bug in trx.c = Fix version number for _ieee80211_is_robust_mgmt_frame) When I try to use 'make' this results in the following: root@Kratos:~/rtlwifi_new/rtl8723be# make make -C /lib/modules/3.14-kali1-amd64/build M=/root/rtlwifi_new/rtl8723be modules make[1]: Entering directory `/usr/src/linux-headers-3.14-kali1-amd64' CC [M] /root/rtlwifi_new/rtl8723be/dm.o CC [M] /root/rtlwifi_new/rtl8723be/fw.o CC [M] /root/rtlwifi_new/rtl8723be/hw.o CC [M] /root/rtlwifi_new/rtl8723be/led.o CC [M] /root/rtlwifi_new/rtl8723be/phy.o CC [M] /root/rtlwifi_new/rtl8723be/pwrseq.o CC [M] /root/rtlwifi_new/rtl8723be/pwrseqcmd.o CC [M] /root/rtlwifi_new/rtl8723be/rf.o CC [M] /root/rtlwifi_new/rtl8723be/sw.o CC [M] /root/rtlwifi_new/rtl8723be/table.o CC [M] /root/rtlwifi_new/rtl8723be/trx.o LD [M] /root/rtlwifi_new/rtl8723be/rtl8723be.o Building modules, stage 2. MODPOST 1 modules WARNING: "rtl_btc_get_ops_pointer" [/root/rtlwifi_new/rtl8723be/rtl8723be.ko] undefined! CC /root/rtlwifi_new/rtl8723be/rtl8723be.mod.o LD [M] /root/rtlwifi_new/rtl8723be/rtl8723be.ko make[1]: Leaving directory `/usr/src/linux-headers-3.14-kali1-amd64' So what does this error mean? WARNING: "rtl_btc_get_ops_pointer" [/root/rtlwifi_new/rtl8723be I Have the feeling I'm almost there. I Even tried to copy both the driver and firmware to the following folders: /lib/modules/3.14-kali1-amd64/kernel/drivers/net/wireless/rtlwifi/rtl8723be/rtl8723be.ko /lib/firmware/rtlwifi/rtl8723befw.bin
For the rtl8723be drivers, just update the kernel. Click here and follow all steps: https://forums.kali.org/showthread.php?22638-rtl8723be-wireless-driver-installation&p=37193&viewfull=1#post37193
Unable to 'make' anything.. Kernel-headers problem? Trying to get my RTL8723BE working
1,421,228,458,000
When installing a library with configure, make and make install, does make install copy <libraryname>.pc to some place? If yes: Where is it? If no: Should we copy it somewhere rather than leave them where they are? I am asking that, because on an old notebook of mine, I saw: add the directory containing libraryname.pc to the PKG_CONFIG_PATH environment variable, so that pkg-config --clags libraryname and pkg-config --libs libraryname can find them. Will dpkg -l be able to track the installed library depending on whether it's path was added to PKG_CONFIG_PATH? Once I copy <libraryname>.pc to some place, will dpkg -l be able to track the installed packages?
In general, ./configure && make && make install without any parameters sticks everything under /usr/local, which would place foo.pc in /usr/local/lib/pkgconfig/foo.pc To make use of this, you'd need to do basically PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:${PKG_CONFIG_PATH} pkg-config --cflags foo, or, compile in this manner: ./configure --prefix=/usr #places built binaries under /usr instead of /usr/local make make install Now the foo.pc file will be where its expected. Note: This places stuff in system folders, so realize you can overwrite important things if you're not careful. And to answer regarding the dpkg question, no. Package managers can only track files installed by them. Now, if you're feeling adventureous, you can write up the files needed to wrap the standard ./configure && make && make install buils process to produce a dpkg installable deb package, which would be tracked :) Its been some time since I last made a debian package, a few years, and to be honest I rather hated the process, so don't expect info from me on that front. I've since switched to archlinux and writing PKGBUILDs (scripts that build arch packages using makepkg) is quite a simple task :)
Where is <libraryname>.pc?
1,421,228,458,000
According to FreeBSD, from version 10 they use Clang/LLVM instead of gcc. on the surface of it all things should perform as been before even better. but I have faced this reality more than I want to. Some codes can't be compiled this way. For example I tried to compile Snapwm. First native FreeBSD make is actually pmake and that is out of the question. So gmake is our choice. but issuing gmake on the code will produce this error: gcc -g -std=c99 -pedantic -Wall -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -c -o snapwm.o snapwm.c gmake: gcc: Command not found gmake: *** [snapwm.o] Error 127 So the question becomes how to compile the code that suffers from these set backs.
Sometimes needs some patch. I've createad which you can apply and can build with gmake. I didn't try the compiled snapwm I've tested only building process. diff -ur Nextwm-master.orig/Makefile Nextwm-master/Makefile --- Nextwm-master.orig/Makefile 2014-03-12 19:46:34.000000000 +0100 +++ Nextwm-master/Makefile 2014-04-16 13:07:08.000000000 +0200 @@ -1,12 +1,12 @@ -CFLAGS+= -g -std=c99 -pedantic -Wall -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 +CFLAGS+= -g -std=c99 -pedantic -Wall -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -I/usr/local/include/ LDADD+= -lX11 -lXinerama -LDFLAGS= -Wl,-O1,--sort-common,--as-needed,-z,relro +LDFLAGS= -Wl,-O1,--sort-common,--as-needed,-z,relro,-L/usr/local/lib EXEC=snapwm PREFIX?= /usr/local BINDIR?= $(PREFIX)/bin -CC=gcc +CC=clang all: $(EXEC) diff -ur Nextwm-master.orig/snapwm.c Nextwm-master/snapwm.c --- Nextwm-master.orig/snapwm.c 2014-03-12 19:46:34.000000000 +0100 +++ Nextwm-master/snapwm.c 2014-04-16 13:03:24.000000000 +0200 @@ -27,6 +27,7 @@ //#include <X11/keysym.h> /* For a multimedia keyboard */ #include <X11/XF86keysym.h> +#include <sys/signal.h> #include <X11/Xproto.h> #include <X11/Xutil.h> #include <X11/Xatom.h>
Building Snapwm on FreeBSD (Problem of gcc and clang)?
1,421,228,458,000
I have on my Arch linux system, php compiled with --enable-calendar=shared, what does that mean? I couldn't find any relevant information on that topic on the web. Problem is, that I have to recompile it with --enable-calendar flag, for some application to work, should I remove =shared, as it is not working right now, complaining that I don't have that extension installed?
PHP extensions can be compiled statically or shared. Static compilation puts the extension directly into PHP (therefore it does not need to be loaded and cannot be unloaded). When using shared compilation --enable-calendar=shared that will create file calendar.so. You can enable or disable it by editing php.ini.
php --enable-calendar=shared
1,421,228,458,000
I want to compile bash 4.2 from source. but http://ftp.gnu.org/gnu/bash/bash-4.2.tar.gz is more 2 years old. Should i apply all the patches from http://ftp.gnu.org/gnu/bash/bash-4.2-patches?
You can checkout the source with git and then compile: git clone git://git.sv.gnu.org/bash.git cd bash ./configure --prefix=/usr make sudo make install that should get you bash version 4.2.45 (ie 4.2 including patch 45) cvs would be faster but the repository for bash is empty for some reason. git clones the whole history 173Mb, with 27Mb real source.
compiling bash 4.2 with patches
1,421,228,458,000
I have SerNet Samba 4.0.9 installed on CentOS 6.4. How can I tell if it was compiled with CUPS support?
The docs, which say they're valid for Samba 3 and 4, say: "...make sure, that your smbd is compiled with CUPS support:" # smbd -b | grep CUPS HAVE_CUPS_CUPS_H HAVE_CUPS_LANGUAGE_H HAVE_CUPS HAVE_LIBCUPS
Does SerNet compile Samba 4 with CUPS support? (How to tell in general?)
1,421,228,458,000
I see that I can get the latest stable Rekonq through http://sourceforge.net/projects/rekonq/, but I want to get the latest developmental-version/daily-build. Where can I obtain the developmental source code?
Looks like you can get it here: $ git clone git://anongit.kde.org/rekonq Page on installing and compiling it is here: https://techbase.kde.org/Projects/rekonq/Compiling_rekonq
Get latest Rekonq developmental source code
1,421,228,458,000
I have built cairo-1.7.6 for use in building pango-1.32.6, and I have installed it to a directory in my home directory: /home/me/local/cairo-1.7.6. Under this directory are the expected include, lib and share directories. However, I don't seem to be able to get the pango ./configure to suck in the cairo dependency from that directory. I have tried setting the CPPFLAGS and LDFLAGS to the relevant directories, and I have looking in ./configure --help but none of the options seem obviously related. Is there a general way to pass a locally installed library's paths to a configure script?
You could try setting LD_LIBRARY_PATH to /home/me/local/cairo-1.7.6/lib then try ./configure --prefix=/home/me/local/pango-1.32.6
Specifying local install directory for ./configure for pango-1.32.6
1,421,228,458,000
I needed to enable SCSI support in CentOS 7.9 so I followed the instructions here: https://wiki.centos.org/HowTos(2f)I_need_the_Kernel_Source.html to add SCSI support and recompile, which worked as expected, but instead of uname -r reporting 3.10.0-1160.108.1.el7.x86_64, it only reports 3.10.0, and the vmlinuz files it creates in /boot are also named this way. This despite all the paths in the rpmbuild directories having the full name. The UTS_RELEASE entry in the include/generated/utsrelease.h file was 3.10.0 so I edited it and recompiled, but it's doing the same thing. How do I recompile the kernel so that uname -r reports the correct version?
By default, uname -r will only give the output of VERSION, PATCHLEVEL & SUBLEVEL as defined by the kernel Makefile as all other settings would by default be blank. In this case, 3.10.0. However, there is also EXTRAVERSION within the Makefile & LOCALVERSION which can be set during config. As such I would have expected LOCALVERSION to be set to -1160.108.1, but for some reason in this case, it is not. You can change it by altering General setup -> Local version - append to kernel release. It is just free form text. You should note that although you expect it to show 3.10.0-1160.108.1.el7.x86_64, I have not seen a single kernel which has ever added on the el7.x86_64 part.
CentOS 7.9 not reporting full version number after recompiling kernel
1,421,228,458,000
I need to install SAGA GIS for some interpolations. Sadly, sudo apt-get install saga will only install version 7.3.0, but I need version 9, preferably 9.3.0. The SourceForge repo doesn't contain Linux binaries. The wiki page on binaries mentions a Launchpad package, but the last build is from 2017. There's also a 9.3.0 package for sid in the Debian repo, but I can't install it: $ sudo apt install ./saga_9.3.0+dfsg-1_amd64.deb Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Hinweis: »saga« wird an Stelle von »./saga_9.3.0+dfsg-1_amd64.deb« gewählt. Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: saga : Hängt ab von: saga-common (= 9.3.0+dfsg-1) soll aber nicht installiert werden Hängt ab von: libc6 (>= 2.35) aber 2.31-0ubuntu9.14 soll installiert werden Hängt ab von: libgdal34 (>= 2.1.0) ist aber nicht installierbar Hängt ab von: libodbc2 (>= 2.3.1) ist aber nicht installierbar Hängt ab von: libproj25 (>= 5.1.0) ist aber nicht installierbar Hängt ab von: libsaga-api9 (>= 9.3.0+dfsg) ist aber nicht installierbar Hängt ab von: libsaga-gdi9 (>= 9.3.0+dfsg) ist aber nicht installierbar Hängt ab von: libstdc++6 (>= 13.1) aber 10.5.0-1ubuntu1~20.04 soll installiert werden Hängt ab von: libwxbase3.2-1 (>= 3.2.4+dfsg) ist aber nicht installierbar Hängt ab von: libwxgtk3.2-1 (>= 3.2.1+dfsg-2) ist aber nicht installierbar E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete. Thus, the only option left is compiling SAGA GIS from source. When following the compilation docs, I run into the following error: $ cmake ../saga-gis -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_INSTALL_RPATH=/usr/local/lib -DPYTHON_INCLUDE_DIR=/usr/include/python3.6m -DPYTHON_LIBRARY=/usr/lib64/libpython3.6m.so -DPYTHON_EXECUTABLE=/usr/bin/python3.6 -DWITH_TRIANGLE=OFF -DWITH_SYSTEM_SVM=ON -DWITH_TOOLS_VIGRA=OFF -DWITH_DEV_TOOLS=ON -DSVM_INCLUDE=/usr/include/libsvm/svm.h ... (works fine) ... $ cmake --build . --config Release [ 7%] Built target saga_api [ 7%] Linking CXX executable saga_cmd /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `stat64@GLIBC_2.33' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `fstat64@GLIBC_2.33' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `dladdr@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `dlclose@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `std::__exception_ptr::exception_ptr::_M_release()@CXXABI_1.3.13' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `dlerror@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_mutexattr_init@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_key_create@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_setspecific@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `std::__exception_ptr::exception_ptr::_M_addref()@CXXABI_1.3.13' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_mutex_timedlock@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_cancel@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_join@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_setname_np@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_mutex_trylock@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `lstat64@GLIBC_2.33' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `dlsym@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_setconcurrency@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_getspecific@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_attr_setstacksize@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_key_delete@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `dlopen@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_mutexattr_settype@GLIBC_2.34' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libwx_baseu_unofficial-3.2.so: undefined reference to `pthread_create@GLIBC_2.34' collect2: error: ld returned 1 exit status make[2]: *** [src/saga_core/saga_cmd/CMakeFiles/saga_cmd.dir/build.make:130: src/saga_core/saga_cmd/saga_cmd] Fehler 1 make[1]: *** [CMakeFiles/Makefile2:2350: src/saga_core/saga_cmd/CMakeFiles/saga_cmd.dir/all] Fehler 2 make: *** [Makefile:130: all] Fehler 2 Here's some info about my system: $ lsb_release -a No LSB modules are available. Distributor ID: Zorin Description: Zorin OS 16.3 Release: 16 Codename: focal $ uname -a Linux dell-zorin 5.15.0-91-generic #101~20.04.1-Ubuntu SMP Thu Nov 16 14:22:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux How can I install the latest SAGA version instead?
Recently, an upgrade from Zorin 16.3 to 17 was released, and now everything works as expected. $ lsb_release -a No LSB modules are available. Distributor ID: Zorin Description: Zorin OS 17 Release: 17 Codename: jammy $ uname -a Linux dell-zorin 6.5.0-15-generic #15~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 12 18:54:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
How to install SAGA GIS 9.3.0?
1,421,228,458,000
Instead of downloading the ISO, is there a way to download all the source packages and compile it locally? I came across the following URL https://knopper.net/knoppix-sources/ and would like to know whether it is possible to somehow download everything and compile everything in sequence locally.
Yes, there is. Let's first look into the documented way of setting up a knoppix image: http://knoppix.net/wiki/Knoppix_Remastering_Howto documents the process. Like with many Linux distributions, you set up an initial installation in a chroot directory, then create a bootable image from that. Because current knoppix is based on debian, I bet the process is a bit more modern then described in the wiki above, and can just be triggered with a single debootstrap invocation, but I haven't found one (only older docs). But the good news is that it's really just a debian based distro - so the process is exactly the same. You would just get a full list of installed packages, use apt source to get all the source packages, then for each package, use apt-get build-dep to install the build dependencies, debuild -b -uc -us to build the package from source, and finally place all the binary packages into a directory that you specify as package source during debootstrap. In essence, you'd be doing a source rebuild of a significant part of debian. I don't know whether that's worth it - debian is very good about reproducible builds and all the packages are checksummed, so that randomly picking packages, rebuilding only these from source and comparing the checksum should yield the same level of trust as building everything from source. Just that you can use debian binary packages, which reduces the build effort from days to minutes.
Is there a way to compile KNOPPIX from source?
1,691,001,434,000
I am trying to build "Transmission" on my machine with Linux Lite v3.6, but cmake is needed. Successfully installed it with sudo apt install cmake, but it installed only cmake 3.5.1. And transmission needs at least 3.9. How to install 3.9?
Linux lite is just an adoption of the Ubuntu long-time stable releases. The oldest still supported of these is Ubuntu 18.04, which already shipped with cmake 3.10. I think Linux lite v3 is based on the now-defunct Ubuntu 16.04. So, your Linux lite must be very very ancient, and you will very likely encounter much more missing components even if you managed to Backport cmake to it. It is time to update your Linux distribution. (That is definitely the easiest and least work way of getting cmake >= 3.9, so this is the answer to your literal question.) Your Linux platform is long out of service. Also, honestly, if you know how to download the source code of transmission and try building it, you're already more proficient with Linux system administration that most of Ubuntu users are. So not sure how much you benefit from Linux lite's restrictions:) Maybe going for a mainstream Linux distro like xubuntu, which is just like Linux lite, xfce running on the Ubuntu distribution base, just with a much richer selection of software and a much larger user base to draw from, makes your life easier. In your specific case, not going Linux lite but an official Ubuntu spin like xubuntu would have allowed you to directly install transmission via apt.
Cmake on Linux Lite 3.6
1,691,001,434,000
I can't understand why including a text file that contains some C lines in a fortran77 code gives me a warning if I do not use #include. I wrote an example of a code that is supposed to read some text to be added to the main file, test.F: program testInclude include 'includetest.txt' end program and the includetest.txt file to be included contains the following #define _TEST_ #ifdef _TEST_ write(*,*) 'check' #endif If I compile it with gfortran test.F I get the following warning: includetest.txt:2:2: 2 | #define _TEST_ | 1 Warning: Illegal preprocessor directive includetest.txt:3:2: 3 | #ifdef _TEST_ | 1 Warning: Illegal preprocessor directive includetest.txt:5:2: 5 | #endif | 1 Warning: Illegal preprocessor directive while no warnings are given if I use #include instead of include in the 2nd line of test.F. Aren't the fortran include statement and the C #include one supposed to do the same exact thing and add some lines of text to another file? What does the warning mean? This happens with gcc 12.2.0 on Arch and Mac OS X, and with gcc 4.8.5 on CentOS.
Files included by the preprocessor #include directive can contain #defines and the like; files included with the compiler INCLUDE statement must contain only FORTRAN statements.
Why compiling Fortran code with include is different from #include?
1,691,001,434,000
I'm running Debian Buster where I build some packages with the devscripts package. I want to build these packages for the current stable Debian release (bullseye) without upgrading my system. I'm not sure where to start. Update my build packages? Set some flag in the build scripts?
You can use pbuilder for this; install it, then run sudo pbuilder create --basetgz /var/cache/pbuilder/bullseye.tgz --distribution bullseye to initialise the Debian 11 build tarball. Then use pdebuild to build your package: pdebuild -- --basetgz /var/cache/pbuilder/bullseye.tgz See the pbuilder tricks page on the Debian wiki for a more general solution; you’ll have to adjust it to match the current stable and oldstable.
Build package for debian stable on old-stable
1,691,001,434,000
Background Hello, OpenDKIM is available on the official apk repository, but does not include important configuration flags I need such as --with-odbx and --with-sql-backend. I was able to compile it relatively easily. However, the resulting OpenDKIM binary cannot verify DKIM headers since it does not support RSA-SHA256. I found this odd since apk add opendkim does support RSA-SHA256. Question How can I compile OpenDKIM on Alpine 3.14 with these additional configuration flags and still have support for RSA-SHA256? Steps to reproduce First, I pre-downloaded OpenDKIM 2.11.0-Beta2 and OpenDBX 1.4.6 into a packages folder. mkdir packages wget -P packages \ https://github.com/trusteddomainproject/OpenDKIM/archive/refs/tags/2.11.0-Beta2.tar.gz \ http://linuxnetworks.de/opendbx/download/opendbx-1.4.6.tar.gz Then I wrote this Dockerfile, based mainly on the APKBUILD file. FROM alpine:3.14 COPY packages /opt/data RUN apk add --no-cache \ alpine-sdk \ automake \ autoconf \ db-dev \ libtool \ mariadb-dev \ readline-dev \ && cd /opt/data \ && tar xzf opendbx-1.4.6.tar.gz \ && cd opendbx-1.4.6/ \ && CPPFLAGS="-I/usr/include/mysql" ./configure --with-backends="mysql" \ && make install RUN apk add --no-cache \ openssl-dev \ libmilter-dev \ && cd /opt/data \ && tar xzf 2.11.0-Beta2.tar.gz \ && cd OpenDKIM-2.11.0-Beta2 \ && autoreconf -vif \ && ./configure \ --sysconfdir=/etc/opendkim \ --with-odbx \ --with-openssl=/usr/lib \ --with-sql-backend \ && make \ && make install Then I built and ran the docker image: docker build -t opendkim-alpine . docker run opendkim-alpine opendkim -V Notice rsa-sha256 is missing from the "Supported signing algorithms. Compare to the output here: docker run alpine:3.14 ash -c 'apk add opendkim && opendkim -V' Notes ./configure failed to complete with an error that libssl could not be found until I specified --with-openssl=/usr/lib. I think this may hint that I need to pass LDFLAGS or CFLAGS, but I don't know what those should be. Debian Buster does include the compilation flags I need. In the APKBUILD file, I have no idea what the values of CFLAGS are and I couldn't easily figure out what default_prepare does. It seems relatively opaque and difficult to find the answers to these questions except by experiment. I've seen other attempts which create an entire alpine build environment and use sed to modify the APKBUILD file to include extra flags. This seemed like overkill. For Googlers, the error message I get when trying to run opendkim in verify mode is opendkim: verify mode requires rsa-sha256 support.
Okay, I figured it out. I fully don't understand why, but I needed to set this env var for ./configure: CPPFLAGS="-I/usr/include/openssl" So the full RUN command becomes: RUN apk add --no-cache \ openssl-dev \ libmilter-dev \ && cd /opt/data \ && tar xzf 2.11.0-Beta2.tar.gz \ && cd OpenDKIM-2.11.0-Beta2 \ && autoreconf -vif \ && CPPFLAGS="-I/usr/include/openssl" ./configure \ --sysconfdir=/etc/opendkim \ --with-odbx \ --with-openssl \ --with-sql-backend \ && make \ && make install I resolved this through trial and error and would love an explanation why OpenDKIM couldn't find openssl located there by default.
Properly compile OpenDKIM on Alpine
1,691,001,434,000
I've tried building packages from qt's website but everytime I try to cmake a specific file that requests qt version 5.15 I'm always told it fails because I'm using the default version 5.12.8. How can I make it so I'm using a new version of qt? APT packages don't seem to solve the issue. I'm attempting to cmake some libs from the kde api repo because I can't find them on my computer and this issue is preventing that. I would like to finish building that kdeconnect app via vscode. running qmake version gives me QMake version 3.1 Using Qt version 5.12.8 in /usr/lib/x86_64-linux-gnu
From the Qt forum: cmake -DCMAKE_PREFIX_PATH=~/Qt/6.1.2/gcc_64/lib/cmake CMakeLists.txt you can use a specific version of Qt as such. The path should be accurate to wherever you've installed your Qt directory.
Can't change Qt version from 5.12.8 to 5.15.X
1,691,001,434,000
I am using the latest stable Linux from Scratch book version. In Step 5.5.1, when configuring Glibc I run the provided script, and receive an error telling me to use the --with-headers configure option, however I am already using it. The book states to configure using: ../configure \ --prefix=/usr \ --host=$LFS_TGT \ --build=$(../scripts/config.guess) \ --enable-kernel=3.2 \ --with-headers=$LFS/usr/include \ libc_cv_slibdir=/lib When doing so I receive the following error: checking installed Linux kernel header files... missing or too old! configure: error: GNU libc requires kernel header files from Linux 3.2.0 or later to be installed before configuring. The kernel header files are found usually in /usr/include/asm and /usr/include/linux; make sure these directories use files from Linux 3.2.0 or later. This check uses <linux/version.h>, so make sure that file was built correctly when installing the kernel header files. To use kernel headers not from /usr/include/linux, use the configure option --with-headers. Any advise on how to proceed would be much appreciated.
Resolved. Simple error on my part. In case someone else runs into this in the future: In the previous step (5.4.1) there may have been an error in the installation of the Linux headers, and to run "cp -rv usr/include $LFS/usr" root may be required. In my case I must have missed this specific command, thus in the next step there were simply no headers for glibc to work with.
When configuring Glibc prior to compiling it I recieve an error concerning kernel headers telling me to use "--with-headers"
1,691,001,434,000
someone suggested me this would be the right place for asking this question and it seems so from other questions. I hope to get an answer here. (by the way, the reason I'm trying to build ubuntu is to add some debug info in the ubuntu kernel to debug an ubuntu install failure on a virtual machine using qemu. The virtual machine is based on qemu's arm64 'virt' machine but has different address map and it has a simple peripheral device model that loads and uses a complex .so file based on multi2sim.) I downloaded ubuntu source by git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git. and according to https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel and the included build process for arm, I did this: LANG=C fakeroot debian/rules clean LANG=C fakeroot debian/rules binary-headers binary-generic binary-perarch I had exported ARCH=arm64 CROSS_COMPILE=aarch64-none-elf or ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- before the commands, or with the command but it ended with errors at the end. One of the error message was You are building kernel with non-retpoline compiler, please update your compiler and I saw I can fix it by changing configuration(https://askubuntu.com/questions/1145943/building-kernel-with-non-retpoline-compiler). So I tried LANG=C fakeroot debian/rules editconfigs But it asks me Do you want to edit config: amd64/config.flavour.generic? when I'm doing it for arm64 architecture. I tried giving ARCH and CROSS_COMPILE option but it always asks me if I want to change amd64 configuration. How can I give it the ARCH and CROSS_COMPILE option for this fakeroot debian/rules build method? p.s. my toolchain info. aarch64-linux-gnu-gcc (Linaro GCC 7.5-2019.12) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. or aarch64-none-elf-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Based on the ARM cross-compilation instructions, you need to export the following: export $(dpkg-architecture -aarm64) export CROSS_COMPILE=aarch64-linux-gnu- But it asks me Do you want to edit config: amd64/config.flavour.generic? If you reply “no”, it will eventually ask you if you want to edit the arm64 configuration. Once the configuration is ste up as you want it, fakeroot debian/rules binary-headers binary-generic binary-perarch will build the packages for you, targeting aarch64.
how to build ubuntu for arm64? (how to give ARCH and CROSS_COMPILE variable to `debian/rules` command)
1,691,001,434,000
so I've cloned this github repository https://github.com/xiangzhai/rt5370 It's a drive for my wifi adapter. My problem is that whenever I try to use the "make" command, it returns this error /lib/modules/5.3.7-gentoo--g243aa7022-dirty/build No such file or directory This is what I've tried so far emerge --sync emerge linux-header emerge build No luck, could anyone help me please I've been trying to fix the issue for hours now
Apparently my kernel wasn't actually compiled. Compiling my kernel fixed the issue.
Build not found when using the command "make" in gentoo linux
1,691,001,434,000
I'm trying to build an LFS system but I've hit a roadbloack, what am I supposed to do for the 2nd passes. I thought maybe I had to re-untar again then compile their but that didn't make a new directory, then I thought a build directory had to be made inside the existing folder but that doesn't work out either, then I tried building inside the existing build directory, then I made a build directory INSIDE the build directory but both did not help at all. I don't imagine I need to include code as I'm certain the processes I've used were incorrect. Any help would be very appreciated thanks!
Chapter 5.3, more precisely the second Important box, tells you to extract the package, go to the directory that was created by the extracting process, follow the instructions, go back to the parent directory and delete the extracted sources. So yes, you have to untar again, since you deleted the extracted directory structure. Most (all?) instructions ask you to make a build directory in the top of the extracted structure.
What are you supposed to do for "pass 2" sections in LFS
1,691,001,434,000
I am trying to understand creation and use of static libraries and shared libraries in Linux using Program Library HOWTO. There are two statements in the link that I am confused about: Static libraries permit users to link to programs without having to recompile its code, saving recompilation time. Static libraries are often useful for developers if they wish to permit programmers to link to their library, but don't want to give the library source code. Regarding 1: The static libraries end up as part of the executable while shared libraries stay separate and are only loaded when the executable starts execution. However, don't both these libraries have the advantage of not having to be recompiled when a new application wants to use them - assuming there are no changes to the library itself? If that's true why does the statement give the impression that it is an advantage of static libraries over shared libraries? Regarding 2: Once again, doesn't this apply to shared libraries as well? The shared libraries also use object files, even though they are generated as PIC in a format specific to the architecture. So, is source code being shared in this case?
I think the guide is supposed to be understood in the order it’s presented in, without assuming external knowledge about libraries. Thus in chapter 2, “Static Libraries”, comparisons don’t involve shared libraries, which haven’t been introduced yet. So both excerpts are comparisons to source code only: compared to providing source code, building static libraries allows compilation objects to be re-used without being recompiled, and without even having to provide their source code.
Static Libraries: Recompilation and sharing of the source code
1,605,709,891,000
I purchased a new Jinco Wifi Adapter wifi adapter, but I am getting this error every time when issuing the make command: [superusr@developer-pc ~]$ cd /opt/rtlwifi_new-rock.new_btcoex/ [superusr@developer-pc rtlwifi_new-rock.new_btcoex]$ sudo make [sudo] password for superusr: make -C /lib/modules/5.8.18-300.fc33.x86_64/build M=/opt/rtlwifi_new-rock.new_btcoex modules make[1]: Entering directory '/usr/src/kernels/5.8.18-300.fc33.x86_64' CC [M] /opt/rtlwifi_new-rock.new_btcoex/btcoexist/halbtc8723b2ant.o In file included from /opt/rtlwifi_new-rock.new_btcoex/btcoexist/halbt_precomp.h:25, from /opt/rtlwifi_new-rock.new_btcoex/btcoexist/halbtc8723b2ant.c:14: /opt/rtlwifi_new-rock.new_btcoex/btcoexist/../wifi.h:1493:2: error: unknown type name ‘__kernel_time_t’ 1493 | __kernel_time_t last_suspend_sec; | ^~~~~~~~~~~~~~~ make[3]: *** [scripts/Makefile.build:281: /opt/rtlwifi_new-rock.new_btcoex/btcoexist/halbtc8723b2ant.o] Error 1 make[2]: *** [scripts/Makefile.build:497: /opt/rtlwifi_new-rock.new_btcoex/btcoexist] Error 2 make[1]: *** [Makefile:1752: /opt/rtlwifi_new-rock.new_btcoex] Error 2 make[1]: Leaving directory '/usr/src/kernels/5.8.18-300.fc33.x86_64' make: *** [Makefile:57: all] Error 2 lsusb output is: Bus 002 Device 004: ID 0bda:f179 Realtek Semiconductor Corp. 802.11n Kernel version - kernel-5.8.18-300.fc33.x86_64 Fedora version - Fedora 33 Wifi - Realtek Semiconductor Corp.
According to the provided lsusb info, 0bda:f179 Realtek Semiconductor Corp. 802.11n, what you're looking for is this driver: https://github.com/kelebek333/rtl8188fu (Turning a comment into an answer to make it easily accessible).
Errors while installing wifi drivers on Fedora
1,605,709,891,000
I need help with installing a software. In general: I try to install PostGIS on a cluster (CentOS) and do not have admin rights. There is a sqlite3 installation (connected to the error), but this seems corrupt. My own one usually works and has (also by install-process) been used previously. I cannot use yum. In detail: For having the MakeFiles build I set flags as I believe to possibly need them: ./configure --prefix="$HOME/.local" CFLAGS="-I$HOME/.local/include" LDFLAGS="-L$HOME/.local/lib" LT_SYS_LIBRARY_PATH="$HOME/.local/lib" LIBS="-L$HOME/.local/lib" SQLITE3_CFLAGS="-I$HOME/.local/include" SQLITE3_LIBS="-L$HOME/.local/lib" But the following error is thrown when running make: /usr/bin/sed: can't read /usr/local/lib/libsqlite3.la: No such file or directory libtool: error: '/usr/local/lib/libsqlite3.la' is not a valid libtool archive Right after (but I don't see the connection): libtool: link: ranlib .libs/liblwgeom.a If I run make again, it jumps that directory. But gets stuck with a similar error (which is not jumped by running make another time): /bin/sh ../../libtool --mode=link gcc -Wall -Wmissing-prototypes -std=gnu99 -I<exp. $HOME>/.local/include -fno-math-errno -fno-signed-zeros -fPIC -DPIC -I../rt_core -I../../liblwgeom -I<exp. $HOME>/.local/include -I/usr/include/gdal -I<exp. $HOME>/.local/include ../rt_core/librtcore.a raster2pgsql.o -L<exp. $HOME>/.local/lib -static ../../liblwgeom/liblwgeom.la -L/usr/lib64 -lgdal -L<exp. $HOME>/.local/lib -lgeos_c -lc -lm -o raster2pgsql libtool: error: cannot find the library '/usr/local/lib/libsqlite3.la' or unhandled argument '/usr/local/lib/libsqlite3.la' I don't get why libtool searches in '/usr/local/lib/'. I didn't find that hardcoded in libtool or the MakeFiles. I'm clueless - and this is above my skill (apperently). Can you help me?
One of the dependencies (proj) linked in its .la file to the malicious sqlite3 version. Reinstalling this dependency solved the issue. What would help in similar cases would be to search the 'wrong path' in the dependencies: find <deps lib dir> -type f -exec grep -l "<wrong path>" {} + Kudos go to https://stackoverflow.com/a/62500481/14339502 who stated the valuable hint that "it seems like you have some other .la file that references it".
Libtool searches wrong directory while path specified
1,605,709,891,000
I'm trying to run busybox on my waveshare stm32 development board but my SOC has "armv7-m" architecture not "armv7-a". so I've put the march flag in the menuconfig of busybox (-march=armv7-m) Additional CFLAGS. But when I'm trying to compile it, it throws me thousands of instants of this Conflicting architecture profiles M/A error for each file while linking. So, I decided to put this flag (-march=armv7-m) Additional LDFLAGSfor linker too, but it didn't help. my platform: Host: | OS: Ubuntu 20 LTS | Kernel: Microsoft WSL2 Linux Kernel | Cross compile Toolchain: Linaro latest stable version |__ Target: | Board: Waveshare CoreH7XXI | SOC: stm32h743 (Single Core Cortex M7 @400MHz) | Architecture: ARMV7-M | Onboard DRAM: 8MB - 400KB(reserved by u-boot) = 7.6MB | Linux Kernel: 5.8.10 (stable 2020-09-17) | Busybox: latest stable version |__ makefile log (it was too long, so I've deleted the middle part of it): LINK busybox_unstripped Your linker does not support --sort-section,alignment Your linker does not support --sort-common Static linking against glibc, can't use --gc-sections Trying libraries: m resolv rt Failed: -Wl,--start-group -lm -lresolv -lrt -Wl,--end-group Output of: arm-linux-gnueabihf-gcc -Wall -Wshadow -Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter -Wunused-function -Wunused-value -Wmissing-prototypes -Wmissing-declarations -Wno-format-security -Wdeclaration-after-statement -Wold-style-definition -finline-limit=0 -fno-builtin-strlen -fomit-frame-pointer -ffunction-sections -fdata-sections -fno-guess-branch-probability -funsigned-char -static-libgcc -falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1 -fno-unwind-tables -fno-asynchronous-unwind-tables -fno-builtin-printf -Os -march=armv7-m -static -march=armv7-m -o busybox_unstripped -Wl,--start-group applets/built-in.o archival/lib.a archival/libarchive/lib.a console-tools/lib.a coreutils/lib.a coreutils/libcoreutils/lib.a debianutils/lib.a klibc-utils/lib.a e2fsprogs/lib.a editors/lib.a findutils/lib.a init/lib.a libbb/lib.a libpwdgrp/lib.a loginutils/lib.a mailutils/lib.a miscutils/lib.a modutils/lib.a networking/lib.a networking/libiproute/lib.a networking/udhcp/lib.a printutils/lib.a procps/lib.a runit/lib.a selinux/lib.a shell/lib.a sysklogd/lib.a util-linux/lib.a util-linux/volume_id/lib.a archival/built-in.o archival/libarchive/built-in.o console-tools/built-in.o coreutils/built-in.o coreutils/libcoreutils/built-in.o debianutils/built-in.o klibc-utils/built-in.o e2fsprogs/built-in.o editors/built-in.o findutils/built-in.o init/built-in.o libbb/built-in.o libpwdgrp/built-in.o loginutils/built-in.o mailutils/built-in.o miscutils/built-in.o modutils/built-in.o networking/built-in.o networking/libiproute/built-in.o networking/udhcp/built-in.o printutils/built-in.o procps/built-in.o runit/built-in.o selinux/built-in.o shell/built-in.o sysklogd/built-in.o util-linux/built-in.o util-linux/volume_id/built-in.o -Wl,--end-group -Wl,--start-group -lm -lresolv -lrt -Wl,--end-group ========== libbb/lib.a(inet_common.o): In function `INET6_resolve': inet_common.c:(.text.INET6_resolve+0x22): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking coreutils/lib.a(mktemp.o): In function `mktemp_main': mktemp.c:(.text.mktemp_main+0x4e): warning: the use of `mktemp' is dangerous, better use `mkstemp' networking/lib.a(ipcalc.o): In function `ipcalc_main': ipcalc.c:(.text.ipcalc_main+0x148): warning: Using 'gethostbyaddr' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking libbb/lib.a(inet_common.o): In function `INET_resolve': inet_common.c:(.text.INET_resolve+0x2c): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking networking/lib.a(inetd.o): In function `reread_config_file': inetd.c:(.text.reread_config_file+0x152): warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking networking/lib.a(netstat.o): In function `ip_port_str': netstat.c:(.text.ip_port_str+0x2c): warning: Using 'getservbyport' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: applets/built-in.o: Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file applets/built-in.o /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(appletlib.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(appletlib.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(compare_string_array.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(compare_string_array.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(concat_path_file.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(concat_path_file.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(default_error_retval.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(default_error_retval.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(get_last_path_component.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(get_last_path_component.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(last_char_is.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(last_char_is.o) . . . . . /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(xgethostbyname.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(xrealloc_vector.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(xrealloc_vector.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(xregcomp.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(xregcomp.o) /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: error: libbb/lib.a(perror_nomsg.o): Conflicting architecture profiles M/A /opt/gcc-arm-linux/bin/../lib/gcc/arm-linux-gnueabihf/5.4.1/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file libbb/lib.a(perror_nomsg.o) collect2: error: ld returned 1 exit status Note: if build needs additional libraries, put them in CONFIG_EXTRA_LDLIBS. Example: CONFIG_EXTRA_LDLIBS="pthread dl tirpc audit pam" make: *** [Makefile:718: busybox_unstripped] Error 1 without adding arm-v7-m flag, it compiles it for cortex A: $ readelf -A busybox Attribute Section: aeabi File Attributes Tag_CPU_name: "7-A" Tag_CPU_arch: v7 Tag_CPU_arch_profile: Application Tag_ARM_ISA_use: Yes Tag_THUMB_ISA_use: Thumb-2 Tag_FP_arch: VFPv3 Tag_Advanced_SIMD_arch: NEONv1 Tag_ABI_PCS_wchar_t: 4 Tag_ABI_FP_rounding: Needed Tag_ABI_FP_denormal: Needed Tag_ABI_FP_exceptions: Needed Tag_ABI_FP_number_model: IEEE 754 Tag_ABI_align_needed: 8-byte Tag_ABI_align_preserved: 8-byte, except leaf SP Tag_ABI_enum_size: int Tag_ABI_VFP_args: VFP registers Tag_CPU_unaligned_access: v6
You should use -mcpu flag instead of -march. Example: -mcpu=cortex-m7
How to compile busybox for cortex-m7 (-march=armv7-m)?
1,605,709,891,000
I've configured my busybox in menuconfig and made it as a static binary (no shared libs) + forced no MMU build. I'm using the prebuilt arm cross compiler and when I enter the below command, it gave me error while building the source code. sudo make -j8 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- it gave me this log: LINK busybox_unstripped Static linking against glibc, can't use --gc-sections Trying libraries: m resolv Failed: -Wl,--start-group -lm -lresolv -Wl,--end-group Output of: arm-linux-gnueabi-gcc -Wall -Wshadow -Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter -Wunused-function -Wunused-value -Wmissing-prototypes -Wmissing-declarations -Wno-format-security -Wdeclaration-after-statement -Wold-style-definition -fno-builtin-strlen -finline-limit=0 -fomit-frame-pointer -ffunction-sections -fdata-sections -fno-guess-branch-probability -funsigned-char -static-libgcc -falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1 -fno-unwind-tables -fno-asynchronous-unwind-tables -fno-builtin-printf -Os -static -o busybox_unstripped -Wl,--sort-common -Wl,--sort-section,alignment -Wl,--start-group applets/built-in.o archival/lib.a archival/libarchive/lib.a console-tools/lib.a coreutils/lib.a coreutils/libcoreutils/lib.a debianutils/lib.a klibc-utils/lib.a e2fsprogs/lib.a editors/lib.a findutils/lib.a init/lib.a libbb/lib.a libpwdgrp/lib.a loginutils/lib.a mailutils/lib.a miscutils/lib.a modutils/lib.a networking/lib.a networking/libiproute/lib.a networking/udhcp/lib.a printutils/lib.a procps/lib.a runit/lib.a selinux/lib.a shell/lib.a sysklogd/lib.a util-linux/lib.a util-linux/volume_id/lib.a archival/built-in.o archival/libarchive/built-in.o console-tools/built-in.o coreutils/built-in.o coreutils/libcoreutils/built-in.o debianutils/built-in.o klibc-utils/built-in.o e2fsprogs/built-in.o editors/built-in.o findutils/built-in.o init/built-in.o libbb/built-in.o libpwdgrp/built-in.o loginutils/built-in.o mailutils/built-in.o miscutils/built-in.o modutils/built-in.o networking/built-in.o networking/libiproute/built-in.o networking/udhcp/built-in.o printutils/built-in.o procps/built-in.o runit/built-in.o selinux/built-in.o shell/built-in.o sysklogd/built-in.o util-linux/built-in.o util-linux/volume_id/built-in.o -Wl,--end-group -Wl,--start-group -lm -lresolv -Wl,--end-group ========== /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: libbb/lib.a(inet_common.o): in function `INET6_resolve': inet_common.c:(.text.INET6_resolve+0x50): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: coreutils/lib.a(mktemp.o): in function `mktemp_main': mktemp.c:(.text.mktemp_main+0x9c): warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: networking/lib.a(ipcalc.o): in function `ipcalc_main': ipcalc.c:(.text.ipcalc_main+0x238): warning: Using 'gethostbyaddr' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: libbb/lib.a(inet_common.o): in function `INET_resolve': inet_common.c:(.text.INET_resolve+0x50): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: networking/lib.a(inetd.o): in function `reread_config_file': inetd.c:(.text.reread_config_file+0x3b0): warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: networking/lib.a(netstat.o): in function `ip_port_str': netstat.c:(.text.ip_port_str+0x50): warning: Using 'getservbyport' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: util-linux/lib.a(rdate.o): in function `rdate_main': rdate.c:(.text.rdate_main+0xec): undefined reference to `stime' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: coreutils/lib.a(date.o): in function `date_main': date.c:(.text.date_main+0x248): undefined reference to `stime' collect2: error: ld returned 1 exit status Note: if build needs additional libraries, put them in CONFIG_EXTRA_LDLIBS. Example: CONFIG_EXTRA_LDLIBS="pthread dl tirpc audit pam" make: *** [Makefile:718: busybox_unstripped] Error 1
Use Linaro arm toolchain instead of glibc. the default arm gnu compiler on ubuntu is not stable. https://releases.linaro.org/components/toolchain/binaries/latest-7/arm-linux-gnueabihf/
cannot cross-compile busybox for arm
1,605,709,891,000
I tried to compile an Android 8 kernel to contain a driver for TP-Link TL-WN722N USB Wi-Fi card for a smartphone, the kernel is flashed successfully, but when I plug the Wi-Fi card via OTG to the phone, it's not recognised by software. Here are some debugging I have done: The Wi-Fi card is showing in lsusb -t output, but no driver binding to it. I can see the module is loaded in /proc/modules and lsmod: wlan 5801121 0 - Live 0x00000000000000 (O) The driver I have picked using make menuconfig before compile was called ATH9K and ATH9K_HTC, so I am not sure why it's wlan here, and the offset being all zeros is a bit weird. Also, this is the only item in the output, I guess all other native modules are compiled directly into the kernel, not externally. There are many things look not very right, but I'm not sure where actually is the problem, any suggestions will be appreciated.
I finally got it working, it turns out the Atheros device requires a .fw firmware file to be placed in right directory to work, I noticed this because an error of loading firmware failed message shows in dmesg every time I plug in the wifi card. I also tried to bind driver to device like @nobody suggested, but I'm not sure if that's working, the driver is not showed in the device folder after binding.
Why is a loaded module not being driver of the device?
1,605,709,891,000
If I installed a new kernel via rpm, I can see the kernel source ( /usr/src/kernel/4.xxx-xxxx-xxxx ) for me to build the driver. It seems covered by kernel-devel rpm. ex: kernel-ml-4.14.15-1.el7.elrepo.x86_64.rpm kernel-ml-devel-4.14.15-1.el7.elrepo.x86_64.rpm Now, I want to install/build the new kernel from the upstream source, what should I do to also have the kernel source be installed as kernel-ml-devel-4.14.15-1.el7.elrepo.x86_64.rpm did? Doing these will install the kernel source? or just install a new kernel? make; make modules; make install; make modules_install
Now, I want to install/build the new kernel from the upstream source, what should I do to also have the kernel source be installed as kernel-ml-devel-4.14.15-1.el7.elrepo.x86_64.rpm did? As you want to rebuild your kernel from scratch, your entry point will be the sources :-) So, just download a kernel from kernel.org, untar it to /usr/src and follow the guide. kernel-devel RPM must be able to find out the path to your sources. If not, and depending on the driver you want to compile, there's several way to recompile it by your own. First thing to look is the documentation of your driver... Here is a good paper about this.
How to install kernel source from upstream kernel
1,605,709,891,000
The current version of Kodi in Debian10's repositories is v17.6. This version didn't work properly (it wasn't usable). Hence I'm trying to install the latest version. I followed the steps of the "Debian/Ubuntu build guide" of the Kodi repository except that I didn't add the PPA. I used sudo apt build-dep kodi as packages "flatbuffers-dev" and "libshairplay-dev" could not be found and there wasn't an installation candidate for "libmysqlclient-dev" when trying to build dependencies manually. When trying to follow the steps of "Build Kodi" of the "Linux build guide" which are the last step of the "Debian/Ubuntu build guide" I get these errors when running command cmake ../kodi -DCMAKE_INSTALL_PREFIX=/usr/local -DX11_RENDER_SYSTEM=gl: CMake Error at CMakeLists.txt:95 (core_add_library): Unknown CMake command "core_add_library". CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.13) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! Do I need to add the PPA and should I? Or is there something else that should be done to compile it? Would it be recommended to install it via the flatpak instead?
The latest version is in Debian bullseye now so the below isn't needed anymore. If you're running Debian 11, just run sudo apt-get install kodi. The latest version is in Debian buster-backports now so the below isn't needed anymore. If you're running Debian 10, just run sudo apt install -t buster-backports kodi. There's a new (currently unofficial) repository for the latest Kodi under Debian There's a new build guide now which works with Debian 10 when running a few additional commands. This worked for me: Run sudo apt-get install rapidjson-dev Follow this guide (you can ignore step "Enable internal dependencies") Run sha256sum ~/Downloads/19.0a2-Matrix.zip (or whatever the file downloaded from GitHub is named) Before running the build command (or after getting error "/usr/bin/ld: cannot find -lunistring") run sudo apt-get install libunistring-dev
How to install latest Kodi on latest Debian?
1,605,709,891,000
I have downloaded pcre from https://ftp.pcre.org/pub/pcre/pcre2-10.34.tar.gz and extracted it to /usr/local/lib when I run ./configure --with-included-apr --with-pcre=/usr/local/lib/pcre2-10.34 I am getting following error configure: error: Did not find pcre-config script at /usr/local/lib/pcre2-10.34
yum install pcre-devel -y fixed the issue, the devel(development) package was missing.
build apache on linux server
1,605,709,891,000
I want to make some changes in ath9k drivers for learning purposes. My problem is that when I try to compile the driver, the make command is giving many implicit declaration errors, setup_timer, ACCESS_ONCE, DECLARE_EWMA are the most frequent ones that show up in the errors. My kernel version is Ubuntu 4.15.0-20-generic and I am using the driver source code from backports-4.14-rc2-1. These are the commands I run: cd backports-4.14-rc2-1 make defconfig-ath9k make I have already installed necessary header files using build-essential. What should I do, so that I can compile my edited source code of drivers?
I was compiling the driver module from the torvalds linux kernel, that was the problem, now I am compiling it from the Ubuntu source code, and it is working...
How to compile ath9k drivers from source?
1,605,709,891,000
As a novice in linux kernel compilation, it's my first time to compile a Linux kernel for myself (I'm trying to use other TCP congestion control algorithms). I followed the steps in How to Compile a Linux Kernel. When trying to run make, I get an error: ✘ XPS-13-9360  ~/linux_compile/linux-5.1.18  make CALL scripts/checksyscalls.sh CALL scripts/atomic/check-atomics.sh DESCEND objtool CC /home/soar/linux_compile/linux-5.1.18/tools/objtool/arch/x86/decode.o In file included from /usr/include/gelf.h:32:0, from arch/x86/../../elf.h:22, from arch/x86/decode.c:26: /usr/include/libelf.h:46:4: error: unknown type name ‘Elf32_Word’ Elf32_Word ch_type; /* Compression format. */ ^~~~~~~~~~ /usr/include/libelf.h:47:4: error: unknown type name ‘Elf32_Word’ Elf32_Word ch_size; /* Uncompressed data size. */ ^~~~~~~~~~ /usr/include/libelf.h:48:4: error: unknown type name ‘Elf32_Word’ Elf32_Word ch_addralign; /* Uncompressed data alignment. */ ^~~~~~~~~~ /usr/include/libelf.h:53:4: error: unknown type name ‘Elf64_Word’ Elf64_Word ch_type; /* Compression format. */ ^~~~~~~~~~ /usr/include/libelf.h:54:4: error: unknown type name ‘Elf64_Word’ Elf64_Word ch_reserved; ^~~~~~~~~~ /usr/include/libelf.h:55:4: error: unknown type name ‘Elf64_Xword’ Elf64_Xword ch_size; /* Uncompressed data size. */ ^~~~~~~~~~~ /usr/include/libelf.h:56:4: error: unknown type name ‘Elf64_Xword’ Elf64_Xword ch_addralign; /* Uncompressed data alignment. */ ^~~~~~~~~~~ /usr/include/libelf.h:253:8: error: unknown type name ‘Elf32_Ehdr’ extern Elf32_Ehdr *elf32_getehdr (Elf *__elf); ^~~~~~~~~~ /usr/include/libelf.h:255:8: error: unknown type name ‘Elf64_Ehdr’ extern Elf64_Ehdr *elf64_getehdr (Elf *__elf); ^~~~~~~~~~ /usr/include/libelf.h:258:8: error: unknown type name ‘Elf32_Ehdr’ extern Elf32_Ehdr *elf32_newehdr (Elf *__elf); ^~~~~~~~~~ /usr/include/libelf.h:260:8: error: unknown type name ‘Elf64_Ehdr’ extern Elf64_Ehdr *elf64_newehdr (Elf *__elf); ^~~~~~~~~~ /usr/include/libelf.h:269:8: error: unknown type name ‘Elf32_Phdr’ extern Elf32_Phdr *elf32_getphdr (Elf *__elf); ^~~~~~~~~~ /usr/include/libelf.h:271:8: error: unknown type name ‘Elf64_Phdr’ extern Elf64_Phdr *elf64_getphdr (Elf *__elf); ^~~~~~~~~~ /usr/include/libelf.h:274:8: error: unknown type name ‘Elf32_Phdr’ extern Elf32_Phdr *elf32_newphdr (Elf *__elf, size_t __cnt); ^~~~~~~~~~ /usr/include/libelf.h:276:8: error: unknown type name ‘Elf64_Phdr’ extern Elf64_Phdr *elf64_newphdr (Elf *__elf, size_t __cnt); ^~~~~~~~~~ /usr/include/libelf.h:283:43: error: unknown type name ‘Elf32_Off’; did you mean ‘Elf32_Chdr’? extern Elf_Scn *elf32_offscn (Elf *__elf, Elf32_Off __offset); ^~~~~~~~~ Elf32_Chdr /usr/include/libelf.h:285:43: error: unknown type name ‘Elf64_Off’; did you mean ‘Elf64_Chdr’? extern Elf_Scn *elf64_offscn (Elf *__elf, Elf64_Off __offset); ^~~~~~~~~ Elf64_Chdr /usr/include/libelf.h:325:8: error: unknown type name ‘Elf32_Shdr’ extern Elf32_Shdr *elf32_getshdr (Elf_Scn *__scn); ^~~~~~~~~~ /usr/include/libelf.h:327:8: error: unknown type name ‘Elf64_Shdr’ extern Elf64_Shdr *elf64_getshdr (Elf_Scn *__scn); ^~~~~~~~~~ In file included from arch/x86/../../elf.h:22:0, from arch/x86/decode.c:26: /usr/include/gelf.h:44:9: error: unknown type name ‘Elf64_Half’ typedef Elf64_Half GElf_Half; ^~~~~~~~~~ /usr/include/gelf.h:47:9: error: unknown type name ‘Elf64_Word’ typedef Elf64_Word GElf_Word; ^~~~~~~~~~ /usr/include/gelf.h:48:9: error: unknown type name ‘Elf64_Sword’ typedef Elf64_Sword GElf_Sword; ^~~~~~~~~~~ /usr/include/gelf.h:51:9: error: unknown type name ‘Elf64_Xword’ typedef Elf64_Xword GElf_Xword; ^~~~~~~~~~~ /usr/include/gelf.h:52:9: error: unknown type name ‘Elf64_Sxword’ typedef Elf64_Sxword GElf_Sxword; ^~~~~~~~~~~~ /usr/include/gelf.h:55:9: error: unknown type name ‘Elf64_Addr’ typedef Elf64_Addr GElf_Addr; ^~~~~~~~~~ /usr/include/gelf.h:58:9: error: unknown type name ‘Elf64_Off’ typedef Elf64_Off GElf_Off; ^~~~~~~~~ /usr/include/gelf.h:62:9: error: unknown type name ‘Elf64_Ehdr’ typedef Elf64_Ehdr GElf_Ehdr; ^~~~~~~~~~ /usr/include/gelf.h:65:9: error: unknown type name ‘Elf64_Shdr’ typedef Elf64_Shdr GElf_Shdr; ^~~~~~~~~~ /usr/include/gelf.h:70:9: error: unknown type name ‘Elf64_Section’ typedef Elf64_Section GElf_Section; ^~~~~~~~~~~~~ /usr/include/gelf.h:73:9: error: unknown type name ‘Elf64_Sym’ typedef Elf64_Sym GElf_Sym; ^~~~~~~~~ /usr/include/gelf.h:77:9: error: unknown type name ‘Elf64_Syminfo’ typedef Elf64_Syminfo GElf_Syminfo; ^~~~~~~~~~~~~ /usr/include/gelf.h:80:9: error: unknown type name ‘Elf64_Rel’ typedef Elf64_Rel GElf_Rel; ^~~~~~~~~ /usr/include/gelf.h:83:9: error: unknown type name ‘Elf64_Rela’ typedef Elf64_Rela GElf_Rela; ^~~~~~~~~~ /usr/include/gelf.h:86:9: error: unknown type name ‘Elf64_Phdr’ typedef Elf64_Phdr GElf_Phdr; ^~~~~~~~~~ /usr/include/gelf.h:92:9: error: unknown type name ‘Elf64_Dyn’ typedef Elf64_Dyn GElf_Dyn; ^~~~~~~~~ /usr/include/gelf.h:96:9: error: unknown type name ‘Elf64_Verdef’ typedef Elf64_Verdef GElf_Verdef; ^~~~~~~~~~~~ /usr/include/gelf.h:99:9: error: unknown type name ‘Elf64_Verdaux’ typedef Elf64_Verdaux GElf_Verdaux; ^~~~~~~~~~~~~ /usr/include/gelf.h:102:9: error: unknown type name ‘Elf64_Verneed’ typedef Elf64_Verneed GElf_Verneed; ^~~~~~~~~~~~~ /usr/include/gelf.h:105:9: error: unknown type name ‘Elf64_Vernaux’ typedef Elf64_Vernaux GElf_Vernaux; ^~~~~~~~~~~~~ /usr/include/gelf.h:109:9: error: unknown type name ‘Elf64_Versym’ typedef Elf64_Versym GElf_Versym; ^~~~~~~~~~~~ /usr/include/gelf.h:113:9: error: unknown type name ‘Elf64_auxv_t’ typedef Elf64_auxv_t GElf_auxv_t; ^~~~~~~~~~~~ /usr/include/gelf.h:117:9: error: unknown type name ‘Elf64_Nhdr’ typedef Elf64_Nhdr GElf_Nhdr; ^~~~~~~~~~ /usr/include/gelf.h:121:9: error: unknown type name ‘Elf64_Move’ typedef Elf64_Move GElf_Move; ^~~~~~~~~~ /usr/include/gelf.h:125:9: error: unknown type name ‘Elf64_Lib’ typedef Elf64_Lib GElf_Lib; ^~~~~~~~~ /usr/include/gelf.h:232:8: error: unknown type name ‘Elf32_Word’; did you mean ‘GElf_Word’? Elf32_Word *__xshndx); ^~~~~~~~~~ GElf_Word /usr/include/gelf.h:238:6: error: unknown type name ‘Elf32_Word’; did you mean ‘GElf_Word’? Elf32_Word __xshndx); ^~~~~~~~~~ GElf_Word arch/x86/decode.c: In function ‘is_x86_64’: arch/x86/decode.c:43:19: error: request for member ‘e_machine’ in something not a structure or union switch (elf->ehdr.e_machine) { ^ arch/x86/decode.c:44:7: error: ‘EM_X86_64’ undeclared (first use in this function); did you mean ‘is_x86_64’? case EM_X86_64: ^~~~~~~~~ is_x86_64 arch/x86/decode.c:44:7: note: each undeclared identifier is reported only once for each function it appears in arch/x86/decode.c:46:7: error: ‘EM_386’ undeclared (first use in this function); did you mean ‘EM_X86_64’? case EM_386: ^~~~~~ EM_X86_64 In file included from arch/x86/decode.c:28:0: arch/x86/decode.c:49:51: error: request for member ‘e_machine’ in something not a structure or union WARN("unexpected ELF machine type %d", elf->ehdr.e_machine); ^ arch/x86/../../warn.h:58:14: note: in definition of macro ‘WARN’ objname, ##__VA_ARGS__) ^~~~~~~~~~~ arch/x86/decode.c:52:1: error: control reaches end of non-void function [-Werror=return-type] } ^ cc1: all warnings being treated as errors mv: cannot stat '/home/soar/linux_compile/linux-5.1.18/tools/objtool/arch/x86/.decode.o.tmp': No such file or directory /home/soar/linux_compile/linux-5.1.18/tools/build/Makefile.build:96: recipe for target '/home/soar/linux_compile/linux-5.1.18/tools/objtool/arch/x86/decode.o' failed make[4]: *** [/home/soar/linux_compile/linux-5.1.18/tools/objtool/arch/x86/decode.o] Error 1 /home/soar/linux_compile/linux-5.1.18/tools/build/Makefile.build:139: recipe for target 'arch/x86' failed make[3]: *** [arch/x86] Error 2 Makefile:50: recipe for target '/home/soar/linux_compile/linux-5.1.18/tools/objtool/objtool-in.o' failed make[2]: *** [/home/soar/linux_compile/linux-5.1.18/tools/objtool/objtool-in.o] Error 2 Makefile:66: recipe for target 'objtool' failed make[1]: *** [objtool] Error 2 Makefile:1699: recipe for target 'tools/objtool' failed make: *** [tools/objtool] Error 2 In libelf.h: and elf.h then I found it's been reported before, but it's still without any solution. What can I do?
Actually I figure out this by myself. It's look like the compiler could not find the header as my view. use the env command, the CPATH is not in /usr/include/ but /home/user/.local/include:$CPATH,so I change the CPATH to /usr/include/, using the method of lkraemer,but it's still could not work out, and the env reveal that the CPATH has been /usr/include/. I think it will be difficult to solve and shutdown my ubuntu and take a break. But I turn on my ubuntu this morning, it works out.
Compile linux kernel error
1,605,709,891,000
My current use case is installing PyODBC via poetry in a Jenkins job build, which is failing because sql.h can't be found. For background, I have two servers, one RHEL 6, one RHEL 7; the RHEL 6 server has unixODBC installed and working with (among other things) odbc.ini in /etc/, sql.h and other headers in /usr/include/. On the non-working RHEL 7 server helpdesk personnel just installed the same version of unixODBC-dev, and all the files seem to instead be in /usr/local/unixODBC/. I believe I correctly understand that /usr/local is for manually installed packages, which I suppose this is, but I'm not clear why these two installs would be done differently, and ultimately if there's a way to make things work on the RHEL server(, or failing that, a phrase I can give back to helpdesk to get this installed the right way.) Edit: Following @Stephen Kitt's suggestion, I went back to HD and they supposedly installed it with yum. Now the error is different (and quite a bit more lengthy, some seemingly repetitive lines have been clipped to fit the post length): [EnvCommandError] Command ['/var/lib/jenkins/.cache/pypoetry/virtualenvs/ds-ops-tools-py3.6/bi n/python', '-m', 'pip', 'install', '--no-deps', 'pyodbc==4.0.26'] errored wi th the following output: Collecting pyodbc==4.0.26 Using cached https://files.pythonhosted.org/packages/b4/41/f3eb5e56af207a8 fcc02f1f84cc3fed9fcf315565e65f418ae815e399929/pyodbc-4.0.26.tar.gz Installing collected packages: pyodbc Running setup.py install for pyodbc: started Running setup.py install for pyodbc: finished with status 'error' Complete output from command /var/lib/jenkins/.cache/pypoetry/virtualenv s/ds-ops-tools-py3.6/bin/python -u -c "import setuptools, tokenize;__file__= '/tmp/pip-build-i2_4l6cq/pyodbc/setup.py';f=getattr(tokenize, 'open', open)( __file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, _ _file__, 'exec'))" install --record /tmp/pip-oqv50di8-record/install-record. txt --single-version-externally-managed --compile --install-headers /var/lib /jenkins/.cache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include/site/python3 .6/pyodbc: running install running build running build_ext building 'pyodbc' extension creating build creating build/temp.linux-x86_64-3.6 creating build/temp.linux-x86_64-3.6/src gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/buffer.cpp -o build/temp.linux-x86_64-3.6/src/buffer.o -Wno- write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_LO NG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/cnxninfo.cpp -o build/temp.linux-x86_64-3.6/src/cnxninfo.o - Wno-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LON G_LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/connection.cpp -o build/temp.linux-x86_64-3.6/src/connection .o -Wno-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE _LONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] src/connection.cpp: In function ‘PyObject* Connection_getinfo(PyObject*, PyObject*)’: src/connection.cpp:835:40: warning: dereferencing type-punned pointer wi ll break strict-aliasing rules [-Wstrict-aliasing] SQLUINTEGER n = *(SQLUINTEGER*)szBuffer; // Does this work on P PC or do we need a union? ^ src/connection.cpp:848:49: warning: dereferencing type-punned pointer wi ll break strict-aliasing rules [-Wstrict-aliasing] result = PyInt_FromLong(*(SQLUSMALLINT*)szBuffer); ^ gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/cursor.cpp -o build/temp.linux-x86_64-3.6/src/cursor.o -Wno- write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_LO NG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/errors.cpp -o build/temp.linux-x86_64-3.6/src/errors.o -Wno- write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_LO NG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/getdata.cpp -o build/temp.linux-x86_64-3.6/src/getdata.o -Wn o-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_ LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/params.cpp -o build/temp.linux-x86_64-3.6/src/params.o -Wno- write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_LO NG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/pyodbccompat.cpp -o build/temp.linux-x86_64-3.6/src/pyodbcco mpat.o -Wno-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -D HAVE_LONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/pyodbcdbg.cpp -o build/temp.linux-x86_64-3.6/src/pyodbcdbg.o -Wno-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_L ONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/pyodbcmodule.cpp -o build/temp.linux-x86_64-3.6/src/pyodbcmo dule.o -Wno-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -D HAVE_LONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/row.cpp -o build/temp.linux-x86_64-3.6/src/row.o -Wno-write- strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_LONG -DS IZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 - Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=4.0.26 -I/var/lib/jenkins/.c ache/pypoetry/virtualenvs/ds-ops-tools-py3.6/include -I/usr/local/include/py thon3.6m -c src/textenc.cpp -o build/temp.linux-x86_64-3.6/src/textenc.o -Wn o-write-strings -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_ LONG -DSIZEOF_LONG_INT=8 -I/usr/include cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] creating build/lib.linux-x86_64-3.6 g++ -pthread -shared -Wl,-rpath /usr/local/lib build/temp.linux-x86_64-3 .6/src/buffer.o build/temp.linux-x86_64-3.6/src/cnxninfo.o build/temp.linux- x86_64-3.6/src/connection.o build/temp.linux-x86_64-3.6/src/cursor.o build/t emp.linux-x86_64-3.6/src/errors.o build/temp.linux-x86_64-3.6/src/getdata.o build/temp.linux-x86_64-3.6/src/params.o build/temp.linux-x86_64-3.6/src/pyo dbccompat.o build/temp.linux-x86_64-3.6/src/pyodbcdbg.o build/temp.linux-x86 _64-3.6/src/pyodbcmodule.o build/temp.linux-x86_64-3.6/src/row.o build/temp. linux-x86_64-3.6/src/textenc.o -L/usr/lib -L/usr/local/lib -L/usr/local/lib -lodbc -lpython3.6m -o build/lib.linux-x86_64-3.6/pyodbc.cpython-36m-x86_64- linux-gnu.so -L/usr/lib64 -lodbc /bin/ld: /usr/lib/libpython3.6m.a(abstract.o): relocation R_X86_64_32S a gainst symbol `_Py_NotImplementedStruct' can not be used when making a share d object; recompile with -fPIC /bin/ld: /usr/lib/libpython3.6m.a(boolobject.o): relocation R_X86_64_32 against `.data' can not be used when making a shared object; recompile with -fPIC [...] /bin/ld: /usr/lib/libpython3.6m.a(parser.o): relocation R_X86_64_32 agai nst `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC /bin/ld: /usr/lib/libpython3.6m.a(getcompiler.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recom pile with -fPIC /bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status error: command 'g++' failed with exit status 1 Edit: I think this is because my libpython*.so files are in /usr/local/lib rather than /usr/lib; I've added /usr/local/lib to ld.so.conf and run ldconfig but that doesn't seem to do anything. Edit 2: I found a suggestion that renaming /usr/lib/libpython3.6m.a would allow the .so files to be 'found' and this seems to have worked! But I'm still puzzled as this exhibited symptoms first of unixODBC not being installed with the package manager (which it wasn't) and then of python not having --shared-packages enabled, which it did, but other files were overriding those packages somehow. It would be great if someone could shed light on that but I realize that it's hard to say without knowing exactly how the system was set up and manipulated by the helpdesk folks who work on it.
The installation on your RHEL 6 server was probably done using the RHEL package of UnixODBC. This is easy to replicate on your RHEL 7 server: yum install unixODBC-devel will install the headers, development files and all their dependencies. We won’t be able to tell you why the two installations were performed differently; only your helpdesk can do that.
UnixODBC-dev installed in /usr/local/, resulting in gcc reporting sql.h can't be found
1,605,709,891,000
I'm adding a generic-package to Buildroot 2019.02.1. This package (fbi) includes <asm/page.h> in the fbtools.c, but the headers are not available in output/target. Compiling the package causes the following error: $ make fbi-rebuild [...] CC fbi.o CC fbtools.o fbtools.c:24:30: fatal error: asm/page.h: No such file or directory #include <asm/page.h> ^ compilation terminated. [...] I've added patches to and selected necessary packages for fbi: $ grep -E '^[^#].*(HEADERS|FBI|JPEG)' .config BR2_KERNEL_HEADERS_VERSION=y BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_9=y BR2_DEFAULT_KERNEL_HEADERS="4.9.17" BR2_PACKAGE_LINUX_HEADERS=y BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0=y [...] BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_9=y BR2_TOOLCHAIN_HEADERS_AT_LEAST="4.9" BR2_PACKAGE_FBI=y BR2_PACKAGE_JPEG=y BR2_PACKAGE_JPEG_SIMD_SUPPORT=y BR2_PACKAGE_LIBJPEG=y BR2_PACKAGE_HAS_JPEG=y BR2_PACKAGE_PROVIDES_JPEG="libjpeg" $ for i in `ls package/fbi/000*`; do echo $i; cat $i | grep -E '^[-+][^-+]'; done package/fbi/0001-fix-verion.patch - fprintf(stderr, "fbi version " VERSION + fprintf(stderr, "fbi version 1.32 " package/fbi/0002-fix-makefile.patch - @echo -e "$(make-config-q)" > $@ + @echo "$(make-config-q)" > $@ $ find output/ -name page.h output/build/linux-headers-4.9.17/fs/nilfs2/page.h output/build/linux-headers-4.9.17/include/asm-generic/page.h [...] output/build/linux-headers-4.9.17/arch/score/include/asm/page.h The kernel I use (also 4.9.17) is not part of Buildroot, but I think that shouldn't be a problem. What is the correct way to compile against the kernel headers within Buildroot? https://www.kraxel.org/releases/fbida/fbi_1.31.tar.gz
It seems impossible to compile against the headers without integrating them into the root file system. I tried to compile fbi out of the Buildroot tree, but this takes too much effort. I'm trying fbv instead of fbi, because it's already in Buildroot.
Buildroot: compile fbi against kernel headers
1,605,709,891,000
I used to have OpenCV3 from the Arch Linux pckage manager(pacman) and it worked fine but when I removed it and install OpenCV 3.4.1 and OpenCV-Contrib from source code nothing worked even the old project when I tryied to recompile them, here is the CMakeLists.txt file: cmake_minimum_required(VERSION 2.8) cmake_policy(SET CMP0012 NEW) project(Face_Detection) find_package(OpenCV 3.4.0 REQUIRED) message("OpenCV Version ${OpenCV_Version}") include_directories(${OpenCV_INCLUDE_DIRS}) link_directories(${OpenCV_LINK_DIRS}) set(SRC main.cpp) add_executable(${PROJECT_NAME} ${SRC}) target_link_libraries(${PROJECT_NAME} ${OpenCV_LIBS}) Here is the main.cpp file (for demonstrating, all prjects don't work anymore after recompiling them) #include "opencv2/core.hpp" #include "opencv2/highgui.hpp" #include "opencv2/face.hpp" #include "opencv2/imgproc.hpp" #include <stdio.h> #include <fstream> #include <sstream> using namespace cv; using namespace cv::face; using namespace std; //Normalize image static Mat norm_0_255(Mat _src){ Mat src (_src); //The returned normalized image Mat dst; switch (src.channels()){ case 1: normalize(src, dst, 0, 255, NORM_MINMAX, CV_8UC1); break; case 3: normalize(src, dst, 0, 255, NORM_MINMAX, CV_8UC3); break; default: src.copyTo(dst); break; } return dst; } //Read CSV which containts the paths to images static void read_csv(const string& filename, vector<Mat>& images, vector<int>& labels, char separator = ';'){ ifstream file(filename.c_str(), ifstream::in); if(!file){ string error_message = "No valid inout file was given\n"; CV_Error(Error::StsBadArg, error_message); } string line, path, classlabel; while(getline(file, line)){ stringstream liness(line); getline(liness, path, separator); getline(liness, classlabel); if(!path.empty() && !path.empty()){ images.push_back(imread(path, 0)); labels.push_back(atoi(classlabel.c_str())); } } } int main(int argc,const char* argv[]){ return 0; } Errors after recompiling the project cmake .. make The remainder errors are the same. Note:This code is from samples , and ofcourse this is part of it, other projects wouldn't work too although they are worked before I reinstalled it.
I have solved it by recompiling OpenCV and recompiling LPACKE for Compiling OpenCV I've used their docs and this blog post *Note for block post I haven't used the last two commands sudo sh -c 'echo "/usr/local/lib" >> /etc/ld.so.conf.d/opencv.conf' sudo ldconfig I used this blog as a guid, I didn't need all the stuff in it *Also I suggest that you should first learn about compiling from source(cmake and make) and also the structure of Linux system(you can find alot online), because the problem was that OpenCV can't found dependcies as someone said to me on G+ post.
Can't link opencv libraries via Cmake in Linux
1,605,709,891,000
Here is the information about my system and the compiler I use: Linux version 4.9.0-5-amd64 ([email protected]) (gcc version 6.3.0 20170516 (Debian 6.3.0-1 8) ) #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) clang version 5.0.1-svn325091-1~exp1 (branches/release_50) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin I have problem with building llvm-6.0.0 with libcxx. I downloaded all of them from llvm download page and put the source code like there: llvm-6.0 build llvm-6.0.0 ...(other stuff) tools clang projects libcxx libcxxabi And here is the command I used: #!/bin/bash #References: https://libcxx.llvm.org/docs/BuildingLibcxx.html cd build #The option for llvm starts from line 5, for libcxx starts from line 15 cmake -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_C_COMPILER=clang-5.0 \ -DCMAKE_CXX_COMPILER=clang++-5.0 \ -DCMAKE_INSTALL_PREFIX=/usr/local/ \ -DLLVM_INSTALL_BINUTILS_SYMLINKS=True \ -DLLVM_INSTALL_CCTOOLS_SYMLINKS=True \ -DLLVM_ENABLE_CXX1Y=True \ -DLLVM_ENABLE_EH=True \ -DLLVM_ENABLE_RTTI=True \ -DLLVM_ENABLE_LTO=Thin \ -DLIBCXX_ENABLE_ASSERTIONS=False \ -DLIBCXX_INSTALL_EXPERIMENTAL_LIBRARY=True \ -DLIBCXX_LIBDIR_SUFFIX=/usr/local/lib \ -DLIBCXX_BENCHMARK_NATIVE_STDLIB="libstdc++"\ -G Unix Makefiles \ .. cmake --build . The cmake gives: [ 0%] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o [ 0%] Linking CXX static library ../libLLVMDemangle.a [ 0%] Built target LLVMDemangle [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APSInt.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ARMBuildAttrs.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ARMAttributeParser.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ARMWinEH.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Allocator.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BinaryStreamError.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BinaryStreamReader.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BinaryStreamRef.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BinaryStreamWriter.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BlockFrequency.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BranchProbability.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/CachePruning.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/circular_raw_ostream.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Chrono.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/COM.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/CodeGenCoverage.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/CommandLine.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Compression.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ConvertUTF.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ConvertUTFWrapper.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/CrashRecoveryContext.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/DataExtractor.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Debug.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/DebugCounter.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/DeltaAlgorithm.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/DAGDeltaAlgorithm.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Error.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ErrorHandling.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/FileUtilities.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/FileOutputBuffer.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/FoldingSet.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/FormattedStream.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/FormatVariadic.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/GlobPattern.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/GraphWriter.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Hashing.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/IntEqClasses.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/IntervalMap.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/JamCRC.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/KnownBits.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/LEB128.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/LineIterator.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Locale.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/LockFileManager.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/LowLevelType.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ManagedStatic.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/MathExtras.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/MemoryBuffer.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/MD5.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/NativeFormatting.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Options.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Parallel.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/PluginLoader.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/PrettyStackTrace.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/RandomNumberGenerator.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Regex.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ScaledNumber.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ScopedPrinter.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/SHA1.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/SmallPtrSet.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/SmallVector.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/SourceMgr.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/SpecialCaseList.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Statistic.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/StringExtras.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/StringMap.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/StringPool.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/StringSaver.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/StringRef.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/SystemUtils.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/TarWriter.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/TargetParser.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ThreadPool.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Timer.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ToolOutputFile.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/TrigramIndex.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Triple.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Twine.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Unicode.cpp.o [ 1%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/YAMLParser.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/raw_os_ostream.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/raw_ostream.cpp.o [ 2%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regcomp.c.o [ 2%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regerror.c.o [ 2%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regexec.c.o [ 2%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regfree.c.o [ 2%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regstrlcpy.c.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/xxhash.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Atomic.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/DynamicLibrary.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Errno.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Host.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Memory.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Mutex.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Path.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Process.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Program.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/RWMutex.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/TargetRegistry.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ThreadLocal.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Threading.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Valgrind.cpp.o [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Watchdog.cpp.o [ 2%] Linking CXX static library ../libLLVMSupport.a [ 2%] Built target LLVMSupport [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/Error.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/Main.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/Record.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/SetTheory.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/StringMatcher.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/TableGenBackend.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/TGLexer.cpp.o [ 2%] Building CXX object lib/TableGen/CMakeFiles/LLVMTableGen.dir/TGParser.cpp.o [ 2%] Linking CXX static library ../libLLVMTableGen.a [ 2%] Built target LLVMTableGen [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/AsmMatcherEmitter.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/AsmWriterEmitter.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/AsmWriterInst.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/Attributes.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CallingConvEmitter.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeEmitterGen.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenHwModes.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenMapTable.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenRegisters.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenSchedule.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenTarget.cpp.o [ 2%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcherEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcherGen.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcherOpt.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcher.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DFAPacketizerEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DisassemblerEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/FastISelEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/FixedLenDecoderEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/GlobalISelEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/InfoByHwMode.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/InstrInfoEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/InstrDocsEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/IntrinsicEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/OptParserEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/PseudoLoweringEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/RegisterBankEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/RegisterInfoEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SDNodeProperties.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SearchableTableEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SubtargetEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SubtargetFeatureInfo.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/TableGen.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/Types.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86DisassemblerTables.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86EVEX2VEXTablesEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86FoldTablesEmitter.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86ModRMFilters.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86RecognizableInstr.cpp.o [ 4%] Building CXX object utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CTagsEmitter.cpp.o [ 4%] Built target obj.llvm-tblgen [ 4%] Linking CXX executable ../../bin/llvm-tblgen ../../lib/libLLVMSupport.a: error adding symbols: Archive has no index; run ranlib to add one clang: error: linker command failed with exit code 1 (use -v to see invocation) utils/TableGen/CMakeFiles/llvm-tblgen.dir/build.make:158: recipe for target 'bin/llvm-tblgen' failed make[2]: *** [bin/llvm-tblgen] Error 1 CMakeFiles/Makefile2:906: recipe for target 'utils/TableGen/CMakeFiles/llvm-tblgen.dir/all' failed make[1]: *** [utils/TableGen/CMakeFiles/llvm-tblgen.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 I tried to fix this problem by: Use cmake --build . --target clean to remove the built files and run cmake --build . again. Follow the instruction given above, change directory into lib, and run ranlib libLLVMSupport.a. But none of these worked: I ran cmake --build . again, and they gave: [ 0%] Built target LLVMDemangle [ 2%] Built target LLVMSupport [ 2%] Built target LLVMTableGen [ 4%] Built target obj.llvm-tblgen [ 4%] Linking CXX executable ../../bin/llvm-tblgen ../../lib/libLLVMSupport.a: error adding symbols: Archive has no index; run ranlib to add one clang: error: linker command failed with exit code 1 (use -v to see invocation) utils/TableGen/CMakeFiles/llvm-tblgen.dir/build.make:158: recipe for target 'bin/llvm-tblgen' failed make[2]: *** [bin/llvm-tblgen] Error 1 CMakeFiles/Makefile2:906: recipe for target 'utils/TableGen/CMakeFiles/llvm-tblgen.dir/all' failed make[1]: *** [utils/TableGen/CMakeFiles/llvm-tblgen.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 I checked the timestamp of lib/libLLVMSupport.a in method 2, and found it was not changed, means it was not regenerated by cmake --build .. How to fix this?
I have finally found out what really caused this error. The cmake was using gnu golden linker, and the archieve libLLVMSupport.a was composed of LLVM IR code, no wonder it went wrong. After I switched to using ld.lld-5.0, all errors were gone.
Can't add symbols to ../../lib/libLLVMSupport.a when building llvm-6.0.0 using llvm-5.0
1,517,398,443,000
So ages ago I knew how to do this but now I have forgot the last command. So for some odd reason alot of python apps I compile to the system and not just python apps don´t have uninstall options in the MAKEFILE. So someone told me to run python setup.py install --record installed-locations.txt instead of the usuall python setup.py install. I am awear I could go and look at that text file and delete each file manually with rm but I remember there was a command that ould look into that text file and automaticly remove them for me. The issue is I don´t remember this command. Does anyone know what command I am talking about or know of a command that could do this?
Found it. cat files.txt | xargs rm -rf So in summory to uninstall apps from system compiled with python follow these steps 1) Download the source code for the exsact version of said app if you do not have it already 2) Extract the file and cd into the extracted files 3) Run as root python setup.py install --record files.txt 4) Now run as root cat files.txt | xargs rm -rf The application should now be uninstalled. If need be go clean up all the config and setting files in your home directory to regain some more space.
Uninstall Python Compiled App on Debian
1,517,398,443,000
I am writing a set of bash scripts. The first, wrapper calls two scripts: do_something and do_something_else. In pseudo code: $ wrapper do_something if exitcode of do_something = 0 then do_something_else else exit with error fi exit success This would generate a log file: $ cat /var/logs/wrapper.log | tail -3 Deleting file 299 Deleting file 300 wrapper ran successfully on 01/01/18 00:01:00 GMT I have two goals: create a log of the entire process. In other words, everything thatdo_something, do_something_else and wrapper send to stdout and stderr I want in one log file that shows the daily run of this script so I can grep for errors. I want to pre-compile do_something, do_something_else and wrapper so I can put them in /usr/bin and scp them to all my systems. This way I have one source in dev and quick running un-editable code in prod. Is this possible?
Here's a sample of how to handle this scenario in one script, without losing the functionality that the OP wants, which is: ability to run multiple blocks of logic, all of them, at once, or one at a time. Ability to log these actions to a file. This is a simple example. If you treat the scripting language like you would any other language, and write organized code, suddenly you can do all kinds of stuff with it. The trick is to not leave blocks of loose logic outside of functions, that way you can switch the stuff easily, use one piece, not the other, debug sections, add a logging function, which is what I'd do usually, error_handler(), and so on. With almost no extra work, that is, you end up with a simple but clean and easy to maintain application, not a bunch of lines of random actions stacked on top of each other. file: my_stuff #!/usr/bin/env bash logfile='logfile.log' function main() { case "$1" in run-all) block_1 block_2 ;; run-1) block_1 ;; run-2) block_2 ;; *) echo 'No start option provided. Exiting' exit 1 ;; esac } function block_1(){ do_something if [ "$?" == 0 ]; then do_something_else echo "Deleting file 299" >> $logfile echo "Deleting file 300" >> $logfile echo "wrapper ran successfully on 01/01/18 00:01:00 GMT" >> $logfile else exit "$?" fi } function block_2(){ do_something if [ "$?" == 0 ]; then do_something_else echo "Deleting file 299" >> $logfile echo "Deleting file 300" >> $logfile echo "wrapper ran successfully on 01/01/18 00:01:00 GMT" >> $logfile else exit "$?" fi } # $@ is the list of start arguments, which main will use # with $1, $2, and so on. main $@ You'd run this like so: ./my_stuff 'run-all' This is of course just an example, but really all you do is organize the logic, arrange it the way you'd do with any language, and then trigger the desired actions. I find that if I start shell scripts assuming they will be used and maintained, and if I write them using functions, then they are as flexible and easy to maintain as any other programming I do.
Create a multi-script bash script that is compiled and keeps a log
1,517,398,443,000
I'm trying to install last TauDEM (Terrain Analysis Using Digital Elevation Models) release in GNU/Linux Debian for using with Python Processing in QGIS. Installing instructions can be watched here. After installing some dependencies (cmake, mpi-default-bin) in my system, when I ran following command: CXX=mpicxx cmake -DCMAKE_INSTALL_PREFIX=/usr/local .. I got a successfully result: -- The C compiler identification is GNU 4.9.2 -- The CXX compiler identification is GNU 4.9.2 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/mpicxx -- Check for working CXX compiler: /usr/bin/mpicxx -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found MPI_C: /usr/lib/libmpi.so;/usr/lib/i386-linux-gnu/libdl.so;/usr/lib/i386-linux-gnu/libhwloc.so -- Found MPI_CXX: /usr/lib/libmpi_cxx.so;/usr/lib/libmpi.so;/usr/lib/i386-linux-gnu/libdl.so;/usr/lib/i386-linux-gnu/libhwloc.so -- Found GDAL: /usr/lib/libgdal.so -- Configuring done -- Generating done -- Build files have been written to: /home/zeito/TauDEM-5.3.8/src/build However, make command produced this kind of error: ‘OFTInteger64’ was not declared in this scope as main part into this complete context: Scanning dependencies of target aread8 [ 0%] Building CXX object CMakeFiles/aread8.dir/aread8mn.cpp.o [ 1%] Building CXX object CMakeFiles/aread8.dir/aread8.cpp.o [ 2%] Building CXX object CMakeFiles/aread8.dir/commonLib.cpp.o /home/zeito/TauDEM-5.3.8/src/commonLib.cpp: In function ‘char* getLayername(char*)’: /home/zeito/TauDEM-5.3.8/src/commonLib.cpp:399:10: warning: address of local variable ‘layername’ returned [-Wreturn-local-addr] char layername[MAXLN]; ^ [ 3%] Building CXX object CMakeFiles/aread8.dir/tiffIO.cpp.o [ 4%] Building CXX object CMakeFiles/aread8.dir/ReadOutlets.cpp.o /home/zeito/TauDEM-5.3.8/src/ReadOutlets.cpp: In function ‘int readoutlets(char*, char*, int, int, OGRSpatialReferenceH, int*, double*&, double*&, int*&)’: /home/zeito/TauDEM-5.3.8/src/ReadOutlets.cpp:165:24: error: ‘OFTInteger64’ was not declared in this scope else if (idtype == OFTInteger64) { ^ /home/zeito/TauDEM-5.3.8/src/ReadOutlets.cpp:166:63: error: ‘OGR_F_GetFieldAsInteger64’ was not declared in this scope id[nxy] = (int)OGR_F_GetFieldAsInteger64(hFeature1, idfld); ^ CMakeFiles/aread8.dir/build.make:146: recipe for target 'CMakeFiles/aread8.dir/ReadOutlets.cpp.o' failed make[2]: *** [CMakeFiles/aread8.dir/ReadOutlets.cpp.o] Error 1 CMakeFiles/Makefile2:60: recipe for target 'CMakeFiles/aread8.dir/all' failed make[1]: *** [CMakeFiles/aread8.dir/all] Error 2 Makefile:117: recipe for target 'all' failed make: *** [all] Error 2 After searching for a while, I couldn't found out any adequate answer. My question is: I missed to install some important dependency for obtaining this type of error.
To install Taudem in GNU/Linux Debian you can download installation script from this link: taudem_ubuntu.tar.bz2 After unpacking it, move to that folder and run script (as superuser) with following command: ./taudem_ubuntu.sh Successfully execution of script also requires these dependencies: cmake, mpi-default-bin After installation, mark check box in Processing options and then, launch Processing Toolbox (Processing menu). Taudem geoalgorithms should be available.
How to solve building error where a variable "... was not declared in this scope"
1,517,398,443,000
I am trying to run code for a video processing application on litmus rt using this, however I am getting the error below. bin/base_task.c: In function ‘main’: bin/base_task.c:151:6: error: ‘codec’ is deprecated [-Werror=deprecated-declarations] if(pFormatCtx->streams[i]->codec->codec_type==AVMEDIA_TYPE_VIDEO) { ^ In file included from bin/base_task.c:20:0: ./include/libavformat/avformat.h:893:21: note: declared here AVCodecContext *codec; ^ bin/base_task.c:159:4: error: ‘codec’ is deprecated [-Werror=deprecated-declarations] pCodecCtx=pFormatCtx->streams[videoStream]->codec; ^
It's not an error per se, it's a warning that's treated as an error because of the -Werror=deprecated-declarations flag. If you disable that the build will proceed further.
codec is deprecated [closed]
1,517,398,443,000
I have to compile buildroot to generate embedded os for raspberry pi. I have an error when I compile buildroot source code this is the error below drivers/staging/olpc_dcon/Kconfig:36: syntax error drivers/staging/olpc_dcon/Kconfig:35: unknown option "should" drivers/staging/Kconfig:37: can't open file "drivers/staging/rtl8192e/Kconfig" make[3]: * [oldconfig] Error 1 make[2]: [oldconfig] Error 2 make[1]: [/home/oussema/xenomai_project/builtroot/essai3/versatile-pb-next-9d8724f884e9280cb406d1a1be370cf1ca0a71d0/buildroot-2015.08.1/output/build/linux-custom/.config] Error 2 make: * [_all] Error 2
This is not a Buildroot error, it's an error happening while Buildroot is compiling the Linux kernel source code, so the problem is in the specific Linux kernel version you have selected, not in Buildroot.
buildroot compiling error
1,517,398,443,000
I'd like to install a very old PHP version on debian 8. Namely PHP 5.1.0. I will not use this in production, it is just for testing purposes. However, if I try to compile it I run into problems with the dom module. After a little bit of research I found out that libxml2 versions >= 2.9 cause problems with those older PHP versions. Now I'd like to know if it is possible to compile libxml2 2.8, save it somewhere and use it to compile php 5.1. If it's possible, can you tell me how?
You definitely can do this, but it can get annoying. I'd put libxml 2.8 in a separate prefix (./configure --prefix=/path/to/prefix/) alongside PHP 5.1.0 (e.g. /opt/php510/ or /usr/local/php510/), since you don't want to risk overriding the newer library with an older one. You'd definitely be best off if you build libxml 2.8 statically, so it gets baked into PHP and you can avoid 'shared library hell' when starting the program. Typically this would be done by adding --disable-shared --enable-static to the configure flags. Then on the PHP end, you'd have to configure it to use the same prefix, and also add the libxml 2.8 library paths to your GCC invocation. If it uses autoconf to build (./configure scripts are usually autoconf generated), you'd want to run something like CFLAGS=-I/opt/php510/include LDFLAGS=-L/opt/php510/lib ./configure --prefix=/opt/php510. CFLAGS is a variable that contains arguments passed to gcc when creating .o object files. -I/path tells GCC to look for headers ("includes", or .h files) in /path in before looking in the default list (typically /usr/include and /include IIRC). LDFLAGS is a variable that contains arguments passed to the linker (typically ld, although it is also possible to use gcc as a linker to combine .o files into an executable program. autoconf respects this variable in both usages). -L/path tells the linker to look for library files (static .a files or shared object .so files) in /path. If you link libxml 2.8 as a shared library you will get an error like libxml.so.2.8 not found since /etc/ld.so.conf hasn't been told to look for shared libraries in /opt/php510/lib. That's why I recommend using a statically linked version. If you have any problems doing this or if something is using a different build system, let me know. You also might be able to just fix PHP to use the libxml >= 2.9 versions of whatever functions are causing it to mess up, although finding old deprecation notices for already-removed functions is sometimes difficult.
How can I compile an old PHP version and dependencies on debian 8? (PHP 5.1.0 in this case)
1,517,398,443,000
I want to compile supertuxkart for notebook on my main computer (v-mint, with distcc daemon). My actions: Clone git+svn repos from official sources. (compile/{stk-code,stk-assets}). cd compile/stk-code mkdir cmake_build && cmake_build cmake .. -DCMAKE_CXX_COMPILER=/usr/bin/distcc -DCMAKE_CXX_FLAGS_RELEASE=g++ export DISTCC_HOSTS=v-mint make -j 14 Compilling... Linking CXX executable bin/supertuxkart //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status distcc[5704] ERROR: compile (null) on localhost failed make[2]: *** [bin/supertuxkart] Error 1 make[1]: *** [CMakeFiles/supertuxkart.dir/all] Error 2 make: *** [all] Error 2 What is wrong?
Create small script (I'm using distg++ in my PATH) contains it: distcc g++ "$@" and run cmake: cmake .. -DCMAKE_CXX_COMPILER=distg++
Distcc ld error
1,517,398,443,000
Conspy is a neat remote control program for the TTY virtual consoles in Linux. I am trying to compile the latest v1.10-1 version, but after installing all the supposedly needed packages, I still have a compilation error that stops the procedure: luis@utilite-desktop:~/Temporal/conspy/conspy-1.10$ make clean test -z "conspy" || rm -f conspy test -z "*~" || rm -f *~ rm -f *.o luis@utilite-desktop:~/Temporal/conspy/conspy-1.10$ make gcc -DPACKAGE_NAME=\"conspy.c\" -DPACKAGE_TARNAME=\"conspy-c\" -DPACKAGE_VERSION=\"1.10\" -DPACKAGE_STRING=\"conspy.c\ 1.10\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"conspy-c\" -DVERSION=\"1.10\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_GETOPT_H=1 -DHAVE_STDARG_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_UNISTD_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void -DHAVE_SELECT=1 -DHAVE_STRTOL=1 -I. -g -O2 -MT conspy.o -MD -MP -MF .deps/conspy.Tpo -c -o conspy.o conspy.c conspy.c: In function 'process_command_line': conspy.c:352:11: warning: ignoring return value of 'strtol', declared with attribute warn_unused_result [-Wunused-result] mv -f .deps/conspy.Tpo .deps/conspy.Po gcc -g -O2 -o conspy conspy.o conspy.o: In function `cleanup': /home/luis/Temporal/conspy/conspy-1.10/conspy.c:542: undefined reference to `endwin' conspy.o: In function `conspy': /home/luis/Temporal/conspy/conspy-1.10/conspy.c:624: undefined reference to `wmove' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:625: undefined reference to `wclrtoeol' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:658: undefined reference to `wmove' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:659: undefined reference to `waddchnstr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:660: undefined reference to `wchgat' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:680: undefined reference to `wmove' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:681: undefined reference to `waddchnstr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:682: undefined reference to `wchgat' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:685: undefined reference to `wmove' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:686: undefined reference to `wrefresh' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:615: undefined reference to `LINES' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:615: undefined reference to `LINES' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:699: undefined reference to `endwin' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:700: undefined reference to `wrefresh' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:552: undefined reference to `LINES' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:552: undefined reference to `stdscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:552: undefined reference to `COLS' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:552: undefined reference to `curscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:729: undefined reference to `wrefresh' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:617: undefined reference to `stdscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:617: undefined reference to `stdscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:618: undefined reference to `stdscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:618: undefined reference to `stdscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:617: undefined reference to `wmove' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:618: undefined reference to `wclrtobot' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:779: undefined reference to `stdscr' conspy.o: In function `setup': /home/luis/Temporal/conspy/conspy-1.10/conspy.c:499: undefined reference to `initscr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:500: undefined reference to `nonl' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:515: undefined reference to `has_colors' conspy.o: In function `main': /home/luis/Temporal/conspy/conspy-1.10/conspy.c:278: undefined reference to `tigetstr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:280: undefined reference to `tigetstr' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:280: undefined reference to `putp' conspy.o: In function `setup': /home/luis/Temporal/conspy/conspy-1.10/conspy.c:517: undefined reference to `start_color' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:529: undefined reference to `init_pair' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:519: undefined reference to `acs_map' /home/luis/Temporal/conspy/conspy-1.10/conspy.c:519: undefined reference to `COLOR_PAIRS' collect2: ld returned 1 exit status make: *** [conspy] Error 1 The compilation yields similar errors on: Ubuntu 14.04 LTS on PC (portable computer from ASUS). Ubuntu 12.04 LTS on Utilite from Compulab (an embedded device like RaspBerry). Why is the building failing with that undefined reference error and how could it be solved?
For those arriving here, these are the needed packages for ConSpy: # apt-get install libtool libncurses5-dev fakeroot sudo automake devscripts The problem (or so I believe): as @SteelDriver pointed, between each make attempt I was not doing the needed ./configure. UPDATE 2015-10-16: There is no need to do /configure since v1.13 and later. In fact, there is no such script on the sources no more. It seems to be included on the compilation script.
Conspy: "Undefined reference" errors when trying to compile the latest version
1,517,398,443,000
Trying to compile obs on debian like here described: https://github.com/jp9000/obs-studio/blob/master/INSTALL gives me this error: Linking C shared library libobs.so /usr/bin/ld: /usr/local/lib/../lib/libavcodec.a(avpacket.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/../lib/libavcodec.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status libobs/CMakeFiles/libobs.dir/build.make:1591: recipe for target 'libobs/libobs.so.0' failed make[2]: *** [libobs/libobs.so.0] Error 1 CMakeFiles/Makefile2:333: recipe for target 'libobs/CMakeFiles/libobs.dir/all' failed make[1]: *** [libobs/CMakeFiles/libobs.dir/all] Error 2 Makefile:137: recipe for target 'all' failed make: *** [all] Error 2 I already tried compiling it with -fPIC but that gave me this error: make: PIC: File or Directory not found make: *** No rule to make target 'PIC'. stop.
I just followed this guide here then it worked: https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
Compile OpenBroadcaster on Debian
1,431,359,411,000
I'm trying to compile Solr 4.10.4 (on Ubuntu 14.04) from source so that I can make use of a patch. I've applied the patch, and successfully compiled the source code. But where do I find the compiled Solr WAR file? When you download the binary Solr distribution, it exists under dist/solr-<version>.war. No dist directory and no solr-<version>.war exists anywhere under the base source directory, solr, solr/build, lucene, or lucene/build. I must be missing something simple. After following the instructions from the README.txt and an error about missing Ivy as a dependency, I ran the following to compile Solr: ant ivy-bootstrap ant compile
After you've compiled Solr, you must go to the solr/ directory, and run the ant command dist in order to build the JARs: ant dist The Solr WAR file will now be present at solr/dist/solr-<version>.war.
Compile Solr source code into WAR
1,431,359,411,000
I am building my first LFS 7.5 using Linux Mint-13 (32-bit) While preparing Binutils for compilation(5.4.1): ../binutils-2.24/configure \ --prefix=/tools \ --with-sysroot=$LFS \ --with-lib-path=/tools/lib \ --target=$LFS_TGT \ --disable-nls \ --disable-werror. I have got following error : bash: --with-sysroot=/mnt/lfs--with-lib-path=/tools/lib--target=i686- lfs-linux-gnu: No such file or directory This is the output I'm getting: lfs@jaassi-virtual-machine /mnt/lfs/tools/binutils-2.24 $ ../binutils-2.24/configure \ --prefix=/tools/binutils-2.24 binutils-2.24/ binutils-2.24.tar.bz2 > --prefix=/tools/binutils-2.24 binutils-2.24/ binutils-2.24.tar.bz2 > --prefix=/tools/binutils-2.24 > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed checking for gawk... gawk checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... 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 for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking whether g++ accepts -static-libstdc++ -static-libgcc... yes checking for gnatbind... no checking for gnatmake... no checking whether compiler driver understands Ada... no checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2 checking for objdir... .libs checking for version 0.10 of ISL... no checking for version 0.11 of ISL... no checking for default BUILD_CONFIG... checking for bison... bison -y checking for bison... bison checking for gm4... no checking for gnum4... no checking for m4... m4 checking for flex... no checking for lex... no checking for flex... no checking for makeinfo... no checking for expect... no checking for runtest... no checking for ar... ar checking for as... as checking for dlltool... no checking for ld... ld checking for lipo... no checking for nm... nm checking for ranlib... ranlib checking for strip... strip checking for windres... no checking for windmc... no checking for objcopy... objcopy checking for objdump... objdump checking for readelf... readelf checking for cc... cc checking for c++... c++ checking for gcc... gcc checking for gcj... no checking for gfortran... no checking for gccgo... no checking for ar... ar checking for as... as checking for dlltool... no checking for ld... ld checking for lipo... no checking for nm... nm checking for objdump... objdump checking for ranlib... ranlib checking for readelf... readelf checking for strip... strip checking for windres... no checking for windmc... no checking where to find the target ar... just compiled checking where to find the target as... just compiled checking where to find the target cc... host tool checking where to find the target c++... host tool checking where to find the target c++ for libstdc++... host tool checking where to find the target dlltool... just compiled checking where to find the target gcc... host tool checking where to find the target gcj... host tool checking where to find the target gfortran... host tool checking where to find the target gccgo... host tool checking where to find the target ld... just compiled checking where to find the target lipo... host tool checking where to find the target nm... just compiled checking where to find the target objdump... just compiled checking where to find the target ranlib... just compiled checking where to find the target readelf... just compiled checking where to find the target strip... just compiled checking where to find the target windres... just compiled checking where to find the target windmc... just compiled checking whether to enable maintainer-specific portions of Makefiles... no configure: creating ./config.status config.status: creating Makefile lfs@jaassi-virtual-machine /mnt/lfs/tools/binutils-2.24 $ --with-sysroot=$LFS $LFS $LFS_TGT lfs@jaassi-virtual-machine /mnt/lfs/tools/binutils-2.24 $ --with-sysroot=$LFS\ > --with-lib-path=/tools/lib\ > --target=$LFS_TGT \ > --disable-nls\ > --disable-werror bash: --with-sysroot=/mnt/lfs--with-lib-path=/tools/lib--target=i686- lfs-linux-gnu: No such file or directory How can I resolve this?
There must be space between parameters.
Getting error during Installation of Cross Binutils in Linux From Scratch -7.5
1,431,359,411,000
Can I use a native build from fedora on ubuntu? What is the difference in compilation between distributions?
The location of libraries might differ between fedora on ubuntu. This could cause a build for fedora not to function on ubuntu and vice versa.
Same native compilation for different distributions
1,431,359,411,000
Somewhere between the 13 and 13.1 releases I was no longer able to compile XBMC from source. I was able to compile v13 when it was first released (from the Gotham branch). Then, 13.1 was announced and I decided not to try the betas/RCs; so I have not attempted to compile those. When the final 13.1 version was released, I tried to compile that one, with the same procedure as I've used every time with success. But this time, it didn't work... I'm failing in the "./configure" step with "could not find a required library". The command terminates with something like: (...) checking for TAGLIB... yes checking for CDIO... yes checking for LIBBLURAY... yes checking for libbluray soname... libbluray.so.1 checking for bd_register_argb_overlay_proc in -lbluray... no checking for library containing iconv_open... no checking for library containing libiconv_open... no configure: error: Could not find a required library. Please see the README for your platform. Here's the full config.log file: http://pastebin.com/nGynLkX6 I'm not sure that's the problem but I manually downloaded, compiled and installed libiconv from http://www.gnu.org/software/libiconv/, it didn't seem to help though. In case it's relevant, I always execute the following commands (in that specific order) to compile a new XBMC version: git clean -xfd git reset --hard git pull --rebase make -C lib/taglib sudo make -C lib/taglib install ./bootstrap ./configure --disable-debug --disable-pulse --disable-vaapi --enable-goom make sudo make install What am I missing here? UPDATE! I have upgraded zlib1g and now I was able to finish the configure step. However, compiling with make, eventually gives me errors on "undefined reference" to libiconv, libiconv_open and libiconv_close. Ideas?
I had to update zlib1g and now it worked :) For the record, here's what I said in the comments above and why I don't have everything updated: I must be missing some package update. The thing is, I'm on Debian Squeeze and most dependencies for this to work must come from Wheezy. I just need to find out which one I need to update from Wheezy to get it to work again. (I can't upgrade to Wheezy because I'm using OpenMediaVault which does not support Wheezy yet). Another problem was that I had to do make uninstall on the manually downloaded iconv package because that was conflicting with something else. Now I was successful :)
Library missing compiling XBMC from source
1,431,359,411,000
I am tryting to make initrd file system following [this tutorial][1] My host system is RHEL 6 64 bit. I am unable to get the required command: genext2fs No rpm is available for it, neither yum is helping me. I hope there is an alternate to this command.
If you want genext2fs, it's easy to find; build it from source. But you probably don't want it. Create an initramfs instead. That's the normal method these days.
Is there any alternative to genext2fs in RHEL?
1,431,359,411,000
I am building the sunxi-linux kernel for a cubieboard and I need the carl9170 driver to make a usb wifi adapter work. I am using the 3.4 sunxi kernel, and no matter what I do in xconfig, I cannot enable the option CONFIG_CARL9170 because it is greyed out. I tried satifying all of its dependcies, but it is still greyed out. How can I enable the carl9170 driver?
It took a long time, but I got it. After running make sun4i_defconfig run make menuconfig and enable wireless and then under wireless make sure CONFIG_80211 is enabled, its probably called mac80211 driver. Then go down to wireless lan and enable atheros wifi. Then finally it will allow you to enable the carl9170 driver. It will probably called something like ath9170 community driver. For some reason this changed the name of the kernel build to include dirty at the end, but it did not matter as it still worked for me.
Enabling carl9170 in xconfig
1,431,359,411,000
I wonder, is it possible to compile Unix along with a my custom program so that it runs only my custom program on start up of computer, as if my program starting with boot up?
If you mean you only want users to be able to run one program, you can replace the user's shell with the absolute path to the program in the passwd file - assuming a local passwd file..
Compile Unix with a custom application [duplicate]
1,431,359,411,000
I have successfully build OpenCV using this linux install tutorial on an Ubuntu distribution in the past, but recently, I needed to build it on a Arch Linux distribution. The command cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local .. -Wno-dev produces an apparently error free log including the following lines Detected version of GNU GCC: 52 (502) ... <skipped lines> ... C Compiler: /usr/bin/cc But when I run the make command, I get the following error /usr/bin/gcc-5: No such file or directory CMake Error at cuda_compile_generated_gpu_mat.cu.o.cmake:208 (message): Error generating /home/cecilia/opencv-3.0.0/build/modules/core/CMakeFiles/cuda_compile.dir /src/cuda/./cuda_compile_generated_gpu_mat.cu.o This is clearly the wrong path. gcc is at usr/bin/gcc. To double check that gcc is on the system path, I ran gcc -v producing Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/gcc/src/gcc-5.2.0/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --disable-multilib --disable-werror --enable-checking=release --with-default-libstdcxx-abi=gcc4-compatible Thread model: posix gcc version 5.2.0 (GCC) Which matches the version number from the cmake log. Why does cmake detect the correct gcc version but make use the wrong path? And how can I resolve this error? p.s. The full cmake log is below in case I missed something that you can spot. -- Detected version of GNU GCC: 52 (502) -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found suitable version "1.2.8", minimum required is "1.2.3") -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8") -- Found OpenEXR: /lib64/libIlmImf.so -- Looking for linux/videodev.h -- Looking for linux/videodev.h - not found -- Looking for linux/videodev2.h -- Looking for linux/videodev2.h - found -- Looking for sys/videoio.h -- Looking for sys/videoio.h - not found -- Looking for libavformat/avformat.h -- Looking for libavformat/avformat.h - found -- Looking for ffmpeg/avformat.h -- Looking for ffmpeg/avformat.h - not found -- found IPP (ICV version): 8.2.1 [8.2.1] -- at: /home/cecilia/opencv-3.0.0/3rdparty/ippicv/unpack/ippicv_lnx -- CUDA detected: 7.5 -- CUDA NVCC target flags: -gencode;arch=compute_20,code=sm_20;-gencode;arch=compute_20,code=sm_21;-gencode;arch=compute_30,code=sm_30;-gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_30,code=compute_30 -- To enable PlantUML support, set PLANTUML_JAR environment variable or pass -DPLANTUML_JAR=<filepath> option to cmake -- Could NOT find PythonInterp: Found unsuitable version "1.4", but required is at least "3.4" (found /usr/bin/python3.4) -- Could NOT find PythonInterp: Found unsuitable version "1.4", but required is at least "3.2" (found ) -- Found apache ant 1.9.6: /bin/ant -- Could NOT find Matlab (missing: MATLAB_MEX_SCRIPT MATLAB_INCLUDE_DIRS MATLAB_ROOT_DIR MATLAB_LIBRARIES MATLAB_LIBRARY_DIRS MATLAB_MEXEXT MATLAB_ARCH MATLAB_BIN) -- Found VTK ver. 6.3.0 (usefile: /usr/lib/cmake/vtk-6.3/UseVTK.cmake) -- Assume that non-module dependency is available: /usr/lib/x86_64-linux-gnu/libz.so (for module opencv_core) -- Assume that non-module dependency is available: /usr/lib64/libgl2ps.so (for module opencv_viz) -- videoio: Removing WinRT API headers by default -- -- General configuration for OpenCV 3.0.0 ===================================== -- Version control: unknown -- -- Platform: -- Host: Linux 4.2.5-1-ARCH x86_64 -- CMake: 3.3.2 -- CMake generator: Unix Makefiles -- CMake build tool: /usr/bin/make -- Configuration: RELEASE -- -- C/C++: -- Built as dynamic libs?: YES -- C++ Compiler: /usr/bin/c++ (ver 5.2.0) -- C++ flags (Release): -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wno-narrowing -Wno-delete-non-virtual-dtor -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -O3 -DNDEBUG -DNDEBUG -- C++ flags (Debug): -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wno-narrowing -Wno-delete-non-virtual-dtor -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -fvisibility-inlines-hidden -g -O0 -DDEBUG -D_DEBUG -- C Compiler: /usr/bin/cc -- C flags (Release): -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wno-narrowing -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -O3 -DNDEBUG -DNDEBUG -- C flags (Debug): -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wno-narrowing -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse -msse2 -mno-avx -msse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -ffunction-sections -fvisibility=hidden -g -O0 -DDEBUG -D_DEBUG -- Linker flags (Release): -- Linker flags (Debug): -- Precompiled headers: YES -- Extra dependencies: /lib64/libwebp.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /lib64/libtiff.so /lib64/libjasper.so /lib64/libjpeg.so /lib64/libImath.so /lib64/libIlmImf.so /lib64/libIex.so /lib64/libHalf.so /lib64/libIlmThread.so gtk-3 gdk-3 pangocairo-1.0 pango-1.0 atk-1.0 cairo-gobject cairo gdk_pixbuf-2.0 gio-2.0 gthread-2.0 gstvideo-1.0 gstapp-1.0 gstbase-1.0 gstriff-1.0 gstpbutils-1.0 gstreamer-1.0 gobject-2.0 glib-2.0 dc1394 v4l1 v4l2 avcodec-ffmpeg avformat-ffmpeg avutil-ffmpeg swscale-ffmpeg avresample gphoto2 gphoto2_port exif /lib64/libbz2.so /usr/lib64/libfreetype.so /usr/lib64/libgl2ps.so /usr/lib64/libjpeg.so /usr/lib64/libpng.so /usr/lib64/libtiff.so /usr/lib64/libz.so vtkCommonColor vtkCommonComputationalGeometry vtkCommonCore vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath vtkCommonMisc vtkCommonSystem vtkCommonTransforms vtkDICOMParser vtkFiltersCore vtkFiltersExtraction vtkFiltersGeneral vtkFiltersGeometry vtkFiltersModeling vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkIOCore vtkIOExport vtkIOGeometry vtkIOImage vtkIOPLY vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingHybrid vtkInteractionStyle vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PS vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL vtkalglib vtkftgl vtkmetaio vtksys dl m pthread rt cudart nppc nppi npps cufft -- 3rdparty dependencies: ippicv -- -- OpenCV modules: -- To be built: hal cudev core cudaarithm flann imgproc ml video viz cudabgsegm cudafilters cudaimgproc cudawarping imgcodecs photo shape videoio cudacodec highgui objdetect ts features2d calib3d cudafeatures2d cudalegacy cudaobjdetect cudaoptflow cudastereo java stitching superres videostab -- Disabled: world -- Disabled by dependency: - -- Unavailable: python2 python3 -- -- GUI: -- QT: NO -- GTK+ 3.x: YES (ver 3.18.2) -- GThread : YES (ver 2.46.1) -- GtkGlExt: NO -- OpenGL support: NO -- VTK support: YES (ver 6.3.0) -- -- Media I/O: -- ZLib: /usr/lib/x86_64-linux-gnu/libz.so (ver 1.2.8) -- JPEG: /lib64/libjpeg.so (ver ) -- WEBP: /lib64/libwebp.so (ver encoder: 0x0202) -- PNG: /usr/lib/x86_64-linux-gnu/libpng.so (ver ..) -- TIFF: /lib64/libtiff.so (ver 42 - 4.0.6) -- JPEG 2000: /lib64/libjasper.so (ver 1.900.1) -- OpenEXR: /lib64/libImath.so /lib64/libIlmImf.so /lib64/libIex.so /lib64/libHalf.so /lib64/libIlmThread.so (ver 2.2.0) -- GDAL: NO -- -- Video I/O: -- DC1394 1.x: NO -- DC1394 2.x: YES (ver 2.2.3) -- FFMPEG: YES -- codec: YES (ver 56.41.100) -- format: YES (ver 56.36.100) -- util: YES (ver 54.27.100) -- swscale: YES (ver 3.1.101) -- resample: YES (ver 2.1.0) -- gentoo-style: YES -- GStreamer: -- base: YES (ver 1.6.1) -- video: YES (ver 1.6.1) -- app: YES (ver 1.6.1) -- riff: YES (ver 1.6.1) -- pbutils: YES (ver 1.6.1) -- OpenNI: NO -- OpenNI PrimeSensor Modules: NO -- OpenNI2: NO -- PvAPI: NO -- GigEVisionSDK: NO -- UniCap: NO -- UniCap ucil: NO -- V4L/V4L2: Using libv4l1 (ver 1.6.3) / libv4l2 (ver 1.6.3) -- XIMEA: NO -- Xine: NO -- gPhoto2: YES -- -- Other third-party libraries: -- Use IPP: 8.2.1 [8.2.1] -- at: /home/cecilia/opencv-3.0.0/3rdparty/ippicv/unpack/ippicv_lnx -- Use IPP Async: NO -- Use Eigen: NO -- Use TBB: NO -- Use OpenMP: NO -- Use GCD NO -- Use Concurrency NO -- Use C=: NO -- Use pthreads for parallel for: -- YES -- Use Cuda: YES (ver 7.5) -- Use OpenCL: YES -- -- NVIDIA CUDA -- Use CUFFT: YES -- Use CUBLAS: NO -- USE NVCUVID: NO -- NVIDIA GPU arch: 20 21 30 35 -- NVIDIA PTX archs: 30 -- Use fast math: NO -- -- OpenCL: -- Version: dynamic -- Include path: /home/cecilia/opencv-3.0.0/3rdparty/include/opencl/1.2 -- Use AMDFFT: NO -- Use AMDBLAS: NO -- -- Python 2: -- Interpreter: /usr/bin/python2.7 (ver 2.7.10) -- -- Python 3: -- Interpreter: NO -- -- Python (for build): /usr/bin/python2.7 -- -- Java: -- ant: /bin/ant (ver 1.9.6) -- JNI: /usr/lib/jvm/default-java/include /usr/lib/jvm/default-java/include/linux /usr/lib/jvm/default-java/include -- Java wrappers: YES -- Java tests: YES -- -- Matlab: -- mex: NO -- -- Documentation: -- Doxygen: /usr/bin/doxygen (ver 1.8.10) -- PlantUML: NO -- -- Tests and samples: -- Tests: YES -- Performance tests: YES -- C/C++ Examples: NO -- -- Install path: /usr/local -- -- cvconfig.h is in: /home/cecilia/opencv-3.0.0/build -- ----------------------------------------------------------------- -- -- Configuring done -- Generating done -- Build files have been written to: /home/cecilia/opencv-3.0.0/build
I copied the opencv directory from my Ubuntu machine and assumed that cmake would overwrite any previously set variables. However, I believe the CMakeCache.txt was not overwritten, leading to the misidentified path. Easy fix: Download clean opencv distribution from http://opencv.org/ Follow tutorial as before.
Building OpenCV on Arch Linux can't find gcc [closed]
1,431,359,411,000
Where's the path of compiled packages from source on debian? for example: git clone git://github.com/lightspark/lightspark.git cd lightspark dpkg-buildpackage [...long output...] dpkg-buildpackage: full upload; Debian-native package (full source is included) Then the packages is compiled successfully, but where the package (.deb) and source packages is located?
The binary and source packages that are generated are written to the directory that is one level above the top level source directory. In your case the top level source directory is lightspark, so it will be in the directory above lightspark. However, you could have easily discovered this by a look at some of the extensive Debian packaging documentation out there. The Debian New Maintainer's Guide, for example. Tip. When copying source, create a separate directory for each source package and then put the source in a subdirectory. E.g. /usr/local/src/lightspark$ git clone git://github.com/lightspark/lightspark.git Then the generated Debian packages will be in /usr/local/src/lightspark.
Where's the path of compiled packages
1,431,359,411,000
When I type the command ./configure --prefix.... the result goes like this : checking whether the C compiler works... no configure: error: in `/root/Downloads/agensgraph': configure error: C compiler cannot create executables See `config.log' for more details My config.log is the following: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by PostgreSQL configure 9.6.2, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --prefix=/usr/local/agensgraph --enable-cassert --enable-debug CFLAGS=-ggdb -0g -g3 -fno-omit-frame-pointer ## --------- ## ## Platform. ## ## --------- ## hostname = cll uname -m = x86_64 uname -r = 3.10.0-514.el7.x86_64 uname -s = Linux uname -v = #1 SMP Tue Nov 22 16:42:41 UTC 2016 /usr/bin/uname -p = x86_64 /bin/uname -X = unknown /bin/arch = x86_64 /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/agensgraph/bin PATH: /home/jessica/spark/apache-maven-3.5.2/bin PATH: /home/jessica/spark/jdk1.8.0_121/bin PATH: /home/jessica/spark/hadoop-2.7.5/bin PATH: /home/jessica/spark/hadoop-2.7.5/sbin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/bin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/sbin PATH: /home/jessica/spark/scala-2.11.6/bin PATH: /home/jessica/spark/sbt/bin PATH: /usr/local/agensgraph/bin PATH: /home/jessica/spark/apache-maven-3.5.2/bin PATH: /home/jessica/spark/jdk1.8.0_121/bin PATH: /home/jessica/spark/hadoop-2.7.5/bin PATH: /home/jessica/spark/hadoop-2.7.5/sbin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/bin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/sbin PATH: /home/jessica/spark/scala-2.11.6/bin PATH: /home/jessica/spark/sbt/bin PATH: /usr/local/agensgraph/bin PATH: /home/jessica/spark/apache-maven-3.5.2/bin PATH: /home/jessica/spark/jdk1.8.0_121/bin PATH: /home/jessica/spark/hadoop-2.7.5/bin PATH: /home/jessica/spark/hadoop-2.7.5/sbin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/bin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/sbin PATH: /home/jessica/spark/scala-2.11.6/bin PATH: /home/jessica/spark/sbt/bin PATH: /usr/local/agensgraph/bin PATH: /home/jessica/spark/apache-maven-3.5.2/bin PATH: /home/jessica/spark/jdk1.8.0_121/bin PATH: /home/jessica/spark/hadoop-2.7.5/bin PATH: /home/jessica/spark/hadoop-2.7.5/sbin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/bin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/sbin PATH: /home/jessica/spark/scala-2.11.6/bin PATH: /home/jessica/spark/sbt/bin PATH: /home/jessica/AgensGraph/bin PATH: /home/jessica/spark/apache-maven-3.5.2/bin PATH: /home/jessica/spark/jdk1.8.0_121/bin PATH: /home/jessica/spark/hadoop-2.7.5/bin PATH: /home/jessica/spark/hadoop-2.7.5/sbin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/bin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/sbin PATH: /home/jessica/spark/scala-2.11.6/bin PATH: /home/jessica/spark/sbt/bin PATH: /home/jessica/AgensGraph/bin PATH: /home/jessica/spark/apache-maven-3.5.2/bin PATH: /home/jessica/spark/jdk1.8.0_121/bin PATH: /home/jessica/spark/hadoop-2.7.5/bin PATH: /home/jessica/spark/hadoop-2.7.5/sbin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/bin PATH: /home/jessica/spark/spark-2.2.1-bin-hadoop2.7/sbin PATH: /home/jessica/spark/scala-2.11.6/bin PATH: /home/jessica/spark/sbt/bin PATH: /usr/local/bin PATH: /usr/local/sbin PATH: /usr/bin PATH: /usr/sbin PATH: /bin PATH: /sbin PATH: /root/bin PATH: /usr/bin PATH: /usr/local/lib ## ----------- ## ## Core tests. ## ## ----------- ## configure:2769: checking build system type configure:2783: result: x86_64-pc-linux-gnu configure:2803: checking host system type configure:2816: result: x86_64-pc-linux-gnu configure:2838: checking which template to use configure:2908: result: linux configure:3003: checking whether to build with 64-bit integer date/time support configure:3032: result: yes configure:3039: checking whether NLS is wanted configure:3071: result: no configure:3079: checking for default port number configure:3104: result: 5432 configure:3533: checking for block size configure:3567: result: 8kB configure:3579: checking for segment size configure:3608: result: 1GB configure:3620: checking for WAL block size configure:3655: result: 8kB configure:3667: checking for WAL segment size configure:3702: result: 16MB configure:3799: checking for gcc configure:3815: found /usr/bin/gcc configure:3826: result: gcc configure:3857: checking for C compiler version configure:3866: gcc --version >&5 gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16) Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3877: $? = 0 configure:3866: gcc -v >&5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux Thread model: posix gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) configure:3877: $? = 0 configure:3866: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:3877: $? = 4 configure:3866: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion' gcc: fatal error: no input files compilation terminated. configure:3877: $? = 4 configure:3897: checking whether the C compiler works configure:3919: gcc -ggdb -0g -g3 -fno-omit-frame-pointer conftest.c >&5 gcc: error: unrecognized command line option '-0g' configure:3923: $? = 1 configure:3961: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "PostgreSQL" | #define PACKAGE_TARNAME "postgresql" | #define PACKAGE_VERSION "9.6.2" | #define PACKAGE_STRING "PostgreSQL 9.6.2" | #define PACKAGE_BUGREPORT "[email protected]" | #define PACKAGE_URL "" | #define PG_MAJORVERSION "9.6" | #define PG_VERSION "9.6.2" | #define AG_VERSION "1.2.0" | #define AG_GIT_REVISION "355d7fc343f65b6a06247d670b8966253c46bf53" | #define USE_INTEGER_DATETIMES 1 | #define DEF_PGPORT 5432 | #define DEF_PGPORT_STR "5432" | #define BLCKSZ 8192 | #define RELSEG_SIZE 131072 | #define XLOG_BLCKSZ 8192 | #define XLOG_SEG_SIZE (16 * 1024 * 1024) | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3966: error: in `/root/Downloads/agensgraph': configure:3968: error: C compiler cannot create executables See `config.log' for more details ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_build=x86_64-pc-linux-gnu ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set=set ac_cv_env_CFLAGS_value='-ggdb -0g -g3 -fno-omit-frame-pointer' ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_DOCBOOKSTYLE_set= ac_cv_env_DOCBOOKSTYLE_value= ac_cv_env_LDFLAGS_EX_set= ac_cv_env_LDFLAGS_EX_value= ac_cv_env_LDFLAGS_SL_set= ac_cv_env_LDFLAGS_SL_value= ac_cv_env_LDFLAGS_set= ac_cv_env_LDFLAGS_value= ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_build_alias_set= ac_cv_env_build_alias_value= ac_cv_env_host_alias_set= ac_cv_env_host_alias_value= ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_host=x86_64-pc-linux-gnu ac_cv_prog_ac_ct_CC=gcc ## ----------------- ## ## Output variables. ## ## ----------------- ## AR='' AWK='' BISON='' BISONFLAGS='' CC='gcc' CFLAGS='-ggdb -0g -g3 -fno-omit-frame-pointer' CFLAGS_SSE42='' CFLAGS_VECTOR='' COLLATEINDEX='' CPP='' CPPFLAGS='' DBTOEPUB='' DEFS='' DLLTOOL='' DLLWRAP='' DOCBOOKSTYLE='' DTRACE='' DTRACEFLAGS='' ECHO_C='' ECHO_N='-n' ECHO_T='' EGREP='' ELF_SYS='' EXEEXT='' FLEX='' FLEXFLAGS='' GCC='' GCOV='' GENHTML='' GREP='' HAVE_IPV6='' INCLUDES='' INSTALL_DATA='' INSTALL_PROGRAM='' INSTALL_SCRIPT='' JADE='' LCOV='' LD='' LDAP_LIBS_BE='' LDAP_LIBS_FE='' LDFLAGS='' LDFLAGS_EX='' LDFLAGS_SL='' LIBOBJS='' LIBS='' LN_S='' LTLIBOBJS='' MKDIR_P='' MSGFMT='' MSGFMT_FLAGS='' MSGMERGE='' NSGMLS='' OBJEXT='' OSX='' PACKAGE_BUGREPORT='[email protected]' PACKAGE_NAME='PostgreSQL' PACKAGE_STRING='PostgreSQL 9.6.2' PACKAGE_TARNAME='postgresql' PACKAGE_URL='' PACKAGE_VERSION='9.6.2' PATH_SEPARATOR=':' PERL='' PG_CRC32C_OBJS='' PG_MAJORVERSION='9.6' PG_VERSION_NUM='' PORTNAME='linux' PROVE='' PTHREAD_CC='' PTHREAD_CFLAGS='' PTHREAD_LIBS='' PYTHON='' RANLIB='' SHELL='/bin/sh' STRIP='' STRIP_SHARED_LIB='' STRIP_STATIC_LIB='' SUN_STUDIO_CC='' TAR='' TAS='' TCLSH='' TCL_CONFIG_SH='' TCL_INCLUDE_SPEC='' TCL_LIBS='' TCL_LIB_SPEC='' TCL_SHARED_BUILD='' TCL_SHLIB_LD_LIBS='' UUID_EXTRA_OBJS='' UUID_LIBS='' WANTED_LANGUAGES='' WINDRES='' XGETTEXT='' XML2_CONFIG='' XMLLINT='' XSLTPROC='' ZIC='' ac_ct_CC='gcc' autodepend='' ax_pthread_config='' bindir='${exec_prefix}/bin' build='x86_64-pc-linux-gnu' build_alias='' build_cpu='x86_64' build_os='linux-gnu' build_vendor='pc' configure_args=' '\''--prefix=/usr/local/agensgraph'\'' '\''--enable-cassert'\'' '\''--enable-debug'\'' '\''CFLAGS=-ggdb -0g -g3 -fno-omit-frame-pointer'\''' datadir='${datarootdir}' datarootdir='${prefix}/share' default_port='5432' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' dvidir='${docdir}' enable_coverage='no' enable_debug='yes' enable_dtrace='no' enable_nls='no' enable_rpath='yes' enable_tap_tests='no' enable_thread_safety='' exec_prefix='NONE' have_docbook='' have_win32_dbghelp='' host='x86_64-pc-linux-gnu' host_alias='' host_cpu='x86_64' host_os='linux-gnu' host_vendor='pc' htmldir='${docdir}' includedir='${prefix}/include' infodir='${datarootdir}/info' install_bin='' krb_srvtab='' ld_R_works='' libdir='${exec_prefix}/lib' libexecdir='${exec_prefix}/libexec' localedir='${datarootdir}/locale' localstatedir='${prefix}/var' mandir='${datarootdir}/man' oldincludedir='/usr/include' pdfdir='${docdir}' perl_archlibexp='' perl_embed_ldflags='' perl_privlibexp='' perl_useshrplib='' prefix='/usr/local/agensgraph' program_transform_name='s,x,x,' psdir='${docdir}' python_additional_libs='' python_includespec='' python_libdir='' python_libspec='' python_majorversion='' python_version='' sbindir='${exec_prefix}/sbin' sharedstatedir='${prefix}/com' sysconfdir='${prefix}/etc' target_alias='' vpath_build='' with_gnu_ld='' with_libxml='' with_libxslt='' with_openssl='' with_perl='' with_python='' with_selinux='' with_system_tzdata='' with_systemd='' with_tcl='' with_uuid='' with_zlib='' ## ----------- ## ## confdefs.h. ## ## ----------- ## /* confdefs.h */ #define PACKAGE_NAME "PostgreSQL" #define PACKAGE_TARNAME "postgresql" #define PACKAGE_VERSION "9.6.2" #define PACKAGE_STRING "PostgreSQL 9.6.2" #define PACKAGE_BUGREPORT "[email protected]" #define PACKAGE_URL "" #define PG_MAJORVERSION "9.6" #define PG_VERSION "9.6.2" #define AG_VERSION "1.2.0" #define AG_GIT_REVISION "355d7fc343f65b6a06247d670b8966253c46bf53" #define USE_INTEGER_DATETIMES 1 #define DEF_PGPORT 5432 #define DEF_PGPORT_STR "5432" #define BLCKSZ 8192 #define RELSEG_SIZE 131072 #define XLOG_BLCKSZ 8192 #define XLOG_SEG_SIZE (16 * 1024 * 1024) configure: exit 77
You are setting CFLAGS to -ggdb -0g -g3 -fno-omit-frame-pointer Out of these, -0g is not valid. You may have meant -g0 (which would disable the debugging enabled by -ggdb). The later -g3 flag enables debugging again.
configure error: C compiler cannot create executables [closed]
1,431,359,411,000
I want to download and build a release of vim, but on the vim github repo - there are over 12,000 releases, and a release is made every few hours. What should I do?
The Vim project has the slightly unusual custom to provide a new release per source code commit, with each commit incrementing the patch release number by 1. It's unlikely to matter too much what patch version of the latest major release you get, unless you want to get a particular patch. Just use the latest release or the release packaged by your Unix system's package manager. In comments, it is revealed that what you actually want is a Vim with Python3 support, for Devuan Beowulf. Using Devuan's package search interface, it appears that the vim-nox package provides Vim with Python3 support: [...] This package contains a version of vim compiled with support for scripting with Lua, Perl, Python 3, Ruby, and Tcl but no GUI.
I want to download a vim release - but there are thousands!