Attachment 33467 Details for Bug 26674 – Makefile update to link egl progs with libm

[patch] Makefile update to link egl progs with libm

0001-Link-egl-progs-to-libm-as-necessary.patch (text/plain), 1.43 KB, created by ataraxia937 on 2010-02-20 19:31:19 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: ataraxia937

Created: 2010-02-20 19:31:19 UTC

Size: 1.43 KB

patch

obsolete

>From a013f49e2b13dce778e392c9e5759b1c10b37ee4 Mon Sep 17 00:00:00 2001
>From: Ray Kohler <ataraxia937@gmail.com>
>Date: Sat, 20 Feb 2010 22:26:43 -0500
>Subject: [PATCH] Link egl progs to libm as necessary.
>
>Signed-off-by: Ray Kohler <ataraxia937@gmail.com>
>---
> progs/egl/Makefile |    8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/progs/egl/Makefile b/progs/egl/Makefile
>index 0ddb2ca..c003cf3 100644
>--- a/progs/egl/Makefile
>+++ b/progs/egl/Makefile
>@@ -48,19 +48,19 @@ eglinfo: eglinfo.o $(HEADERS) $(LIB_DEP)
> 	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS)
> 
> eglgears: eglgears.o $(HEADERS) $(LIB_DEP)
>-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) $(LIBDRM_LIB)
>+	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) $(LIBDRM_LIB) -lm
> 
> eglscreen: eglscreen.o $(HEADERS) $(LIB_DEP)
> 	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) $(LIBDRM_LIB)
> 
> peglgears: peglgears.o $(HEADERS) $(LIB_DEP)
>-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) $(LIBDRM_LIB)
>+	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) $(LIBDRM_LIB) -lm
> 
> xeglgears: xeglgears.o $(HEADERS) $(LIB_DEP)
>-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lX11
>+	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lX11 -lm
> 
> xeglthreads: xeglthreads.o $(HEADERS) $(LIB_DEP)
>-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lX11
>+	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lX11 -lm
> 
> xegl_tri: xegl_tri.o $(HEADERS) $(LIB_DEP)
> 	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lX11
>-- 
>1.7.0
>

Actions: View | Splinter Review

Attachments on bug 26674: 33467

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.