Marc Espie <[email protected]> writes: > On Thu, Jul 19, 2018 at 04:15:43PM +0200, Grégoire Jadi wrote: > >> Hello ports@, >> >> I have troubles building gcc and gdb from devel/avr. avr-binutils and >> avr-libc build fine. I have two boxes: one running the latest snapshot >> and one following -current from sources. I encounter the same problem on >> both boxes. >> >> # gcc >> >> I manage to build avr-gcc by removing `-I /usr/local/include' from the >> CFLAGS. >> >> libiberty includes "ansidecl.h". Because of the -I command, it picked >> the one from /usr/local/include instead of the one bundled with gcc and >> they differ a lot. /usr/local/include/ansidecl.h has no macros PARAMS, >> VA_OPEN, etc. >> >> I don't understand why the -I command is used but I also don't >> understand why it didn't work for me though someone™ is clearly building >> the binary packages for pkg_add... > > pkglocate ansidecl.h > will tell you it comes from the gdb port. > > maybe the guys who built the package didn't have it installed on their > system ? Not that surprising... considering it's not a hugely frequent > dependency. sqlports gives me only qt-creator, ocaml, rust, and gnustep's > projectcenter. > > Anyway, it's a bug. If you can provide a patch, that will help.
What would be a correct fix? Removing the -I command or fixing gdb so that the includes go into /usr/local/lib/gdb/... (or something similar but not into /usr/local/include)? >> - Did I messed up my installations and have the wrong ansidecl.h file? >> - Do package builders use a different configuration than the Makefile in >> ports? (I've never tried dpb(1)) > > You should :) > > package builders start builds on clean systems. Personally, I do everything > in a separate chroot, and dpb periodically removes dependencies (because > otherwise, it would overflow about everything). > > You actually *don't* have an ansidecl.h file on a base system. Certainly > not under /usr/local. Ok, I'll look at dpb :) >> # gdb >> >> gdb-6.8.tar.gz cannot be found on any GNU mirrors (the closer is >> gdb-6.8a.tar.gz). And the fallback on OpenBSD distfiles fails too >> because it tries to fetch distfiles/gdb/gdb/gdb-6.8.tar.gz instead of >> distfiles/gdb/gdb-6.8.tar.gz (two /gdb/ is too much). > > Nope, not any more. You're not -current. About one week behind, I > believe. Ok. I will check, upgrade and report if it fails. >> Hardcoding MASTER_SITES to >> https://ftp.openbsd.org/pub/OpenBSD/distfiles/gdb/ did the trick. >> >> But again, how can the packages be built if the URLs fails? > > People did grab the distfiles before it vanished. Ok. Is it a bug or is it expected? >> >> So, what am I doing wrong? Did I miss some configuration steps or >> misread some documentation? > > You are missing quite a few clues, yes. > > New to OpenBSD ?... Yes. I hope I won't miss the same clues again :) Thank you for your answers. Best,
