Is there a way to disable the implicit `-L/usr/lib64` with `architecture "x86_64"`

[Emily-TTG]

What's your question?
When building a project with the architecture set to x86_64 and the compiler being either GCC or Clang (only tested with gmake, unsure about other backends), premake adds a -L/usr/lib64 near the start of the linker command line. This leads to the linker preferring system libraries over ones specified in linkoptions that appear later in the command line.

Some of my library paths are specified via. linkoptions as I am consuming pkg-config output.

Is there a way to disable this behaviour while still having the architecture set? It is undesirable for me as I want to ensure my project draws from local dependencies during linkage instead of whatever system ones the user may or may not have installed.

Anything else we should know?
A basic reproduction of this issue can be achieved by the following:

-- premake5.lua
workspace "Workspace"
	configurations { "Debug", "Release" }

	project "Test"
		kind "ConsoleApp"
		architecture "x86_64"

		files { "test.c" }
		linkoptions { "-Lwhatever" }

$ premake5 gmake
$ make verbose=1
...
g++ -o "bin/Debug/Test" obj/Debug/test.o   -L/usr/lib64 -m64 -s -Lwhatever

[nickclark2016]

Currently, there's no API to disable this. You may be able to get around this by doing something like:

premake.tools.gcc.libraryDirectories.architecture.x86_64 = {}

That said, we should probably provide an API to opt out of this behavior. Thoughts on something like usesystemlibs "Off". I'm trying to figure out what a good name would be. @samsinsane thoughts?

[Jarod42]

I indeed got similar issues mixing links and linkoptions from some xxx-config.
I workaround that by replacing links by linkoptions.

premake.tools.gcc.librayDirectories.architecture = nil might be a workaround to avoid to add -L/usr/lib64 in your case.

[Emily-TTG]

@Jarod42 that workaround seems to work for me yes. Will keep an eye here for a more formal solution in future

[samsinsane]

@nickclark2016 do we even need to specify these paths? Are they not part of the default paths in GCC and Clang?

[nickclark2016]

I was honestly wondering the same question here. I don't think we do.

[Jarod42]

From history, it was added by 458dcb8#diff-7d5bd87bc5ac480437d0167a366cbc58cac4934d00f91a740fcc4fb5e7e2d70e

That -L/usr/lib64 seems indeed superfluous.