Failed to install with make install

Question

Failed to install with make install

ValorKand opened this issue 10 months ago · 7 comments

Describe the bug

Hello :D, i'm trying to install the toolbox from the source, because i'm using Fedora Linux, i've Swift already installing and correctly working. But when I'm trying to install the toolbox i receive a error message.

To Reproduce

I downloaded the latest version of the source code from the releases section
Extracted the file into my download folder
Into the folder in run the make install command from terminal
And i receive the next error output:

swiftc ./scripts/build.swift
warning: direct reference to protected function $sSJ12isWhitespaceSbvg' in /usr/libexec/swift/5.8.1/bin/../lib/swift/linux/libswiftCore.so' may break pointer equality
./build
Swift/ErrorType.swift:200: Fatal error: Error raised at top level: build.ShellError(terminationStatus: 128)
Current stack trace:
0 libswiftCore.so 0x00007f5ba6e6f150 swift_stdlib_reportFatalErrorInFile + 112
1 libswiftCore.so 0x00007f5ba6b603bf + 1442751
2 libswiftCore.so 0x00007f5ba6b601d7 + 1442263
3 libswiftCore.so 0x00007f5ba6b5efe0 assertionFailure(::file:line🎏) + 364
4 libswiftCore.so 0x00007f5ba6bbde46 + 1826374
5 build 0x00005583e6c65137 + 8503
6 libc.so.6 0x00007f5ba684614a + 164170
7 libc.so.6 0x00007f5ba6846180 __libc_start_main + 139
8 build 0x00005583e6c64e65 + 7781
make: *** [Makefile:5: build] Instrucción ilegal (core dumped) [Núcleo vaciado a un archivo]
make: *** Se borra el archivo 'build'

Steps to reproduce the behavior:

Add package with configuration '...'
Send request with options '...'
See error

Expected behavior

I expected to run correctly the vapor toolbox, so, I follow correctly all the described steps in the installation documentation.

Environment

Vapor Framework version: 18.7.4
Vapor Toolbox version: 18.7.4
OS version: Fedora Linux 39 Workstation Edition

Additional context

Add any other context about the problem here.

Answer 1 · 2024-01-24T17:50:34.000Z

Can you try with Swift 5.9.2? And if that doesn't work, what's the output of swift build -c release

Answer 2 · 2024-01-25T02:54:27.000Z

Can you try with Swift 5.9.2? And if that doesn't work, what's the output of swift build -c release

I tried with the 5.9.2 version, and it doesn't work, the output of swift build -c release is:

/home/davidvales/Descargas/toolbox/.build/checkouts/swift-log/Sources/Logging/Logging.swift:1392:64: error: value of optional type 'UnsafeMutablePointer?' must be unwrapped to a value of type 'UnsafeMutablePointer'
strftime(&buffer, buffer.count, "%Y-%m-%dT%H:%M:%S%z", localTime)
^
/home/davidvales/Descargas/toolbox/.build/checkouts/swift-log/Sources/Logging/Logging.swift:1391:13: note: short-circuit using 'guard' to exit this function early if the optional value contains 'nil'
let localTime = localtime(&timestamp)
^
guard else { return <#default value#> }
/home/davidvales/Descargas/toolbox/.build/checkouts/swift-log/Sources/Logging/Logging.swift:1391:25: note: coalesce using '??' to provide a default when the optional value contains 'nil'
let localTime = localtime(&timestamp)
^
?? <#default value#>
/home/davidvales/Descargas/toolbox/.build/checkouts/swift-log/Sources/Logging/Logging.swift:1391:25: note: force-unwrap using '!' to abort execution if the optional value contains 'nil'
let localTime = localtime(&timestamp)
^
!
/home/davidvales/Descargas/toolbox/.build/checkouts/swift-log/Sources/Logging/Logging.swift:1392:64: note: coalesce using '??' to provide a default when the optional value contains 'nil'
strftime(&buffer, buffer.count, "%Y-%m-%dT%H:%M:%S%z", localTime)
^
?? <#default value#>
/home/davidvales/Descargas/toolbox/.build/checkouts/swift-log/Sources/Logging/Logging.swift:1392:64: note: force-unwrap using '!' to abort execution if the optional value contains 'nil'
strftime(&buffer, buffer.count, "%Y-%m-%dT%H:%M:%S%z", localTime)
^
!
error: fatalError
[1/9] Compiling c-nioatomics.c

Answer 3 · 2024-01-25T12:00:14.000Z

@ValorKand ah this was due to Swift Log not working on musl. Can you pull down the latest changes from main and try again? #444 should have fixed it

Answer 4 · 2024-01-25T13:27:47.000Z

@ValorKand ah this was due to Swift Log not working on musl. Can you pull down the latest changes from main and try again? #444 should have fixed it

@0xTim hi, I tried pull the main again. with the swift build -c release the output is:

define RENAME_NOREPLACE (1 << 0)

/home/davidvales/Descargas/toolbox/.build/checkouts/swift-nio/Sources/CNIOLinux/shim.c:204:9: warning: 'RENAME_EXCHANGE' macro redefined [-Wmacro-redefined]
#define RENAME_EXCHANGE 2
^
/usr/include/stdio.h:170:10: note: previous definition is here

define RENAME_EXCHANGE (1 << 1)

2 warnings generated.
[44/44] Linking vapor
Build complete! (76.86s)

it seems that is all ok, so, i run the make install and i got the next error:

swiftc ./scripts/build.swift
./build
Swift/ErrorType.swift:200: Fatal error: Error raised at top level: build.ShellError(terminationStatus: 1)

💣 Program crashed: Illegal instruction at 0x00007f52aa763d12

Thread 0 "build" crashed:

0 0x00007f52aa763d12 assertionFailure(:_:file:line🎏) + 354 in libswiftCore.so
1 0x00007f52aa7cacfc swift_errorInMain + 619 in libswiftCore.so
2 0x00005607000e5167 main + 54 in build
3 0x00007f52a976514a __libc_start_call_main + 121 in libc.so.6
4 0x00007f52a976520b __libc_start_main@GLIBC_2.2.5 + 138 in libc.so.6

Backtrace took 0.05s

make: *** [Makefile:5: build] Instrucción ilegal (core dumped) [Núcleo vaciado a un archivo]
make: *** Se borra el archivo 'build'

😭

Answer 5 · 2024-01-26T18:42:19.000Z

Ok so something is likely different on Fedora to what the toolbox supports. We (and Swift) don't officially support Fedora so you probably are going to struggle.

What I would say is that if you're developing a Vapor app, you might want to use a supported platform. If this is for deployment, consider Docker. And if you want to preserve you can try manually running the steps in the Makefile to see what is failing and to install it manually. We could accept a patch to make it work on Fedora but I suspect that it will be more involved than that

Answer 6 · 2024-01-27T18:26:28.000Z

Okay, i see, so, i will try it in a supported platform, thanks for the help and the attention :3

Answer 7 · 2024-01-28T00:18:59.000Z

Ok so something is likely different on Fedora to what the toolbox supports. We (and Swift) don't officially support Fedora so you probably are going to struggle.

What I would say is that if you're developing a Vapor app, you might want to use a supported platform. If this is for deployment, consider Docker. And if you want to preserve you can try manually running the steps in the Makefile to see what is failing and to install it manually. We could accept a patch to make it work on Fedora but I suspect that it will be more involved than that

I resolve the problem.

I erase all of vapor firstly.
clone the vapor repo again and git pull origin main
then, swift build -c release --disable-sandbox, the build finished successfully.
Finally, sudo cp .build/release/vapor /usr/local/bin (manually copy the compiled program to path)