search for: mkspec

All, I am trying to build a custom kernel, following the howto and some stuff i found on the forums (mkspec.patch) 1. the mkspec.patch gives an error: [root at centos linux]# patch -p1 < mkspec.patch (Stripping trailing CRs from patch.) patching file scripts/package/mkspec Hunk #1 succeeded at 103 with fuzz 2 (offset 22 lines). Hunk #2 FAILED at 115. 1 out of 2 hunks FAILED -- saving rejects to fil...

Let's say I want to use a much newer kernel - even one from the future, such as the upcoming 2.6.24. :-) What would y'all smart folks do in this case, in order to avoid any possible nasty consequences? Would you import the config file from the original CentOS5 kernel into the new kernel, and let the kernel deal with the differences? I.e. have the old configuration as some sort of

Hi, Usually I'm not one to complain about "old" version of the CentOS kernel and/or software, since I appreciate CentOS' stability. So this might be the exception that confirms the rule. I've been jumping through several burning loops these past days to configure my little MSI Wind netbook, and I'm currently considering going for a more recent kernel. There's no

...written here should also work on 1.9 release, as I've tested Qt build last time just before 1.9 release. 1. Specs Qt uses it's own configuration and build system called "qmake". We should slightly change its configuration to allow usage of llvm-gcc4 instead of original gcc. --- mkspecs/common/g++.conf 2006-11-27 20:26:01.000000000 +0300 +++ mkspecs/common/g++.conf 2006-12-15 01:20:47.993289310 +0300 @@ -1,5 +1,5 @@ -QMAKE_CC = gcc +QMAKE_CC = /path/to/llvm-gcc/llvm-gcc QMAKE_LEX = flex QMAKE_LEXFLAGS += QMAKE_YACC...

...ms with symlinks. When running the script I receive a lot of error messages from this type: rsync: open(backup/sammy-root/2009-07-29/usr/share/pixmaps/cxassoc-cxoffice-0-application_x-crossover-exe.png) failed!!: No such file or directory (2) rsync: open(backup/sammy-root/2009-07-29/usr/share/qt/mkspecs/default) failed!!: Is a directory (21) rsync: open(backup/sammy-root/2009-07-29/usr/share/texmf-dist/scripts/context/stubs/unix/luatools) failed!!: No such file or directory (2) Unfortunately the DS doesn't support the -v option so I have no "normal" output. When I browse to th...

...ent. I tried LLVM on one of my bigger Qt 3.x based projects. I used llvm from SVN trunk (r39999) and SVN llvm-gcc-4.01 (r370) and did compile every file with /usr/src/llvm/dist/bin/g++ -c -pipe -g \ -Wall -Wextra -Wno-sign-compare \ ... lots of -Dxxxx ... \ --emit-llvm -I/usr/share/qt3/mkspecs/default \ -I. -I.. -I../../../include/qt3 -I.obj/ \ -o .obj/FILENAME.o FILENAME.cpp so that I later had 211 .o files, all in the binary bytecode format. I tried it that way because I thought that then the possibilities for inter-process and inter-module optimizations are probably the highe...

...y\QtSingleApplication\src -I..\src\plugins\thirdParty\LLVM\include -I..\src\plugins\thirdParty\LLVM\lib\Target\X86 -I..\src\plugins\thirdParty\LLVM\src -I..\src\plugins\thirdParty\LLVM\tools\clang\include -IC:\Qt\5.4\msvc2013_64\include -IC:\Qt\5.4\msvc2013_64\include\QtCore -IC:\Qt\5.4\msvc2013_64\mkspecs\win32-msvc2013 /showIncludes -DLLVMPlugin_EXPORTS -DLLVM_PLUGIN -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DUNICODE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -D_UNICODE...

...4.4). The command line for compiling my example is: joaquin@CUARTO ~/.wine/drive_c/Qt/4.0.1/examples/tutorial/t1 $ /opt/xmingw/bin/i386-mingw32msvc-g++ main.cpp -o t1.exe -DQT_EDITION=QT_EDITION_DESKTOP -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_GUI_LIB -DQT_THREAD_SUPPORT -pipe -O2 -w -I../../../mkspecs/linux-g++ -I. -I../../../include/QtGui -I../../../include/QtCore -I../../../include -I../../../include/ActiveQt -I. -L/home/joaquin/.wine/drive_c/Qt/4.0.1/lib -lQtCore4 -lQtGui4 And the content of program is: #include <QApplication> #include <QPushButton> int main(int argc, char *...

