Bug 21281 - Mesa 7.4.1 dont produce .so 's, missing *.dylib
Summary: Mesa 7.4.1 dont produce .so 's, missing *.dylib
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/FFB (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium blocker
Assignee: Default DRI bug account
QA Contact:
Keywords: regression
Depends on:
Reported: 2009-04-19 06:25 UTC by w.landgraf
Modified: 2010-12-02 11:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description w.landgraf 2009-04-19 06:25:17 UTC
mesa 7.4.1 compiles but dont produce drivers by missing .dylib 's f.ex. libGLw.1/dylib: no such file or directory

In several progs - like /common/utils.c , glcontextmodes.c , clientattrib.c - it was necessary to delete the lines with GLcontextModes  bindToTexturl.Rgb, .Rgba, texture, targets and another one, they would not be part of that.

After these corrections, at least libglut.so.3.7.1 and some drivers are  produced, but the main GL libs not. 

Also, in some makefiles it was necessary to write expressively the lib install path, because it produces seperated "  's which gave problems to the compiler.

I compile/pack habitually progs for a distro, made about 1500 packages, I would give the quality of the programming/testing/service of mesa the predicate 'very bad'.  It's one of the buggiest programs and what normally needs days to get compiled.  

Comment 1 Brian Paul 2009-04-20 14:55:22 UTC
I don't really understand all your comments.

For example, AFAIK, *.dylib files are only applicable to MacOS, not Linux.

I don't recall anyone else reporting the problems you describe.  Perhaps you could be more specific about one or two of the issues you're seeing.
Comment 2 Matt Turner 2010-12-02 11:05:43 UTC
But is filed against an old version and a component that doesn't exist anymore, and doesn't really make sense on top of that. Closing. Please reopen with a better description if this is a problem.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.