On Thursday 18 July 2013 16:59:52 Matt Turner wrote:
> On Mon, Feb 4, 2013 at 6:27 PM, Mike Frysinger wrote:
> > The current gen_matypes logic assumes that the host compiler will produce
> > information that is useful for the target compiler. Unfortunately, this
> > is
from the gen_matypes.c source, then process
it with a shell script to create a usable header. This is similar to how
the linux kernel creates its asm-offsets.c file.
Signed-off-by: Mike Frysinger
---
configure.ac| 6 ++
src/mesa/x86-64/Makefile.am | 10 ++
src/mes
-off-by: Mike Frysinger
---
bin/mklib | 42 --
1 file changed, 24 insertions(+), 18 deletions(-)
diff --git a/bin/mklib b/bin/mklib
index 9bac29e..086b268 100755
--- a/bin/mklib
+++ b/bin/mklib
@@ -319,6 +319,25 @@ case $ARCH in
fi
fi
On Wed, Jun 13, 2012 at 8:13 AM, Dan Nicholson wrote:
> On Tue, Jun 12, 2012 at 3:52 PM, Mike Frysinger
> wrote:
> > On Tue, Jun 12, 2012 at 6:47 PM, Dan Nicholson
> wrote:
> >>
> >> On 6/12/12, Stéphane Marchesin wrote:
> >> > From: Mike Frysi
On Tue, Jun 12, 2012 at 6:47 PM, Dan Nicholson wrote:
> On 6/12/12, Stéphane Marchesin wrote:
> > From: Mike Frysinger
> >
> > The intent of the message above it is right (we need to build those
> > dependencies in that order) but the implementation is wrong, as it
from the gen_matypes.c source, then process
it with a shell script to create a usable header. This is similar to how
the linux kernel creates its asm-offsets.c file.
Signed-off-by: Mike Frysinger
---
Note: please keep me on cc as i'm not subscribed
configs/autoconf.in|2 ++
co
