From: 桂永林 <guiyonglin@huaqin.com>
To: "LIU Hao" <lh_mouse@126.com>, "Tom Kacvinsky" <tkacvins@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>, 柳茂昕 <liumaoxin@huaqin.com>,
李闯闯 <lichuangchuang@huaqin.com>
Subject: Re: Re: GCC link error help!
Date: Mon, 11 Oct 2021 15:57:19 +0800 (GMT+08:00) [thread overview]
Message-ID: <1cf5571.17138.17c6e5b269b.Coremail.guiyonglin@huaqin.com> (raw)
In-Reply-To: <0e6a4bba-872f-92e5-af61-e5cc94a2b547@126.com>
Hellow Tom and Liu Hao,
Thanks for your quickly and warmly reply!!! We will try to discuss with our customer to try these suggested mesthods to resolve this proble.
Thanks again!
Operagui
发件人：LIU Hao <lh_mouse@126.com>
发送时间：2021-10-11 14:43
主题：Re: GCC link error help!
收件人："Tom Kacvinsky"<tkacvins@gmail.com>,"桂永林/图灵研究院软件三部/图灵研究院"<guiyonglin@huaqin.com>
抄送："gcc-help"<gcc-help@gcc.gnu.org>,"柳茂昕/图灵研究院软件三部/图灵研究院"<liumaoxin@huaqin.com>,"李闯闯/图灵研究院软件三部/图灵研究院"<lichuangchuang@huaqin.com>
在 10/11/21 1:10 PM, Tom Kacvinsky via Gcc-help 写道:
>>
>> It seems that the link can not fond some lib, but the real reason is that
>> the project path and source code file on windows environment is too long.
>> But,if we use the same GCC version to compile my project on Linux
>> enviroment, it can compile sucess. The GCC compiler and source code we used
>> on Linux is same with Windos.
>> We don't know how the GCC restict the path lenth and source code file
The conventional DOS path has a hard limit of 259 characters: 3 for the drive letter and immediate
colon-slash, and 256 for the path itself. (If the null terminator is counted then it's 260
characters, which is exactly the value of `PATH_MAX`.)
The simple solution is to move the toolchain to somewhere shallower, apparently.
The permanent solution to this problem would be using UNC paths. For example, instead of writing
`C:\Windows`, you write `\\?\C:\Windows`. This makes use of a 64KiB buffer, but please note Windows
NT uses UTF-16 paths, so the length limit of a path is 32767 UTF-16 code units.
--
Best regards,
LIU Hao
next prev parent reply other threads:[~2021-10-11 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 3:23 桂永林
2021-10-11 5:10 ` Tom Kacvinsky
2021-10-11 6:43 ` LIU Hao
2021-10-11 7:57 ` 桂永林 [this message]
2021-10-20 14:53 ` GCC link problem help! 桂永林
2021-10-20 16:17 ` Xi Ruoyao
2021-10-21 3:36 ` 桂永林
2021-10-21 12:04 ` Xi Ruoyao
2021-10-21 12:34 ` Jonathan Wakely
2021-10-22 3:37 ` 桂永林
[not found] ` <617231DF.3080808@huaqin.com>
2021-10-22 3:39 ` 桂永林
2021-10-22 7:06 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1cf5571.17138.17c6e5b269b.Coremail.guiyonglin@huaqin.com \
--to=guiyonglin@huaqin.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=lichuangchuang@huaqin.com \
--cc=liumaoxin@huaqin.com \
--cc=tkacvins@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).