I successfully run configure and on running make I get the following error:
/usr/bin/ld: cannot open output file znc: Is a directory
I've not had this before and apart from using the latest nightly, nothing else has changed.
I successfully run configure and on running make I get the following error:
/usr/bin/ld: cannot open output file znc: Is a directory
I've not had this before and apart from using the latest nightly, nothing else has changed.
<!-- github-sync-id:26227374 -->
Show config.log, where are sources, and anything in sources or prefix dirs?
2014/1/24 swarfega notifications@github.com
> I successfully run configure and on running make I get the following error:
>
> /usr/bin/ld: cannot open output file znc: Is a directory
>
> I've not had this before and apart from using the latest nightly, nothing
> else has changed.
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475
> .
<!-- github-comment-id:33209542 -->
I use --prefix=/home/swarfega/znc which is what I've always used.
Here is the config.log: http://pastebin.com/jgJRYa7E
I use --prefix=/home/swarfega/znc which is what I've always used.
<!-- github-comment-id:33213089 -->
Did you put sources to /home/swarfega/znc/ too?
2014/1/24 swarfega notifications@github.com
> Here is the config.log: http://pastebin.com/jgJRYa7E
>
> I use --prefix=/home/swarfega/znc which is what I've always used.
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33213089
> .
<!-- github-comment-id:33218446 -->
I did what I usually do, configure;make;make install. Is there an additional step I need to take with the latest builds?
I did what I usually do, configure;make;make install. Is there an additional step I need to take with the latest builds?
<!-- github-comment-id:33219508 -->
You didn't answer my questions.
Where did you put sources? Which path?
What else is in that path?
What is in /home/swarfega/znc?
2014/1/24 swarfega notifications@github.com
> I did what I usually do, configure;make;make install. Is there an
> additional step I need to take with the latest builds?
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33219508
> .
<!-- github-comment-id:33222263 -->
Ok, waiting for answers to other my questions.
2014/1/24 swarfega notifications@github.com
> Theres no /home/swarfega/znc atm, make didnt get round to creating it
> before it errored.
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33222367
> .
<!-- github-comment-id:33222489 -->
I'm still waiting for the answers.
2014/1/24 swarfega notifications@github.com
> I've not touched the sources. I've not needed to in the past.
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33223229
> .
<!-- github-comment-id:33224239 -->
I'm asking for `ls -laR /path/to/source/dir`
2014/1/24 swarfega notifications@github.com
> make has compiled the modules, if thats what you're asking.
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33227741
> .
<!-- github-comment-id:33229448 -->
Finally :)
So, for some reason you have 2 directories with source:
/home/swarfega/znc-1.3, and /home/swarfega/znc-1.3/znc
Both of them contain files like configure.ac, .cpp, .h, all modules.
/home/swarfega/znc-1.3 was actually used to build ZNC.
Any idea why /home/swarfega/znc-1.3/znc/ exists?
Finally :)
So, for some reason you have 2 directories with source:
/home/swarfega/znc-1.3, and /home/swarfega/znc-1.3/znc
Both of them contain files like configure.ac, .cpp, .h, all modules.
/home/swarfega/znc-1.3 was actually used to build ZNC.
Any idea why /home/swarfega/znc-1.3/znc/ exists?
2014/1/24 swarfega notifications@github.com
> http://pastebin.com/ZejEaLNi
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33229871
> .
<!-- github-comment-id:33233134 -->
wget
tar zxfv
(this unpacks the files to the "znc" directory (as a side note, older versions of znc used to unpack it to "znc-" so I didnt have to rename the directory))
Because I want to use "znc" as my prefix I rename the unpacked znc directory to something random like "znc-1.3".
Then cd to it.
configure --prefix=/home/swarfega/znc
make
make install
Heres the order that I compile znc in:
wget <latest git nightly>
tar zxfv <znc file>
(this unpacks the files to the "znc" directory (as a side note, older versions of znc used to unpack it to "znc-<version>" so I didnt have to rename the directory))
Because I want to use "znc" as my prefix I rename the unpacked znc directory to something random like "znc-1.3".
Then cd to it.
configure --prefix=/home/swarfega/znc
make
make install
<!-- github-comment-id:33234364 -->
mv znc znc-1.3 renames znc to znc-1.3 only if znc-1.3 doesn't exist
yet (this is simplification, also there is a case of overwriting files,
etc.).
But if znc-1.3 exists, and is a directory, the command "renames" znc to znc-1.3/znc (moves it)
We need to fix nightly tarballs to have proper name of directory already,
instead of just "znc"
wget
tar zxfv
(this unpacks the files to the "znc" directory)
Because I want to use "znc" as my prefix I rename the unpacked znc
directory to something random like "znc-1.3".
Then cd to it.
configure --prefix=/home/swarfega/znc
make
make install
`mv znc znc-1.3` renames `znc` to `znc-1.3` only if `znc-1.3` doesn't exist
yet (this is simplification, also there is a case of overwriting files,
etc.).
But if `znc-1.3` exists, and is a directory, the command "renames" `znc` to
`znc-1.3/znc` (moves it)
We need to fix nightly tarballs to have proper name of directory already,
instead of just "znc"
2014/1/24 swarfega notifications@github.com
> Heres the order that I compile znc in:
>
> wget
> tar zxfv
> (this unpacks the files to the "znc" directory)
>
> Because I want to use "znc" as my prefix I rename the unpacked znc
> directory to something random like "znc-1.3".
> Then cd to it.
> configure --prefix=/home/swarfega/znc
> make
> make install
>
> —
> Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/475#issuecomment-33234364
> .
<!-- github-comment-id:33234948 -->
ah I see the issue then. Is there another command I can use to either get tar to extract it to znc-1.3 or to rename the directory in the classic Windows sense?
ah I see the issue then. Is there another command I can use to either get tar to extract it to znc-1.3 or to rename the directory in the classic Windows sense?
<!-- github-comment-id:33235406 -->
ok I made a directory called "znc_1.3" then extracted the files into that. Rather than use prefix=/home/swarfega/znc I decided to use /home/swarfega/znc13.
But now I'm getting the following errors with whichever prefix I use:
Now you can run "make" to compile ZNC
swarfega@cal:~/znc_1.3/znc$ make
Packing man page znc.1.gz...
Packing man page znc-buildmod.1.gz...
Building module adminlog...
Linking module adminlog...
Building module alias...
alias.cpp: In constructor 'CAliasMod::CAliasMod(void_, CUser_, CIRCNetwork_, const CString&, const CString&)':
alias.cpp:291: error: invalid static_cast from type '' to type 'void (CModule::_)(const CString&)'
make[1]: *** [alias.o] Error 1
make: *** [modules] Error 2
ok I made a directory called "znc_1.3" then extracted the files into that. Rather than use prefix=/home/swarfega/znc I decided to use /home/swarfega/znc13.
But now I'm getting the following errors with whichever prefix I use:
Now you can run "make" to compile ZNC
swarfega@cal:~/znc_1.3/znc$ make
Packing man page znc.1.gz...
Packing man page znc-buildmod.1.gz...
Building module adminlog...
Linking module adminlog...
Building module alias...
alias.cpp: In constructor 'CAliasMod::CAliasMod(void_, CUser_, CIRCNetwork_, const CString&, const CString&)':
alias.cpp:291: error: invalid static_cast from type '<unresolved overloaded function type>' to type 'void (CModule::_)(const CString&)'
make[1]: **\* [alias.o] Error 1
make: **\* [modules] Error 2
<!-- github-comment-id:33285038 -->
Now nightly tarballs properly have long dir name inside: znc-git-2014-01-28.tar.gz contains znc-git-2014-01-28/
Now nightly tarballs properly have long dir name inside:
`znc-git-2014-01-28.tar.gz` contains `znc-git-2014-01-28/`
<!-- github-comment-id:33525744 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I successfully run configure and on running make I get the following error:
/usr/bin/ld: cannot open output file znc: Is a directory
I've not had this before and apart from using the latest nightly, nothing else has changed.
Show config.log, where are sources, and anything in sources or prefix dirs?
2014/1/24 swarfega notifications@github.com
Here is the config.log: http://pastebin.com/jgJRYa7E
I use --prefix=/home/swarfega/znc which is what I've always used.
Did you put sources to /home/swarfega/znc/ too?
2014/1/24 swarfega notifications@github.com
I did what I usually do, configure;make;make install. Is there an additional step I need to take with the latest builds?
You didn't answer my questions.
Where did you put sources? Which path?
What else is in that path?
What is in /home/swarfega/znc?
2014/1/24 swarfega notifications@github.com
Theres no /home/swarfega/znc atm, make didnt get round to creating it before it errored.
Ok, waiting for answers to other my questions.
2014/1/24 swarfega notifications@github.com
I've not touched the sources. I've not needed to in the past.
I'm still waiting for the answers.
2014/1/24 swarfega notifications@github.com
make has compiled the modules, if thats what you're asking.
I'm asking for
ls -laR /path/to/source/dir2014/1/24 swarfega notifications@github.com
http://pastebin.com/ZejEaLNi
Finally :)
So, for some reason you have 2 directories with source:
/home/swarfega/znc-1.3, and /home/swarfega/znc-1.3/znc
Both of them contain files like configure.ac, .cpp, .h, all modules.
/home/swarfega/znc-1.3 was actually used to build ZNC.
Any idea why /home/swarfega/znc-1.3/znc/ exists?
2014/1/24 swarfega notifications@github.com
Heres the order that I compile znc in:
wget
tar zxfv
(this unpacks the files to the "znc" directory (as a side note, older versions of znc used to unpack it to "znc-" so I didnt have to rename the directory))
Because I want to use "znc" as my prefix I rename the unpacked znc directory to something random like "znc-1.3".
Then cd to it.
configure --prefix=/home/swarfega/znc
make
make install
mv znc znc-1.3renamesznctoznc-1.3only ifznc-1.3doesn't existyet (this is simplification, also there is a case of overwriting files,
etc.).
But if
znc-1.3exists, and is a directory, the command "renames"znctoznc-1.3/znc(moves it)We need to fix nightly tarballs to have proper name of directory already,
instead of just "znc"
2014/1/24 swarfega notifications@github.com
ah I see the issue then. Is there another command I can use to either get tar to extract it to znc-1.3 or to rename the directory in the classic Windows sense?
ok I made a directory called "znc_1.3" then extracted the files into that. Rather than use prefix=/home/swarfega/znc I decided to use /home/swarfega/znc13.
But now I'm getting the following errors with whichever prefix I use:
Now you can run "make" to compile ZNC
swarfega@cal:~/znc_1.3/znc$ make
Packing man page znc.1.gz...
Packing man page znc-buildmod.1.gz...
Building module adminlog...
Linking module adminlog...
Building module alias...
alias.cpp: In constructor 'CAliasMod::CAliasMod(void_, CUser_, CIRCNetwork_, const CString&, const CString&)':
alias.cpp:291: error: invalid static_cast from type '' to type 'void (CModule::_)(const CString&)'
make[1]: *** [alias.o] Error 1
make: *** [modules] Error 2
Now nightly tarballs properly have long dir name inside:
znc-git-2014-01-28.tar.gzcontainsznc-git-2014-01-28/Thanks Darth!