Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Managed buid issues, magic .d file modification

Hi,

after some digging I found the problem.
It was a JVM problem!
My System was configured to use java-gcj instead Sun's java
implementation. Seems the are copying the trailing zero in a string
function which leads to korrupted .d files...WOW ;-)

Regards
Stefan

Am Donnerstag, den 03.11.2005, 09:45 -0500 schrieb Treggiari, Leo:
> Hi Stefan,
> 
> See bugzilla #108715 for a discussion regarding dependency management
> and .d files.  Your input to the discussion is welcome.  I had to put
> down considering the issue for a while to attend to other things...
> 
> Regards,
> Leo
> 
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Stefan Klug
> Sent: Thursday, November 03, 2005 9:24 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Managed buid issues, magic .d file modification
> 
> Hi everybody,
> 
> I have an issue with the managed buid in CDT.
> 
> Some of the .d files get corrupted (Many NULL caracters inside the
> file).
> When I ussue the build manually via the shell everything goes fine, but
> as soon as I let eclipse build the project, the .d files are generated
> correctly, until the link process.
> What happens to these files afterwards?
> Are they parsed/modified in any way by CDT? I'm really clueless here, as
> it isn't a mistake of make, but a magical file modification afterwards.
> 
> Whould be nice if someone could shed some light on this.
> 
> Thanks
> 	Stefan Klug
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 



Back to the top