Em 15-05-2013 18:37, Matias A. Fonzo escreveu:
> El Wed, 15 May 2013 16:12:15 -0500
> William Harrington <[email protected]> escribió:
>>
>> On May 15, 2013, at 4:12 PM, Matias A. Fonzo wrote:
>>
>>> Seems the `less' of busybox, the output of `less -V' is:
>>>
>>> less 451 (POSIX regular expressions)
>>> [..]
>>>
***********************************************************************
>>> So.. the integer cannot be compared.
***********************************************************************
>>
>> This is a jhalfs build of LFS. Thus no busybox.
>
> OK.
>
> I have less-444 and less-451, the string "(POSIX regular
> expressions)" come from the latest versions.
Ok, starting to understand the problem. Fortunately, seems not to be
elsewhere in a more vital place of the system, so not much to worry, I
believe.
Thank you very much, Matias.
Em 15-05-2013 18:20, Michael E. Maher escreveu:> On Wed, 2013-05-15 at
18:11 -0300, Fernando wrote:
>> Em 15-05-2013 17:54, Michael E. Maher escreveu:>
>>
>>> On Wed, 2013-05-15 at 17:47 -0300, Fernando wrote:
>>>> error message:
>>>> /usr/bin/xzless: line 49: test: 458 (POSIX regular expressions):
integer
>>>> expression expected
...
>>>> Line 49 of xzless is:
>>>>
>>>> if test "$(less -V | { read ver && echo ${ver#less }; })" -ge 429; then
>>>
>>> Looks like the command:
>>> `less -V | { read ver && echo ${ver#less }; }'
>>> Is giving something other than an integer (from: integer expression
>>> expected).
>>>
>>> Could you give us the output of:
>>> $ less -V
>>> $ less -V | { read ver && echo ${ver#less }; }
...
>> root [ /tmp ]# less -V
>> less 458 (POSIX regular expressions)
...
>> root [ /tmp ]# less -V | { read ver && echo ${ver#less }; }
>> 458 (POSIX regular expressions)
...
> Hi Fernando,
>
> The mail from Matias really says it all, it's the extra `(POSIX regular
> expressions)' which is screwing up the integer comparison `if test "..."
> -ge 429; then'.
>
> This seems like a bug in either:
> less -V giving too much information for xz
> - or -
> xzless assuming that less -V is a certain way
>
> For a quick (untested) hack, you could remove the check or change the
> statement to:
>
***********************************************************************
> if test "$(less -V | { read ver && echo ${ver#less }; } | awk '{print
> $1}')" -ge 429; then
***********************************************************************
> I'm sure others on this list will be able to give much better answers.
> It's probably good to file a bug with the relevant upstream in any case.
>
>
> Hope that helps,
> Thanks,
> Michael
Thank you, Michael. I believe it will help a lot, indeed.
I will use the test you propose, as xzless is much used by me, annoying
having always that message.
I am not very comfortable in filing a bug, but will search a little more
and will do it, if it is not there yet.
Em 15-05-2013 17:53, William Harrington escreveu:>
> On May 15, 2013, at 3:47 PM, Fernando wrote:
>
>> xzless
>> /home/fernando/Downloads/blfs/links-2.7-2013.05.15-17h21m20s.log.xz
>
> /usr/bin/xzless: line 49: test: 458 (POSIX regular expressions): integer
> expression expected
>
> Line 49 is also an error when a filename isn't given.
>
> Works fine here.
>
> xzless links-2.7.tar.xz
>
> I get output
>
***********************************************************************
> xzless (without a filename)
>
> get the error plus this:
>
> /usr/bin/xzless: line 49: test: 458 (POSIX regular expressions): integer
> expression expected
> Missing filename ("less --help" for help)
***********************************************************************
>
> Sincerely,
>
> William Harrington
Thanks, William,
Tested that, the same happens here.
Again, thank you all for the replies.
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
