<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 13-10-01 11:11 AM, Martin-Éric Racine wrote: </div> <blockquote cite="mid:CAPZXPQdagv-M_E0t4RK+COOeVLPP4tefXNdcBru5vEMt+0dvGg@mail.gmail.com" type="cite"> <pre wrap="">2013/10/1 Gaetan Nadon <a class="moz-txt-link-rfc2396E" href="mailto:memsize@videotron.ca"><memsize@videotron.ca></a>: </pre> <blockquote type="cite"> <pre wrap="">If you are going for a round of upgrades, here are some suggestions. COPYING: review the content of the file to insure it matches the copyright statements in the source code (which may have changed). NEWS: review content README: review content TODO: dating from 2007. Update or delete </pre> </blockquote> <pre wrap=""> Agreed. </pre> <blockquote type="cite"> <pre wrap="">The configure.ac file is in pristine condition. You may bump the minimum autoconf versionfrom 2.59 to 2.60 like other xorg modules. </pre> </blockquote> <pre wrap=""> Why not. Most distros seem to have something around 2.64 as current. </pre> </blockquote> Great <blockquote cite="mid:CAPZXPQdagv-M_E0t4RK+COOeVLPP4tefXNdcBru5vEMt+0dvGg@mail.gmail.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">You may also bump xorg-macros version from 1.4 to whatever your development environment is at. This will tell developers which feature they are allowed to use from xorg-macros package. </pre> </blockquote> <pre wrap=""> We purposely choose to remain conservative on this aspect.</pre> </blockquote> Still good. <blockquote cite="mid:CAPZXPQdagv-M_E0t4RK+COOeVLPP4tefXNdcBru5vEMt+0dvGg@mail.gmail.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">I can help with the m4 directory, there are some pitfalls to avoid, as simple as it may look. </pre> </blockquote> <pre wrap=""> I borrowed the attached bits from xf86-video-intel. Does this look good?</pre> </blockquote> They have a macro checked-in git in the m4 dir. You cannot have an empty m4 dir under git control. Some project put a dummy README file but I prefer putting a .gitignore there containing the libtool stuff to ignore: libtool libtool.m4 ltmain.sh lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4 which fits perfectly with the overall design of having of .gitignore per directory. Given you don't have a macro of your own in m4, you won't need ACLOCAL_AMFLAGS = ${ACLOCAL_FLAGS} -I m4 in the toplevel makefile. Starting automake 1.14, implementation changes make this variable obsolete. When testing, do a fresh module clone. While we are talking build, I have a couple of questions; <blockquote> <ol> <li>Is there anything that would make it difficult for Geode to move up to libtool 2.2?</li> <li>If yes, and if the rest of xorg was to move to libtool 2.2, would that be a problem for building geode with libtool 1.5? (do you typically build geode only or do you also build other modules like libraries, apps, server, etc...) </li> </ol> </blockquote> Thanks! <blockquote cite="mid:CAPZXPQdagv-M_E0t4RK+COOeVLPP4tefXNdcBru5vEMt+0dvGg@mail.gmail.com" type="cite"> <pre wrap=""> Martin-Éric </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Xorg-driver-geode mailing list <a class="moz-txt-link-abbreviated" href="mailto:Xorg-driver-geode@lists.x.org">Xorg-driver-geode@lists.x.org</a> <a class="moz-txt-link-freetext" href="http://lists.x.org/mailman/listinfo/xorg-driver-geode">http://lists.x.org/mailman/listinfo/xorg-driver-geode</a> </pre> </blockquote> </body> </html>