[cups_dev 0005175]: cups-config is not GCC-compatible

Mantis Bug Tracker via bug-notifications bug-notifications at lists.opencsw.org
Mon Jun 2 10:10:36 CEST 2014


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=5175 
====================================================================== 
Reported By:                laurent
Assigned To:                cgrzemba
====================================================================== 
Project:                    cups_dev
Issue ID:                   5175
Category:                   packaging
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2014-05-28 17:10 CEST
Last Modified:              2014-06-02 10:10 CEST
====================================================================== 
Summary:                    cups-config is not GCC-compatible
Description: 
The cups-config command is called by configure scripts, and returns a line
that contains -x parameters specific to Studio:

/opt/csw/bin/cups-config --libs
-lcups -lgss -L/opt/csw/lib -R/opt/csw/lib -I/opt/csw/include
-I/opt/csw/include -xO3 -m32 -xarch=pentium_pro -xchip=pentium_pro
-I/opt/csw/include/dbus-1.0 -I/opt/csw/lib/dbus-1.0/include
-DDBUS_API_SUBJECT_TO_CHANGE -m32 -L/opt/csw/lib -lkrb5 -lk5crypto
-lcom_err -lresolv -lsocket -lnsl -L/opt/csw/lib -lgnutls -L/opt/csw/lib
-lgcrypt -lgpg-error -lz -lpthread -lresolv -lnsl -lsocket -lm

That makes it difficult to build things depending on it (cups-filters)
====================================================================== 

---------------------------------------------------------------------- 
 (0010845) cgrzemba (manager) - 2014-06-02 10:10
 https://www.opencsw.org/mantis/view.php?id=5175#c10845 
---------------------------------------------------------------------- 
this was pulled through krbconfig. krbconfig is fixed now so simply
repackaging helps to fix.



More information about the bug-notifications mailing list