Re: buildincludes: don't know how to make libelf.h etc.
On 11/19/15 10:39 AM, Franco Fichtner wrote: > Hi Bryan, > > Apologies for the delay. Yes, this is still happening. > > This is the script I'm using with some trampoline things in > a makefile and a common.sh script. It works on releng/10.1 and > releng/10.2 without modification: > > https://github.com/opnsense/tools/blob/master/build/base.sh > > In any of the 11-CURRENT revisions of the last two weeks I've > ran into this issue for buildworld, but not for buildkernel. > > If I run this command sequence in a shell directly, 11-CURRENT > builds fine. > > My latest step was filtering the environment while calling > buildworld and I've had no issues. While it's true that the > environment is polluted with variables for various build > steps, it feels like a regression, because that wasn't needed > on 10.x at all. > > I've double-checked by running the unfiltered script again > and it runs into the same issues as described in the original > message. > > What is the stance regarding environment poisoning and the > source tree build framework? Is this a best effort setup > or does identifying the bad env variables matter? I can > probably chase them down if needed. > >> On 10 Nov 2015, at 1:21 AM, Bryan Drewery wrote: >> >> What exact release of 10.1 are you on? The release, or somewhere in head >> during the 10.1 lifecycle? > > 10.1-RELEASE-p24 > >> What revision were you trying to build? > > Any of the HEAD revisions of the last two weeks, sorry for > not being more specific here, but this wasn't related to any > specific code churn. > >> What do you have in /etc/make.conf and /etc/src.conf? > > https://github.com/opnsense/tools/blob/master/config/latest/make.conf > https://github.com/opnsense/tools/blob/master/config/latest/src.conf > >> What exact command did you run? > > See above. > >> Can you provide a full buildworld log please? Nothing sticks out as a problem in the above. Do you have unknown files in your checkout? Can you check with 'git status' or 'svn status' ? > > Only if really needed. > I think it will be needed. Feel free to send me it off list. > > Cheers, > Franco > -- Regards, Bryan Drewery ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildincludes: don't know how to make libelf.h etc.
Hi Bryan, Apologies for the delay. Yes, this is still happening. This is the script I'm using with some trampoline things in a makefile and a common.sh script. It works on releng/10.1 and releng/10.2 without modification: https://github.com/opnsense/tools/blob/master/build/base.sh In any of the 11-CURRENT revisions of the last two weeks I've ran into this issue for buildworld, but not for buildkernel. If I run this command sequence in a shell directly, 11-CURRENT builds fine. My latest step was filtering the environment while calling buildworld and I've had no issues. While it's true that the environment is polluted with variables for various build steps, it feels like a regression, because that wasn't needed on 10.x at all. I've double-checked by running the unfiltered script again and it runs into the same issues as described in the original message. What is the stance regarding environment poisoning and the source tree build framework? Is this a best effort setup or does identifying the bad env variables matter? I can probably chase them down if needed. > On 10 Nov 2015, at 1:21 AM, Bryan Drewery wrote: > > What exact release of 10.1 are you on? The release, or somewhere in head > during the 10.1 lifecycle? 10.1-RELEASE-p24 > What revision were you trying to build? Any of the HEAD revisions of the last two weeks, sorry for not being more specific here, but this wasn't related to any specific code churn. > What do you have in /etc/make.conf and /etc/src.conf? https://github.com/opnsense/tools/blob/master/config/latest/make.conf https://github.com/opnsense/tools/blob/master/config/latest/src.conf > What exact command did you run? See above. > Can you provide a full buildworld log please? Only if really needed. Cheers, Franco ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildincludes: don't know how to make libelf.h etc.
On 11/9/2015 4:21 PM, Bryan Drewery wrote: > On 11/8/2015 10:41 AM, Franco Fichtner wrote: >> Hi everyone, >> >> I'm trying to build 11-CURRENT, but seeing missing header files >> in lib/libelf, lib/libdwarf and lib/nucurses during a seemingly >> simple `make buildworld' run. >> >> The include files land e.g. in a tmp/legacy/usr/include object >> path and copying them manually fixes that particular issue until >> the next error is triggered. >> >> I'm currently using 10.1 to build 11-CURRENT. Has anyone else >> seen this or has any idea how to solve this? >> >> > > Are you still having this problem? > > What exact release of 10.1 are you on? The release, or somewhere in head > during the 10.1 lifecycle? > > What revision were you trying to build? > > What do you have in /etc/make.conf and /etc/src.conf? > > What exact command did you run? > > Can you provide a full buildworld log please? > Also check your source tree for unknown files, such as with 'svn status'. You might have files in there which prevent an objdir from being used properly. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: buildincludes: don't know how to make libelf.h etc.
On 11/8/2015 10:41 AM, Franco Fichtner wrote: > Hi everyone, > > I'm trying to build 11-CURRENT, but seeing missing header files > in lib/libelf, lib/libdwarf and lib/nucurses during a seemingly > simple `make buildworld' run. > > The include files land e.g. in a tmp/legacy/usr/include object > path and copying them manually fixes that particular issue until > the next error is triggered. > > I'm currently using 10.1 to build 11-CURRENT. Has anyone else > seen this or has any idea how to solve this? > > Are you still having this problem? What exact release of 10.1 are you on? The release, or somewhere in head during the 10.1 lifecycle? What revision were you trying to build? What do you have in /etc/make.conf and /etc/src.conf? What exact command did you run? Can you provide a full buildworld log please? -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
buildincludes: don't know how to make libelf.h etc.
Hi everyone, I'm trying to build 11-CURRENT, but seeing missing header files in lib/libelf, lib/libdwarf and lib/nucurses during a seemingly simple `make buildworld' run. The include files land e.g. in a tmp/legacy/usr/include object path and copying them manually fixes that particular issue until the next error is triggered. I'm currently using 10.1 to build 11-CURRENT. Has anyone else seen this or has any idea how to solve this? Cheers, Franco ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
