Current state of things: ``` src_prepare() { sed -i -e "s/^CC.*/CC = $(tc-getCC)/" \ -e "s/^CFLAGS.*/CFLAGS = ${CFLAGS}/" \ -e "s/ar rs/$(tc-getAR) rs/" \ -e "s:^prefix.*:prefix = /usr:" \ -e "s:/man/:/share/man/:" \ -e "/for f/s:lib:$(get_libdir):" \ -e "s:shared:shared -Wl,-soname,liblmdb.so.0:" \ "${S}/Makefile" || die } ``` As you can see, it uses '/' as a separator inside statements containing paths.
no, this is expected and working, "for f" is the pattern to search for as we don't want to edit every occurrence of "lib" in the Makefile
If this is expected, there's nothing to worry about then.
Ok, it seems I have to point it out explicitly. ``` src_prepare() { sed -i -e "s/^CC.*/CC = $(tc-getCC)/" \ <---------- HERE -e "s/^CFLAGS.*/CFLAGS = ${CFLAGS}/" \ <---------- NOT SURE -e "s/ar rs/$(tc-getAR) rs/" \ <---------- HERE -e "s:^prefix.*:prefix = /usr:" \ -e "s:/man/:/share/man/:" \ -e "/for f/s:lib:$(get_libdir):" \ -e "s:shared:shared -Wl,-soname,liblmdb.so.0:" \ "${S}/Makefile" || die } ```
InGit.