Opened 11 years ago
Closed 11 years ago
#39767 closed defect (worksforme)
poppler @0.22.5_0: build fails with delete_la_files enabled
Reported by: | larryv (Lawrence Velázquez) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.99 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), dbevans (David B. Evans), cooljeanius (Eric Gallager), jeremyhu (Jeremy Huddleston Sequoia) | |
Port: | poppler gettext |
Description
I uninstalled all my ports, set delete_la_files yes
in my macports.conf, and encountered this when subsequently building poppler.
:info:build grep: /opt/local/lib/libintl.la: No such file or directory :info:build sed: /opt/local/lib/libintl.la: No such file or directory :info:build libtool: link: `/opt/local/lib/libintl.la' is not a valid libtool archive :info:build make[3]: *** [libpoppler.la] Error 1
I don’t know whether poppler needs to be fixed, or whether gettext should set destroot.delete_la_files no
.
Attachments (2)
Change History (15)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Summary: | poppler @0.22.5: build cannot find libintl.la with delete_la_files enabled → poppler @0.22.5_0: build fails with delete_la_files enabled |
---|
comment:2 follow-up: 3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
There's no mention of libintl or lintl or gettext in the poppler code or in the log (until that error message). Where is this request for libintl.la coming from?
Have you tried again, a few times? Is the issue reproducible? We previously had intermittent "not a valid libtool archive" errors (#30809) that we could not explain that went away on retrying.
Changed 11 years ago by larryv (Lawrence Velázquez)
less… colorful… version, using 2.2.0-rc1 instead of my sailor-tongued trunk checkout
Changed 11 years ago by larryv (Lawrence Velázquez)
Attachment: | main.2.log added |
---|
with use_parallel_build=no
comment:3 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to ryandesign@…:
There's no mention of libintl or lintl or gettext in the poppler code or in the log (until that error message). Where is this request for libintl.la coming from?
Have you tried again, a few times? Is the issue reproducible? We previously had intermittent "not a valid libtool archive" errors (#30809) that we could not explain that went away on retrying.
I’ve tried the build around 10 times, unsuccessfully. Disabling parallel building didn’t help, either.
comment:4 Changed 11 years ago by larryv (Lawrence Velázquez)
Version: | 2.2.99 → 2.1.99 |
---|
comment:5 follow-up: 7 Changed 11 years ago by cooljeanius (Eric Gallager)
Maybe poppler could use an explicit library dependency on gettext? That's what I do in my local copy of the poppler portfile, at least... Although I'm not running with delete_la_files
turned on though, so idk if that would necessarily fix this problem... it's worth a shot, though.
comment:7 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to egall@…:
Maybe poppler could use an explicit library dependency on gettext? That's what I do in my local copy of the poppler portfile, at least... Although I'm not running with
delete_la_files
turned on though, so idk if that would necessarily fix this problem... it's worth a shot, though.
It would fix nothing. I already have gettext installed, as indicated by the ls
output I provided in comment:1. And as Ryan said in comment:2, poppler doesn’t seem to reference or request gettext or anything related to gettext.
comment:8 Changed 11 years ago by larryv (Lawrence Velázquez)
Cc: | jeremyhu@… added |
---|
Jeremy, do you also see this issue building poppler with delete_la_files
enabled?
comment:9 follow-up: 12 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
poppler builds fine for me on SnowLeopard through Mavericks using delete_la_files.
Are you building everything from source?
My hunch is that you have some prebuilt packages (meaning they were not built with delete_la_files) and some built from-source.
We should probably force not using prebuilt packages if the user changes delete_la_files from the default state.
comment:10 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
What is the output of 'ls -l /opt/local/lib/*.la'
I bet if you deleted all of those it would work...
comment:11 Changed 11 years ago by jmroot (Joshua Root)
Well, the ability to set delete_la_files in macports.conf is undocumented for a reason. The only good reason to change it from the default is if you installed an older version of base on Mavericks and don't want to rebuild all your ports yet. So yeah, if you change it, you're responsible for dealing with the consequences, like not being able to use the standard archives.
comment:12 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to jeremyhu@…:
poppler builds fine for me on SnowLeopard through Mavericks using delete_la_files.
Are you building everything from source?
My hunch is that you have some prebuilt packages (meaning they were not built with delete_la_files) and some built from-source.
ARGH. I think you’re right.
% grep -l 'libintl\.la' /opt/local/lib/*.la /opt/local/lib/libcairo-gobject.la /opt/local/lib/libcurl.la /opt/local/lib/libgdbm.la /opt/local/lib/libgio-2.0.la /opt/local/lib/libgirepository-1.0.la /opt/local/lib/libglib-2.0.la /opt/local/lib/libgmodule-2.0.la /opt/local/lib/libgobject-2.0.la /opt/local/lib/libgthread-2.0.la /opt/local/lib/libharfbuzz.la /opt/local/lib/libidn.la /opt/local/lib/libneon.la /opt/local/lib/libpopt.la /opt/local/lib/libsvn_client-1.la /opt/local/lib/libsvn_delta-1.la /opt/local/lib/libsvn_diff-1.la /opt/local/lib/libsvn_fs-1.la /opt/local/lib/libsvn_fs_base-1.la /opt/local/lib/libsvn_fs_fs-1.la /opt/local/lib/libsvn_fs_util-1.la /opt/local/lib/libsvn_ra-1.la /opt/local/lib/libsvn_ra_local-1.la /opt/local/lib/libsvn_ra_neon-1.la /opt/local/lib/libsvn_ra_serf-1.la /opt/local/lib/libsvn_ra_svn-1.la /opt/local/lib/libsvn_repos-1.la /opt/local/lib/libsvn_subr-1.la /opt/local/lib/libsvn_wc-1.la %
comment:13 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
< ... set 'buildfromsource always'
And the file in question does not exist.