Opened 21 years ago

Closed 20 years ago

#826 closed defect (wontfix)

nALFS fails to build w/o .la objects

Reported by: winkie@… Owned by: jamie@…
Priority: normal Milestone:
Component: nALFS - Front End (GUI) Version: SVN
Severity: minor Keywords:
Cc:

Description

Let me begin by saying that I remove all *.la objects on my system, a very non-standard thing to do. Everything I use compiles & works fine like this, except nALFS. It fails to build because /usr/lib/lib{curl,xml2}.la are missing.

Replacing those paths in the Makefile with -l{curl,xml2} fixes it, and the

resulting binary works fine. Something is unnecessarily (IMHO) hardcoding the use of libtool objects from the host.

Change History (5)

comment:1 by jwrober@…, 20 years ago

Version: CVSSVN

comment:2 by jamie@…, 20 years ago

Status: newassigned

Offending lines seem to be

line 120: XML2_LIB=${XML2_CONFIG} --libs | sed -e 's/^-L\(.*\) -lxml2.*$/\1/'/libxml2.la

line 152: CURL_LIB=${CURL_CONFIG} --libs | sed -e 's/^-L\(.*\) -lcurl.*$/\1/'/libcurl.la

of bootstrap.configure.

comment:3 by jamie@…, 20 years ago

Owner: changed from alfs-log@… to jamie@…
Status: assignednew

comment:4 by kpfleming@…, 20 years ago

I respectfully disagree that this is a valid issue. When packages install their libraries using libtool, and other libtool-using packages depend on those libraries, it makes sense to use the .la files. There are lots of situations where people can install their packages in non-standard ways and the presence of the .la files will actually _allow_ nALFS to properly link and operate against those libraries. Changing the Makefile to not use the .la files will eliminate this option.

In my mind, this is no different than removing all the .pc files put in by packages that use pkg-config; if you do that, you'll never be able to build large parts of GNOME/KDE, and the maintainers of those packages certainly won't accomodate that situation. We shouldn't either.

comment:5 by jamie@…, 20 years ago

Resolution: wontfix
Status: newclosed

As there has only been one report of a problem with this and its a non-standard anyway I'm going to go with Kevins recommendations and close this with WONTFIX.

Note: See TracTickets for help on using tickets.