On 2/26/24 1:41 PM, Richard W.M. Jones wrote:
> It's a bit unfortunate that Rust used the shebang syntax here,
> although in practice they couldn't be confused as these files
> shouldn't ever be executable.
It's _possible_ to play comment tricks for executable rust scripts,
because rustc allows an
Hello,
On Monday, February 26, 2024 4:38:35 PM EST Fabio Valentini wrote:
> > I've run across a strange problem building a package that has some rust
> > files in it. The build goes fine until the end when it starts to check for
> > shebangs. It ends like this:
> >
> >
> > /usr/src/debug/suricat
https://doc.rust-lang.org/reference/attributes.html
If I understand this page of The Rust Reference correctly,
then moving the #![no_std] attribute from the first line of the file
shouldn't break anything. So you can try side-stepping the issue
by patching the file and adding "// lol pointless comm
On Mon, Feb 26, 2024 at 04:25:02PM -0500, Steve Grubb wrote:
> Hello,
>
> I've run across a strange problem building a package that has some rust files
> in it. The build goes fine until the end when it starts to check for
> shebangs.
> It ends like this:
>
> /usr/src/debug/suricata-7.0.3-1.fc
On Mon, Feb 26, 2024, 22:25 Steve Grubb wrote:
> Hello,
>
> I've run across a strange problem building a package that has some rust
> files
> in it. The build goes fine until the end when it starts to check for
> shebangs.
> It ends like this:
>
>
> /usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rus
Hello,
I've run across a strange problem building a package that has some rust files
in it. The build goes fine until the end when it starts to check for shebangs.
It ends like this:
/usr/src/debug/suricata-7.0.3-1.fc41.x86_64/rust/vendor/alloc-no-stdlib/src/
lib.rs has shebang which doesn't st
