Re: [OpenIndiana-discuss] compile package
In regard to: Re: [OpenIndiana-discuss] compile package, Francis.D said (at...: I'm going to install an IO on a dedicated desktop. I noticed that there is a lot of library missing to compile packages. By using sources. I have tested some applications but there is still a library missing or the version is too old. What version of OpenIndiana were you working with? I've done a lot of compilation, including stuff for a graphical desktop environment, on OI. I've found that depending on how your system was installed, it's possible that a lot of the development-related stuff didn't get installed. You may want to consider doing a sudo pkg install build-essential That's a "meta package" that will pull in a lot of build-related packages. I've found that for some of the stuff I've built, I've needed other packages that weren't included by build-essential, but build-essential covers a lot. Note that because of the way OI is packaged, you may need to do a "sudo pkg update" before being able to install 'build-essential' (yes, there are ways around that, but start with the simple case). 'pkg update' updates everything, including the kernel. Be sure you're ready for that. Reading the man page for 'pkg' and focusing on 'pkg search' and the '-r' flag will help you get started "finding things". Also, for libraries that have licenses that are atypical OR that have algorithms that may be restricted in some countries, you may be able to find those in a separate repository that is not configured by default. I'm talking about 'hipster-encumbered'. You'll want to do some reading on the wiki and/or the mailing list archives for this list to learn more about hipster-encumbered and setting up additional repositories. Again the 'pkg' man page will have useful information. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
On Tue, Sep 11, 2018 at 11:30 PM, Francis.D wrote: > Sorry I haven't tested yet. > Yesterday I broke my system. I'm going to make myself a dedicated > environment because on my laptop it's not ideal. > I'm going to install an IO on a dedicated desktop. I noticed that there is > a lot of library missing to compile packages. By using sources. > I have tested some applications but there is still a library missing or the > version is too old. > Can you be more specific? > > > Le mar. 11 sept. 2018 à 15:48, Aurélien Larcher < > aurelien.larc...@gmail.com> > a écrit : > > > On Mon, Sep 10, 2018 at 5:58 PM, Aurélien Larcher < > > aurelien.larc...@gmail.com> wrote: > > > > > > > > > > > On Mon, Sep 10, 2018 at 5:01 PM, Francis.D wrote: > > > > > >> I have downloaded the vlc archive. > > >> It seems there are a few Warnings and I can't go any further. I'll try > > >> to fix the problems. > > >> > > > > > I updated my ffmpeg and vlc branches to 3.2.11 and 3.0.4 respectively. > > I tested that the resulting package works reasonably well. > > > > > > > > > > > > You need to update ffmpeg and recompile gstreamer plugins first. > > > See https://github.com/OpenIndiana/oi-userland/pull/4034 > > > > > > Also oi-userland provides set environment variables and such to avoid > > > issues e.g related to using non-GNU commands. > > > It is better to use the same environment especially if you are not > > > experienced with packaging on OI. > > > > > > Clone oi-userland, gmake setup at the top directory, then pull my > ffmpeg > > > and vlc branches. > > > > > > > > >> > > >> here is the result of the command ./configure > > >> > > >> root@oifanboy:~/paquet/vlc-3.0.4# ./configure > > >> ./configure: line 4734: : cannot execute [Is a directory] > > >> ./configure[4734]: | sed -e 's/\\//g': not found [No such file or > > >> directory] > > >> checking build system type... i386-pc-solaris2.11 > > >> checking host system type... i386-pc-solaris2.11 > > >> checking for a BSD-compatible install... /usr/bin/ginstall -c > > >> checking whether build environment is sane... yes > > >> checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p > > >> checking for gawk... gawk > > >> checking whether make sets $(MAKE)... yes > > >> checking whether make supports nested variables... yes > > >> checking whether UID '0' is supported by ustar format... yes > > >> checking whether GID '0' is supported by ustar format... yes > > >> checking how to create a ustar tar archive... gnutar > > >> checking whether make supports nested variables... (cached) yes > > >> checking whether to enable maintainer-specific portions of > Makefiles... > > >> yes > > >> 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 whether make supports the include directive... yes (GNU > style) > > >> checking dependency style of gcc... gcc3 > > >> checking how to run the C preprocessor... gcc -E > > >> checking for grep that handles long lines and -e... /usr/bin/ggrep > > >> checking for egrep... /usr/bin/ggrep -E > > >> checking for ANSI C header files... yes > > >> checking for sys/types.h... yes > > >> checking for sys/stat.h... yes > > >> checking for stdlib.h... yes > > >> checking for string.h... yes > > >> checking for memory.h... yes > > >> checking for strings.h... yes > > >> checking for inttypes.h... yes > > >> checking for stdint.h... yes > > >> checking for unistd.h... yes > > >> checking minix/config.h usability... no > > >> checking minix/config.h presence... no > > >> checking for minix/config.h... no > > >> checking whether it is safe to define __EXTENSIONS__... yes > > >> checking whether gcc supports C11... 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 how to run the C preprocessor... gcc -E > > >> checking for gcc... gcc > > >> checking whether we are using the GNU Objective C compiler... yes > > >> checking whether gcc accepts -g... yes > > >> checking dependency style of gcc... gcc3 > > >> checking for egrep... (cached) /usr/bin/ggrep -E > > >> checking whether make sets $(MAKE)... (cached) yes > > >> checking dependency style of gcc... gcc3 > > >> checking for flex... flex > > >> checking lex output file root... lex.yy > > >> checking lex library... -ll > > >> checking whether yytext is a pointer... yes > > >> checking for bison... bison -y > > >> checking for desktop-file-validate...
Re: [OpenIndiana-discuss] compile package
Sorry I haven't tested yet. Yesterday I broke my system. I'm going to make myself a dedicated environment because on my laptop it's not ideal. I'm going to install an IO on a dedicated desktop. I noticed that there is a lot of library missing to compile packages. By using sources. I have tested some applications but there is still a library missing or the version is too old. Le mar. 11 sept. 2018 à 15:48, Aurélien Larcher a écrit : > On Mon, Sep 10, 2018 at 5:58 PM, Aurélien Larcher < > aurelien.larc...@gmail.com> wrote: > > > > > > > On Mon, Sep 10, 2018 at 5:01 PM, Francis.D wrote: > > > >> I have downloaded the vlc archive. > >> It seems there are a few Warnings and I can't go any further. I'll try > >> to fix the problems. > >> > > > I updated my ffmpeg and vlc branches to 3.2.11 and 3.0.4 respectively. > I tested that the resulting package works reasonably well. > > > > > > > You need to update ffmpeg and recompile gstreamer plugins first. > > See https://github.com/OpenIndiana/oi-userland/pull/4034 > > > > Also oi-userland provides set environment variables and such to avoid > > issues e.g related to using non-GNU commands. > > It is better to use the same environment especially if you are not > > experienced with packaging on OI. > > > > Clone oi-userland, gmake setup at the top directory, then pull my ffmpeg > > and vlc branches. > > > > > >> > >> here is the result of the command ./configure > >> > >> root@oifanboy:~/paquet/vlc-3.0.4# ./configure > >> ./configure: line 4734: : cannot execute [Is a directory] > >> ./configure[4734]: | sed -e 's/\\//g': not found [No such file or > >> directory] > >> checking build system type... i386-pc-solaris2.11 > >> checking host system type... i386-pc-solaris2.11 > >> checking for a BSD-compatible install... /usr/bin/ginstall -c > >> checking whether build environment is sane... yes > >> checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p > >> checking for gawk... gawk > >> checking whether make sets $(MAKE)... yes > >> checking whether make supports nested variables... yes > >> checking whether UID '0' is supported by ustar format... yes > >> checking whether GID '0' is supported by ustar format... yes > >> checking how to create a ustar tar archive... gnutar > >> checking whether make supports nested variables... (cached) yes > >> checking whether to enable maintainer-specific portions of Makefiles... > >> yes > >> 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 whether make supports the include directive... yes (GNU style) > >> checking dependency style of gcc... gcc3 > >> checking how to run the C preprocessor... gcc -E > >> checking for grep that handles long lines and -e... /usr/bin/ggrep > >> checking for egrep... /usr/bin/ggrep -E > >> checking for ANSI C header files... yes > >> checking for sys/types.h... yes > >> checking for sys/stat.h... yes > >> checking for stdlib.h... yes > >> checking for string.h... yes > >> checking for memory.h... yes > >> checking for strings.h... yes > >> checking for inttypes.h... yes > >> checking for stdint.h... yes > >> checking for unistd.h... yes > >> checking minix/config.h usability... no > >> checking minix/config.h presence... no > >> checking for minix/config.h... no > >> checking whether it is safe to define __EXTENSIONS__... yes > >> checking whether gcc supports C11... 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 how to run the C preprocessor... gcc -E > >> checking for gcc... gcc > >> checking whether we are using the GNU Objective C compiler... yes > >> checking whether gcc accepts -g... yes > >> checking dependency style of gcc... gcc3 > >> checking for egrep... (cached) /usr/bin/ggrep -E > >> checking whether make sets $(MAKE)... (cached) yes > >> checking dependency style of gcc... gcc3 > >> checking for flex... flex > >> checking lex output file root... lex.yy > >> checking lex library... -ll > >> checking whether yytext is a pointer... yes > >> checking for bison... bison -y > >> checking for desktop-file-validate... desktop-file-validate > >> checking for c11-gcc... no > >> checking for c11... no > >> checking for c99-gcc... no > >> checking for c99... c99 > >> checking for an ANSI C-conforming const... yes > >> checking for inline... inline > >> checking for C/C++ restrict keyword... __restrict > >> checking whether g++ supports C++11 features by default... yes >
Re: [OpenIndiana-discuss] compile package
On Mon, Sep 10, 2018 at 5:58 PM, Aurélien Larcher < aurelien.larc...@gmail.com> wrote: > > > On Mon, Sep 10, 2018 at 5:01 PM, Francis.D wrote: > >> I have downloaded the vlc archive. >> It seems there are a few Warnings and I can't go any further. I'll try >> to fix the problems. >> > I updated my ffmpeg and vlc branches to 3.2.11 and 3.0.4 respectively. I tested that the resulting package works reasonably well. > > You need to update ffmpeg and recompile gstreamer plugins first. > See https://github.com/OpenIndiana/oi-userland/pull/4034 > > Also oi-userland provides set environment variables and such to avoid > issues e.g related to using non-GNU commands. > It is better to use the same environment especially if you are not > experienced with packaging on OI. > > Clone oi-userland, gmake setup at the top directory, then pull my ffmpeg > and vlc branches. > > >> >> here is the result of the command ./configure >> >> root@oifanboy:~/paquet/vlc-3.0.4# ./configure >> ./configure: line 4734: : cannot execute [Is a directory] >> ./configure[4734]: | sed -e 's/\\//g': not found [No such file or >> directory] >> checking build system type... i386-pc-solaris2.11 >> checking host system type... i386-pc-solaris2.11 >> checking for a BSD-compatible install... /usr/bin/ginstall -c >> checking whether build environment is sane... yes >> checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p >> checking for gawk... gawk >> checking whether make sets $(MAKE)... yes >> checking whether make supports nested variables... yes >> checking whether UID '0' is supported by ustar format... yes >> checking whether GID '0' is supported by ustar format... yes >> checking how to create a ustar tar archive... gnutar >> checking whether make supports nested variables... (cached) yes >> checking whether to enable maintainer-specific portions of Makefiles... >> yes >> 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 whether make supports the include directive... yes (GNU style) >> checking dependency style of gcc... gcc3 >> checking how to run the C preprocessor... gcc -E >> checking for grep that handles long lines and -e... /usr/bin/ggrep >> checking for egrep... /usr/bin/ggrep -E >> checking for ANSI C header files... yes >> checking for sys/types.h... yes >> checking for sys/stat.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for memory.h... yes >> checking for strings.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for unistd.h... yes >> checking minix/config.h usability... no >> checking minix/config.h presence... no >> checking for minix/config.h... no >> checking whether it is safe to define __EXTENSIONS__... yes >> checking whether gcc supports C11... 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 how to run the C preprocessor... gcc -E >> checking for gcc... gcc >> checking whether we are using the GNU Objective C compiler... yes >> checking whether gcc accepts -g... yes >> checking dependency style of gcc... gcc3 >> checking for egrep... (cached) /usr/bin/ggrep -E >> checking whether make sets $(MAKE)... (cached) yes >> checking dependency style of gcc... gcc3 >> checking for flex... flex >> checking lex output file root... lex.yy >> checking lex library... -ll >> checking whether yytext is a pointer... yes >> checking for bison... bison -y >> checking for desktop-file-validate... desktop-file-validate >> checking for c11-gcc... no >> checking for c11... no >> checking for c99-gcc... no >> checking for c99... c99 >> checking for an ANSI C-conforming const... yes >> checking for inline... inline >> checking for C/C++ restrict keyword... __restrict >> checking whether g++ supports C++11 features by default... yes >> checking whether C compiler accepts -Werror=unknown-warning-option... no >> checking whether C compiler accepts -Werror=invalid-command-line-argument... >> no >> checking whether C compiler accepts -Werror=unknown-warning-option... >> (cached) no >> checking whether C compiler accepts >> -Werror=invalid-command-line-argument... (cached) no >> checking for 3rd party libraries path... not found >> checking how to print strings... print -r >> checking for a sed that does not truncate output... /usr/bin/gsed >> checking for fgrep... /usr/bin/ggrep -F >> checking for ld used by gcc... /usr/bin/ld >> checking if the linker (/usr/bin/ld) is GNU
Re: [OpenIndiana-discuss] compile package
On Mon, Sep 10, 2018 at 5:01 PM, Francis.D wrote: > I have downloaded the vlc archive. > It seems there are a few Warnings and I can't go any further. I'll try > to fix the problems. > You need to update ffmpeg and recompile gstreamer plugins first. See https://github.com/OpenIndiana/oi-userland/pull/4034 Also oi-userland provides set environment variables and such to avoid issues e.g related to using non-GNU commands. It is better to use the same environment especially if you are not experienced with packaging on OI. Clone oi-userland, gmake setup at the top directory, then pull my ffmpeg and vlc branches. > > here is the result of the command ./configure > > root@oifanboy:~/paquet/vlc-3.0.4# ./configure > ./configure: line 4734: : cannot execute [Is a directory] > ./configure[4734]: | sed -e 's/\\//g': not found [No such file or > directory] > checking build system type... i386-pc-solaris2.11 > checking host system type... i386-pc-solaris2.11 > checking for a BSD-compatible install... /usr/bin/ginstall -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether make supports nested variables... yes > checking whether UID '0' is supported by ustar format... yes > checking whether GID '0' is supported by ustar format... yes > checking how to create a ustar tar archive... gnutar > checking whether make supports nested variables... (cached) yes > checking whether to enable maintainer-specific portions of Makefiles... yes > 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 whether make supports the include directive... yes (GNU style) > checking dependency style of gcc... gcc3 > checking how to run the C preprocessor... gcc -E > checking for grep that handles long lines and -e... /usr/bin/ggrep > checking for egrep... /usr/bin/ggrep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking minix/config.h usability... no > checking minix/config.h presence... no > checking for minix/config.h... no > checking whether it is safe to define __EXTENSIONS__... yes > checking whether gcc supports C11... 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 how to run the C preprocessor... gcc -E > checking for gcc... gcc > checking whether we are using the GNU Objective C compiler... yes > checking whether gcc accepts -g... yes > checking dependency style of gcc... gcc3 > checking for egrep... (cached) /usr/bin/ggrep -E > checking whether make sets $(MAKE)... (cached) yes > checking dependency style of gcc... gcc3 > checking for flex... flex > checking lex output file root... lex.yy > checking lex library... -ll > checking whether yytext is a pointer... yes > checking for bison... bison -y > checking for desktop-file-validate... desktop-file-validate > checking for c11-gcc... no > checking for c11... no > checking for c99-gcc... no > checking for c99... c99 > checking for an ANSI C-conforming const... yes > checking for inline... inline > checking for C/C++ restrict keyword... __restrict > checking whether g++ supports C++11 features by default... yes > checking whether C compiler accepts -Werror=unknown-warning-option... no > checking whether C compiler accepts -Werror=invalid-command-line-argument... > no > checking whether C compiler accepts -Werror=unknown-warning-option... > (cached) no > checking whether C compiler accepts > -Werror=invalid-command-line-argument... (cached) no > checking for 3rd party libraries path... not found > checking how to print strings... print -r > checking for a sed that does not truncate output... /usr/bin/gsed > checking for fgrep... /usr/bin/ggrep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... no > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p > checking the name lister (/usr/bin/nm -p) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 786240 > checking how to convert i386-pc-solaris2.11 file names to > i386-pc-solaris2.11 format...
Re: [OpenIndiana-discuss] compile package
I have downloaded the vlc archive. It seems there are a few Warnings and I can't go any further. I'll try to fix the problems. here is the result of the command ./configure root@oifanboy:~/paquet/vlc-3.0.4# ./configure ./configure: line 4734: : cannot execute [Is a directory] ./configure[4734]: | sed -e 's/\\//g': not found [No such file or directory] checking build system type... i386-pc-solaris2.11 checking host system type... i386-pc-solaris2.11 checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether UID '0' is supported by ustar format... yes checking whether GID '0' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... (cached) yes checking whether to enable maintainer-specific portions of Makefiles... yes 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 whether make supports the include directive... yes (GNU style) checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/ggrep checking for egrep... /usr/bin/ggrep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether gcc supports C11... 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 how to run the C preprocessor... gcc -E checking for gcc... gcc checking whether we are using the GNU Objective C compiler... yes checking whether gcc accepts -g... yes checking dependency style of gcc... gcc3 checking for egrep... (cached) /usr/bin/ggrep -E checking whether make sets $(MAKE)... (cached) yes checking dependency style of gcc... gcc3 checking for flex... flex checking lex output file root... lex.yy checking lex library... -ll checking whether yytext is a pointer... yes checking for bison... bison -y checking for desktop-file-validate... desktop-file-validate checking for c11-gcc... no checking for c11... no checking for c99-gcc... no checking for c99... c99 checking for an ANSI C-conforming const... yes checking for inline... inline checking for C/C++ restrict keyword... __restrict checking whether g++ supports C++11 features by default... yes checking whether C compiler accepts -Werror=unknown-warning-option... no checking whether C compiler accepts -Werror=invalid-command-line-argument... no checking whether C compiler accepts -Werror=unknown-warning-option... (cached) no checking whether C compiler accepts -Werror=invalid-command-line-argument... (cached) no checking for 3rd party libraries path... not found checking how to print strings... print -r checking for a sed that does not truncate output... /usr/bin/gsed checking for fgrep... /usr/bin/ggrep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p checking the name lister (/usr/bin/nm -p) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 786240 checking how to convert i386-pc-solaris2.11 file names to i386-pc-solaris2.11 format... func_convert_file_noop checking how to convert i386-pc-solaris2.11 file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... no checking how to recognize dependent libraries... (cached) pass_all checking for dlltool... no checking how to associate runtime and link libraries... print -r -- checking for ar... ar checking for archiver @FILE support... no checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -p 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
Re: [OpenIndiana-discuss] compile package
On 10/09/2018 16:14, Francis.D wrote: Merci Jean-Pierre. I checked the qt version install and actually the 2 versions of qt are installed on hipster. Yesterday I also installed * build-essential * and I would like to build some packages because we are really limited or we have old versions. but I need to study and understand the process of building Oi userland. This is not a criticism. The team is small and if I can contribute it will make me happy. But for the moment I'm trying some local compilations. I'am also tried gnumeric without no success. gnumeric is available in Hipster 2018-04 as desktop/gnumeric -- Dr.Udo Grabowski Inst.f.Meteorology & Climate Research IMK-ASF-SAT http://www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technology http://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
On 10/09/2018 16:14, Francis.D wrote: Merci Jean-Pierre. I checked the qt version install and actually the 2 versions of qt are installed on hipster. Yesterday I also installed * build-essential * and I would like to build some packages because we are really limited or we have old versions. but I need to study and understand the process of building Oi userland. This is not a criticism. The team is small and if I can contribute it will make me happy. But for the moment I'm trying some local compilations. I'am also tried gnumeric without no success. I'm going to drop smplayer because it seems to be missing files to compile under OI smplayer was available under oi_151a8, these are the old dependences from the manifest: depend fmri=SUNWcs@0.5.11-0.151.1.5 type=require depend fmri=system/library@0.5.11-0.151.1.5 type=require depend fmri=service/gnome/desktop-cache@0.2.2-0.151.1.5 type=require depend fmri=sfe/system/library/gcc-runtime@4.6.3-0.151.1.5 type=require depend fmri=library/zlib@1.2.3-0.151.1.5 type=require depend fmri=library/desktop/g++/qt@4.7.4-0.151.1.5 type=require depend fmri=system/library/math@0.5.11-0.151.1.5 type=require depend fmri=SUNWcsd@0.5.11-0.151.1.5 type=require depend fmri=sfe/system/library/gcc-46-runtime@4.6.3-0.151.1.5 type=require -- Dr.Udo Grabowski Inst.f.Meteorology & Climate Research IMK-ASF-SAT http://www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technology http://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
On Mon, Sep 10, 2018 at 4:14 PM, Francis.D wrote: > Merci Jean-Pierre. > > I checked the qt version install and actually the 2 versions of qt are > installed on hipster. Yesterday I also installed * build-essential * > and I would like to build some packages because we are really limited > or we have old versions. > but I need to study and understand the process of building Oi userland. > This is not a criticism. The team is small and if I can contribute it > will make me happy. > > Some notes at: - https://wiki.openindiana.org/oi/2.+Overview+of+the+Build+System - https://wiki.openindiana.org/oi/3.+Common+Tasks > But for the moment I'm trying some local compilations. I'am also tried > gnumeric without no success. > > I'm going to drop smplayer because it seems to be missing files to > compile under OI > I will try VLC 3.0.4 > You can look at updating my recipe: https://github.com/OpenIndiana/oi-userland/pull/4035 > > regard > > 2018-09-10 3:20 UTC−04:00, Jean-Pierre : > > Francis.D wrote: > >> Hi all, > >> I'm trying to compile smplayer. I have previously installed gcc + > >> automake > >> + autoconf > >> > >> I downloaded the source package smplayer-18.6.0.tar.bz2 package and > >> unzip. > >> Then I executed the command cd > >> root@oifanboy:~/downloads/smplayer-18.6.0# > >> When I run the command ./configure I always get this message > >> bash: ./configure: No such file or directory > > > > Being curious, I downloaded the source file, and there is > > no configure in it (actually there are a couple of them, but > > they are not targeted at building smplayer). > > > > There is a Makefile, which relies on qmake, so you have to > > install qt and adjust the Makefile to the current version of > > qt and to the appropriate paths... > > > > qt is apparently available on > > http://sfe.opencsw.org/localhostoih/en/catalog.shtml > > > > This is a good start for learning how to develop or port > > applications to OI. > > > >> I tried ./configure --prefix=usr without no success > >> > >> I also install intltool and I tried with another software * gnumeric* > >> without not more success > >> > >> If anyone have a tuto step by step OI, what I need to install for > compile > >> software etc... > >> > >> thank > >> > > > > > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
Merci Jean-Pierre. I checked the qt version install and actually the 2 versions of qt are installed on hipster. Yesterday I also installed * build-essential * and I would like to build some packages because we are really limited or we have old versions. but I need to study and understand the process of building Oi userland. This is not a criticism. The team is small and if I can contribute it will make me happy. But for the moment I'm trying some local compilations. I'am also tried gnumeric without no success. I'm going to drop smplayer because it seems to be missing files to compile under OI I will try VLC 3.0.4 regard 2018-09-10 3:20 UTC−04:00, Jean-Pierre : > Francis.D wrote: >> Hi all, >> I'm trying to compile smplayer. I have previously installed gcc + >> automake >> + autoconf >> >> I downloaded the source package smplayer-18.6.0.tar.bz2 package and >> unzip. >> Then I executed the command cd >> root@oifanboy:~/downloads/smplayer-18.6.0# >> When I run the command ./configure I always get this message >> bash: ./configure: No such file or directory > > Being curious, I downloaded the source file, and there is > no configure in it (actually there are a couple of them, but > they are not targeted at building smplayer). > > There is a Makefile, which relies on qmake, so you have to > install qt and adjust the Makefile to the current version of > qt and to the appropriate paths... > > qt is apparently available on > http://sfe.opencsw.org/localhostoih/en/catalog.shtml > > This is a good start for learning how to develop or port > applications to OI. > >> I tried ./configure --prefix=usr without no success >> >> I also install intltool and I tried with another software * gnumeric* >> without not more success >> >> If anyone have a tuto step by step OI, what I need to install for compile >> software etc... >> >> thank >> > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
On 09/10/18 09:20, Jean-Pierre wrote: Francis.D wrote: Hi all, I'm trying to compile smplayer. I have previously installed gcc + automake + autoconf I downloaded the source package smplayer-18.6.0.tar.bz2 package and unzip. Then I executed the command cd root@oifanboy:~/downloads/smplayer-18.6.0# When I run the command ./configure I always get this message bash: ./configure: No such file or directory Being curious, I downloaded the source file, and there is no configure in it (actually there are a couple of them, but they are not targeted at building smplayer). There is a Makefile, which relies on qmake, so you have to install qt and adjust the Makefile to the current version of qt and to the appropriate paths... qt is apparently available on http://sfe.opencsw.org/localhostoih/en/catalog.shtml This is a good start for learning how to develop or port applications to OI. I tried ./configure --prefix=usr without no success I also install intltool and I tried with another software * gnumeric* without not more success If anyone have a tuto step by step OI, what I need to install for compile software etc... thank ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi all, just note on qt: OI /hipster supplies 2 versions: $ pkg info library/qt4 library/qt5 | grep FMRI FMRI: pkg://openindiana.org/library/qt4@4.8.7-2018.0.0.5:20180529T173314Z FMRI: pkg://openindiana.org/library/qt5@5.8.0-2018.0.0.4:20180525T010509Z Regards. -- Predrag Zečević Technical Support Analyst 2e Systems GmbH tel: +49 - 6196 - 95058 - 15 mob: +49 - 174 - 3109288 fax: +49 - 6196 - 95058 - 94 e-mail: predrag.zece...@2e-systems.com headquarter: 2e Systems GmbH, Koenigsteiner Str. 87, 65812 Bad Soden am Taunus, Germany registration: Amtsgericht Koenigstein (Germany), HRB 7303 managing director: Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
Francis.D wrote: Hi all, I'm trying to compile smplayer. I have previously installed gcc + automake + autoconf I downloaded the source package smplayer-18.6.0.tar.bz2 package and unzip. Then I executed the command cd root@oifanboy:~/downloads/smplayer-18.6.0# When I run the command ./configure I always get this message bash: ./configure: No such file or directory Being curious, I downloaded the source file, and there is no configure in it (actually there are a couple of them, but they are not targeted at building smplayer). There is a Makefile, which relies on qmake, so you have to install qt and adjust the Makefile to the current version of qt and to the appropriate paths... qt is apparently available on http://sfe.opencsw.org/localhostoih/en/catalog.shtml This is a good start for learning how to develop or port applications to OI. I tried ./configure --prefix=usr without no success I also install intltool and I tried with another software * gnumeric* without not more success If anyone have a tuto step by step OI, what I need to install for compile software etc... thank ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
thank for your answers ! I read of course the install.txt file but the instructions are not very detailed. I tried too make PREFIX=/usr make PREFIX=/usr install without no success I attach install file regard Le dim. 9 sept. 2018 à 23:23, Jerry Kemp a écrit : > assuming an accidental typo, but, and assuming you wanted a base/prefix > directory of /usr , it would be > > # ./configure --prefix=/usr > > I state this without going into specifics for this particular application. > > regarding this comment:: > ... > When I run the command ./configure I always get this message > bash: ./configure: No such file or directory > ... > > there isn't always necessarily a "configure" file or "Configure" file or > even "config" > > but, more often than not, there is an "INSTALL" file and/or README file or > a "docs" directory that can get you kicked off in the > right direction. > > This should be more than enough to point you in the right direction. Once > you get going, and, if you have more specific errors or > issues, come back and repost, and we all can go from there. > > Jerry > > > > > > Original Message > From: Francis.D > Sent: Sun, Sep 9, 2018 10:04 PM CDT > To: Discussion list for OpenIndiana > Subject: [OpenIndiana-discuss] compile package > > Hi all, > I'm trying to compile smplayer. I have previously installed gcc + automake > + autoconf > > I downloaded the source package smplayer-18.6.0.tar.bz2 package and unzip. > Then I executed the command cd > root@oifanboy:~/downloads/smplayer-18.6.0# > When I run the command ./configure I always get this message > bash: ./configure: No such file or directory > I tried ./configure --prefix=usr without no success > > I also install intltool and I tried with another software * gnumeric* > without not more success > > If anyone have a tuto step by step OI, what I need to install for compile > software etc... > > thank > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > This document explains how to compile and install SMPlayer. Compiling SMPlayer should be easy. It only depends on Qt 4. 1) How to make a deb package 2) How to make a rpm package 3) Generic compilation 4) Changing installation path 5) How to compile in Windows 1) How to make a deb package Be sure you have installed the following packages: libqt4-dev, zlib1g-dev, fakeroot, build-essential, devscripts, debhelper and g++. sudo apt-get install libqt4-dev zlib1g-dev fakeroot build-essential devscripts debhelper g++ (Packages to compile with Qt5: qtbase5-dev qt5-qmake qt5-default qtscript5-dev qttools5-dev-tools qtbase5-private-dev libqt5webkit5-dev) Now run ./create_deb.sh 2) How to make a rpm package Building a rpm package is not easy. Better get a binary package from this repository: https://software.opensuse.org/download.html?project=home%3Asmplayerdev=smplayer 3) Generic compilation -- (obsolete) 4) Changing installation path - By default smplayer will be installed in /usr/local. You can change it by using PREFIX and DESTDIR. Examples: make PREFIX=/usr make PREFIX=/usr install That would install smplayer under /usr. DESTDIR will be useful for package maintainers. make PREFIX=/usr make PREFIX=/usr DESTDIR=/tmp/ install That would compile smplayer for /usr but in fact it will be installed in /tmp/usr/ 5) How to compile in Windows (obsolete) ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] compile package
assuming an accidental typo, but, and assuming you wanted a base/prefix directory of /usr , it would be # ./configure --prefix=/usr I state this without going into specifics for this particular application. regarding this comment:: ... When I run the command ./configure I always get this message bash: ./configure: No such file or directory ... there isn't always necessarily a "configure" file or "Configure" file or even "config" but, more often than not, there is an "INSTALL" file and/or README file or a "docs" directory that can get you kicked off in the right direction. This should be more than enough to point you in the right direction. Once you get going, and, if you have more specific errors or issues, come back and repost, and we all can go from there. Jerry Original Message From: Francis.D Sent: Sun, Sep 9, 2018 10:04 PM CDT To: Discussion list for OpenIndiana Subject: [OpenIndiana-discuss] compile package Hi all, I'm trying to compile smplayer. I have previously installed gcc + automake + autoconf I downloaded the source package smplayer-18.6.0.tar.bz2 package and unzip. Then I executed the command cd root@oifanboy:~/downloads/smplayer-18.6.0# When I run the command ./configure I always get this message bash: ./configure: No such file or directory I tried ./configure --prefix=usr without no success I also install intltool and I tried with another software * gnumeric* without not more success If anyone have a tuto step by step OI, what I need to install for compile software etc... thank ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
