RE: Bazel Symbolic Links

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Yes, Bazel cares for everything and that's why we are getting this problem.
We just wanted to check with you if there is an option in GCC to not resolve symbolic links. We hoped GCC is flexible enough to handle this or you have good ideas to solve this.
It would be disappointing if it's not possible to solve, as we would prefer not to search for another compiler.

Thanks & Regards,
Vaishali Pundir

-----Original Message-----
From: Jeff Law <jeffreyalaw@xxxxxxxxx>
Sent: Friday, December 13, 2024 7:39 PM
To: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>; Pundir, Vaishali (623) <vaishali.pundir@xxxxxxxxxxxxxxxxx>
Cc: Andrew C Aitchison <andrew@xxxxxxxxxxxxxxx>; gcc-help <gcc-help@xxxxxxxxxxx>
Subject: Re: Bazel Symbolic Links

[**EXTERNAL E-MAIL**]

On 12/13/24 2:33 AM, Jonathan Wakely via Gcc-help wrote:
> On Fri, 13 Dec 2024, 06:32 vaishali.pundir--- via Gcc-help, <
> gcc-help@xxxxxxxxxxx> wrote:
>
>> Hi Mr. Andrew C Aitchison,
>>
>> We have tried using the "-no-canonical-prefixes" option, but
>> unfortunately, it didn't resolve the issue. Below is the list of
>> compiler options we are using:
>>
>>          "-DBRS_PLATFORM_RH850",
>>          "-DBRS_COMP_GHS",
>>          "-DVMEM_30_RH850FACI01_HSM_ACTIVE",
>>          "-fprofile-arcs",
>>           "-ftest-coverage",
>>           "-g",
>>           "-O2",
>>          "-no-canonical-prefixes",
>>          "-Iexternal/+_repo_rules+test_sip /components/xxxx",
>>
>> The "-I" include path is a symbolic link to a local directory
>> dynamically created by Bazel. During compilation, it is being
>> resolved automatically to an absolute path like
>> D:/test/sip_test/components/xxxx/test.h, which is causing problems because Bazel does not accept absolute paths.
>>
>
> Why does bazel care how paths are resolved during compilation? You are
> not providing enough information to understand your issue.
Bazel cares about *everything*.  It's kind of inherent in its design to want to know every file accessed during a build.

> https://bazel.build/basics/hermeticity


We could debate the pros/cons, but bazel is what it is...  I avoid it when I can.

jeff

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.





[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux