sudo make install
bvnf.space
sudo make install
1–10 of 38 posts
Re: sudo make install
#2Re: sudo make install
#3Re: sudo make install
#4I’ve been working on Makefiles lately and its funny how many compatibility issues there are. I was doing Sed substitutions and found I needed to change the -i flag to make it work between Mac and Linux. I was really hoping for ultimate portability but ended up learning lots of hacks that lead to portability
Re: sudo make install
#5I’ve been working on Makefiles lately and its funny how many compatibility issues there are. I was doing Sed substitutions and found I needed to change the -i flag to make it work between Mac and Linux. I was really hoping for ultimate portability but ended up learning lots of hacks that lead to portability
Re: sudo make install
#6I’ve been working on Makefiles lately and its funny how many compatibility issues there are. I was doing Sed substitutions and found I needed to change the -i flag to make it work between Mac and Linux. I was really hoping for ultimate portability but ended up learning lots of hacks that lead to portability
Re: sudo make install
#7Tools like checkinstall are the way to go, at a minimum.
Re: sudo make install
#8There is now a proposal to add CURDIR to POSIX: https://www.austingroupbugs.net/view.php?id=1626
Re: sudo make install
#9I’ve been working on Makefiles lately and its funny how many compatibility issues there are. I was doing Sed substitutions and found I needed to change the -i flag to make it work between Mac and Linux. I was really hoping for ultimate portability but ended up learning lots of hacks that lead to portability
Differences in GNU/BSD sed is hardly a bug in Make.
But it is a good example of something that you might expect to be more standard than it is between platforms, because of its age and relative ubiquity, where the differences get highlighted when trying to create (not just with make but other tools too) a consistent build process for a project.
Re: sudo make install
#10I’ve been working on Makefiles lately and its funny how many compatibility issues there are. I was doing Sed substitutions and found I needed to change the -i flag to make it work between Mac and Linux. I was really hoping for ultimate portability but ended up learning lots of hacks that lead to portability
sed -i '' .... is compatible with both. It's not a big deal.
$ sed -i '' 's/foo/FOO/' ip.txt
sed: can't read s/foo/FOO/: No such file or directory
See also: https://stackoverflow.com/questions/5694228/sed-in-place-fla...