Linux linux-2c5j 3.1.0-desktop #1 SMP PREEMPT Thu Nov 3 16:26:25 CET 2011 i686 i686 i386 GNU/Linux
While trying to compile Mesa 7.11 in order to install the newest Intel video drivers for my 915i chipset the ./configure coplains as follows:
No package 'libdrm_nouveau' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables NOUVEAU_CFLAGS
and NOUVEAU_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Now I would like to avoid to install libdrm-nouveau because this is a laptop with intel only chipset. I looked at the manpage but I am not sure which flags I should set (c-flags??) and how the right sintax would be.
Thanks for every suggestion.
So I tried ./configure --help in the respective directory and found out by try and error the right (hope) syntax:
`configure' configures Mesa 7.11.0 to adapt to many kinds of systems.
Usage: ./configure [OPTION]... [VAR=VALUE]...
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
Defaults for the options are specified in brackets.
Edit: which I did overcome by installing the LLVM from the repos. Now it is through and says run make to build MESA. One question to whoever knows this: I did run ./configure on mesa without “prefix”. Does opensuse use standard directories for MESA or do I have to specify a specific prefix when compiling it?
Forgive me my ignorance. I am compiling from the source of Mesa (since 11.1 does not have any support any more and I need to have the newest Intel driver running). The spec file that I did well open is the program running within the rpm install, right?
In what step would I use this information. For (after) running make? Or within the ./configure step.
Have patience, the learning curve is steep in this point. So taking into account that I am not working in IT but I am more a “well minded kamikaze with excellent suicidal attitude”, I will need slightly more “hints” to understand.
BTW, the config.log says the following up to now: MESA config.log - Pastebin.com
Which seems quite O.K. to me, but the errors about confdefs.h.
or am I wrong?
> After a long runs this ends with:
> In file included from …/…/…/…/src/gbm/main/common.h:31,
> from gbm_driint.h:33,
> from gbm_dri.c:42:
> /usr/include/libudev.h:28:2: error: #error “#define
> LIBUDEV_I_KNOW_THE_API_IS_SUBJECT_TO_CHANGE is needed to usethis
> experimental library version” gmake: *** [gbm_dri.o] Error 1
> gmake: Leaving directory
> `/usr/src/packages/BUILD/Mesa-7.11/src/gbm/backends/dri’ gmake: ***
[default] Error 1 gmake: Leaving directory /usr/src/packages/BUILD/Mesa-7.11/src/gbm/backends' gmake: *** > [default] Error 1 gmake: Leaving directory > /usr/src/packages/BUILD/Mesa-7.11/src/gbm’ make: *** [subdirs] Error
1 make: Leaving directory `/usr/src/packages/BUILD/Mesa-7.11/src’
> make: *** [default] Error 1 error: Bad exit status from
> /var/tmp/rpm-tmp.31032 (%install)
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.31032 (%install)
> Well, this brings the next question: how do I define “libudev”, or
> better where? :\ (if you are still knowledgeable about this error).
I have no idea if that is really the right thing to do here but what about #define LIBUDEV_I_KNOW_THE_API_IS_SUBJECT_TO_CHANGE
just before the #include <libudev.h>
in the files which include libudev.h
PC: oS 11.4 (dual boot 12.1 RC2) 64 bit | Intel Core firstname.lastname@example.orgGHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom email@example.comGHz | KDE 4.6.0 | nVidia
ION | 3GB Ram
To come back on this project, since I have the original source code…and it compiles without errors, I might use this one. Question to anyone: if I do uninstall Mesa and then do the make, make install, in case it does NOT write in the right directory, would a manual elimination of the new directory and a reinstall of the rpm work?
Just to know how much risk I am taking right now.
P.S. note that the compile.log talks about a “build-in spec file for suse” and seems to write to these directories:
Hello. I hope that Malcolmlevis or Martin are around to give an hand to this question. Or naturally whoever sees this.
I tried to do the last step after ./configure, make = make install. The install goes up to a point where it complains about a wrong version (what I understand of gmake but I am not 100% sure). I would like to print out the error message but substantially … i do not know how.
While installing I am in Init 1 (I thought this would be a convenient idea, you can tell me if I am wrong). I do not know however how to log the error message from init 1 in the command line. Is there any way to protocol an install done via “make install”? How would I do this?
A lot of questions, even if you know only one answer, do not hesitate to post.
(as this is Evergreen 11.1, I departure from Mesa 7.2).
glxinfo | grep OpenGL
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.2
GNU Make 3.81
Copyright (C) 2006 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
This program built for i686-pc-linux-gnu
Am 26.11.2011 17:56, schrieb stakanov:
> make install | error txt | outpubt.tx
This will not redirect the error output stream and will result in an
“>” redirects stdout to a file
“2>” redirects stderr to a file