Processing commands for control at bugs.debian.org: > # the following bugs are closed by packages in NEW > # > tags 431773 pending Bug#431773: libqt4-dev: Missing mkspec files on hppa Tags were: lenny sid patch Bug#427398: scandir syscall broken on hppa Bug#433768: getdent(3) broken on hppa Tags added: pending > tags 433755 pending Bug#433755: Please include dropped header file serial_reg.h in linux-libc-dev Tags were: upstream Tags added: pending > tags 43...

drivers/gpu/drm/nouveau/core/engine/device/nve0.c: In function ?nve0_identify?: drivers/gpu/drm/nouveau/core/engine/device/nve0.c:152:43: error: ?nvc0_devinit_oclass? undeclared (first use in this function) drivers/gpu/drm/nouveau/core/engine/device/nve0.c:152:43: note: each undeclared identifier is reported only once for each function it appears in There's no such object nvc0_devinit_oclass.

...ted to debug info, e.g. to -g. Because I later compiled the same program with RELEASE settings, e.g. $ /usr/src/llvm/dist/bin/g++ -c -pipe --emit-llvm \ -fvisibility=hidden -fvisibility-inlines-hidden \ -Wall -Wextra -Wno-sign-compare -Os \ ... lots of -Dxxxx ... \ -I/usr/share/qt3/mkspecs/default -I. -I.. \ -I../../../include/qt3 -I.obj/ \ -o .obj/FILENAME.o .obj/FILENAME.cpp and linked the result like this: $ /usr/src/llvm/dist/bin/llvm-ld \ -v -stats -native -verify-each -strip-all \ -o main \ ... lots of *.o files ... \ -L/usr/share/qt3/lib -L/usr/X11R6...

At the current time, the environment is using qt3 values, as in $ env | grep QT QTDIR=/usr/lib/qt-3.3 QTINC=/usr/lib/qt-3.3/include QTLIB=/usr/lib/qt-3.3/lib $ env | grep PATH PATH=/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/bin:/usr/bin:/home/pauljohn/bin I also have QT4 installed, and I want programs to find those libraries and include files instead of these ones.

...y\QtSingleApplication\src -I..\src\plugins\thirdParty\LLVM\include -I..\src\plugins\thirdParty\LLVM\lib\Target\X86 -I..\src\plugins\thirdParty\LLVM\src -I..\src\plugins\thirdParty\LLVM\tools\clang\include -IC:\Qt\5.4\msvc2013_64\include -IC:\Qt\5.4\msvc2013_64\include\QtCore -IC:\Qt\5.4\msvc2013_64\mkspecs\win32-msvc2013 /showIncludes -DLLVMPlugin_EXPORTS -DLLVM_PLUGIN -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DUNICODE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -D_UNICODE...

...ude/libxml2 -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtSvg -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -Imoc -isystem /usr/include/libdrm -I/usr/lib64/qt5/mkspecs/linux-g++ -o obj/exception.o src/exception.cpp In file included from src/exception.cpp:18:0: src/exception.h:41:11: error: ?underlying_type_t? in namespace ?std? does not name a type constexpr std::underlying_type_t<Enum> enum_cast (Enum obj_type) noexcept ^ src/exception.cpp: In constructor...

...fPIC -g -W -Wall -m64 -fPIC -DQT_NO_CAST_TO_ASCII -DDEBUG -DLINUX -DLITTLEENDIAN -DQT -DQT_THREAD_SUPPORT -DQT3_SUPPORT -DQT_DEBUG -DBOOST_ALL_NO_LIB -I. -I/home/oyvind/oharboe/packages/linux-amd64-gcc_4_1/qt-4_7_1_patched/include -I/home/oyvind/oharboe/packages/linux-amd64-gcc_4_1/qt-4_7_1_patched/mkspecs/linux-g++-64 -I/home/oyvind/oharboe/packages/linux-amd64-gcc_4_1/boost-1_37_0_patched--python-2_6_1/include -I/home/oyvind/oharboe/packages/linux-amd64-gcc_4_1/python-2_6_1/include/release/python2.6 testsuite/test.cpp In file included from testsuite/test.cpp:8: In file included from ./testsuite/pr...

Whoops, phone rang and I forgot to cc to the list before I typed the message. ----- Forwarded Message ---- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Ruben Van Boxem <vanboxem.ruben at gmail.com> > Sent: Wed, January 5, 2011 3:38:21 PM > Subject: Re: [LLVMdev] include/Config/config.h discrepancies between CMake and >autofoo builds > > > >

2011/1/5 Óscar Fuentes <ofv at wanadoo.es>: > Ruben Van Boxem <vanboxem.ruben at gmail.com> writes: > >> Yeah that's the two different ones I mean. Everything MS (intrinsics, >> language features etc...) is purely version-bound, so I don't even get >> why CMake insists on checking every known function prototype of for >> example "recv"