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 <david.hol...@oracle.com> 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
