Thank you Vladimir, but I'm 100percent positive that patches are applied, i could add my build log but it is quite lengthy , the extract is:
I: Running env PATH=/usr/sbin:/usr/bin:/sbin:/bin dpkg-buildpackage -rfakeroot -us -uc -uc -us dpkg-buildpackage: info: source package openjdk-lts dpkg-buildpackage: info: source version 11.0.19+7~us1-0ubuntu1~18.04.1.1692386031.126726.1 dpkg-buildpackage: info: source distribution bionic-security dpkg-buildpackage: info: source changed by Vladimir Petko < [email protected]> dpkg-source --before-build jdk11u-jdk-11.0.19-7 dpkg-buildpackage: info: host architecture amd64 dpkg-source: info: applying system-pcsclite.diff dpkg-source: info: applying hotspot-mips-align.diff dpkg-source: info: applying icc_loading_with_symlink.diff dpkg-source: info: applying icedtea-override-redirect-compiz.diff dpkg-source: info: applying libpcsclite-dlopen.diff dpkg-source: info: applying jexec.diff dpkg-source: info: applying default-jvm-cfg.diff dpkg-source: info: applying adlc-parser.diff dpkg-source: info: applying multiple-pkcs11-library-init.diff dpkg-source: info: applying s390x-thread-stack-size.diff dpkg-source: info: applying s390x-opt.diff dpkg-source: info: applying jdk-getAccessibleValue.diff dpkg-source: info: applying jtreg-location.diff dpkg-source: info: applying jdk-i18n-pt_BR.diff dpkg-source: info: applying disable-doclint-by-default.diff dpkg-source: info: applying 8199220.diff dpkg-source: info: applying machine-flag.diff dpkg-source: info: applying zero-x32.diff dpkg-source: info: applying hotspot-disable-exec-shield-workaround.diff dpkg-source: info: applying atk-wrapper-security.diff dpkg-source: info: applying dnd-files.diff dpkg-source: info: applying hotspot-libpath.diff dpkg-source: info: applying reproducible-properties-timestamp.diff dpkg-source: info: applying reproducible-javadoc-timestamp.diff dpkg-source: info: applying Don-t-optimize-fdlibm-fork-for-Zero-on-linux-sparc-Z.patch dpkg-source: info: applying keep-gtk2-as-default.patch dpkg-source: info: applying riscv64.diff dpkg-source: info: applying reproducible-character-data.diff dpkg-source: info: applying reproducible-module-info.diff dpkg-source: info: applying reproducible-copyright-headers.diff dpkg-source: info: applying reproducible-build-user.diff dpkg-source: info: applying reproducible-build-jmod.diff dpkg-source: info: applying hotspot-test-fix-npe-on-missing-file.patch dpkg-source: info: applying disable-thumb-assertion.patch dpkg-source: info: applying update-assertion-for-armhf.patch dpkg-source: info: applying log-generated-classes-test.patch dpkg-source: info: applying update-permission-test.patch dpkg-source: info: applying ldap-timeout-test-use-ip.patch dpkg-source: info: applying test-use-ip-address.patch dpkg-source: info: applying exclude-broken-tests.patch debian/rules clean dh_testdir dh_testroot dh_prep I'm building with "debuild -uc -us " maybe it is not enough? On Tue, Aug 29, 2023 at 11:04 PM Vladimir Petko < [email protected]> wrote: > Hi, > > Yes, patches from debian/patches. They can be applied with quilt[1] > and only patches listed in series are needed. > > Best Regards, > Vladimir. > > [1] https://linux.die.net/man/1/quilt > > On Wed, Aug 30, 2023 at 1:19 AM Mykhaylo Lodygin > <[email protected]> wrote: > > > > Hello Vladimir, thank you for your attention, > > did you mean set of patches located in debian/patches ? those are > patched (all in the series file) or some other? > > Mykhaylo > > > > On Mon, Aug 28, 2023 at 11:11 PM Vladimir Petko < > [email protected]> wrote: > >> > >> Hi, > >> > >> I believe this was due to building OpenJDK from Debian original > >> tarball that does not contain bundled libraries. Building from it > >> requires applying Debian patches via `quilt push -a` and using > >> configure arguments from `debian/rules`. > >> > >> Best Regards, > >> Vladimir. > >> > >> On Tue, Aug 29, 2023 at 1:02 AM David Holmes <[email protected]> > wrote: > >> > > >> > On 28/08/2023 9:54 pm, Mykhaylo Lodygin wrote: > >> > > Hello colleagues, > >> > > I've build JDK locally successfully, but got several tests "FAILED". > >> > > >> > What did you build? images? what about test-images? > >> > > >> > > Tried to run one of the failing test separately with "make test > >> > > TEST="<path_to_test>". > >> > > Were unable to do so due to build error - the compiler was > unfamiliar to > >> > > include path to winscard.h, fixed with configuration option: > >> > > bash configure --with-extra-cflags="-I/usr/include/PCSC" > >> > > >> > What test(s), on what platform? > >> > > >> > > next error was incapability of linker to link with libjpeg - fixed > with > >> > > adding --with-libjpeg=system to configure. > >> > > the issue was solved, but a new one was added with missing libgif. > >> > > I was curious and tried a test that "Passed", thinking that > "failure" > >> > > could had happen due to inability to build the test. Tried > >> > > sun/util/calendar/zi/Beyond2037.java but got a very similar error of > >> > > inability to link with liblcms2-2. > >> > > I'm flabbergasted, hence my questions are: does "make test" target > is > >> > > expected to rebuild JDK's code? does my approach of adding options > to > >> > > configure script is proper one? How come a test could be "Passed" > while > >> > > running it separately results in inability to build the test? > >> > > >> > As Erik indicated we need more information/details. > >> > > >> > Cheers, > >> > David > >> > > >> > > >> > > Thank you. > >> > > Mykhaylo Lodygin >
