found the problem. change DIRS in /sys/src/ape/lib/ap/mkfile to
include $objtype (the badly named patch mkfile-broken i just submitted
has the fix). you'll need to recompile libap.
the old mkfile had the $objtype hidden in the 'for' loop in install.
putting it in the DIRS definition makes it more
oops, the first line in my paste in the previous message should not
have "/386/lib/libc.a" in it: it's a leftover from editing. the line
should match the output from mk as it shows in /sys/src/ape/cmd/diff
i just did a pull: it's not only links that fails, it's everything in
/sys/src/ape/cmd :)
from a first glance it looks like not all libraries are linked (a few
pragmas missing?). for example, by adding libc to the mix you get rid
of all warnings but one. the following example is from
/sys/src/ape
That's what I used, and I just tried again with the same
result. I guess that means I have something messed up
somewhere else?
Greg
> use /n/sources/contrib/andrey/links.tgz it compiles fine.
>
> On 7/15/07, Gregory Pavelcak <[EMAIL PROTECTED]> wrote:
>> png_debug_malloc: undefined: memset in pn
use /n/sources/contrib/andrey/links.tgz it compiles fine.
On 7/15/07, Gregory Pavelcak <[EMAIL PROTECTED]> wrote:
png_debug_malloc: undefined: memset in png_debug_malloc
test_one_file: undefined: setjmp in test_one_file
test_one_file: undefined: strcpy in test_one_file
test_one_file: undefined:
png_debug_malloc: undefined: memset in png_debug_malloc
test_one_file: undefined: setjmp in test_one_file
test_one_file: undefined: strcpy in test_one_file
test_one_file: undefined: memcmp in test_one_file
png_memcpy_check: undefined: memcpy in png_memcpy_check
png_check_keyword: undefined: strlen
