On Fri, 30 Aug 2013 04:03:25 +0200 Cedric Blancher wrote: > On 29 August 2013 22:11, Glenn Fowler <[email protected]> wrote: > > > > On Thu, 29 Aug 2013 22:02:21 +0200 Roland Mainz wrote: > >> On Thu, Aug 29, 2013 at 7:45 PM, Glenn Fowler <[email protected]> > >> wrote: > >> > > >> > the AT&T Software Technology ast alpha 2013-08-29 source release > >> > has been posted to the download site > >> > http://www.research.att.com/sw/download/alpha/ > >> > the package names and md5 checksums are > >> > INIT 132e0403af573fa1cb1e202267fedeb8 > >> > ast-open 334615fb3a652575106194c281d27b5c > >> > ast-ksh ebcc56d9ab673aaafbb163d6eee1a93c > >> > the md5 sums should match the ones listed on the download page > > > > when using non-default options please qualify "doesn't build" > > (even though you provided the cc line which hints at it) > > in this case I believe its > > "... doesn't build using PACKAGE_OPTIONS=map-libc ..." > > which means this or something equivalent > > bin/package make PACKAGE_OPTIONS=map-libc
> Wait. > Isn't PACKAGE_OPTIONS=map-libc enabled by default when no other > options are given? It doesn't make sense to build without it, at least > on Linux. right now its not on by default anywhere however it looks like its a losing battle to expect symbols from a user lib to override those symbols referenced inside a system library I believe that malloc & friends are the only ones that will survive in the end for now it will stay this way but probably within the next few months map-libc will be the default except for malloc so ast malloc will be used everywhere and we'll have a similar option that will map malloc => _ast_malloc _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
