Re: [Tinycc-devel] Tiny c availability

On Thu, Jul 09, 2020 at 10:09:56AM +0200, Christian Jullien wrote: > Many starts with more than one :o) Even the Pirahã appear to agree that many doesn't start before three. > Five BIG projects is not that bad. > > Let me start with few I very often (if not daily) compile: > - OpenLisp (daily) >

Re: [Tinycc-devel] Tiny c availability

I compile gawk with it all the time and gawk passes its test suite. I use it mainly when I want a quick build to test something. My big wish for tcc is that it'd produce debug info for use with GDB. Arnold Daniel Glöckner wrote: > On Thu, Jul 09, 2020 at 10:09:56AM +0200, Christian Jullien

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Michael, If you have a moment, can you please test if my macos fix for dyld also works on your configuration? My changes tell tcc to find dyld in the same directory as it binary. Clearly, DYLD_LIBRARY_PATH can't be use as, for security reasons, it is reset when call subprocess. Thx.

Re: [Tinycc-devel] Tiny c availability

On Thu, Jul 09, 2020 at 06:29:11AM +0200, Christian Jullien wrote: > We are many to use it daily as main C compiler for really big projects. It think that's a bit exaggerated. From what I saw on this list you can count the number of people who use it for "really big projects" on one hand. A few

Re: [Tinycc-devel] Tiny c availability

Many starts with more than one :o) Five BIG projects is not that bad. Let me start with few I very often (if not daily) compile: - OpenLisp (daily) - bigz (daily) - gnumake (every major version) - sqlite (daily - part of OpenLisp build) - tcc (almost daily) They already count for FIVE :o) What

Re: [Tinycc-devel] Tiny c availability

I've built mpv with tcc on both Ubuntu and Alpine linux, though not recently. It did require patching waf (the build system) because it's very picky with compiler identification, as well as some minor patches in mpv to replace few #pragma once with normal include guards. tcc builds st (

Re: [Tinycc-devel] Tiny c availability

arn...@skeeve.com wrote in <202007091312.069dcmxx000...@freefriends.org>: |> arn...@skeeve.com wrote in |> <202007090906.069964j4023...@freefriends.org>: |>|I compile gawk with it all the time and gawk passes its test suite. |>|I use it mainly when I want a quick build to test something. |>|

Re: [Tinycc-devel] Tiny c availability

arn...@skeeve.com wrote in <202007090906.069964j4023...@freefriends.org>: |I compile gawk with it all the time and gawk passes its test suite. |I use it mainly when I want a quick build to test something. | |My big wish for tcc is that it'd produce debug info for use with GDB. Oh please not

Re: [Tinycc-devel] Tiny c availability

> arn...@skeeve.com wrote in > <202007090906.069964j4023...@freefriends.org>: > |I compile gawk with it all the time and gawk passes its test suite. > |I use it mainly when I want a quick build to test something. > | > |My big wish for tcc is that it'd produce debug info for use with GDB.

Re: [Tinycc-devel] Tiny c availability

Hello, On Thu, 9 Jul 2020, arn...@skeeve.com wrote: I compile gawk with it all the time and gawk passes its test suite. I use it mainly when I want a quick build to test something. My big wish for tcc is that it'd produce debug info for use with GDB. Recent mob has some changes that make

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

What's the fix? I tried looking at the earlier messages, but didn't see a diff/patch. For me on osx 10.13 (real MBA) I also have the same issue when using --disable-static, but it seems fine without it, including -run. On Thursday, July 9, 2020, 06:38:10 PM GMT+3, Michael Matz wrote:

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Oh, I missed the commits from today. Indeed, with latest mob (6bd0ced) this now succeeds: ./configure --disable-static && make && make test However, when building and installing like this: ./configure --disable-static --prefix=$(pwd)/dist && make && make test && make install Then it

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Seems that moving ./dist/lib/libtcc.dylib to ./dist/bin/ makes it work, compile programs successfully, and -run works as well. So it seems that install target doesn't take everything into account. On Thursday, July 9, 2020, 07:17:38 PM GMT+3, avih wrote: Oh, I missed the commits

Re: [Tinycc-devel] Tiny c availability

I added USES file which list known projects working with tcc. To be completed -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Steffen Nurpmeso Sent: Thursday, July 09, 2020 15:47 To: tinycc-devel@nongnu.org Subject: Re:

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Thanks avih, another step is missing (it works well with default install location) Can you please test this: $ install_name_tool -add_rpath "@executable_path/../lib/" tcc $ make install $ ./dist/bin/tcc -vv tcc version 0.9.27 (x86_64 Darwin) install: /Users/jullien/tinycc/dist/lib/tcc …

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Hello, On Thu, 9 Jul 2020, Christian Jullien wrote: Got it! Once again Apple does things in your back. Whatever starts with DYLD_ is processed directly by the system in a different way on a real mac (tested on Catalina and High Sierra). Read:

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

?? can you please try with mob and give me the complete log? The fix is “macos: tcc searches for libtcc.dyln in the same directory as its executable” C. From: avih [mailto:avih...@yahoo.com] Sent: Thursday, July 09, 2020 17:52 To: jull...@eligis.com; tinycc-devel@nongnu.org Subject:

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Thanks Michael, Good to know. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz Sent: Thursday, July 09, 2020 17:38 To: jull...@eligis.com; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] macos:

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Hello Christian, (I missed the question earlier, apologies) On Thu, 9 Jul 2020, Christian Jullien wrote: If you have a moment, can you please test if my macos fix for dyld also works on your configuration? Yes, it works fine here on my emulated macOS. Ciao, Michael.

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

I’ve found another (and better) way to achieve this: -Wl,-rpath,"@executable_path/$(TOP) " -Wl,-rpath,"@executable_path/$(TOP)/../lib" It is commited, can you please test this one. From: Tinycc-devel

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Thanks. I can confirm current mob (6c94df6) does work also with custom prefix, as well as building in a custom dir (mkdir build && cd build && ../configure ...). However, looking at that commit, I thought it would break with a custom --libdir, like ./configure --libdir=$(pwd)/dist/mylibs but I

Re: [Tinycc-devel] Tiny c availability

Michael Matz wrote: > Hello, > > On Thu, 9 Jul 2020, arn...@skeeve.com wrote: > > > I compile gawk with it all the time and gawk passes its test suite. > > I use it mainly when I want a quick build to test something. > > > > My big wish for tcc is that it'd produce debug info for use with GDB. >

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

Note to self: Make sure to double check before posting. Turns out ./dist/lib/ remained from the previous install, which I didn't delete before testing with --libdir=$(pwd)/dist/mylibs. Indeed, it only creates ./dist/mylibs, and indeed it fails to find the dylib when running ./dist/bin/tcc,

Re: [Tinycc-devel] Tiny c availability

Christian Jullien wrote in <003901d65604$ce397be0$6aac73a0$@orange.fr>: |I added USES file which list known projects working with tcc. To be \ |completed With zest. --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one

Re: [Tinycc-devel] macos: DYLD_LIBRARY_PATH no longer works after cleanup

I've pushed a fix to mob to support arbitrary libdir (c69290fb). The relative path is now used during `make test', while the fixed libdir is used after install. On Thursday, July 9, 2020, 09:12:06 PM GMT+3, avih via Tinycc-devel wrote: Note to self: Make sure to double check

Re: [Tinycc-devel] Tiny c availability

Hi, which zest are you talking about (I found many references but none seem to be for C). Can you please point me on the official page? -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Steffen Nurpmeso Sent: Thursday, July 09,