Hello
The problem I'm currently facing is the removal (unset) of the LDFLAGS variable
within the glibc compile step.
A bit of background information:
I'm working on reproducible builds and found one major problem which occurs by
many of the packages. By default, the debug information is extract
ngliche Nachricht-
Von: Patrick Ohly [mailto:patrick.o...@intel.com]
Gesendet: Dienstag, 25. Oktober 2016 11:32
An: Blaettler, Michael (BT CPS R&D ZG FW ITW)
Cc: yocto@yoctoproject.org; Ismo Puustinen; André Draszik
Betreff: Re: AW: [yocto] curl-native and ca-bundle
On Tue, 2016-10-25 at 05:49 +, Blae
]
Gesendet: Montag, 24. Oktober 2016 15:14
An: Blaettler, Michael (BT CPS R&D ZG FW ITW)
Cc: yocto@yoctoproject.org; Ismo Puustinen; André Draszik
Betreff: Re: [yocto] curl-native and ca-bundle
On Mon, 2016-10-24 at 07:20 +0000, Blaettler, Michael wrote:
> Hi all
>
> We just had an issue
Hi all
We just had an issue in regard to curl-native.
By default curl is configured with the
"--with-ca-bundle=${sysconfdir}/ssl/certs/ca-certificates.crt" flag.
In case curl-native is builded the ${sysconfdir} of the current project is
compiled into the binary. Due to sstate caching the binary
Hi all
I am currently struggling with selecting the Java virtual machine and Java
compiler. I'd like to use the Java VM and Java Compiler provided by
openjdk-8-native in the meta-java layer.
It was possible to build openjdk-8-native without any problems but after
sourcing the environment-script