h2o / h2o

H2O - the optimized HTTP/1, HTTP/2, HTTP/3 server

Home Page:https://h2o.examp1e.net

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Again C99 build error on FreeBSD

utrenkner opened this issue · comments

On Friday, I wanted to test the new fix for "handling of headers appearing more than once" (#3185). However, I could not get over a C99 error on FreeBSD 13.1-RELEASE-p5, which looks similar to earlier problems (#2933 , #2944). I tried further today, but without luck:

/home/uwe/test/h2o/deps/neverbleed/neverbleed.c:1302:11: error: implicit declaration of function 'pthread_setaffinity_np' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
    ret = pthread_setaffinity_np(pthread_self(), sizeof(NEVERBLEED_CPU_SET_T), &cpuset);
          ^

Does anyone know how to work around this?

@dch @kazuho You solved similar problems, in the past. May I kindly ask you to have a look at this issue? Maybe it can be fixed rather easily, based on your previous solutions?

@dch @kazuho I am not a developer, but to me it looks as if the solution used in main.c could be adapted for neverbleed.c.

Hey sorry for the delay, I think the issue has been addressed now, with #3220 incorporating h2o/neverbleed#56.

@kazuho Many thanks - I confirm that both problems are solved (wrong folding of set-cookie fields, C99 error)!

@dch That would be great! I managed to modify the current version of www/h2o-devel for the latest commit 43cf4e6. I successfully built the package from this version. I'll send you my patch directly, because GH somehow does not let me attach it here.

Hey sorry for the inconvenience.

As you may have noticed, we have a vulnerability fix that has to be merged; please see GHSA-p5hj-phwj-hrvx.

@dch I would appreciate it if you could pick that up as well.

FWIW regarding the release model, I am sorry that we are failing to make releases, I had recently started my work to transition to a new model; please see #3230.

@Kazuhu Thank you for the heads-up concerning the security patch.

@dch I have just sent you my updated patch for www/h2o-devel including the security relevant commit. I do not know how you want to deal with www/h2o, though. You may have to bring that to the latest patch level as well. Maybe with the new release model, the -devel port becomes obsolete anyway?