for the inconvenience.
are talking to tinycc-devel which … hum? … is for devel!
macos port is new it seems natural to have more (devel)
emails than before.
did a very good job chasing issues with different
./configure options. Thanks again Avi.
makes macos more robust and compatible with Linux behavior.
I talk privately to other contributors (something I do
sometime), we may lose useful advices from other persons
knowing macos very well.
be glad to follow what maintainers will ask me to do on
a nice day.
Please consider not fucking everybody's mailing-list.
I ain't a chat hu ?
But FYI your contribution is welcomed, many thanks.
Le 09/07/2020 à 23:16, avih via
Tinycc-devel a écrit :
I've pushed a fix to mob to support arbitrary libdir
The relative path is now used during `make test', while
the fixed libdir is used after install.
to self: Make sure to double check before
Turns out ./dist/lib/ remained from the
previous install, which I didn't delete
before testing with
Indeed, it only creates ./dist/mylibs, and
indeed it fails to find the dylib
when running ./dist/bin/tcc, (make test still
I can confirm current mob
(6c94df6) does work also with
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
--libdir=$(pwd)/dist/mylibs but I
tried it and it still worked.
Turns out it creates both
./dist/lib and ./dist/mylibs, and
libtcc.dylib is at both
of them as well as tcc/ and its
content (duplicated at both dirs),
is only at ./dist/lib/ .
Is that expected? I never tried
using --libdir before, but commit
6c94df6 makes it look
a bit hardcoded, so I tried it
now. Wouldn't it be better to
specify the absolute
install [libdir] ?
found another (and
better) way to achieve
is commited, can you
please test this one.
avih, another step
is missing (it works
well with default
you please test
work for me. If it
also works for you
I’ll add this step
to macos build
On Behalf Of avih
Thursday, July 09,
To: firstname.lastname@example.org; email@example.com
longer works after
Seems that moving
./dist/lib/libtcc.dylib to ./dist/bin/ makes it work,
-run works as
So it seems that
Oh, I missed
--prefix=$(pwd)/dist && make && make test &&
the tcc binary
Abort trap: 6
When not using
--disable-static, then tcc runs fine, compiles and even -run works.
?? can you please try with mob
and give me
The fix is
“macos: tcc searches for libtcc.dyln in the same directory as its executable”
09, 2020 17:52
the fix? I
at the earlier
For me on osx
MBA) I also
have the same
but it seems
(I missed the
On Thu, 9 Jul
> If you
have a moment,
can you please
test if my
macos fix for
> works on
Yes, it works
fine here on
Tinycc-devel mailing list