Custom Query (204 matches)
Results (106 - 108 of 204)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#155 | fixed | create a rpm for the bjnp cups backend | ||
Description |
cups 2.1.3-7 Attempting to print the cups Test Page from the browser interface fails which displays "Filter failed". I killed cupsd and opened the log with a text editor - I did try opening the error log from the Admin page of the browser interface but and unknown username/password combination is required. The log indicates the print job failed due to "gstoraster stopped with status 11." |
|||
#156 | fixed | autoconf: Make options with spaces supported in LDFLAGS etc. | ||
Description |
autoconf has a problem that prevents from using options with spaces in LDFLAGS and other similar variables (e.g. a typical #!/bin/sh ac_link='python.exe -c "import sys; print sys.argv" $LDFLAGS' LDFLAGS="-lcx -Zlinker 'DISABLE 1121'" eval "$ac_link" You will get this output: ['-c', '-lcx', '-Zlinker', "'DISABLE", "1121'"]
Where you can clearly see that the value for the -Zlinker option was split instead of being passed as a whole. In case of a compiler, this makes it think that Note that the problem only shows up in autoconf when LDFLAGS appears in eval and such. And this happens in many places, e.g. in AC_CHECK_LIB functions which simply start always failing in such a case. |
|||
#159 | fixed | dash appears to mangle variable expansion in RPM scriptlets, etc. | ||
Description |
Installing libodin with dash as default shell creates junk entries in ODIN.INI, rendering (for example) Java half-broken: [DEVDIRECTORIES] WINDOWS=M:^Kar\lib\odin [ODINSYSTEM] PE_EXE=M:\usin\PE.EXE PEC_EXE=M:\usin\PEC.EXE W16ODIN_EXE=M:\usin\W16ODIN.EXE This junk handling is also propagated to the Odin32 registry entries. Apparently, bash handles these things properly, as does ash. However, shifting from dash to ash as the default shell is not very easy. |