I have made some changes to software and when I try to do make and make install, these changes are not being implemented. The output of the code I am getting is that of the older code. I haven't made any changes else where. So where could the problem possibily be?
Maybe you can try
make clean
make
make install
Related
So I started working on my first open-source contribution in ruby. There I have the library I'm working on in the /lib/ folder. Now when I tried changing the code, my program (which uses the library) still uses the old code.
For example: Broke a function on purpose by deleting its end keyword (which should be causing an immediate crash), but it kept working perfectly after I did.
Another example was changing the code in such a way it should still work (mutating the output string) but it still returned the old string.
user~$ bin/ruby-hyphen -V "this is a test sentence"
this is a test sen-tence
Does anyone know if I have to tell the runtime to refresh it or something along those lines?
I found out why that happened. The file has a *.gemspec, which made it act as if it was a gem. To see the changes I needed to enter:
gem build *.gemspec
bundle exec rake install
Or, if you want to develop quicker: change everywhere you require it into a require_relative. That should also fix it. I hope this question helps someone in the future!
When I do make of buildroot appears this error
make: *** [package/pkg-generic.mk:293: /home/vitor/buildroots/buildroot/output/build/host-gcc-final-11.3.0/.stamp_built]
Error 2
Does anyone know the solution?
Thanks already for the time
Note: The first time I have do buildroot it worked fine, but for an work I needed to change some files and since that stop working, so I deleted that buildroot and tried to do a new ones and always appear this error.
Recommandation: don't use the current "master" of Buildroot if you're new to Buildroot, but instead use a release tag. As Arnout said, you did not post enough lines of the error to really know, but based on the package that failed I suspect you're encountering one of the issues we've had with the update of glibc to version 2.36, which is not yet part of any Buildroot stable release.
Use Buildroot 2022.02 or 2022.08, but not Buildroot master if you're interested in having something that "works" :-)
I'm kinda new to using composer (but I think it is awesome) so please pardon the noob question.
Folks are requesting exports fancier than csv so I thought I'd install phpOffice excel using composer. But, the master is 'build failing' and the develop is 'build error'. An I correct in assuming the master build failed means I should not install this with composer because it won't work?
In researching this I also found phpOffice spreadsheet, but that appears to be in development still.
Any other alternatives if I cannot use phpOffice excel due to the build status issue?
Regardless of what package you are talking about, if the builds for any of the branches are failing it just means that the builds for any of the branches are failing, that's it.
The master and develop branches may be well ahead of the latest tag, and chances are the maintainers are experimenting with it, and working towards a passing build again.
If you trust the maintainers not to release broken software, then it's safe to use one of the tagged versions, so for example, run
$ composer require phpoffice/phpexcel:^1.8.1
to install the latest stable version.
Note It appears that phpoffice/phpexcel:1.8.1 has been released on 2015-05-01; quite some time has passed since. Whether or not this package works for you, then, is something you have to find out for yourself.
For reference, see:
https://packagist.org/packages/phpoffice/phpexcel
I have written a small makefile to build a little projects. I'm running make 3.82.90. this make-version is coming with the mingw installation.
I have a second pc, which is unable to run the makefile. The make version is 5.2. I don't know this version, it seems to come frome another programm. Mingw is even installed on this pc.
Does anyone knows where this make comes from?
Maybe I must change a environment variable, that the mingw make is found first. Know somebody which one?
The different make is from borland. Call of mingw-32 solved the problem.
I am trying to create an installer and it will install another *.msi.
But it is failure, because can't install at the same time.
If it is possible to pause main installer and install another msi??
You can do it by creating a bootstrapper package. check this post on how to create a bootstrapper package.
Perhaps you have a custom action to install something else, and that something else is an MSI-based setup, and that nearly always won't work (without going into gory details) or is a really bad idea.