[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OS/2: command-line length limit
From: |
KO Myung-Hun |
Subject: |
Re: OS/2: command-line length limit |
Date: |
Fri, 17 Dec 2010 21:20:38 +0900 |
User-agent: |
Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.1.16) Gecko/20101127 SeaMonkey/2.0.11 |
Hi/2.
Ralf Wildenhues wrote:
> Hello again,
>
> * KO Myung-Hun wrote on Sun, Nov 28, 2010 at 07:20:32AM CET:
>> --- libltdl/m4/libtool.m4.org 2010-09-22 17:41:18.000000000 +0900
>> +++ libltdl/m4/libtool.m4 2010-11-27 16:03:50.000000000 +0900
>> @@ -1624,6 +1624,9 @@
>> lt_cv_sys_max_cmd_len=32768
>> fi
>> ;;
>> + os2*)
>> + lt_cv_sys_max_cmd_len=-1
>> + ;;
>> *)
>> lt_cv_sys_max_cmd_len=`(getconf ARG_MAX) 2> /dev/null`
>> if test -n "$lt_cv_sys_max_cmd_len"; then
>
> Is there really no maximum for the command line length on OS/2?
It depends on a shell. I know, a default shell, cmd.exe, has 1024 length
limit. But 4OS2.exe has other limit.
In case of pdksh which is used really, it seems to have no limits.
Although a computed length by libtool is 8192, it could handle a longer
command line than 8192.
When porting VLC to OS/2, qt4 module needed a very long command line. So
libtool try to create a reload object. The maximum length was 8192 at
that time. Setting it to -1 does not need a reload object.
By this, I set the maximum length to -1.
> That would be really surprising to me, on a system which limits
> it DLL basenames to 8 characters. ;-)
> But if it is so, then the patch is obviously ok.
>
What a stupid heritage from a legacy FAT !!!
> Or did you do this in order to avoid an expensive check?
One of the causes. ^^
> What does the check do without the above change? Does it finish?
> Does the machine hang or need a reboot?
>
As I said above, the result is 8192.
--
KO Myung-Hun
Using Mozilla SeaMonkey 2.0.11
Under OS/2 Warp 4 for Korean with FixPak #15
On AMD ThunderBird 1GHz with 512 MB RAM
Korean OS/2 User Community : http://www.ecomstation.co.kr