digitalmars.D.ldc - LDC collisions of libs -oq option
- Smoke (8/8) Jun 27 2016 When trying to compile for LDC I get package collision errors.
- David Nadlinger via digitalmars-d-ldc (8/10) Jun 27 2016 $ ldc2 -help | fgrep oq
- Smoke (6/18) Jun 27 2016 -oq seemed to fix the problem
- Smoke (18/40) Jul 03 2016 Anyone have any idea about this? It's preventing me from using my
- Vladimir Panteleev (4/7) Jul 03 2016 https://github.com/CyberShadow/DustMite/wiki#initial-test-fails
- Smoke (2/9) Jul 05 2016 I tried that and it didn't do anything, same error.
- Vladimir Panteleev (10/22) Jul 06 2016 Did you even read the linked page?
When trying to compile for LDC I get package collision errors. This doesn't happen to DMD, and the packages are not the same. e.g., package.d in different directories collide. ldc says to look at the -oq option. Google can't find the -oq option. Error: Output file 'Base.obj' for module 'libs.Base' collides with previous module 'good.Base'. See the -oq option Works find in DMD. All the files are in different directories.
Jun 27 2016
On 27 Jun 2016, at 17:38, Smoke Adams via digitalmars-d-ldc wrote:ldc says to look at the -oq option. Google can't find the -oq option.$ ldc2 -help | fgrep oq -oq - Write object files with fully qualified namesWorks find in DMD. All the files are in different directories.There are several points to be considered/possible explanations here. Could you please post an example command line to make sure we are both talking about the same situation? — David
Jun 27 2016
On Monday, 27 June 2016 at 16:42:39 UTC, David Nadlinger wrote:On 27 Jun 2016, at 17:38, Smoke Adams via digitalmars-d-ldc wrote:-oq seemed to fix the problem but now I get an linker error and VD range violation crash. Referencing global in another module! Of course I have no idea what global or what module all this is happening in ;/ Works fine in DMD.ldc says to look at the -oq option. Google can't find the -oq option.$ ldc2 -help | fgrep oq -oq - Write object files with fully qualified namesWorks find in DMD. All the files are in different directories.There are several points to be considered/possible explanations here. Could you please post an example command line to make sure we are both talking about the same situation? — David
Jun 27 2016
On Monday, 27 June 2016 at 16:52:01 UTC, "Smoke" Adams wrote:On Monday, 27 June 2016 at 16:42:39 UTC, David Nadlinger wrote:Anyone have any idea about this? It's preventing me from using my code. I tried dustmite but just got None => No object.Exception DustMite\dustmite.d(244): Initial test fails ---------------- 0x00402AEE 0x00442B87 0x00442B4B 0x00442A4C 0x0043122C 0x74B03744 in BaseThreadInitThunk 0x771B9E54 in RtlSetCurrentTransaction 0x771B9E1F in RtlSetCurrentTransaction This is preventing me from testing my code in LDC. I really have no idea what is causing the error. It would be nice if the error messages were more informative. Again, DMD has no problem with this.On 27 Jun 2016, at 17:38, Smoke Adams via digitalmars-d-ldc wrote:-oq seemed to fix the problem but now I get an linker error and VD range violation crash. Referencing global in another module! Of course I have no idea what global or what module all this is happening in ;/ Works fine in DMD.ldc says to look at the -oq option. Google can't find the -oq option.$ ldc2 -help | fgrep oq -oq - Write object files with fully qualified namesWorks find in DMD. All the files are in different directories.There are several points to be considered/possible explanations here. Could you please post an example command line to make sure we are both talking about the same situation? — David
Jul 03 2016
On Monday, 4 July 2016 at 02:44:54 UTC, "Smoke" Adams wrote:This is preventing me from testing my code in LDC. I really have no idea what is causing the error. It would be nice if the error messages were more informative.https://github.com/CyberShadow/DustMite/wiki#initial-test-fails The latest DustMite version adds a hint to that error message to use --no-redirect.
Jul 03 2016
On Monday, 4 July 2016 at 02:52:39 UTC, Vladimir Panteleev wrote:On Monday, 4 July 2016 at 02:44:54 UTC, "Smoke" Adams wrote:I tried that and it didn't do anything, same error.This is preventing me from testing my code in LDC. I really have no idea what is causing the error. It would be nice if the error messages were more informative.https://github.com/CyberShadow/DustMite/wiki#initial-test-fails The latest DustMite version adds a hint to that error message to use --no-redirect.
Jul 05 2016
On Wednesday, 6 July 2016 at 04:26:56 UTC, "Smoke" Adams wrote:On Monday, 4 July 2016 at 02:52:39 UTC, Vladimir Panteleev wrote:Did you even read the linked page? The error message means that your test command is wrong. You need to figure out what's wrong with the test command that you specified and fix it. --no-redirect can't possibly fix the "initial test fails" error message - it can only provide you more information in case your test command prints out an error message, which would otherwise be suppressed by default. Please put in a little effort before complaining.On Monday, 4 July 2016 at 02:44:54 UTC, "Smoke" Adams wrote:I tried that and it didn't do anything, same error.This is preventing me from testing my code in LDC. I really have no idea what is causing the error. It would be nice if the error messages were more informative.https://github.com/CyberShadow/DustMite/wiki#initial-test-fails The latest DustMite version adds a hint to that error message to use --no-redirect.
Jul 06 2016
On Wednesday, 6 July 2016 at 15:01:14 UTC, Vladimir Panteleev wrote:On Wednesday, 6 July 2016 at 04:26:56 UTC, "Smoke" Adams wrote:Um, do you fucking realize that I'm using Visual D and it automates this? Of course not, you just assumed I was doing it by hand. Please put a little less assumptions in your post then you won't be a jack ass. See, you want to blame me because of your large ego. I'm just an ignorant idiot and all the problems is my fault, right? Maybe you should go tell that to the maintainer of Visual D since he's the one that can't seem to get it right. Else, maybe keep in mind that you're not as smart as you think you are and assume less and the world would be a lot friendlier.On Monday, 4 July 2016 at 02:52:39 UTC, Vladimir Panteleev wrote:Did you even read the linked page? The error message means that your test command is wrong. You need to figure out what's wrong with the test command that you specified and fix it. --no-redirect can't possibly fix the "initial test fails" error message - it can only provide you more information in case your test command prints out an error message, which would otherwise be suppressed by default. Please put in a little effort before complaining.On Monday, 4 July 2016 at 02:44:54 UTC, "Smoke" Adams wrote:I tried that and it didn't do anything, same error.This is preventing me from testing my code in LDC. I really have no idea what is causing the error. It would be nice if the error messages were more informative.https://github.com/CyberShadow/DustMite/wiki#initial-test-fails The latest DustMite version adds a hint to that error message to use --no-redirect.
Jul 24 2016
On Sunday, 24 July 2016 at 10:04:40 UTC, "Smoke" Adams wrote:I'm just an ignorant idiot and all the problems is my fault, right?Well said. There's a reason I didn't respond to your posts so far, but now I simply had to. So let's just leave it at that.
Jul 24 2016
"Smoke" Adams <SA2432 gmail.com> On Sunday, 24 July 2016 at 10:57:51 UTC, kinke wrote:On Sunday, 24 July 2016 at 10:04:40 UTC, "Smoke" Adams wrote:Way to side with your egotistical friend. Birds of a feather flock together. Note how Vlad was the first to start the insults. I simply reported on the objective facts then he comes along and tells me I need to stop complaining, then you agree with him. Way to go assholes, your doing great!I'm just an ignorant idiot and all the problems is my fault, right?Well said. There's a reason I didn't respond to your posts so far, but now I simply had to. So let's just leave it at that.
Jul 24 2016