Summary: | build error: hardcode_minus_L | ||
---|---|---|---|
Product: | UIM | Reporter: | UTUMI Hirosi <utuhiro78> |
Component: | Other | Assignee: | uim-bugs |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | patch |
Description
UTUMI Hirosi
2009-05-02 02:09:55 UTC
I guess gettext related m4 files in our repository are too old. You can try "gettextize -f -c" before invoking ./autogen.sh, and see what happens. If it works I should remove these files from our repository and insert gettextize command in the autogen.sh. *** Bug 21519 has been marked as a duplicate of this bug. *** ###################################################### take 1 ###################################################### $ gettextize -f -c Copying file ABOUT-NLS Copying file config.rpath Not copying intl/ directory. Copying file po/Makefile.in.in Copying file po/Makevars.template Copying file po/Rules-quot Copying file po/boldquot.sed Copying file po/en@boldquot.header Copying file po/en@quot.header Copying file po/insert-header.sin Copying file po/quot.sed Copying file po/remove-potcdate.sin Adding an entry to po/ChangeLog (backup is in po/ChangeLog~) Copying file m4/gettext.m4 Copying file m4/iconv.m4 Copying file m4/lib-ld.m4 Copying file m4/lib-link.m4 Copying file m4/lib-prefix.m4 Copying file m4/nls.m4 Copying file m4/po.m4 Copying file m4/progtest.m4 Adding an entry to m4/ChangeLog (backup is in m4/ChangeLog~) Updating Makefile.am (backup is in Makefile.am~) Updating configure.ac (backup is in configure.ac~) Creating ChangeLog Please run 'aclocal -I m4' to regenerate the aclocal.m4 file. You need aclocal from GNU automake 1.9 (or newer) to do this. Then run 'autoconf' to regenerate the configure file. You will also need config.guess and config.sub, which you can get from the CVS of the 'config' project at http://savannah.gnu.org/. The commands to fetch them are $ wget 'http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess' $ wget 'http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub' You might also want to copy the convenience header file gettext.h from the /usr/share/gettext directory into your package. It is a wrapper around <libintl.h> that implements the configure --disable-nls option. Press Return to acknowledge the previous three paragraphs. ###################################################### take 2 ###################################################### $ ./autogen.sh m4/expat.m4:10: warning: underquoted definition of AM_WITH_EXPAT m4/expat.m4:10: run info '(automake)Extending aclocal' m4/expat.m4:10: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal configure.ac:1564: error: `po/Makefile.in' is already registered with AC_CONFIG_FILES. ../../lib/autoconf/status.m4:305: AC_CONFIG_FILES is expanded from... configure.ac:1564: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 ###################################################### take 3 ###################################################### $ aclocal -I m4 m4/expat.m4:10: warning: underquoted definition of AM_WITH_EXPAT m4/expat.m4:10: run info '(automake)Extending aclocal' m4/expat.m4:10: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal configure.ac:1564: error: `po/Makefile.in' is already registered with AC_CONFIG_FILES. ../../lib/autoconf/status.m4:305: AC_CONFIG_FILES is expanded from... configure.ac:1564: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 ////// I'm using automake-1.10.2. (In reply to comment #3) > take 3 > ###################################################### > $ aclocal -I m4 > m4/expat.m4:10: warning: underquoted definition of AM_WITH_EXPAT > m4/expat.m4:10: run info '(automake)Extending aclocal' > m4/expat.m4:10: or see > http://sources.redhat.com/automake/automake.html#Extending-aclocal > configure.ac:1564: error: `po/Makefile.in' is already registered with > AC_CONFIG_FILES. > ../../lib/autoconf/status.m4:305: AC_CONFIG_FILES is expanded from... > configure.ac:1564: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > aclocal: autom4te failed with exit status: 1 Hmm... it isn't easier than I expected. What happens if you remove po/Makefile.in from the list of AC_CONFIG_FILES() in configure.ac? Or can you find where po/Makefile.in is registered before line 1564 of configure.ac? OK. I investigated the libtool-2 problem on Fedora 11 Preview. I also encountered the "libtool: link: unsupported hardcode properties" error. It seems missing config.rpath causes this problem. Could try reverting to the original state (i.e. revert to the original m4 files) and copy /usr/share/gettext/config.rpth to the root of uim build directory, and then ./autogen.sh && ./configure --enable-maintainer-mode && make ? I think this should solve the problem. BTW, I also tried "gettextize -f -c" and ./autogen.sh on Fedora 11 Preview, and it turned out that uim compiles without any breakage too. I'm not sure why you got "configure.ac:1564: error: `po/Makefile.in' is already registered with AC_CONFIG_FILES.". So, to avoid gettextize problem which may depend on the build environment, I'm going to update m4 files in uim repository instead of removing them from the repository and put gettexize in autogen.sh as I proposed in the previous comment. > copy /usr/share/gettext/config.rpath Cool. Everything is working properly now. I can build uim, and uim-qt4 works fine on kwrite4. Thank you so much. > I also encountered the "libtool: link: unsupported hardcode properties" error. Ah, maybe I got the error too. I uploaded uim source RPM for Mandriva 2009.1. http://sourceforge.net/project/showfiles.php?group_id=109779&package_id=119961 I think people need uim-1.5.6. :-) fixed in r5955 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.