No dice. g++ -Wall -D_FILE_OFFSET_BITS=64 -D__FreeBSD__=10 -O -g -arch i386 - arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -I/usr/local/ include -o procfs procfs.o procfs_displays.o procfs_proc_info.o procfs_tpm.o sequencegrab/libprocfs_sequencegrab.a -L/usr/local/lib - lfuse -framework Carbon -framework IOKit -framework ApplicationServices -framework Accelerate -framework OpenGL - weak_library /usr/lib/libproc.dylib -arch i386 -arch ppc /usr/local/ lib/libpcrecpp.a /usr/local/lib/libpcre.a sequencegrab/ libprocfs_sequencegrab.a -framework AudioUnit -framework Cocoa - framework CoreAudioKit -framework Foundation -framework QuartzCore - framework QuickTime -framework QuartzCore /usr/bin/ld: for architecture ppc /usr/bin/ld: can't open: /usr/lib/libproc.dylib (No such file or directory, errno = 2) collect2: ld returned 1 exit status /usr/bin/ld: for architecture i386 /usr/bin/ld: can't open: /usr/lib/libproc.dylib (No such file or directory, errno = 2) collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//ccoYXAfo.out (No such file or directory) make: *** [procfs] Error 1
On Jun 8, 10:40 am, Amit Singh <[EMAIL PROTECTED]> wrote: > That's because in the top-level Makefile, LDFLAGS still has "-lproc". > At runtime, the linker is looking for libproc.dylib, although the > binary doesn't actually need anything from that library. > > I've changed the Makefile to weak link against libproc. Try that. > > Amit > > On Jun 8, 8:33 am, Christopher <[EMAIL PROTECTED]> wrote: > > > Amit, > > > You are correct, I'm on a G5 system. You are definitely on the right > > track, though I'm still having the same problem. Whatever you did > > cleaned up a minor link error that I was getting in sequencegrabber (I > > had fixed it earlier by removing the -arch i386 from the > > sequencegrabber Makefile). > > > So in short, I'm getting a perfectly clean compilation now from > > unmodified source (minus the deprecated QuickDraw stuff), but on both > > the downloaded binary and the compilation binary, I'm still getting > > the same dyld error. > > > Chris > > > On Jun 8, 1:50 am, Amit Singh <[EMAIL PROTECTED]> wrote: > > > > Hmm ... you must be on a PowerPC system. procfs-1.5 has a feature that > > > depends on libproc, which (IIRC) is x86-only because it uses an x86- > > > only system call. I should have remember this earlier. > > > > I've reorganized the code so that the feature (the /proc/<pid>/fds > > > file) doesn't get compiled for PowerPC. Either try recompiling the > > > latest source or try the binary for procfs 1.51. > > > > Amit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
