What happens to licenses when porting/rewriting libraries to another language?

Question

Software porting

We have created our own programming language in which we write a virtual machine, our project uses different libraries with different licenses. For example: Cairo, Pango, JPEGLib, PNGLib, ZLib, Harfbuzz, Vulcan, OpenGL, MP3, OGG....

Our language is similar in syntax to: Java, AS3, JS, C.

What happens to licenses when porting/rewriting these libraries into another/our language?

1. For example: the Java and C# languages ​​are close, will the license be preserved when the library is ported from Java to C#, since the changes will not be significant?
   
2. Or for example: the Java and PHP languages ​​have different syntaxes, will the license be preserved when the library is ported from Java to PHP, since the changes will be significant?
   

With similar syntax of languages, an automatic porter is possible, with different syntaxes, you will have to make manual edits and the depth of code change will be higher.

That is, the question lies within the framework of changing the syntax / decomposition of the code and maintaining or losing the license.

Answer 1

Software created using the Cleanroom methods is a standalone product and is not licensed under another product's license.
But the output of an automatic porter, as well as the work of a rewriter-Indian that did not pass the Turing test, is derivative work and is subject to the restrictions of the license of the original product.

Answer 2

I could be wrong, but it seems to me that the general case is like this:

• If the library code in your language is the result of a machine translation by your preprocessor/compiler of the source code of the original library, plus it is technically possible for users to do it themselves, you are supplying an alternative tool, but not an alternative library. A machine conversion cannot be considered a derivative work, since a computer cannot be the author of the work. (If, due to the imperfection of the tool, you attach processed libraries to it, you are only making it easier for users - perhaps only during the release of pre-release versions, and full machine conversion is planned in the future).
  
• If you manually write a library in your own language in one way or another, even if based on the borrowed code of the original libraries, and the result cannot be reproduced by a machine in the field, your library is a derivative product (or even a product with partial borrowing ( remaster) -- depending on the coefficient of manual labor). Such a product may well have its own license that does not violate the terms of the original license (names, etc.). A person, even a Hindu, can be the author of a work.