🚀 go-pugleaf

Since 3.0, I've lost the ability to compile a profiled application and
link it with the library sys_p.  I can find no way to perform linking
using cc that doesn't generate reams of duplicate symbols if I tell
it to link with sys_p; i.e.,

% cc -g -pg -O -Wall -DPROFILE -ObjC -sectcreate __ICON
__header g.iconheader -segprot __ICON r r -sectcreate __ICON app
/usr/lib/NextStep/Workspace.app/application.tiff -o g.profile/g
profile_obj/g_main.o -lNeXT_p -lsys_p

... generates ...

/bin/ld: multiple definitions of symbol .objc_class_name_MethodSignature
/lib/libsys_p.a(NXProxy.o) definition of absolute .objc_class_name_MethodSignature (value 0x0)
/lib/libsys_s.a(NXProxy.o) definition of absolute .objc_class_name_MethodSignature (value 0x0)

... etc., on and on and on.

Further, invoking ld by hand seems to "work" -- it will generate a
runnable binary without complaint -- but programs generated in this
manner seg fault from within objc_msgSend before getting very far.
I.e.,

% ld -ObjC -sectcreate __ICON __header g.iconheader -segprot __ICON r
r -sectcreate __ICON app /usr/lib/NextStep/Workspace.app/application.tiff
-o g.profile/g profile_obj/g_main.o /lib/crt0.o -lNeXT_p -lsys_p

... generates a program without error; its exit code is 0.  But if
you run the program, it crashes instantly.  Note that this particular
program doesn't even have any code I wrote; it has no central brain.
It's the complete minimum possible application generated with PB and
IB.

Anyone know why it doesn't work?  Or better yet, how to make it
work?

...jkd
--
jdawson@ccwf.cc.utexas.edu (John Dawson)