gmime no longer builds on leopard
A few days ago I installed pan2 and all its dependencies. I'm having problems trying to compile wine so I deleted /opt/local and reinstalled macports. Now, gmime won't build. I get the following error: (cd .libs/libgmime-2.0.lax/libutil.a && ar x /opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_mail_gmime/work/gmime-2.2.10/gmime/../ util/.libs/libutil.a) gcc -dynamiclib ${wl}-flat_namespace ${wl}-undefined ${wl}suppress - o .libs/libgmime-2.0.2.2.10.dylib .libs/gmime.o .libs/gmime- charset.o .libs/gmime-cipher-context.o .libs/gmime-common.o .libs/ gmime-content-type.o .libs/gmime-data-wrapper.o .libs/gmime- disposition.o .libs/gmime-filter.o .libs/gmime-filter-basic.o .libs/ gmime-filter-best.o .libs/gmime-filter-charset.o .libs/gmime-filter- crlf.o .libs/gmime-filter-enriched.o .libs/gmime-filter-from.o .libs/ gmime-filter-gzip.o .libs/gmime-filter-html.o .libs/gmime-filter- md5.o .libs/gmime-filter-strip.o .libs/gmime-filter-windows.o .libs/ gmime-filter-yenc.o .libs/gmime-gpg-context.o .libs/gmime- header.o .libs/gmime-iconv.o .libs/gmime-iconv-utils.o .libs/gmime- message.o .libs/gmime-message-part.o .libs/gmime-message- partial.o .libs/gmime-multipart.o .libs/gmime-multipart- encrypted.o .libs/gmime-multipart-signed.o .libs/gmime-object.o .libs/ gmime-param.o .libs/gmime-parse-utils.o .libs/gmime-parser.o .libs/ gmime-part.o .libs/gmime-session.o .libs/gmime-session-simple.o .libs/ gmime-stream.o .libs/gmime-stream-buffer.o .libs/gmime-stream- cat.o .libs/gmime-stream-file.o .libs/gmime-stream-filter.o .libs/ gmime-stream-fs.o .libs/gmime-stream-mem.o .libs/gmime-stream- mmap.o .libs/gmime-stream-null.o .libs/gmime-utils.o .libs/internet- address.o .libs/libgmime-2.0.lax/libutil.a/cache.o .libs/ libgmime-2.0.lax/libutil.a/gtrie.o .libs/libgmime-2.0.lax/libutil.a/ list.o .libs/libgmime-2.0.lax/libutil.a/md5-utils.o .libs/ libgmime-2.0.lax/libutil.a/memchunk.o .libs/libgmime-2.0.lax/libutil.a/ url-scanner.o -L/opt/local/lib /opt/local/lib/libgobject-2.0.dylib / opt/local/lib/libgmodule-2.0.dylib /opt/local/lib/ libgthread-2.0.dylib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/ libintl.dylib -lz /opt/local/lib/libiconv.dylib -install_name /opt/ local/lib/libgmime-2.0.2.dylib -Wl,-compatibility_version -Wl,5 -Wl,- current_version -Wl,5.10 ld: warning, duplicate dylib /opt/local/lib/libz.1.dylib ld: duplicate symbol _g_bit_nth_lsf in .libs/gmime-charset.o and .libs/ gmime.o collect2: ld returned 1 exit status make[3]: *** [libgmime-2.0.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for gmime): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing.
Hi Michael, Sorry to take so long to reply to this; unfortunately I don't currently find the time to read macports-users much, so I miss posts that I really should reply to.
A few days ago I installed pan2 and all its dependencies. I'm having problems trying to compile wine so I deleted /opt/local and reinstalled macports. Now, gmime won't build. I get the following error:
<snip />
ld: warning, duplicate dylib /opt/local/lib/libz.1.dylib ld: duplicate symbol _g_bit_nth_lsf in .libs/gmime-charset.o and .libs/gmime.o
collect2: ld returned 1 exit status
Since you say that it fails on Leopard, and since I don't get this problem on 10.4.11, it looks to me like it's a bug with Leopard's linker (the ld program). If others can help me confirm that it does indeed occur on Leopard but not on Tiger or Panther, then it'd be great if you could report it upstream to the developer of gmime. It may well be, however, that he won't change the upstream source, arguing that it's a bug with Leopard's linker and so not his problem (a view which I can sympathise with, though I wouldn't agree with it). If that's the case, I think I'd be able to implement a patch by myself; it wouldn't be elegant, but there wouldn't be any significantly better ways around it either. So, others can let me know whether or not they can reproduce the error, that'd be great. We can then look at whether or not to report this upstream. Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
Hi Micheal, Just a quick follow-up: would you be able to file this as a ticket in Trac [1] and assign it to me (see the guide for instructions on how to do so [2])? If you haven't got an account on Trac yet, you can create one with the "Register" link in the top-right corner of any page at trac.macports.org (we enforce registration to avoid spam). Thanks. Kind regards, Maun Suang [1] http://trac.macports.org/projects/macports/newticket [2] http://guide.macports.org/#project.tickets Quoting Boey Maun Suang <boeyms@macports.org>:
Hi Michael,
Sorry to take so long to reply to this; unfortunately I don't currently find the time to read macports-users much, so I miss posts that I really should reply to.
A few days ago I installed pan2 and all its dependencies. I'm having problems trying to compile wine so I deleted /opt/local and reinstalled macports. Now, gmime won't build. I get the following error:
<snip />
ld: warning, duplicate dylib /opt/local/lib/libz.1.dylib ld: duplicate symbol _g_bit_nth_lsf in .libs/gmime-charset.o and .libs/gmime.o
collect2: ld returned 1 exit status
Since you say that it fails on Leopard, and since I don't get this problem on 10.4.11, it looks to me like it's a bug with Leopard's linker (the ld program). If others can help me confirm that it does indeed occur on Leopard but not on Tiger or Panther, then it'd be great if you could report it upstream to the developer of gmime.
It may well be, however, that he won't change the upstream source, arguing that it's a bug with Leopard's linker and so not his problem (a view which I can sympathise with, though I wouldn't agree with it). If that's the case, I think I'd be able to implement a patch by myself; it wouldn't be elegant, but there wouldn't be any significantly better ways around it either.
So, others can let me know whether or not they can reproduce the error, that'd be great. We can then look at whether or not to report this upstream.
Kind regards,
Maun Suang
-- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
participants (2)
-
Boey Maun Suang
-
Michael Staggs