pcl-1.6 is available Reproducible: Always Steps to Reproduce: This version is not yet in the tree. Actual Results: It should be. Expected Results: Emerges fine.
Created attachment 196301 [details] The new ebuild This ebuild is mostly identical to the old one for version 1.4, except that the URL had to be modified slightly in order to match upstream's new homepage layout. Tested on amd64: Emerges like a charm.
Created attachment 196329 [details] Test case application for verifying library operation The attached source file for the verification test. Verified to work as expected on amd64. The test team for other platforms might want to use this.
Created attachment 196330 [details] The expected output of the verification text When compiled with the command $ gcc -fno-stack-check -ggdb3 -Wall -O0 -lm hilo.c -lpcl -o hilo and run with the command $ ./hilo .332414645 2 2>& 1 > compare_output the following command should not produce any output $ diff -u run_output compare_output if the verification test is to be successful. The verification tests uses 3 participating coroutines to play a simple number guessing game: One generates pseudo-random number, one impersonates a quiz master, and the last one tries to find the secret number.
Closing bug with resolution fixed, because 1.10 is in Portage alread (even though 1.6 never did make it).
Reopening bug: When I closed the bug premeturely, I was missing the subtle fact that 1.10 came from my own overlay rather than from the Portage tree... ;-) Anyway, updating bump request to 1.10.
Created attachment 233285 [details] Ebuild for version 1.10
Fixed type in Bug title - it's 1.10, not 1.19. Sorry!
Fixed typo in bug title - it's 1.10, not 1.19. Sorry!
Created attachment 233289 [details] Test case application for version 1.10 verifying library operation Updated instructions from Comment #3 for pcl-1.10: When compiled with the command $ gcc -fno-stack-check -ggdb3 -Wall -O0 -lm hilo.c -lpcl -pthread -o hilo and run with the command $ ./hilo .332414645 2 2>& 1 > compare_output the following command should not produce any output $ diff -u run_output compare_output if the verification test is to be successful. The verification tests uses 3 participating coroutines to play a simple number guessing game: One generates pseudo-random number, one impersonates a quiz master, and the last one tries to find the secret number.
Bumped, thanks for the report.
