I have multiple problems with synth and its environment and can someone not find a way to debug these issues. It seems that they are all related to the configuration files synth defines and reads:
The first issue has to do with the /etc/make.conf file, where I define many options for my packages (e.g. I don't need wayland or qt dependencies etc.).
The relevant part comes from the manual page of synth:
For me /etc/make.conf is never read or appended to. Only when /usr/local/etc/synth/LiveSystem-make.conf is an exact copy of /etc/make.conf does synth read my build options. Am I doing something wrong that /etc/make.conf is completely ignored?
The second part has to do with additional variables one can define during build time; the relevant man page entry is:
I'm using the package x11-wm/dwm from the ports tree. It offers an environment variable called
Also this file is completely ignored when building the package with synth. Event though /usr/local/etc/synth/LiveSystem-environment is defined with the proper line.
I can go on with the
Is there any way for me to look at the currently defined environment variables inside synth while it is running or during a test? Something with its setting is seriously off and I doubt that this is a bug in any form since a lot of people are using it succesfully.
The first issue has to do with the /etc/make.conf file, where I define many options for my packages (e.g. I don't need wayland or qt dependencies etc.).
The relevant part comes from the manual page of synth:
Code:
<profile>-make.conf
This is an optional, user-provided file. If it exists,
the builder's /etc/make.conf will be appended with the
contents of this file. For the default profile, the
file would normally be located at
/usr/local/etc/synth/LiveSystem-make.conf
The second part has to do with additional variables one can define during build time; the relevant man page entry is:
Code:
<profile>-environment
This is an optional, user-provided file. It contains a
list of name-value pairs joins with an equals sign
(e.g. HTTP_PROXY=http://proxyserver:8888), one pair per
line. If the file exists, these variables will be de-
fined in the builder environment. For the default pro-
file, the file would normally be located at
/usr/local/etc/synth/LiveSystem-environment
DWM_CONF=/path/to/personal/config.h
to customize its behaviour during compilation. Also this file is completely ignored when building the package with synth. Event though /usr/local/etc/synth/LiveSystem-environment is defined with the proper line.
I can go on with the
OPTIONS_SET += BOOTSTRAP
not working with lang/gcc6-aux and other options working..Is there any way for me to look at the currently defined environment variables inside synth while it is running or during a test? Something with its setting is seriously off and I doubt that this is a bug in any form since a lot of people are using it succesfully.