Opened 13 years ago
Closed 13 years ago
#29621 closed defect (invalid)
libplist @1.4 Build failure: Missing Macro Definitions
Reported by: | macports@… | Owned by: | rmstonecipher@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ||
Port: | libplist |
Description
Hi...
Libplist fails to build on 10.6.7 using XCode 3.2.6. It seems some macros (G_GNUC_INTERNAL, G_USEC_PER_SEC, etc.) are undeclared when they are needed in plist.h . A build log is attached.
Excerpt (first lines with errors):
In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.c:25: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:55: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'plist_t' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:56: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'plist_data_t' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:57: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'plist_data_t' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:58: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'gboolean' In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/bplist.c:31: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:55: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'plist_t' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:56: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'plist_data_t' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:57: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'plist_data_t' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/work/libplist-1.4/src/plist.h:58: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'gboolean'
Attachments (2)
Change History (7)
Changed 13 years ago by macports@…
Attachment: | libplist_build.txt added |
---|
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | rmstonecipher@… openmaintainer@… removed |
---|---|
Owner: | changed from macports-tickets@… to rmstonecipher@… |
It builds fine for me on 10.6.7 with Xcode 3.2.6. Can you please attach a complete main.log -- one that does not contain lines containing "Skipping completed"?
sudo port clean sudo port install libplist
Changed 13 years ago by macports@…
Attachment: | libplist_main.log added |
---|
comment:3 Changed 13 years ago by macports@…
Is there a possibility, that we could try to figure out why libplist fails to recognize the glib headers ?
I'm digging around a bit, but I am no port expert. What I see is, that glib.h should be included from the code, but somehow is not. Could this have its roots in the configure part? How is the path to the glib files obtained?
comment:4 Changed 13 years ago by macports@…
Instead of using the headers from the macports directory, some old stuff which was installed to /Library/Frameworks/GLib.framework was included. I put that into the trash and now libplist builds.
Would it be possible to change the configure script to prefer the glib installation from the macports directory (/opt/local/lib) before any other installation on the system? It would prevent such installation trouble...
Thanks anyway.
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
That's going to be a general problem with all ports -- software installed in /Library/Frameworks, /usr/local, /usr, /sw, can conflict with MacPorts ports. Just uninstall those other installations.
Output of sudo port -d build libplist >~/libplist_build.txt 2>&1