<fenrig>
I've streamlined the recipe, but I'm still tripping over Openwrt-libtool
<karlp>
the customconfigure looks dubious.
<karlp>
can you not just pass CONFIGURE_ARGS +=--disbale-dep tracking or whatever?
<fenrig>
I can try that
<fenrig>
though that will probably not fix the error
<karlp>
also, having to hack on the upstream autohell thatmuch is also a nasty sign
<karlp>
have you tried speaking to upstream?
<karlp>
if PKF_FIXUP=autoreconfig isn't enough, it means youre autowinning.
<fenrig>
well by default upsteam only makes a static archive
<fenrig>
so I just add the stuff to make an so out of it
<fenrig>
I will disable my patch and try again
<fenrig>
though I know its working on my x86 and some propietary build system
<karlp>
upstream only doing static is a pretty good sign that they dont' give a ratsarse about anyone else in the world except their single worldview...
<fenrig>
I guess they do it on a need basis
<fenrig>
holy fuck
<fenrig>
without my patch it works -.-
<fenrig>
grrr
<plntyk2>
older code with autotools is succeptible to build-system bitrot - changed macros etc
<karlp>
"works" or "compiles" :)
<fenrig>
yeah but its recent
Tapper has joined #openwrt-devel
<plntyk2>
most ppl patching generated configure instead of the configure.ac recipes etc.
<karlp>
autotools doesn't care about recent, they onyl care about breaking things.
<fenrig>
I'm working on configure.ac and Makefile.am
<fenrig>
hence why I'm having so much pain with it xD
<fenrig>
I'm not an autotools expert in anyway
<plntyk2>
some other projects might have working patches too - checking fedora or debian repos for that stuff
<fenrig>
well its not that widely used it
<fenrig>
so its quite funny the story
<fenrig>
its the open container initiative documentation that can compile to code
<fenrig>
docker uses it
<fenrig>
but officially its go lang
<jow>
so the actual goal is to enable building of a shared libocispec.so ?
<fenrig>
so some red hat dude (might be wrong) created the C counterpart, to compile the spec to a static library
<fenrig>
so yeah, cause we want to use it embedded. And we are using this library in several places, so the space optimization would come in nicely
<fenrig>
also it seems they favor having their own copy of yajl, so I removed that as well
SamantazFox has joined #openwrt-devel
<jow>
it seems you can simply pass --disable-embedded-yajl to configure
nlowe has joined #openwrt-devel
<fenrig>
thats right
<jow>
or rather --enable-embedded-yajl=no
<fenrig>
but there is something else wrong in my autotools modif that causes this right?
<fenrig>
yeah but I will probably disable the version for now
<jow>
right, likely makes sense if upstream defines none
<fenrig>
I think getting it from the make install target if possible is better, cause I dont need all those headers and the makefile.am has the bookkeeping to know what is being generated so I'd like to keep it that way.
cjdns has joined #openwrt-devel
dorf_ has quit [Remote host closed the connection]
dorf_ has joined #openwrt-devel
_whitelogger has joined #openwrt-devel
<fenrig>
jow: Ty I made a combination and now I got the make install target working as well
mustafacan has joined #openwrt-devel
<mustafacan>
hello, I'm compiling 21.02-rc2, I want to bump the kernel to 5.4.124. Is there a guide (or a script) to how to do that? I can't seem to figure it out :/
<Grommish>
The switch to DSA in 21.02, I'm hearing grumbles about it
<Grommish>
Tapper: Going good.. I've been worried about ya. Haven't heard from ya!
<JohnA>
Grommish, i am 80, and I don't want to leave orphan code behind!
<Grommish>
JohnA: First of all.. You rock for even dealing with it in that case
<Grommish>
Don't think otherwise :)
<Tapper>
Grommish: I am ok mate. the weather has got a bit better here in the UK so my wife and me took the kids to the beach. Plus bin fixing up the garden a bit.
* Tapper
salutes JohnA
<Grommish>
JohnA: Ask away.. Although you might not get an answer right away as people stay in channel and check when they can.. So, if you stay connected, it'll give you the best chance.. Otherwise, I would recommend the forums as a place to post as well
<stintel>
I reckon he's old enough to know how IRC works ;)
<Grommish>
And the other channel, of course
<Grommish>
Cross-posting isn't bad.. spamming the cross-post is hehe
<stintel>
JohnA: respect! I hope I'll still be messing around with open source at that age!
<JohnA>
Grommish, Thanks!
<JohnA>
stintel, I still write stuff, not very much and for in house only.
<JohnA>
jow, is there anything I can do to get PPPoE working on my 21.02
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<rmilecki>
Grommish: very few ppl take throughput seriously unfortunately
<rmilecki>
Grommish: even less can debug it
<rmilecki>
Grommish: most ppl make random claims like "DSA switch broke it"
<rmilecki>
while there are tons of kernel places that have impact of network performance
<Grommish>
rmilecki: *nod* In this case, the reporter is willing to do the testing.. He approached on the discord
<rmilecki>
Grommish: it's close to impossible
<rmilecki>
to do proper testing you need to bisect kernel
<Grommish>
Gotcha..
<rmilecki>
Grommish: before even trying that think for much effort it takes
<rmilecki>
to apply hunderds of OpenWrt patches on every kernel commit you want to test
<rmilecki>
fix them up as needed (they don't apply cleanly)
<Grommish>
Yeah, I've experienced that when migrating to 5.10 before it was done in the repo
<Grommish>
Having to go rip out the upstream merged general stuff
<Grommish>
total PITA
nlowe has joined #openwrt-devel
<Grommish>
Well.. I did tell them I'd bring it up, and I have :)
<Grommish>
Appreciate it rmilecki!
<rmilecki>
long term solutions: upstream as many patches as you can
<rmilecki>
*solution
<rmilecki>
almost noone cares abut that one too ;)
<Grommish>
I've got no experience with DSA unfortunately.. I need to learn
<Grommish>
Because this ER10x is being a stupid with the DSA and swconfig mixing
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nlowe has joined #openwrt-devel
rejoicetreat has quit [Ping timeout: 480 seconds]
SamantazFox has joined #openwrt-devel
SamantazFox has quit [Ping timeout: 480 seconds]
philipp64|work has quit [Quit: philipp64|work]
philipp64 has quit [Quit: philipp64]
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tohojo has quit [Ping timeout: 480 seconds]
tohojo has joined #openwrt-devel
nlowe has joined #openwrt-devel
nlowe has quit []
Tapper has quit [Ping timeout: 480 seconds]
nlowe has joined #openwrt-devel
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Tapper has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
cjdns has quit [Quit: Lost terminal]
tohojo has quit [Ping timeout: 480 seconds]
deathcamel57 has joined #openwrt-devel
Borromini has joined #openwrt-devel
<deathcamel57>
I've never submitted an OpenWRT community maintained packages PR. Could someone do me a huge solid and check out if I filed it correctly? It's weird, because when I signed off, almost 9500 commits were appended to my pull request. I'm not sure why.
philipp64|work has joined #openwrt-devel
<xdarklight>
deathcamel57: at first glance it looks like you based your patch on the master branch, but expecting it to be pulled into the openwrt-19.07 branch
<xdarklight>
deathcamel57: so your pull request contains all changes which are in master, but not in the openwrt-19.07 branch
<deathcamel57>
Thanks a ton xdarklight! I'm working on a new PR now.
fenrig has quit [Remote host closed the connection]
philipp64|work has quit [Quit: philipp64|work]
<deathcamel57>
Mind checking PR #15770 if you have time @xdarklight? Not sure if there are any PR rules that the community has that I don't know about.
<xdarklight>
deathcamel57: there's a typo in the patch subject (enviornments -> environments). also I would add [19.07] to the title of the pull request (not the patch subject) like it's done here: https://github.com/openwrt/packages/pull/15758
<xdarklight>
deathcamel57: apart from that: I'm not very experienced with the packages tree, so I am also hoping that more experienced people can give their feedback
<stintel>
you don't need to close a PR, you can just force push :)
<deathcamel57>
Thanks to both of you. Used OpenWRT for years, yet never filed any upstream PR's.