You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by GitBox <gi...@apache.org> on 2020/09/24 09:01:56 UTC

[GitHub] [incubator-nuttx] xiaoxiang781216 opened a new pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

xiaoxiang781216 opened a new pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888


   ## Summary
   by define _FILE_OFFSET_BITS to 64 described here:
   https://man7.org/linux/man-pages/man2/stat.2.html
   
   ## Impact
   
   ## Testing
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] acassis commented on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
acassis commented on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-699220207


   > > Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   > > EOVERFLOW
   > > pathname or fd refers to a file whose size, inode number, or
   > > number of blocks cannot be represented in, respectively, the
   > > types off_t, ino_t, or blkcnt_t. This error can occur when,
   > > for example, an application compiled on a 32-bit platform
   > > without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
   > > size exceeds (1<<31)-1 bytes.
   > 
   > @acassis Your means define _FILE_OFFSET_BITS only when mkdeps.c is compiled with CONFIG_SIM_M32? But it is no much difference because 64bits interface is default option on 64bits OS.
   
   Yes, you are right, the default is 64-bit. I was on 32-bit mode yet :-)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] acassis commented on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
acassis commented on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698327219


   Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   
   EOVERFLOW
                 pathname or fd refers to a file whose size, inode number, or
                 number of blocks cannot be represented in, respectively, the
                 types off_t, ino_t, or blkcnt_t.  This error can occur when,
                 for example, an application compiled on a 32-bit platform
                 without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
                 size exceeds (1<<31)-1 bytes.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] xiaoxiang781216 edited a comment on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
xiaoxiang781216 edited a comment on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698349259


   > Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   > 
   > EOVERFLOW
   > pathname or fd refers to a file whose size, inode number, or
   > number of blocks cannot be represented in, respectively, the
   > types off_t, ino_t, or blkcnt_t. This error can occur when,
   > for example, an application compiled on a 32-bit platform
   > without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
   > size exceeds (1<<31)-1 bytes.
   
   @acassis Your means define _FILE_OFFSET_BITS only when mkdeps.c is compiled with CONFIG_SIM_M32? But it is no much difference because 64bits interface is default option on 64bits OS.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] xiaoxiang781216 edited a comment on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
xiaoxiang781216 edited a comment on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698349259


   > Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   > 
   > EOVERFLOW
   > pathname or fd refers to a file whose size, inode number, or
   > number of blocks cannot be represented in, respectively, the
   > types off_t, ino_t, or blkcnt_t. This error can occur when,
   > for example, an application compiled on a 32-bit platform
   > without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
   > size exceeds (1<<31)-1 bytes.
   
   @acassis Your means define _FILE_OFFSET_BITS only when mkdeps.c is compiled with CONFIG_SIM_M32? But it isn't much difference because 64bits interface is default option on 64bits OS.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] xiaoxiang781216 commented on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
xiaoxiang781216 commented on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698349259


   > Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   > 
   > EOVERFLOW
   > pathname or fd refers to a file whose size, inode number, or
   > number of blocks cannot be represented in, respectively, the
   > types off_t, ino_t, or blkcnt_t. This error can occur when,
   > for example, an application compiled on a 32-bit platform
   > without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
   > size exceeds (1<<31)-1 bytes.
   
   Your means define _FILE_OFFSET_BITS only when mkdeps.c is compiled with CONFIG_SIM_M32? But it isn't much difference because 64bits interface is default option on 64bits OS.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] xiaoxiang781216 edited a comment on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
xiaoxiang781216 edited a comment on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698349259






----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] acassis commented on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
acassis commented on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698327219


   Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   
   EOVERFLOW
                 pathname or fd refers to a file whose size, inode number, or
                 number of blocks cannot be represented in, respectively, the
                 types off_t, ino_t, or blkcnt_t.  This error can occur when,
                 for example, an application compiled on a 32-bit platform
                 without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
                 size exceeds (1<<31)-1 bytes.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] xiaoxiang781216 commented on pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
xiaoxiang781216 commented on pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888#issuecomment-698349259


   > Hi @xiaoxiang781216, should this value be defined to 64-bit on 32-bit arch only when the application is compiled with "-D_FILE_OFFSET_BITS=64" ? Without "-D_FILE_OFFSET_BITS=64" I think the default is 32-bit and the EOVERFLOW will happen:
   > 
   > EOVERFLOW
   > pathname or fd refers to a file whose size, inode number, or
   > number of blocks cannot be represented in, respectively, the
   > types off_t, ino_t, or blkcnt_t. This error can occur when,
   > for example, an application compiled on a 32-bit platform
   > without -D_FILE_OFFSET_BITS=64 calls stat() on a file whose
   > size exceeds (1<<31)-1 bytes.
   
   Your means define _FILE_OFFSET_BITS only when mkdeps.c is compiled with CONFIG_SIM_M32? But it isn't much difference because 64bits interface is default option on 64bits OS.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [incubator-nuttx] acassis merged pull request #1888: tools/mkdeps: Fix EOVERFLOW returned by stat when CONFIG_SIM_M32=y

Posted by GitBox <gi...@apache.org>.
acassis merged pull request #1888:
URL: https://github.com/apache/incubator-nuttx/pull/1888


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org